Schema markup helps search engines and AI systems read your facts: who you are, what you sell, what it costs and who wrote what. But a lot of structured data on the web is broken, duplicated or misleading. These 12 mistakes are the ones we see most often, with the fix for each. See schema markup for AEO for the basics.
1. Duplicate Organization schema
A theme, an SEO plugin and a tag manager each output their own Organization block, sometimes with different names or logos.
Fix: keep one source of Organization markup, ideally on the home or About page, with a stable @id. See Organization schema and the entity home.
2. Inconsistent brand name
"Acme", "Acme AI" and "Acme Technologies Pvt Ltd" across pages and profiles.
Fix: one name, with legalName and alternateName for variants. See entity SEO.
3. Missing or broken sameAs
No links to official profiles, or links to deleted accounts.
Fix: list every official profile (LinkedIn, X, YouTube, Crunchbase, Wikidata) and check they resolve.
4. Markup that doesn't match the page
Schema says ₹999; the page says ₹1,299. Schema lists FAQs that aren't on the page.
Fix: generate schema from the same data that renders the page. Never mark up hidden content.
5. Self-serving or fake reviews
Marking up reviews you wrote about yourself, or ratings with no visible reviews.
Fix: only mark up genuine reviews visible on the page, following Google's review snippet guidelines. See reviews and AI recommendations.
6. Wrong type for the page
Using Product for a service, or Article for a category page.
Fix: choose the most specific accurate type: Service, SoftwareApplication, LocalBusiness subtype, CollectionPage.
7. Missing required or recommended properties
Product without offers, Article without author or date, LocalBusiness without address.
Fix: check each type's required and recommended fields in the Rich Results Test. See Product schema and merchant feeds.
8. Outdated availability and prices
Products marked InStock that sold out months ago; old prices after a change.
Fix: automate schema from live inventory and pricing. AI shopping answers quote these facts.
9. Authors as plain text
"author": "Admin" or no author on articles.
Fix: use Person with name, URL to an author page and sameAs to professional profiles. See author expertise and E-E-A-T.
10. Disconnected entities
Organization, WebSite, Article and Product blocks on the same page that never reference each other.
Fix: connect them with @id references (publisher, author, brand, isPartOf) so engines see one graph.
11. Schema injected only by JavaScript
Markup added client-side may be missed by crawlers that don't render JavaScript, including many AI crawlers.
Fix: output JSON-LD in the server-rendered HTML. See JavaScript rendering and AI crawlers.
12. Never re-validating
Schema breaks quietly after theme updates, plugin changes or migrations.
Fix: validate key templates after every release and check Search Console's enhancement reports monthly. See site migrations and AI visibility.
Quick audit checklist
| Check | Tool |
|---|---|
| Valid JSON-LD on key templates | Schema Markup Validator |
| Rich result eligibility | Rich Results Test |
| Site-wide errors and warnings | Search Console enhancements |
| One Organization block, correct sameAs | View source |
| Prices and availability match page | Manual spot check |
| Schema present without JavaScript | View source / curl |
What schema can and can't do
Schema clarifies facts; it doesn't make weak content rank or force AI citations. Treat it as accuracy infrastructure: when it's right, engines understand you; when it's wrong, they may get your facts wrong too. See technical AEO audit checklist.
Example of a connected graph
A blog post page might include:
- Organization with
@idhttps://example.com/#organization - WebSite with
publisherpointing to that@id - Person (author) with an author page URL and
sameAs - BlogPosting with
author,publisherandisPartOfreferences - BreadcrumbList for the page path
Because each block references the others, engines read one coherent set of facts rather than five disconnected snippets. Keep the Organization block identical across the site so the entity never changes from page to page.
When to ask a developer
Most schema fixes in SEO plugins are settings changes. Ask a developer when markup is hard-coded in templates, generated from product databases, injected by a tag manager, or duplicated by several systems. A short ticket with the page URL, the validator error and the expected output usually gets it fixed quickly.
The bottom line
Fewer, accurate, connected schema blocks beat many conflicting ones. Make markup match the page, keep facts current, connect your entities and re-validate after every change.
