If you want one AI-visibility job that's quick, free, and almost nobody else has done, this is it. FAQPage schema takes the questions your clients actually ask, and the answers you already give, and packages them in a format AI assistants and search engines can read and quote directly. It's a small block of code, it doesn't change how your page looks, and in our June 2026 study of UK independent accountancy firms, the number using it was zero. That makes it an open goal.
What is FAQ schema?
FAQ schema (FAQPage markup) is a block of structured data that lists questions and their answers in a format machines read reliably. It sits invisibly in your page's code and gives AI assistants ready-made question-and-answer content they can lift straight into an answer, instead of extracting it from your prose and risking getting it wrong.
"Schema" is shorthand for schema.org, the shared vocabulary that Google, Microsoft and the major AI companies all understand. FAQPage is the type for a page that answers frequently asked questions. When you mark up your FAQs this way, you're handing the machines a clean list: "here is a question, here is the answer," over and over. That's exactly the shape an assistant wants when it's building a reply to a client.
Why does it help with AI visibility?
Because assistants quote answers, and FAQ markup gives them pre-packaged answers to quote. It does the assistant's extraction work for it: clean question, clean answer, no guessing. That makes your content easier to surface accurately.
When someone asks an assistant "do I need an accountant for a limited company in Leeds?", the assistant looks for sources that already answer that question plainly. A page that buries the answer in three paragraphs of marketing copy is harder to quote than one that says, in a structured FAQ: "Q: Do I need an accountant for a small limited company? A: ..." FAQ schema turns your existing knowledge into the most quotable possible format. It won't guarantee you get named (nobody can promise that, because these tools are third-party and change without notice), but it removes friction between your answers and the assistant's reply.
In our June 2026 study of UK independent accountancy firms, 0 of the 24 firms whose homepages we could read carried FAQPage schema.
FAQ markup is one of the cheapest ways to hand an AI assistant ready-made answers it can lift directly. In this (small, non-representative) sample, nobody was doing it.
// Source: Renownly, UK Accountancy AI-Visibility Foundations Report, data collected 3 June 2026. Convenience sample, n=34 (24 readable homepages). Indicative, not a national statistic.
A quick word on history: Google removed the rich-result display (the expandable FAQ snippets in blue-link search) for most sites back in 2023. That's worth knowing, but it doesn't make FAQ markup pointless. The structured data is still there in your page for AI assistants and answer engines to read and use. The visible blue-link decoration went away; the machine-readable Q&A did not.
The copy-paste block
Here's a complete FAQPage block. Replace the amber placeholder questions and answers with your own. The golden rule: only mark up content that genuinely appears on the page, and keep every answer true. Marking up questions you don't actually display, or stuffing answers with claims, is exactly the kind of thing that gets a site distrusted.
// Paste into the <head> of the page that has these FAQs
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do I need an accountant for a small limited company?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A limited company must file annual accounts with Companies House and a Corporation Tax return with HMRC. Most directors use an accountant to handle these, run payroll and keep the company compliant. We act for limited companies across Leeds and West Yorkshire."
}
},
{
"@type": "Question",
"name": "How much does an accountant cost for a small business?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Fees depend on the work involved. Our limited-company packages start from £XX per month and include year-end accounts, the Corporation Tax return and ongoing support. We give a fixed quote up front, with no surprise bills."
}
},
{
"@type": "Question",
"name": "How do I switch accountants?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Switching is straightforward. You tell us who your current accountant is, we send them a professional clearance letter to request your records, and we handle the handover. There is usually nothing for you to chase. Most switches complete within a couple of weeks."
}
},
{
"@type": "Question",
"name": "Do you support Making Tax Digital (MTD) and Xero?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We are MTD-ready and work with Xero, QuickBooks and FreeAgent. We can set you up on the right software, migrate your existing records and make sure your VAT and income-tax filings meet HMRC's Making Tax Digital rules."
}
}
]
}
</script>Notice how each answer is plain, specific and true: real services, a real place, a real process. That's not just good schema practice, it's good for human readers too, and it's exactly the clear, answer-shaped content assistants prefer to quote.
Which questions should you use?
Use the questions clients genuinely ask, phrased the way they phrase them. The best FAQ schema mirrors real enquiries, not the language you'd use in a brochure.
Mine your own inbox and phone calls first. The questions that land in your "new enquiry" emails are gold, because they're the exact wording prospective clients use, which is the wording assistants try to match. Beyond those, these tend to earn their place for an independent UK firm:
- 1Fit and "who you help." "Do you work with contractors / landlords / e-commerce sellers / sole traders?" These match the specific queries clients ask an assistant.
- 2Price. "How much does an accountant cost for a small business?" You don't have to publish exact fees, but a clear, honest range or "from" figure beats silence.
- 3Switching. "How do I switch accountants?" A common worry, and a question you can answer reassuringly and accurately.
- 4Software and compliance. "Do you support Making Tax Digital?" "Do you use Xero / QuickBooks / FreeAgent?" Specific, factual, easy to match.
- 5Sector and local specifics. "Do you handle IR35 for contractors?" "Are you a chartered accountant in [town]?" These tie your specialism and location together, which is what local AI answers turn on.
How to add and validate it
// Step by step
From draft to live in under fifteen minutes
- Write the visible FAQ first. Put the real questions and answers on a page (your homepage, a services page, or a dedicated FAQ page). The schema must reflect what's actually there.
- Fill in the block above to match that visible content, word for word where you can.
- Add it to the page's <head>, the same way you'd add any schema: a header-scripts plugin on WordPress, "code injection" on Squarespace or Wix, or directly in the HTML on a hand-coded site.
- Validate with Google's Rich Results Test (search.google.com/test/rich-results) and the Schema.org Validator (validator.schema.org). Both confirm the JSON parses cleanly.
If the validator throws an error, it's nearly always punctuation: a missing comma between questions, or a smart-quote that slipped in from a word processor. Draft in a plain-text editor to keep your quotation marks straight.
The honest caveat
FAQ schema makes your answers easy to quote. It doesn't, by itself, decide whether you get named, the assistants weigh many signals and vary run to run. But because it's quick, free and (in our sample) entirely unused by competitors, it's about the highest-leverage hour you can spend on AI visibility right now. Pair it with the AccountingService schema that tells assistants you're an accountancy firm, and you've covered two of the most-missed foundations in one afternoon.