Design preview · booking is demo onlyView the growth plan ↗
Preview review center · October 2026

The look is the start.
Growth is the plan.

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.

What’s here. What’s next.

Ready in this preview

A recognizable experience

Original logo, truck, mascot, and food assets; custom surf art; distinctive typography; responsive layouts; easy navigation.

Built
Ready in this preview

Clearer conversion path

Event pages, a three-step booking demo, structured review, useful FAQs, email links, and a persistent mobile booking action.

Built
Ready in this preview

Technical foundations

Readable static HTML, page titles and descriptions, social previews, schema, local fonts, optimized assets, canonical URLs, and protected preview indexing.

Built
Owner input needed

The facts people ask for

Correct phone and public business identity; current menu and sauces; event minimums, capacity, packages, lead time, response time, and travel terms.

Confirm
Owner input needed

Proof that belongs to you

Recent authentic reviews, real event stories, photo permissions, any verified restaurant relationship, and venue partners.

Collect
Account work needed

Authority beyond the website

Google Business Profile, correct directory links, restaurant-site referral, Search Console, Bing Webmaster Tools, and conversion measurement.

Activate
Reserved for real information

The content runway.

These are content slots and briefs, not published business claims. Keep them out of production until approved.


Content slotWhat belongs hereWhat we need
Pricing & minimumsMenu/event packages, host-paid vs guest-paid, minimum spend, travel fees, and what a quote includes.Owner-approved figures; no dollar amounts invented.
Booking expectationsResponse window, lead time, deposits, final guest-count deadline, payment, cancellation, and weather rules.Documented terms and operational confirmation.
Event capacity & setupGuests per service window, truck footprint, parking, power, venue permissions, and access.Verified limits from the operating team.
Corporate event storyA real event: organizer’s problem, date/venue, service plan, result, photos, and permission.Platform-reported event leads need owner verification.
Wedding / community storiesSeparate proof for these services, with actual photos and attributed comments.Real examples only; remove the slot if unsupported.
Current weekly stopsDate, time, venue, address, map link, and expiry behavior; an honest empty state.A named person who can keep the schedule accurate.
Menu & dietary informationReconciled menu and sauce board, portion sizes, ingredients, allergens, fryers, and cross-contact information.Owner approval; no allergen-free guarantees.
Reviews & relationshipsRecent 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 guidesOriginal answers on choosing a venue, organizing an office lunch, and planning food for a celebration.Operational expertise and real examples, not generic keyword pages.
SEO & answer-engine visibility

Earn the answer.

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.

The order that matters.

PriorityWorkWhy
First: align the businessConfirm 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 questionsApprove menu, pricing/minimums, capacity, terms, and venue requirements. Publish useful service-page answers.Less guesswork before an inquiry.
Then: earn local proofKeep Google profile accurate, collect neutral Google reviews, add real case studies and venue relationships.Credible local evidence beyond the website.
At launch: measure and validateActivate 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 evidenceReview queries, profile interactions, actual requests, quote-to-booking outcomes, fresh stops, and authentic content.Sustained improvement based on demand.
Practical follow-on services

Build the business,
not just the page.

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.

Guidance behind the plan

A more detailed, sourced audit is saved with the project as docs/OVERHAUL-SEO-AEO-AUDIT.md, outside the webroot.

Bring Dirty Birds to your event Book the truck ↗