AI Overviews for Uptown Houston Private Dining Rooms

Service charge or gratuity? Write it the way the bill does

Texas treats a labeled gratuity differently from other charges, so the word on your page matters. A summary that blurs the two can mislead a host before they ever email you.

Hosts ask about the extra charges before they ask about the food. How much is added? Is it the tip? Does it count toward the minimum? If your page says 'plus service' and your bill says 'gratuity', an AI summary might pick either word, and the host arrives at the tasting with the wrong idea.

We're not tax advisers, and we'd never write your tax treatment for you. What we'd do is copy the exact label from your real private dining bill, then ask your accountant or general manager to confirm the sentence around it. The page, the contract and the bill should all use the same word for the same charge.

Should we explain Texas tax rules on the page?

We wouldn't. Quote your own charges plainly and leave tax law to your accountant. A page that tries to teach tax gets quoted out of context, which is the exact problem we're trying to avoid.

What if our gratuity changes for big parties?

Say so in the same sentence as the percentage, with the party size where it changes. A split rule written in two separate paragraphs is easy for a summary to half-quote.

Has anyone switched your site out of Google's AI answers?

One switch in Search Console's Settings can take a whole site out of Google's AI answers. Check it before rewriting anything, then find out who else could flip it.

It's the Monday after a holiday-party weekend, and your events manager is wading through forty emails. Not one host mentions an AI answer, and somebody wonders aloud whether the private dining page needs a rewrite. Before anyone touches a sentence, rule out the dull explanation. Somebody may have told Google to leave your site out of its AI features altogether.

That's more likely than it sounds at a restaurant group. Search Console access piles up over the years: the owner, a general manager, the head office's marketing team and an agency from three menus ago. Any of them could have opted the site out during a test or a legal worry and never mentioned it. So the first job is a short list of who holds access, with one question for each of them.

1. Open Settings in Search Console Sign in with an account that owns the property and find the Search generative AI control.
2. Read the current choice If the site is opted out, screenshot the setting with today's date before anyone changes it.
3. List everyone with access Under users and permissions, note every owner and full user. Old agencies and managers who left last year turn up here more often than you'd hope.
4. Ask before flipping it back If the head office opted out on purpose, we'd find out why first. There may be a group policy you'd want to hear about before arguing.
5. Then check the page itself View the private dining page's source and search for nosnippet. A page-wide nosnippet tag stops Google from citing the page in AI answers at all, while data-nosnippet around the capacity table hides just that text.

FAQ markup won't park your questions under the result

Google stopped showing FAQ rich results in Search in May 2026, after limiting them to government and health sites in 2023. Your questions and answers still belong on the page as plain text.

Every so often an owner hears that FAQ schema will make their questions drop down right under their search result. That display is gone now for every site. For a restaurant today, it's not a reason to pay for anything. The questions are still worth writing, because hosts read them and AI tools can quote clear answers from ordinary page text.

We'd put the planning questions in a simple question and answer section on the private dining page itself. Each answer opens with the direct fact, then adds the condition. If a developer wants to add markup too, fine, as long as it matches the visible words exactly.

Picture the tasting where a host slides a phone across the table and points at your FAQ. The weekday minimum it quotes is two menus old, and your events manager has to walk it back while the host's face falls. Markup didn't cause that, and markup can't fix it. Whoever changes the minimums should change the FAQ answers that same afternoon.

Should we delete the FAQ schema our old agency added?

No need. Google says leftover FAQPage markup doesn't cause problems, even though it no longer earns any special display. We'd just make sure it still matches the answers on the page, since stale markup with old minimums is its own small mess.

Why did the FAQ report disappear from our Search Console?

Because Google retired it. After the display ended in May 2026, the FAQ rich result report and Rich Results Test support for FAQs went away in June. Nothing's broken on your account, and there's nothing to reinstall.

How many questions should the private dining page answer?

As many as your events inbox actually brings in, and no more. We'd rather answer ten real questions well than thirty invented ones, and we'd add a new one whenever the same question shows up three times in a month.

Do the questions need to be worded exactly as hosts type them?

Close to it. We'd keep the host's plain wording for the question and put the polish into the answer, so the page sounds like a conversation your events manager has every week.

Answers that still tell the truth when cut in half

Summaries trim long answers, and the trimmed part is often the condition. Keep each number and its condition inside the same short sentence.

Every example in that table is invented, but the pattern is easy to spot on real pages. People write the rule first and the exception second, because that's how rules sound in a staff meeting. A summary that keeps only the first sentence ends up telling a host the opposite of what you meant.

We rewrite with a simple habit: number, condition and alternative in one breath. It feels a touch clunky at first. Then your events manager notices the inbox has fewer 'but I read that you can't' emails, and the clunkiness starts looking clever.

Won't one-sentence answers sound robotic?

Not if you write them the way your events manager talks. We'd read each answer aloud with them, and if it doesn't sound like something they'd say on the phone, we rewrite it.

Should the page show a range, like 20 to 40 guests?

Only with the formats attached. A bare range invites a host to pick the number they like. Seated 24, standing 40 is clearer than 20 to 40 guests.

Guests driving in past the Galleria

The Galleria sits in Uptown, and its crowds shape how dinner guests arrive. Write an arrival paragraph a host can paste straight into an invitation.

Put 30 million visitors a year near your front door, and a host planning a Friday dinner in December has a fair question. How will guests get in, and where do they leave the car? If your page answers that in two sentences, the host copies them straight into the invitation. That's your arrival plan traveling to every guest.

Here's a quick test before the paragraph goes live. Paste it into a blank email and send it to a friend who's never eaten at your place. Ask them, from memory, where they'd leave the car and which door they'd walk through. Wherever they hesitate, the paragraph needs a few more words.

Requested dates, tentative holds and confirmed bookings

Hosts write in asking whether a date is open. Your page can't answer that honestly, but it can explain exactly how holds, deposits and confirmations work.

Is the private room open on a specific Friday?

On the page, we'd never guess. The answer explains how to ask, how fast the events team replies and what information speeds things up, like the date, a backup date and the head count.

Do you hold dates while a host decides?

If you do, say how long a hold lasts and what ends it. If you don't, say that plainly, so nobody assumes their inquiry reserved the room.

When is a booking actually confirmed?

Name the moment, such as a signed agreement plus a deposit. A host who thinks an email reply confirmed the date is a host who'll be upset later.

This is where AI summaries can quietly cause trouble. If your page says 'we're happy to accommodate your date', a tool might boil that down to 'the room is available'. A host then plans around a date nobody confirmed. The fix is boring and precise language: requested, held, confirmed, each with its own meaning.

We'd write those three words into a short 'how booking works' box on the private dining page and use them the same way in your email templates. When the words match everywhere, both people and machines have a harder time mixing them up.

• Requested: the host asked about a date, and nothing is reserved yet.
• Held: the events team is keeping the date for a stated number of days.
• Confirmed: the agreement is signed and the deposit is paid.
• Released: a hold expired or the host passed, and the date is open again.

Room photos and floor plans that do the explaining

Planners judge a room by its photos before they read a word. Show each room set the way it's actually sold, and describe the layout in text too.

• Each room set for a seated dinner, shot from the doorway at eye level.
• The same room set for a standing reception, if you sell it that way.
• Any screen, microphone or sound setup, turned on and visible.
• The table settings and centerpieces that come standard.
• The view or the entrance guests pass on the way in.
• A simple floor plan with the seated and standing counts written on it.

Floor plans are gold for planners and invisible to anyone who can't see the image, including search tools reading your page. So we'd write the layout in a sentence or two beside it: one long table for 20, or three rounds of eight, with the screen on the short wall. That text also gives an AI answer something accurate to quote.

Photo captions deserve the same care. A caption like 'The Wine Room set for a seated dinner of 24' is dull and extremely handy. It matches the capacity line, confirms the format and helps anyone scanning the page on a phone between meetings.

We'd name the rooms consistently as well. Say the menu calls it the Cellar, the floor plan says Private Room B and the booking email says the downstairs room. A planner can't be sure those are the same space. Pick one name and use it everywhere.

Should we show prices next to each room's photos?

We'd show the minimum near the room description, with the date conditions attached. Putting a number under a photo on its own invites it to be quoted without the conditions.

Do we need a video walkthrough of the rooms?

It's a nice extra for hosts who can't visit before booking. Keep it short, show each setup once and add a caption naming the room, so it sits alongside the written details.

A room-at-a-glance block for planners comparing three venues

Planners weigh three rooms at once. Give them a six-line block of counts, minimums and fees that reads the same whether a person or a summary lifts it.

Here's a planner's Tuesday. Three tabs are open, one per private dining page, and a spreadsheet waits with columns for seated count, minimum, gratuity and parking. Whichever page fills that row fastest tends to get the first email. Summaries behave much the same way, pulling whatever lines are easiest to lift, so a tidy block of short lines helps both readers.

Once a month we'd search a planner's usual questions from a signed-out phone, save a dated screenshot and hold it against the block line by line. If a summary quotes a number that isn't in the block, that's the line we'd chase first.

Can Search Console tell us whether AI answers mention our room?

Partly. Google added a generative AI performance report to Search Console in June 2026, and every site had it by August 31. It counts impressions from AI Overviews and AI Mode by page, country, device and date. It shows no clicks and never the words of an answer, so the dated screenshot stays your only record of what a host actually read.

Where should the block sit on the page?

Near the top, right under the room's name and first photo, ahead of the menus and the chef's story. We'd end it with the month and year someone last checked every line. A planner filling in a spreadsheet shouldn't have to scroll past dessert to find the head count.

Why short lines instead of a table?

A table looks tidy on a laptop, but on a phone it often needs a sideways scroll, and pasted into an email it can arrive scrambled. One fact per line survives both, and a host can copy just the lines their boss asked about.

When an AI answer gets your room wrong

Wrong numbers travel. When an answer misstates your capacity or minimum, fix the sources it's likely reading first, then watch whether the answer follows.

1. Capture the wrong answer Screenshot it with the date, the exact question and the cited links.
2. Fix your own page first It's the source you control, so it should be the clearest and most current.
3. Chase the outside listings Directories, event sites and old press mentions can carry stale numbers for years.
4. Use Google's feedback option if one appears Report the error, but don't count on it. Fixing the sources does more.
5. Recheck on your normal schedule Resist checking hourly. Monthly checks show real change without driving you up the wall.

We can't reach inside Google and correct an answer, and anyone who says they can is overselling. What we can do is make sure every source a summary might read tells the same true story. When the page, the directories and the old posts agree, a wrong answer has much less to stand on.

The room-at-a-glance block doubles as your master record. When a directory or a wedding site asks for your details, whoever answers copies from the block, not from memory. Then the same mistake can't creep back in six months later through a form someone filled out in a hurry.

Should we delete the old blog post with the wrong capacity?

We'd usually correct it instead. A dated note at the top keeps any links to it working and tells readers the number changed. Deleting it can leave copies elsewhere with nothing to contradict them.

How long before an AI answer picks up our fix?

There's no fixed timeline, and we won't pretend to know one. We record the date of each fix and compare it with later checks, so you can see when the answer caught up.

A refresh before the busy party months

Holiday party inquiries lean on last year's details unless you update them first. A short refresh keeps menus, minimums and blackout dates current before planners start writing.

We'd set these as calendar reminders on day one, owned by named people on your team. None of them takes long. The point is that each update happens before the questions arrive, so hosts read this year's facts while they're still comparing venues.

The payoff shows up in your inbox more than in any chart. Hosts arrive at the first call already knowing the room, the minimum and how to get there. Your events manager can spend that first call on the menu.

When should the holiday refresh happen?

Before your own inquiries for the season usually start arriving. Your events manager knows that date from last year's inbox, and we'd set the reminder a few weeks ahead of it.

What if holiday minimums aren't decided yet?

Say when they'll be posted and invite hosts to ask in the meantime. We'd rather the page admit a gap than show last year's numbers as if they still apply.