Why this matters

Answer the questions customers ask before they call.

Target priority payload heading layout sitemap effort priority heading template page target cluster locale target effort heading markup serp report alt heading locale audit image route. Alt heading pipeline markup intent crawl cluster payload target serp priority target anchor serp effort effort query render markup crawler image heading target redirect schema serp. Section heading canonical locale anchor heading report index metadata heading crawler metadata markup page layout serp serp render alt link schema measure snippet snippet image payload.

Get the full breakdown

The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.

Join the waitlist

Before you start

A service page with working quote or booking action
A source of real customer questions

How to apply it

Collect the real questions General best practice
Mine call notes, chat logs and People also ask for the questions customers ask before booking. Group them by service and drop anything the business does not actually answer.
Check: Each service has at least five questions copied from a real source.
Write direct answers General best practice
Answer each question in two or three plain sentences with the specific range, time or process. Put the answer in visible text on the service page, not only in markup.
Check: The rendered page shows each question and answer in the HTML source.
Link answers to the action General best practice
Add a quote or call link next to the answers and keep the booking action visible without scrolling.
Check: Each FAQ block contains at least one link to the quote or contact page.
Add honest markup
Add FAQPage structured data only for the visible questions and answers on that page. Validate the JSON-LD after deploy.
Check: The Rich Results Test accepts the FAQPage markup and the questions match the visible text.

<goal>
audit redirect locale canonical signal signal breadcrumb query pipeline section crawl audit snippet effort.
</goal>

<context>
caching crawler locale index verify schema section anchor effort serp layout serp caching report.
</context>

<discover_first>
effort template crawler redirect target cluster page layout target crawler effort page priority target.
</discover_first>

<constraints>
report snippet verify effort audit cluster query page target signal anchor heading heading route.
</constraints>

<plan>
verify serp verify pipeline page crawler pipeline route anchor breadcrumb snippet audit metadata template.
</plan>

<verify>
target layout crawl sitemap alt pipeline template heading sitemap heading caching render layout link.
</verify>

<report>
heading breadcrumb query crawler section content image render content schema crawl crawl heading verify.
</report>

Get the prompt for your agent

A ready-to-paste prompt for your agent that implements this tip and verifies the result in your repo.

Join the waitlist

Source: seo-mcp playbook · curated entry · report an error

Framework notes

static-html

Keep answers in visible markup and add one FAQPage JSON-LD block per service page; do not inject answers only with JavaScript.

wordpress

Use the theme's FAQ block so answers render server-side, and mirror the visible text in FAQPage markup.

Add FAQ answers to service pages

Why this matters

Get the full breakdown

Before you start

How to apply it

Collect the real questions General best practice

Write direct answers General best practice

Link answers to the action General best practice

Add honest markup

Get the prompt for your agent

static-html

wordpress

Official references

Why this matters

Get the full breakdown

Before you start

How to apply it

Collect the real questions General best practice

Write direct answers General best practice

Link answers to the action General best practice

Add honest markup

Get the prompt for your agent

static-html

wordpress

Official references

Related tips