What Google says about schema and AI search
Google’s guide to its generative AI features, first published in May 2026 and updated in July, lists “overfocusing on structured data” as something you can skip. Its AI features rely on the same crawling, indexing and ranking systems as normal search. The guide still recommends structured data as part of normal SEO, because it supports rich results.
Some industry studies claim that pages with schema get cited more often by AI assistants. No AI company has confirmed that schema causes citations; well-built pages simply tend to have both. Treat schema as clean labelling, not a ranking shortcut.
Which schema types matter in 2026
| Schema type | Add it to | Google rich result in 2026? | Why it’s still worth it |
|---|---|---|---|
| Organization | Home or About page | Yes: logo and business details | Ties your website to your social profiles and brand facts |
| LocalBusiness | Contact or location pages | Yes: business details | Confirms address, hours, phone and service area |
| Article or BlogPosting | Every blog post | Yes | Names the author and dates, supporting trust |
| Person or ProfilePage | Author pages | Yes: profile pages | Shows a real expert stands behind the content |
| BreadcrumbList | All pages | Yes | Explains your site structure |
| Product with Offer | Product pages | Yes: product snippets and merchant listings | Price, availability and reviews in a reliable format |
| Event | Event pages | Yes | Dates, venue and tickets |
| VideoObject | Pages with video | Yes | Helps videos appear in search and AI features |
| FAQPage | Pages with a real FAQ | No, since 7 May 2026 | Still valid; describes visible Q&A clearly |
| HowTo | Step-by-step guides | No, since 2023 | Valid, but no Google display |
| Service | Service pages | No Google rich result | Valid schema.org type that describes what you sell |
One rule applies to every type: markup must match content people can see on the page. Hidden or invented markup, such as fake reviews, breaks Google’s guidelines.
Structured data Google has retired
| When | What changed |
|---|---|
| 2023 | HowTo rich results removed; FAQ rich results limited to government and health sites |
| June 2025 | Seven types phased out, including Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing |
| January 2026 | Practice problem markup removed from Search Console reports |
| 7 May 2026 | FAQ rich results stopped appearing for all sites |
| June to August 2026 | FAQ report, Rich Results Test support and API data removed |
You do not need to delete old markup. Google says unused structured data causes no problems.
Copy-ready example: Organization schema
Place this on your home page and replace the placeholder values with your real details:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company Name",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.png",
"description": "One sentence on what you do, for whom and where.",
"email": "hello@example.com",
"telephone": "+91-XXXXXXXXXX",
"address": {
"@type": "PostalAddress",
"streetAddress": "Street address",
"addressLocality": "City",
"addressRegion": "State",
"postalCode": "PIN code",
"addressCountry": "IN"
},
"sameAs": [
"https://www.linkedin.com/company/your-company",
"https://www.instagram.com/your-company"
]
}
The sameAs links matter most for AI systems: they connect your website to your other profiles, so every source describes one clearly identified business.
Copy-ready example: Article schema with a named author
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Your post title",
"datePublished": "2026-11-01",
"dateModified": "2026-11-01",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://www.example.com/author/author-name/",
"jobTitle": "Head of SEO",
"sameAs": ["https://www.linkedin.com/in/author-name"]
},
"publisher": {
"@type": "Organization",
"name": "Your Company Name",
"logo": {"@type": "ImageObject", "url": "https://www.example.com/logo.png"}
}
}
How to add and test schema on WordPress
- Use Rank Math or Yoast to generate Organization, Article and BreadcrumbList markup automatically.
- Fill in the plugin’s knowledge graph settings: name, logo and social profiles.
- Set each post’s author to a real person with an author page.
- Test syntax with the Schema Markup Validator (validator.schema.org).
- Test rich result eligibility with Google’s Rich Results Test, for the types Google still supports.
- Watch Search Console’s Enhancements reports for errors after publishing.
Copy-ready example: LocalBusiness schema
For a business customers visit, add LocalBusiness (or a more specific type such as Dentist or Restaurant) to your contact or location page:
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Your Business Name",
"url": "https://www.example.com/",
"image": "https://www.example.com/storefront.jpg",
"telephone": "+91-XXXXXXXXXX",
"priceRange": "₹₹",
"address": {
"@type": "PostalAddress",
"streetAddress": "Street address",
"addressLocality": "City",
"addressRegion": "State",
"postalCode": "PIN code",
"addressCountry": "IN"
},
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"],
"opens": "10:00",
"closes": "19:00"
}],
"sameAs": ["https://www.instagram.com/your-business"]
}
Make sure every value matches your Google Business Profile exactly.
A practical schema set for a service business
| Page | Schema to add |
|---|---|
| Home | Organization (or LocalBusiness), WebSite |
| About | Organization with founder and sameAs links |
| Team or author pages | Person or ProfilePage |
| Service pages | Service (optional), BreadcrumbList |
| Contact or location pages | LocalBusiness with address and opening hours |
| Blog posts | BlogPosting with named author, BreadcrumbList |
| Pages with a real FAQ | FAQPage (valid, though no Google rich result) |
| Pages with embedded video | VideoObject |
Common schema mistakes
| Mistake | Why it’s a problem | Fix |
|---|---|---|
| Markup describes content that isn’t on the page | Breaks Google’s structured data guidelines | Only mark up visible content |
| Different business details in schema and profiles | Sends conflicting signals | Use one set of facts everywhere |
| Duplicate Organization blocks from several plugins | Confusing, sometimes contradictory data | Let one plugin or one template output it |
| Fake or self-written review markup | Policy violation and trust risk | Remove it; earn genuine reviews |
| Outdated prices or hours | Wrong information in search and AI answers | Update schema when details change |
| Never testing after site changes | Errors go unnoticed | Re-test after updates and redesigns |
How AI engines use structured data: what’s known and what isn’t
| Engine | What’s publicly known |
|---|---|
| Google AI Overviews and AI Mode | Google says structured data isn’t required and no special schema is needed; it still supports rich results and helps Google understand pages |
| Microsoft Bing and Copilot | Bing reads schema.org structured data as part of understanding pages, and Copilot grounds answers in Bing’s index |
| ChatGPT, Perplexity, Claude | No public documentation on whether their search features use structured data when choosing sources |
The safe conclusion: structured data helps search engines read your facts unambiguously, which supports every system built on top of them. It doesn’t replace clear visible content, crawler access or a strong reputation.
Step-by-step: audit the schema on your existing site
- List your page types: home, about, services, contact, blog posts, products, location pages.
- Test one example of each in the Schema Markup Validator to see what’s already there.
- Look for duplicates and conflicts, such as two Organization blocks with different names or phone numbers.
- Compare with visible content and your Google Business Profile. Every fact in the markup should match.
- Remove anything misleading, such as self-review stars or markup for content that isn’t on the page.
- Fill the gaps using the practical schema set above, starting with Organization and LocalBusiness.
- Re-test in the validator and, for supported types, Google’s Rich Results Test.
- Schedule a check after every redesign, plugin change or change to your business details.
Keep schema and your entity consistent
Schema works best as one part of a consistent identity. Your business name, logo, address, phone, founders and social profiles should be the same in your markup, on your website, in Google Business Profile and on LinkedIn. When every source agrees, search engines and AI assistants can describe you with confidence.
Copy-ready Person schema for author pages
Named, credible authors help readers decide whether to trust a page, and Google’s guidance on helpful, people-first content asks whether it is clear who created the content. Give each author a profile page with a short bio, their role, their experience and links to their professional profiles. Then describe that person with Person markup on the profile page:
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Author Name",
"jobTitle": "Head of SEO",
"url": "https://futurecreeps.com/author/author-name/",
"image": "https://futurecreeps.com/images/author-name.jpg",
"worksFor": {
"@type": "Organization",
"name": "FutureCreeps",
"url": "https://futurecreeps.com/"
},
"sameAs": [
"https://www.linkedin.com/in/author-name/"
]
}
On each article, set the Article markup’s author to the same person, with the same name and a link to the profile page, so the post, the author page and the markup all agree. Replace the placeholder name, photo and links with real ones. Never invent credentials or use a made-up persona: the bio must describe a real person who wrote or reviewed the content.
If you use WordPress, Yoast and Rank Math can generate author markup from the WordPress user profile. In that case, fill in the profile fields (name, bio, photo and social links) rather than adding a second, conflicting block, then check the page in the Rich Results Test or the Schema Markup Validator.
This is also the fix for posts currently published under “admin”. An “admin” byline gives readers, search engines and AI assistants nothing to connect the content to.
Frequently asked questions
Does schema markup help my site appear in AI Overviews?
Google says it is not required and there is no special schema for AI features. It still helps Google understand your pages and keeps you eligible for rich results.
Should I remove FAQ schema now that FAQ rich results are gone?
No. FAQPage is still a valid type, and Google says unused markup causes no problems. Keep it where the page has a real, visible FAQ.
Does ChatGPT read schema markup?
OpenAI has not published details on how its search uses structured data. Clear visible content matters most; schema is a helpful extra layer.
Which schema should a small business add first?
Organization or LocalBusiness on your home and contact pages, then Article markup with a named author on blog posts.
Can I mark up my own customer reviews on my website?
You can describe reviews in schema, but Google does not show review stars for businesses reviewing themselves on their own LocalBusiness or Organization pages. Focus on genuine Google reviews instead.
Should I use JSON-LD or microdata?
Google recommends JSON-LD because it’s the easiest to add and maintain. It sits in a script block and doesn’t change how your page looks.
Can a WordPress plugin handle all my schema?
Plugins like Rank Math and Yoast cover Organization, Article and BreadcrumbList well. You may still need custom markup for LocalBusiness details, services or video, and you should check plugins don’t output duplicate blocks.
Does schema help with Bing and Copilot?
Structured data is a standard that Bing also reads, so the same markup helps Bing understand your pages, which feed Microsoft’s Copilot answers. Clear visible content still matters most.
Is Service schema worth adding to service pages?
It’s optional. Google doesn’t show a rich result for it, but it’s a valid schema.org type that describes what you offer, where and at what price. Add it if it’s easy to keep accurate.
How often should I review my structured data?
After any redesign, theme or plugin change, and whenever your business details, prices or hours change. A quarterly spot-check of key page types is a sensible routine.
Can wrong schema hurt my rankings?
Misleading markup can lead Google to ignore your structured data or apply a manual action that removes rich result eligibility. It’s far better to have less markup that’s accurate than lots of markup that isn’t.
Need your structured data checked? Ask for a free technical SEO and AI visibility audit.
Sources
- Google Search Central: Optimizing your website for generative AI features (updated 10 July 2026)
- Quattr: FAQ schema in 2026, what's confirmed and what's not (8 July 2026)
- Google Search Central Blog: Simplifying the search results page (June 2025)