Most restaurant websites lose searches to Google Business Profile

That's fine. GBP captures most "[restaurant name]" and "[cuisine] near me" traffic. What it doesn't capture is the long-tail commercial-intent queries that drive private events, catering contracts, brand-story press mentions, and reservations for occasions ("rehearsal dinner restaurants [city]," "private dining for 30 guests," "catering for office lunch [neighborhood]").

These queries land on your website, not GBP. And they convert at higher dollar values than walk-in dinner. WordBinder's local-restaurants-hospitality skill builds the supporting content layer that converts these searches.

The page archetypes a restaurant site needs

Private dining / events pages

The highest-value B2B page on most restaurant sites. Captures rehearsal-dinner traffic, corporate-event traffic, holiday-party traffic. Page needs: room capacity, minimums (food and beverage), available menu options (set menus, family-style, buffet), AV capabilities, photos of the space, and a dedicated inquiry form (separate from regular reservations).

Catering pages

Corporate catering is recurring revenue. The catering page needs: menu options at different price points, minimum order, delivery radius and fees, lead-time requirements, dietary accommodations (gluten-free, kosher, vegan), and a quote-request flow.

Menu / cuisine pages

If you have a distinctive cuisine (Sichuan, Neapolitan pizza, Texas BBQ, omakase sushi), a dedicated cuisine page captures research-mode searches. Page explains what the cuisine is, what distinguishes the restaurant's approach, and the signature dishes.

About / brand story

The page press cites, Yelp reviewers reference, and high-end customers read before booking. Tells the founding story, the chef's background, the sourcing philosophy. Builds the authority that converts a comparison-shopper.

Location pages

Multi-location restaurants need one page per location with address, hours, location-specific menu variations, that location's chef/GM, and parking and transit info. Schema is Restaurant with geo.

Seasonal features

Holiday menus, summer cocktail features, restaurant week, oyster festivals. These pages capture peak-season search demand and need to be planned 8 weeks ahead of the season they target. The Refresh pillar watches them for decay and surfaces them when they need refresh.

What the local-restaurants skill knows

  • Schema is event-type-aware. Private-event pages get EventVenue schema with capacity and amenities. Catering pages get Service schema. Menu pages get Menu schema.
  • Photography emphasis. Restaurant search depends heavily on imagery. The skill writes pages that explicitly call out where the photo deck belongs (top of page, between sections, in the gallery).
  • Local-amenity references. Pages mention the neighborhood, nearby landmarks, transit stops, and where to park — the things locals expect a real local page to include.

Try it on private events

Most restaurants leave private-event revenue on the table because the page doesn't surface for "private dining [city]" queries. Run a brief through WordBinder for your highest-value private-event page. Trial is free for 14 days.