What is the difference between schema and featured snippets?
Structured data, often called schema markup, is code that labels the content of a page in a standard vocabulary from schema.org. It says, for example, that a page is an article, that a block of text is a question and its answer, or that a business has this address and these opening hours.
A featured snippet is the highlighted answer Google sometimes shows at the top of results. It is pulled automatically from the visible text of a page that Google already ranks reasonably well. You cannot switch one on with markup.
So the two do different jobs. Schema removes ambiguity. Snippet-ready writing supplies the answer. A page that does both is easier to understand, and the writing habits behind it also help AEO and GEO.
Does FAQ schema still give rich results?
Mostly no, for ordinary business sites. In 2023 Google reduced FAQ rich results so that they appear mainly for well-known, authoritative government and health websites. A local business that adds FAQPage markup should not expect the expandable question display in results. Google's guidance can change, so check the current Google Search documentation before you decide.
That is not a reason to delete FAQ sections. A visible FAQ answers long-tail questions, supports People Also Ask style queries, and gives AI assistants short passages to quote. If you add FAQPage markup, it must match the visible text exactly, and it should never contain content that visitors cannot see.
Our own guides follow this approach: write FAQs for readers first, then add markup only where it is accurate and low effort.
Which schema should each page type use?
Use the type that describes the page honestly, and fill in properties that are visible on the page.
| Page type | Schema to use | What it describes | Notes |
|---|---|---|---|
| Home page | Organization or LocalBusiness, WebSite | Who you are, logo, contact details, social profiles | Use LocalBusiness only if you serve customers at a location or area. |
| Service page | Service, plus Organization as provider | What you offer, where you offer it, and offers | Match names and areas to the visible text. |
| Location or city page | LocalBusiness with address, hours, areaServed | A physical or service-area business | Keep name, address and phone identical to your Google Business Profile. |
| Blog post or guide | Article or BlogPosting, with author and dates | Headline, author, published and modified dates | Show the same dates on the page. |
| Every inner page | BreadcrumbList | The navigation path to the page | Mirrors the visible breadcrumb trail. |
| Product page | Product with Offer | Name, price, availability, reviews if genuine | Only mark up reviews that are real and visible. |
| FAQ section | FAQPage (optional) | Question and answer pairs | Rich results are limited, so it is optional. Keep it matched to visible text. |
Always validate markup after changes. Property requirements and eligibility for rich results change over time.
How to write a snippet-ready answer
Start from a real question
Use Search Console queries, People Also Ask and customer enquiries. Phrase it as a person would.
Use the question as a heading
An H2 or H3 that mirrors the query connects the passage to the search.
Give the answer in 40 to 60 words
Define the term or give the number first. Make the answer complete on its own.
Follow with the matching format
A numbered list for steps, bullets for options, a table for comparisons. See the snippet types table.
Add detail, then mark up what is visible
Expand with examples and limits, then add Article, BreadcrumbList and any other schema that matches the page.
How do you test structured data?
| Tool | What it checks | When to use it |
|---|---|---|
| Rich Results Test (Google) | Whether a page's markup is valid and eligible for supported rich results | Before and after publishing a template |
| Schema Markup Validator (schema.org) | Whether the markup is valid schema.org syntax, regardless of Google eligibility | To catch syntax and type mistakes |
| Google Search Console | Enhancement reports for detected structured data and errors across the site | Weekly checks after launch |
| URL Inspection tool | What Google saw on the live page, including detected markup | When a specific page looks wrong |
Tool names and features change. Confirm current options in Google's documentation.
Build schema in, do not bolt it on
The cleanest way to get schema right is to generate it from the same data that creates the page, so the visible text and the markup cannot drift apart. That is how we plan it in our web development projects and in technical SEO work.
Once the markup is live, make sure Google can see it. Google Search Console set-up gives you the reports that show errors, and our guide on getting your site indexed covers what to do if pages are missing. For the wider picture of what a good site includes, read what makes a website SEO-friendly.
FAQ schema and featured snippets: common questions
Does FAQ schema help me win featured snippets?
Not directly. Snippets are taken from visible page text that Google already ranks well. Markup labels content for machines, but a clear, concise answer under a question heading is what makes a page snippet-ready.
Is FAQ schema still worth adding?
Since Google restricted FAQ rich results to a small set of sites in 2023, the visible benefit for most businesses is small. A visible FAQ is still useful. Add markup only if it matches the text exactly.
Which schema types matter most for a business website?
Organization or LocalBusiness on the home page, Service on service pages, Article on blog posts and BreadcrumbList across inner pages. Add Product with Offer for e-commerce. Match everything to visible content.
How do I test my structured data?
Use Google's Rich Results Test and the Schema Markup Validator for individual pages, then monitor the enhancement reports in Search Console across the site. Re-test after template changes.
Can wrong schema hurt my site?
Misleading or spammy markup can lead to a manual action or loss of rich-result eligibility. Mark up only what visitors can see, and keep details such as prices and hours accurate.
Should I use JSON-LD or microdata?
Google recommends JSON-LD for most cases, and it is easier to maintain because it sits apart from the page layout. Check the current documentation for your use case.
Do AI assistants use schema?
It is not confirmed how much AI answer engines rely on it. Structured data helps machines understand a page, so it is worth keeping accurate, but do not expect a guaranteed boost in AI answers.