Where does a short spoken answer belong on a vegan dining page?
Quick answer
On a sentence already visible on the page, usually the first answer in the festive FAQ. Mark only that block. Do not hide a script or mark the whole menu. Do not invent a voice-traffic percentage. The questions themselves: hotel festive FAQ.
Vs other Intelligence guides
| Guide | Job |
|---|---|
| Hotel festive FAQ | Which questions exist. This page marks one visible answer for speech. |
| FAQ pages | How FAQ blocks are written. Speakable does not add a second hidden FAQ. |
| Review snippets | Stars and review markup. Not the spoken sentence. |
| Menu HTML vs PDF | The menu is HTML. Do not mark the entire menu as the spoken answer. |
| Menu claims | What the menu may say. The spoken line cannot go past that. |
| IndexNow | The Bing ping. Markup is a separate step after the page is live. |
| This guide | Where does a short spoken answer belong on a vegan dining page |
Composite operator guidance. Not a voice-assistant partnership. Do not treat a worksheet sentence count as a typical voice-traffic lift.
Three texts. One may be marked.
| Text | What it is | This week |
|---|---|---|
| Visible answer | One or two sentences guests already see | Usually the first festive FAQ answer. |
| Hidden script | Words only in JSON or a display-none block | Do not add one. |
| Markup | A speakable pointer at the visible block | Add it only after the sentence is on the page. |
Staff line: "If a guest cannot read it, a speaker does not get a private version."
Proof ladder (spoken answer)
| What is true this week | You may do | You freeze |
|---|---|---|
| A short answer is visible. It matches the menu and the FAQ. | Point speakable at that block only. | A longer hidden script. A carbon claim that is not on the page. |
| The FAQ is missing | Write the visible FAQ first. Festive FAQ. | Markup with nothing to read. |
| The line is the whole menu | Leave the menu as HTML. Menu HTML. | Marking every dish. |
| You want Bing to notice the page | IndexNow after the page is live. | Treating speakable as the ping. |
Spoken-answer kit
- Pick one visible sentence or two from the festive FAQ. Read them aloud. If they take more than a few breaths, shorten the visible text first.
- Check every claim in that sentence against the menu page. Menu claims.
- Point the markup at that block by a selector guests can see. No display-none.
- Do not mark reviews, the full menu, or the footer.
- A person views source and confirms the words in the markup also appear in the HTML body.
- Ping is separate. IndexNow after publish.
| Leave out | Why |
|---|---|
| A hidden "say this instead" paragraph | Voice and the page have to match. |
| The entire FAQ | One answer. The rest stays readable, unmarked. |
| A new green superlative | Claims calculator. |
| Review stars inside the spoken block | Review snippets are a different markup. |
Allow vs banned
| Surface | Allow | Kill |
|---|---|---|
| Festive FAQ answer | One visible short answer, then markup | Hidden script. Whole-page mark. |
| Menu | HTML for guests | Speakable on every dish |
| Reviews | Their snippet guide | Spoken stars |
| Board story | Pages where the spoken line is visible | Invented voice-traffic percentage |
EmpCo from 27 September 2026 still applies to that spoken sentence in the EU. Do not publish a voice-traffic lift for the tag.
10-check spoken-answer log (run this week)
View the page and the source. Log Y/N.
| # | Check | Pass |
|---|---|---|
| 1 | Is the spoken sentence visible on the page? | Yes. |
| 2 | Is it one short answer, not the whole menu? | Yes. |
| 3 | Any display-none or JSON-only sentence? | Remove it. |
| 4 | Claims match the menu? | Menu claims. |
| 5 | FAQ exists before markup? | Festive FAQ. |
| 6 | Review markup left separate? | Review snippets. |
| 7 | Menu still HTML? | Menu HTML. |
| 8 | IndexNow not treated as this tag? | IndexNow. |
| 9 | A person compared source to the screen? | Yes. |
| 10 | A vendor promised voice traffic from the tag? | Ignore. No invented %. |
Fix the block that week. Hidden text was marked: delete it. The whole menu was marked: narrow it to one answer. Do not invent a voice-traffic percentage.
Spoken-answer freeze (labeled example)
Replace every cell from the live page. Do not copy the example as a voice benchmark.
| Field | Worked example | Your cell |
|---|---|---|
| Visible sentence marked | 1 sentence example, or NONE | [sentence] |
| Festive pages checked | 8 pages example | [pages] |
| Hidden spoken blocks | 3 leftover hidden blocks example. Delete them. | [hidden] |
| Pages that mark the whole menu | 2 leftover full-menu marks example. Narrow them. | [whole_menu] |
Those cells are worksheet labels. If [sentence] is NONE, do not add speakable markup.
Go / no-go
| Call | When |
|---|---|
| No-go | Hidden text, whole menu, a claim that is not visible, no FAQ yet |
| Go on one visible answer | Guests can read it, markup points at it, claims match the menu |
| Partial go | Delete hidden blocks and narrow the selector today |
Score hidden blocks and full-menu marks. Voice traffic is not a KPI.
The sentence guests see is the sentence a speaker may use.
Mark one short visible answer. Leave hidden scripts and the full menu unmarked.
Template fields and 7-day run
| Field | Fill with | Do not invent |
|---|---|---|
[sentence] | Visible FAQ answer, or NONE | A hidden script |
[selector] | The block guests see | A display-none node |
[signer] | Person who compares source to the screen | A tag with no reader |
[markets] | US / EU / UK / both | A voice-traffic figure |
Brief: "Sentence: [sentence]. Selector: [selector]. Signer: [signer]. Markets: [markets]. If the sentence is NONE, add no speakable markup. No voice-traffic %."
- Day 1: Read festive pages. Fill [hidden] and [whole_menu].
- Day 2: Choose one visible answer or mark NONE.
- Day 3: Check claims against the menu.
- Day 4: Add markup only if the sentence is visible.
- Day 5: Compare source to the screen.
- Day 6: Keep review snippets and IndexNow on their pages.
- Day 7: Run the 10-check log.
Frequently asked questions
Where does a short spoken answer belong on a vegan dining page?
On a sentence already visible on the page, usually the first answer in the festive FAQ. Mark only that block. Do not hide a script, mark the whole menu, or add a claim that is not on the page. Do not invent a voice-traffic percentage.
Can the spoken text differ from the page?
No. Guests have to be able to read the same words.
May we mark the whole menu?
No. One short answer. The menu stays HTML and unmarked.
Is this the same as a review snippet?
No. Stars have their own markup. This tag is one visible sentence.
What do we measure if not voice traffic %?
Whether the marked sentence is visible, leftover hidden blocks, and leftover full-menu marks.