FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 3 of 6

Schema per page type

A page type to schema table, the FAQPage change, decision rules and testing.

5 min readUpdated 2026-11-07
All chaptersChapter 3 of 6
  1. 01What AEO is and what changes
  2. 02Answer-first copy
  3. 03Schema per page type
  4. 04llms.txt and AI crawlers
  5. 05FAQ, comparison and glossary pages
  6. 06Measuring it, and what nobody can promise

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 typeSchema typeFill in at leastIn Google's gallery
Every pageOrganization (on the home page at least), BreadcrumbList below homeName, URL, logo, contact, social profiles; each crumb's name and URLYes, both
HomeOrganization, WebSiteSite name and URLOrganization yes, WebSite no
ServiceServicename, serviceType, provider, areaServed, offers if publicNo
Physical productProductName, price, availability, real ratingsYes
Software productSoftwareApplicationName, description, rating if realYes (Software app)
Blog post or guideArticle or BlogPostingheadline, image, datePublished, dateModified, authorYes (Article)
Case studyArticleSame as aboveYes (Article)
Glossary termDefinedTermname, description, inDefinedTermSetNo
Page with a visible FAQFAQPageEach question and its visible answerNo longer
Physical locationLocalBusinessAddress, hours, contactYes (Local business)
Team or founder profileProfilePage with a PersonName, role, linksYes (Profile page)
Comparison pageBreadcrumbList, plus FAQPage if it has a visible FAQSkip Product markup for rivals' productsSee 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

  1. 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.
  2. Is it true of this page? Markup must represent the page truthfully. A service page is not a Product because Product has richer results.
  3. 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.
  4. Who owns it? If nobody updates it when the page changes, generate it or leave it out.
  5. 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 Person for people and Organization for organisations
  • add a url or sameAs with 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.ts does 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.

ToolWhenWhat it tells you
Rich Results TestWhile buildingWhether the markup is valid, and sometimes a preview
URL InspectionAfter publishingWhether Google found the structured data on the page
Rich result status reportsOngoingWhether 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.

Takeaways

What to remember from chapter 3.

  • Mark up only what is visible and true of the page.
  • Google says no special schema is needed for its AI features.
  • Google no longer shows FAQ rich results. Keep FAQPage only if it is accurate and cheap to maintain.
  • Generate JSON-LD from page data, then test it in the Rich Results Test and URL Inspection.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.