tech

How to fix: schema.org primary type valid

Why this matters

Search engines recognise the standard Schema.org types (Organization, WebSite, Article, Product, FAQPage, etc.). Custom invented types get ignored — stick to the catalogue.

Background

The @type field on your JSON-LD must be a recognised schema.org type ('Article', 'Organization', 'Product', etc.). Misspellings ('Artcle') or made-up types ('BlogPost' instead of 'BlogPosting') get silently dropped by Google.

References

Schema.org @type vocabulary

How to fix

Code snippet for each stack we cover. Pick the one matching your server / framework.

nginx

No server config — content fix.

apache

Same.

cloudflare

Same.

wordpress

Validate every page's schema via https://validator.schema.org — fix typos in @type values.

flask

Same — validate as part of CI.

express

Same.

rails

Same.

Verify it's working

validator.schema.org — every @type value should be a recognised vocabulary term (no 'Detected as: unknown').

Want to know if your site has this issue?

Run a free 53-check audit — security, GDPR, NIS2, and technical SEO.

Audit my site →