Schema Markup for AEO: What to Add and What to Avoid
Which structured data types help explain a business, which claims to avoid, and how to test the markup you generate.
Get a focused website audit
Share your website and the business problem you want to solve. We will review your enquiry and discuss a suitable next step.
Structured data can help search systems interpret the subject of a page, but it cannot turn a weak offer into a trusted recommendation. The most useful schema is accurate, consistent and supported by content a visitor can inspect.
Which Business Facts Should Your Schema Describe?
For a service business, decide which legal or trading name, canonical website, service descriptions, served markets and contact information are verifiable. For ecommerce, identify actual products, variants, prices and availability. Use one source of truth across the website rather than several contradictory biographies.
Schema.org vocabulary is broad, while Google's rich-result eligibility is narrower. Adding a property does not mean Google will display a special treatment, and there is no universal JSON-LD type that makes an LLM recommend a brand.
How to Choose Structured Data Types for Your Pages
Use the appropriate type for the page's job. A homepage can describe the organisation; a service page can describe a service and its provider; editorial articles can use BlogPosting or Article; and products can use Product with genuinely supported offers.
Do not place Product prices on a general blog post merely because the topic mentions a product. Do not assert a physical branch in a city where there is no office.
| Page | Potentially appropriate schema | What to verify |
|---|---|---|
| Company homepage | Organization / WebSite | Identity and links |
| Service landing page | Service / WebPage | Real service description |
| Editorial guide | BlogPosting / Article | Title, author and dates |
| Product page | Product / Offer | Actual price, stock and variants |
How to Generate JSON-LD from Verifiable Facts
Use the free Schema Markup Generator to produce editable markup from supplied business facts. Review the generated output, replace sample details and make sure its URL references match the final page.
Never invent aggregate ratings, fake testimonials, awards, office addresses or client statistics. These claims can undermine trust and may violate search guidelines. A correct JSON document with false business facts is not good structured data.
How to Validate Schema Against Visible Page Content
First check that the JSON parses and uses appropriate schema.org properties. Then run Google's Rich Results Test for features it supports, and consult Search Central's structured-data guidance for policy requirements.
Compare the markup with the HTML text users see. Test after the theme is published, since a preview URL may not behave like the final canonical page. Avoid duplicated or conflicting structured-data blocks from several Shopify apps.
What Schema Can and Cannot Do for AI Visibility
Treat markup as a supporting layer. Descriptive content, crawlability, accurate internal linking, original proof and clear buyer-facing answers remain necessary. A tool can generate good syntax; editorial judgement is needed to decide what deserves to be marked up.
Google's AI search guidance says that there is no special AI-specific schema required for AI Overviews and AI Mode. Use schema to describe reality, not to promise visibility.
Schema Validation Tools and Related Services
Open the Schema Generator · Run an AEO Audit · Explore technical SEO
If you need help turning a diagnostic into an implementation plan, book a review of your technical search foundations. We can review the evidence, explain the options and scope the work before recommending a retainer.
Editorial team: Working Weekends. Examples are illustrative unless a source is identified.
Add Working Weekends as a Preferred Source on Google ↗