Schema markup for AI search

The five types that carry the most weight

Add these before anything exotic.

• Organization or ProfessionalService: your identity, area served and offerings
• Service: each service you sell, linked to the organization as provider
• Article: authored content, with dates and publisher
• FAQPage: question and answer pairs that appear on the page
• BreadcrumbList: where the page sits in your site hierarchy

Use stable @id references

Give your organization a single @id and reference it from every other node instead of repeating the details. That turns a pile of unrelated snippets into a connected graph, which is exactly what an entity resolver needs.

Common mistakes

Each of these can neutralize otherwise good markup.

• FAQ schema for questions that are not visible on the page
• Review or rating markup that is not backed by real reviews
• Duplicate Organization nodes with different names or URLs
• Schema left in place after the underlying content changed

Validate and keep it in sync

Run the Rich Results Test and the Schema.org validator after every content change that touches a marked-up section. Stale schema is worse than no schema, because it makes your entity look unreliable.