# FAQ and How-To Answer Blocks — MetaPilot **Tagline:** 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. --- ## 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 1. **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. 2. **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. 3. **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. --- ## 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; MetaPilot renders 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. Wix works differently — answer blocks load in the browser on Wix; Google reads them, but 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. You choose the chrome once for the whole account: bordered, plain, or a card. ### Liveness monitoring 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. ### Per-block view counts Each block reports how many people actually saw it over the last 30 days, counted anonymously — no cookie, no storage, no identifier. --- ## Plan Availability Answer blocks are on **every plan, including Free**, which covers **10** pages with an FAQ and **10** more with a How-To. - FAQ and How-To draw on separate allowances — putting one of each on a page costs one of each, not two. - Drafting is free; only publishing uses the allowance. AI drafting is metered on your regeneration allowance. - On the Free tier each published block carries one quiet **"Powered by MetaPilot"** line, linked `rel="nofollow"`. Any paid plan removes it. --- ## Frequently Asked **Will this get me FAQ rich results in Google?** No. Google retired FAQ rich results entirely on 7 May 2026 (after restricting them to authoritative government and health sites in 2023); How-To rich results were retired in 2023. The markup is still valid. The value here is AEO plus genuine on-page content that ranks on its own merits. **Can one page have both an FAQ and a How-To?** Yes. Each is written, placed and positioned independently, drawing on separate allowances. **Do I need a developer?** No. Nothing is added to your codebase and nothing is deployed. You write the answers and click where they go. **Can I use HTML in an answer?** No. Answers are plain text; blank lines become paragraphs. This is a deliberate security boundary. **What happens if I redesign the page?** Liveness monitoring re-checks every published block and alerts you if it stops appearing, telling you exactly which one to re-place. **Will it look like my site or like a widget?** Like your site. Font, size and text colour are inherited from the page. You choose the chrome once for the whole account: bordered, plain, or a card. **Does anything of yours appear on my page?** On the Free tier, one quiet "Powered by MetaPilot" line per block, linked `rel="nofollow"`. Any paid plan removes it. --- ## Keep Reading - Why FAQs work for AEO - What is Answer Engine Optimization? - Structured data for every page - Schema liveness monitoring - How injection works at the edge