A recognizable experience
Original logo, truck, mascot, and food assets; custom surf art; distinctive typography; responsive layouts; easy navigation.
Built
Book the truck ↗A separate design proposal and content framework for Dirty Birds. This page makes the remaining client decisions visible. It is excluded from search alongside the whole preview.
Original logo, truck, mascot, and food assets; custom surf art; distinctive typography; responsive layouts; easy navigation.
BuiltEvent pages, a three-step booking demo, structured review, useful FAQs, email links, and a persistent mobile booking action.
BuiltReadable static HTML, page titles and descriptions, social previews, schema, local fonts, optimized assets, canonical URLs, and protected preview indexing.
BuiltCorrect phone and public business identity; current menu and sauces; event minimums, capacity, packages, lead time, response time, and travel terms.
ConfirmRecent authentic reviews, real event stories, photo permissions, any verified restaurant relationship, and venue partners.
CollectGoogle Business Profile, correct directory links, restaurant-site referral, Search Console, Bing Webmaster Tools, and conversion measurement.
ActivateThese are content slots and briefs, not published business claims. Keep them out of production until approved.
| Content slot | What belongs here | What we need |
|---|---|---|
| Pricing & minimums | Menu/event packages, host-paid vs guest-paid, minimum spend, travel fees, and what a quote includes. | Owner-approved figures; no dollar amounts invented. |
| Booking expectations | Response window, lead time, deposits, final guest-count deadline, payment, cancellation, and weather rules. | Documented terms and operational confirmation. |
| Event capacity & setup | Guests per service window, truck footprint, parking, power, venue permissions, and access. | Verified limits from the operating team. |
| Corporate event story | A real event: organizer’s problem, date/venue, service plan, result, photos, and permission. | Platform-reported event leads need owner verification. |
| Wedding / community stories | Separate proof for these services, with actual photos and attributed comments. | Real examples only; remove the slot if unsupported. |
| Current weekly stops | Date, time, venue, address, map link, and expiry behavior; an honest empty state. | A named person who can keep the schedule accurate. |
| Menu & dietary information | Reconciled menu and sauce board, portion sizes, ingredients, allergens, fryers, and cross-contact information. | Owner approval; no allergen-free guarantees. |
| Reviews & relationships | Recent review source links, reviewer permission as needed, current dates, official affiliation, and authorized photos. | No stale “a week ago,” manufactured reviews, or unsupported awards. |
| Useful planning guides | Original answers on choosing a venue, organizing an office lunch, and planning food for a celebration. | Operational expertise and real examples, not generic keyword pages. |
Search visibility comes from accurate facts, useful pages, a credible local footprint, and a fast, usable experience. No website can promise first place on Google or inclusion in an AI answer.
This proposal creates the on-site foundation. The next layer is owner-approved evidence and consistent listings.
We use ordinary semantic HTML and factual structured data. There is no special “AI schema,” fabricated review rating, invented street address, or guaranteed FAQ rich result.
The preview stays noindex. Production needs confirmed content, canonical migration, a real sitemap, verified booking, and an explicit launch.
| Priority | Work | Why |
|---|---|---|
| First: align the business | Confirm one official phone, domain, Instagram, business identity, and service area. Fix conflicting directory/restaurant-site links. | A clear entity for customers, Google, and assistants. |
| Then: answer purchase questions | Approve menu, pricing/minimums, capacity, terms, and venue requirements. Publish useful service-page answers. | Less guesswork before an inquiry. |
| Then: earn local proof | Keep Google profile accurate, collect neutral Google reviews, add real case studies and venue relationships. | Credible local evidence beyond the website. |
| At launch: measure and validate | Activate booking, confirm intake/email receipt separately, migrate URLs, verify indexability, connect webmaster tools and conversion events. | A safe launch with measurable inquiries. |
| Each month: improve from evidence | Review queries, profile interactions, actual requests, quote-to-booking outcomes, fresh stops, and authentic content. | Sustained improvement based on demand. |
Potential next engagements: business-profile and directory cleanup; menu and package copy; a real photo session; event case studies; schedule maintenance; booking intake improvements; conversion reporting; and local venue partnerships.
A more detailed, sourced audit is saved with the project as docs/OVERHAUL-SEO-AEO-AUDIT.md, outside the webroot.