How to add FAQ schema to a page
Implement FAQPage JSON-LD on a page so questions and answers can appear as a rich result in Google search.
FAQ schema (FAQPage in schema.org) lets Google display question-and-answer pairs directly in search results as an expandable accordion. The visible-question area on the search result is significantly larger than a normal blue link, lifting click-through rate. This guide implements FAQ schema correctly.
Prerequisites
- • A page with at least 3 genuine question/answer pairs
- • Access to edit the page's HTML or use a CMS that supports custom blocks
Steps
- 1
Write at least 3 genuine Q&A pairs
Google requires the questions and answers to actually appear on the page (not just in the structured data) and to be genuinely useful. Don't include marketing copy or rephrased product descriptions — write real customer questions.
- 2
Render the questions and answers visibly on the page
Each question is a heading or accordion title; each answer is the body that follows. Visible rendering is mandatory — schema without matching visible content is a policy violation.
- 3
Generate the FAQPage JSON-LD
Use the schema.org FAQPage type with @type: 'Question' for each pair, and @type: 'Answer' for the answer. The text in the schema must match the visible text on the page word-for-word.
- 4
Embed the JSON-LD in a script tag
Place the generated JSON inside `<script type='application/ld+json'>` in the page's head or body. Most modern frameworks let you do this in the page template.
- 5
Validate in Google's Rich Results Test
Open https://search.google.com/test/rich-results, paste your URL (or the rendered HTML), and confirm the FAQPage schema validates without warnings. Fix any errors before deploying.
- 6
Deploy and request indexing
Deploy the change. In Google Search Console, request indexing for the URL. Rich results typically start appearing within 1-7 days.
- 7
Monitor for rich-result eligibility
Check Search Console > Enhancements > FAQ regularly. Pages eligible for FAQ rich results appear here; warnings about errors or unmet requirements show what to fix.
Notes
- • Don't include the same FAQ block on dozens of pages — Google may consider this duplicate content and stop showing the rich result.
- • FAQ rich results have become less common since Google's August 2023 update — Google now only displays them for 'well-known, authoritative government and health websites'. The schema is still worth adding for AI Overview citation, but expect fewer rich-result impressions than in years past.
Related guides
How to find orphaned pages on your site
Identify the pages on your site that have zero internal links pointing to them — invisible to crawlers and unable to rank.
How to find and fix broken internal links
Identify broken internal and external links across your site and fix them with redirects or content updates.
How to write a meta description that earns clicks
Craft a meta description that summarises the page accurately and maximises click-through rate from search results.
Related resources
Designing an Effective FAQ Page for Your Website
BlogMaster your FAQ page with smart design tips 📄✅
Use case: Route support tickets by intent, urgency, and topic
Use caseSupport inboxes and ticket queues mix billing questions, bug reports, sales enquiries, and outright emergencies in one undifferentiated stream, and manually tagging each one before routing it to the right team is a chore nobody wants. Webanto's chat endpoint can classify each inbound message against a fixed taxonomy you define, intent, urgency, topic, and return the label as JSON in a single call, so routing logic downstream just reads a field instead of guessing from free text. Because Qwen3.6 reasons before committing to a label, it copes better with sarcasm, mixed-intent messages ('also, is this normal, and also please cancel') and non-native phrasing than a keyword-matching rule set, though edge cases still need a fallback queue rather than blind auto-routing.
Use case: Replace keyword site search with meaning-based search
Use caseKeyword site search fails the moment a visitor's wording doesn't match your copy — someone searching 'cancel my plan' gets nothing if your help article is titled 'Manage your subscription'. Semantic search fixes this by matching on meaning instead of exact terms: Webanto's POST /api/v1/embeddings endpoint (model nomic-embed-text) converts every page, product, or article on your site into a vector, and converts each search query into a vector at request time, so results rank by conceptual closeness rather than shared words. Webanto only returns the vectors — you store and query them yourself, in pgvector or a dedicated vector database, alongside whatever nearest-neighbour search your stack already supports. It's a genuine upgrade for long-tail and conversational queries, though exact-match lookups such as an order number or a SKU are usually still better served by a plain keyword or field lookup running alongside it.
Webanto vs Constant Contact: which email platform should you pick?
ComparisonWebanto and Constant Contact serve overlapping audiences from opposite ends of the spectrum. Constant Contact is a long-established small-business and nonprofit favourite, known for hands-on support, event and RSVP marketing, and an approachable editor — strengths that make it easy to start but come with contact-based pricing and lighter automation. Webanto is a modern platform built on a durable workflow engine, with flat per-plan pricing, unlimited sends, native Shopify and WooCommerce sync, and a unified email, social, and content model. Constant Contact is the safer choice if guided onboarding, event tools, and a familiar small-business brand matter most. Webanto is the better choice if you want deeper automation, native store integration, and flat pricing that does not climb with your contact count.
Advanced SEO Techniques: Boost Your Rankings Today
Blog🚀 Master advanced SEO techniques to skyrocket your rankings! 📈 Start today!
Link Building
Service
Browse all guides
See every how-to guide we've published — across email, SEO, ecommerce, and social media.