The most citable thing a page can have. Written once, published twice.
Add an FAQ or a How-To to any page, visually and with no code, and MetaPilot publishes it in two forms from one source: real content your visitors read, and FAQPage / HowTo JSON-LD that answer engines read. Change the answer and both change together.
{ "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "Do you offer annual billing?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, annual plans save 10%." } }] } ↑ rendered from the same row as the visible section on /pricing. They cannot disagree.
The problem
AI answer engines love question-and-answer pairs. They are pre-chunked, pre-attributed, and quotable as-is, which is exactly why they get cited.
But getting one onto a live page usually means a developer, a template edit and a deploy. And getting the markup to match means doing the work twice and hoping the two stay in sync. They do not. Structured data claiming answers a visitor cannot see on the page is the precise thing that gets a site’s rich results suppressed.
How it works
-
Write the content
Questions and answers, or named steps and instructions. There is a “Draft with AI” action if you would rather start from what the page already says. It writes into the form unsaved, so you read every word before anything is published.
-
Click where it goes
MetaPilot loads your real page in a picker. Click the spot, choose above, below or inside, set the alignment and width, and preview it. No CSS selectors, no developer.
-
Publish
Your connected channel renders the section into the live page and merges the matching schema.org node into that page’s graph, both from the same stored text. How completely depends on the channel: see what each one delivers.
What you get
FAQPage JSON-LD that cannot drift from the page
Both outputs are derived from the same items on every request, so markup describing answers a visitor cannot see is structurally impossible. Build-time generators write the copy and the markup separately; we render both from one row, at serve time.
Real on-page content, in the raw HTML
On Cloudflare and Shopify the section is server-rendered before any JavaScript runs, so a crawler that does not execute JS still sees it, and the page earns the long-tail question traffic regardless of what the markup does.
Wix works differently, and the difference matters on this page. Answer blocks and Ask AI load in the browser on Wix. Google reads them; most AI crawlers do not. The JSON-LD half is server-rendered on every channel.
Answer engine optimization content, placed visually
The same picker that places the Ask AI widget. Click, preview, publish. Nothing is added to your codebase and nothing is deployed.
HowTo structured data from the same source
Named steps become a readable set of instructions on the page and a HowTo node in the structured data. One page can carry both an FAQ and a How-To, placed independently.
Styled to your site, not ours
Font, size and text colour inherit from the host page, so the block is set in your type rather than in ours. You choose the chrome once for the whole account: bordered, plain, or a card. Not once per page, because the answer is the same every time.
We tell you when it falls off
If a redesign breaks the anchor and the section quietly disappears, liveness monitoring notices and alerts you. A page still serving FAQ markup for content that is gone is worse than one with no markup at all.
You can see whether anyone reached it
Each block reports how many people actually saw it over the last 30 days. It is counted anonymously: no cookie, no storage, no identifier, nothing about who. A block nobody sees is usually on a page nobody visits, which is a placement problem you can fix.
Plan availability
Answer blocks are on every plan, including Free, which covers 10 pages with an FAQ and 10 more with a How-To. There is nothing extra to buy: every plan covers more pages than it manages, so you run out of pages long before you run out of blocks.
FAQ and How-To draw on separate allowances, so putting one of each on a page costs one of each rather than two of anything. Drafting is free, only publishing uses the allowance, and AI drafting is metered on your regeneration allowance.
On the Free tier each published block carries one quiet “Powered by MetaPilot” line inside it, linked with rel="nofollow" so it can never affect your own link profile. Any paid plan removes it.
Frequently asked
No, and we will not claim it. Google retired FAQ rich results entirely on 7 May 2026, after restricting them to authoritative government and health sites back in 2023; How-To rich results were retired in 2023. The markup is still valid and Google says it is fine to keep. The value here is AEO plus genuine on-page content that ranks on its own merits.
Yes. Each is written, placed and positioned independently. FAQ and How-To draw on separate allowances, so a page carrying one of each spends one FAQ slot and one How-To slot rather than two of anything.
No. Nothing is added to your codebase and nothing is deployed. You write the answers and click where they go.
No. Answers are plain text, and blank lines become paragraphs. That is a deliberate security boundary: this content is injected into your live production pages, and an organization can have members who are not its owner.
Liveness monitoring re-checks every published block and alerts you if it stops appearing, telling you exactly which one to re-place.
Like your site. Font, size and text colour are inherited from the page, so the block is set in your own type. What you do choose is the chrome, once for the whole account rather than once per page: bordered, plain, or a card. Dividers and the card surface are mixed against your own text colour, so they read correctly on a light page and a dark one without being told which.
On the Free tier, one quiet "Powered by MetaPilot" line inside each block, linked rel="nofollow" so it cannot affect your link profile. Any paid plan removes it. Nothing else is added, on any tier.
Put your best answers where the engines read them
Write five questions, click where they go, publish. Your visitors and the answer engines get the same thing.
Ask an AI whether answer blocks would help you