The highest-ROI single action
The structured pages AI engines quote word for word
FAQ schema hands an engine a question and its answer, already paired and already labelled. There is nothing left for it to infer. It is the cheapest item on the fix list and the one most sites have skipped.
Every plan queries all 6. See how each engine picks who it names
What we measured
sites we crawled during a scan carry no FAQ schema at all, and those 39 are not a random sample: every one of those firms ran a scan because someone suspected it was missing from AI answers.
Engines queried
ChatGPT, Claude, Perplexity, Gemini, Google AI Mode, Microsoft Copilot. Every plan, including the free one.
Answers kept
Every answer is stored word for word, so any number on your report can be checked against the text it came from.
The gap this closes
- An engine reading marketing prose has to infer what your answer would be.
- 26 of 39 readable crawls we ran carry no FAQ schema at all, and those firms all suspect they are absent, so this is not a random sample.
- That is two thirds of a group already worried about being invisible.
- It is the cheapest item on the fix list and the one most often skipped.
What you end up with
- Finished pages with the markup already inside them, not a checklist telling you to add it.
- Question and answer pre-paired and labelled, so nothing is left to inference.
- Valid FAQPage JSON-LD that matches the visible text exactly.
- A fix measured in an afternoon, not a rebuild.
How it works
Three steps, and you only do the first one.
The clusters come from losing questions
We do not brainstorm questions. The scan already recorded which buying questions an engine answered by naming a competitor, and the clusters are drawn from those, in buying-intent order, so the first page you publish is aimed at a question that decides a shortlist.
Each answer has to stand on its own
An engine quotes one answer, not your page. So every answer is written to survive being lifted out of context: specific, self-contained, and phrased the way a buyer phrases it, not the way your category writes about itself. Compliance detail, company size and tech stack go in, because that is what the qualifying question turns on.
The markup matches the page, and the next scan referees it
Schema that claims content a reader cannot see gets treated as spam, so every question and answer in the JSON-LD renders on the page as well. The next scan re-crawls your site, reports whether the markup is live, and asks the original question again on all six engines. Nobody has to take your word for it, or ours.
What you get on each plan
You get finished pages with the markup already inside them, not a checklist telling you to add markup. This is what lands, per plan, with the monthly volume read live from the plan configuration.
Track
Free- No drafting on this tier
- The question clusters where somebody else was named
- Ranked by buying intent
- The crawl reports whether you carry FAQ markup today
- Next scan tells you if the markup went live
Fix
$99/mo- FAQ pages built monthly against your top clusters
- FAQ blocks ride along inside every other draft
- Valid FAQPage JSON-LD matching the visible text
- Each page shows the answer that lost the question
- Publishes through your CMS, nothing without your say-so
Dominate
$499/mo- Enough volume to blanket a category, not pick at it
- Clusters chosen across the wider question budget
- Video and newsletter reuse the same answers
- One cluster answered on site, YouTube and newsletter
- Contested clusters get built before empty ones
Rule
$1999/mo- The same run across every brand in the workspace
- A human picks which categories to blanket first
- One good client report becomes a book of work
The proof, including the parts that flatter nobody
Our own scans are why this sits at the top of the fix list and not in the middle. Across 46 completed reports, the best any engine managed was naming the brand in 7.4% of the buying questions we asked it, and the others sat between 0.4% and 4.0%, measured on firms that arrived already suspecting they were missing.
Being listed somewhere is not the same as being retrievable, and we have the harder version of that number. When we asked four engines to recommend managed IT providers across 15 North American regions, 139 of the 228 firms listed in those regions' own Clutch directories were named by no engine at all. Structure is what the engines can read. A directory entry is what they can ignore.
Read the MSP AI Visibility Report 2026 →A worked example: the block and the markup it ships with
Here is one pair from a page built for a firm losing the question of whether a small clinic can pass a HIPAA audit with an outsourced IT provider. The firm is illustrative; the structure is what every page ships with. The answer is written to survive being lifted out of the page, because that is what happens to it.
What the reader sees
- Q. Can a 20-person clinic pass a HIPAA audit with an outsourced IT provider?
- A. Yes, and the audit turns on evidence rather than headcount. A provider has to supply a signed business associate agreement, an asset inventory, access logs going back six years, documented annual risk analysis, and encryption at rest and in transit. Ask for those five artefacts before you sign. A provider who cannot produce them for an existing client will not produce them for you.
What ships in the page head, matching word for word
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Can a 20-person clinic pass a HIPAA audit with an outsourced IT provider?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, and the audit turns on evidence rather than headcount. A provider has to supply a signed business associate agreement, an asset inventory, access logs going back six years, documented annual risk analysis, and encryption at rest and in transit. Ask for those five artefacts before you sign. A provider who cannot produce them for an existing client will not produce them for you."
}
}]
}Three properties make that answer quotable. It commits in the first clause, so a system extracting one sentence still gets your position. It carries five checkable specifics, which is what separates an answer worth citing from an answer worth skipping. And it names the qualifying detail a buyer actually holds in their head, the clinic size and the audit, so the answer matches the question a real person typed.
The page it lives on carries the rest of the cluster: the business associate agreement, the six-year log retention, what happens during a breach investigation. One page, one cluster, every pair marked up, every pair visible.
How it actually works
The mechanism, for anyone who wants it. Open a card to read the detail.
What the markup does to an answer
A page of marketing prose forces a reading system to do inference. It has to decide which sentence was meant as an answer, which question that answer belongs to, where the answer stops, and whether the surrounding paragraph changes its meaning. Every one of those decisions can go wrong, and a system that has a cheaper option takes the cheaper option.
Read the detail
FAQPage markup removes all four decisions. Each question is a labelled string, each answer is a labelled string, and the pairing is declared instead of inferred. A machine assembling a response gets a quotable unit with a source attached and no ambiguity about where it ends. That is the whole trick, and it is why this sits at the top of a fix list rather than in the middle of one.
The second effect is quieter. Structured data also tells a reader what kind of thing your page is about, so an Organization block, a Service block and a set of question and answer pairs together describe a firm, what it sells, and what it says about the questions buyers ask. Systems that decide who to name are looking for exactly that description.
Google cutting FAQ rich results made this more valuable
In 2023 Google restricted FAQ rich results to a short list of government and health sites, and a lot of teams read that as the end of the format and pulled the markup out. The rich result went away. The parsing did not, and the same markup now feeds AI Overviews and AI Mode, which is the surface that answers the buying question a blue link used to answer.
Read the detail
So the market position is unusual and worth being blunt about. A format got written off for the wrong reason, a large share of sites removed it or never added it, and the systems that matter most for vendor selection still read it. Cheap, unclaimed and machine-readable is a rare combination.
The four ways markup gets ignored
The first is schema that overstates the page. Markup claiming an answer a reader cannot see is treated as spam, and the penalty lands on all of your structured data, not on the one block that lied. Everything we ship renders the same text it declares, and our own test suite compares the JSON-LD against the visible page byte for byte before a deploy.
Read the detail
The second is invalid types. An invented type name reads as nothing at all, and our own report validation had to start stripping schema recommendations that named types Schema.org does not define. The third is placement: markup written into the page by a script the crawler never runs is markup nobody sees, so it belongs in the served HTML. The fourth is nesting. Blocks buried inside a graph get missed by naive parsers, which is a defect we found in our own crawler when a valid Offer block on our pricing page read as absent.
None of those are hard to avoid. All four are common, and all four turn work you already paid for into work that does nothing.
What it costs
The prices and monthly volumes below read from the live plan configuration, so this page cannot drift from what your account gets.
| Plan | Price | Questions | Scans |
|---|---|---|---|
| Track | Free | 5 | 1/mo |
| Fix | $99/mo | 10 | 4/mo |
| Dominate | $499/mo | 25 | 4/mo |
Rule is portfolio level and sales-assisted, and it is the right conversation if you are running this across more than one brand.
See where you stand first
Run a free scan and find out which of these gaps you actually have.
Get your free auditFrequently asked questions
What is FAQ schema?
A structured-data format defined by Schema.org that labels question and answer pairs so a machine reads them without guessing. Search engines and AI engines both parse it, and the AI benefit is now the bigger of the two by some distance.
Do the answers have to match what is visible on the page?
Yes, always. Markup that claims content a reader cannot see is treated as spam and can get every bit of your structured data ignored. Every page we ship renders the same questions and answers that its schema declares.
Can I add FAQ schema myself with a plugin?
The markup, yes: plugins emit valid JSON-LD and that part is solved. The part that moves visibility is knowing which questions to answer, phrased the way buyers ask an engine, with answers specific enough to quote. That comes from scan data, not from a plugin.
Does it still help with Google?
Yes, for a different reason than in 2022. Google cut most FAQ rich results in classic search, and the same markup still feeds AI Overviews and AI Mode, which is where the value now sits.
How many FAQ pages does a site need?
Enough to cover the question clusters your buyers ask, which for most B2B firms is a dozen or more. We build them in buying-intent order, so the pages that can win a shortlist go before the pages that explain a category.
How do I know it worked?
The next scan re-crawls your site and reports whether the markup is live, then asks the question that prompted the page again on every engine. A fix you cannot verify is a fix you are taking on faith.
Sources and further reading
- SE Ranking, structured data in AI answers (via Search Engine Land): 71% of pages ChatGPT cites include structured data; 65% for Google AI Mode.
- Schema.org FAQPage specification: The machine-readable format AI engines parse to extract question-answer pairs.
Related solutions