The short answer
Give each page type the structured data that truthfully describes it, in JSON-LD, generated from the same data as the page. Start with Organization and BreadcrumbList, then add Article, Service, Product or FAQPage where the page really is one. Be clear about what this buys you. Google says there is no special schema you need to add for AI Overviews or AI Mode, and that structured data should match the visible text. Schema labels your facts. It does not earn citations by itself.
For syntax, examples and how to add it in Webflow or Astro, read our schema markup guide. This chapter is the decision table.
Page type to schema: the table
The last column shows whether the feature was listed in Google's structured data gallery when we read it. This changes, so check the current docs. "No" does not make the type wrong. It means you should expect no special Google display from it.
| Page type | Schema type | Fill in at least | In Google's gallery |
|---|---|---|---|
| Every page | Organization (on the home page at least), BreadcrumbList below home | Name, URL, logo, contact, social profiles; each crumb's name and URL | Yes, both |
| Home | Organization, WebSite | Site name and URL | Organization yes, WebSite no |
| Service | Service | name, serviceType, provider, areaServed, offers if public | No |
| Physical product | Product | Name, price, availability, real ratings | Yes |
| Software product | SoftwareApplication | Name, description, rating if real | Yes (Software app) |
| Blog post or guide | Article or BlogPosting | headline, image, datePublished, dateModified, author | Yes (Article) |
| Case study | Article | Same as above | Yes (Article) |
| Glossary term | DefinedTerm | name, description, inDefinedTermSet | No |
| Page with a visible FAQ | FAQPage | Each question and its visible answer | No longer |
| Physical location | LocalBusiness | Address, hours, contact | Yes (Local business) |
| Team or founder profile | ProfilePage with a Person | Name, role, links | Yes (Profile page) |
| Comparison page | BreadcrumbList, plus FAQPage if it has a visible FAQ | Skip Product markup for rivals' products | See above |
Build yours with the schema generator, then check it with the tests below.
FAQPage: what changed
Google's documentation says FAQ rich results no longer appear in Google Search, and it has removed the documentation for that feature. Plenty of older advice still treats FAQ markup as a way to win extra space on the results page. Do not plan on that.
Should you remove it? Our rule:
- Keep it if it is generated from your visible FAQ and costs you nothing to maintain. FAQPage is still a type on schema.org, and it states your questions and answers clearly. We have not read any vendor saying its AI product uses it, so treat it as tidy labelling, nothing more.
- Remove it if it is hand-written, out of date or does not match the page. Wrong markup is worse than none.
- Do not add it to win a display in Google. That display is gone.
The visible FAQ is what matters. Chapter 5 covers it.
Decision rules
- Is it visible? Google's guidelines say not to mark up content that readers cannot see. If it is not on the page, it does not go in the markup.
- Is it true of this page? Markup must represent the page truthfully. A service page is not a Product because Product has richer results.
- Is it complete? Items missing required properties are not eligible for rich results. Article has no required properties in Google's docs, but add the recommended ones that apply.
- Who owns it? If nobody updates it when the page changes, generate it or leave it out.
- One main type. A page can hold several items. Include a main type that reflects what the page is about, and connect related items with
@id.
Article and author details
Most marketing sites get this slightly wrong, and it is easy to fix. Google's Article docs recommend headline, image, datePublished, dateModified and author. For authors, the docs ask you to:
- include every author shown on the page
- give each author a separate entry
- put only the name in
author.name, with no job title or company in that field - use
Personfor people andOrganizationfor organisations - add a
urlorsameAswith a valid address
Only change dateModified when you really changed the content. A date that moves every build tells readers nothing.
Generate it from one source
Hand-written schema drifts away from the page. Build it from the data that renders the page instead.
- Coded sites. A shared function takes the page data and prints JSON-LD. On this site,
src/lib/seo.tsdoes this. - Webflow. Site-wide Organization code goes in site settings. Per-page and CMS schema goes in page custom code, using CMS fields. Need a hand? See our Webflow SEO service.
- Sanity or any headless CMS. Keep the fields in the content model and print them at build time.
Test it in three places
Google names three tools, and they catch different problems.
| Tool | When | What it tells you |
|---|---|---|
| Rich Results Test | While building | Whether the markup is valid, and sometimes a preview |
| URL Inspection | After publishing | Whether Google found the structured data on the page |
| Rich result status reports | Ongoing | Whether a template or serving change broke the markup later |
These tools catch technical errors, not quality problems. Google says quality needs a human check, so also read the markup against the page. Structured data issues can also bring a manual action. Google says that costs a page its rich result eligibility, and that it does not affect ranking. You can see any in the Manual Actions report.
What this site uses
For a real reference: every page built with our shared helper includes an Organization node, plus BreadcrumbList below the home page. Service pages add Service, blog posts add BlogPosting with a named author, case studies add Article, glossary terms add DefinedTerm, and pages with a visible FAQ add FAQPage from the same data as the FAQ. You can see the terms in our JSON-LD and schema markup glossary entries.


