Implementing & Testing Schema
Writing schema is only half the job. You must add it correctly and validate it, or the rich result silently never appears. Here is the exact workflow.
How to add it
- Write your JSON-LD block (or generate it from your CMS/framework).
- Place it in the page — the
<head>or anywhere in the<body>both work for JSON-LD. - Make sure it renders in the final HTML (view source and search for
application/ld+json).
How to test it
- Rich Results Test (search.google.com/test/rich-results) — shows which rich results your page is eligible for and any errors.
- Schema Markup Validator (validator.schema.org) — checks the syntax against Schema.org.
- Search Console — the Enhancements reports show valid and invalid items across your whole site over time.
Good: Add schema → run the Rich Results Test → fix errors → request indexing → check Search Console a week later.
Bad: Add schema and assume it works — then wonder for months why no rich result shows.
Rich Results Test · Schema Markup Validator · Google Search Console (Enhancements) · your framework’s built-in schema (this very site outputs Organization, LocalBusiness, Article, FAQ and Breadcrumb schema automatically).
Always validate on the live URL, not just pasted code — it catches issues your CMS introduces during rendering.
Pro tips
- Validate the live URL, not just the code snippet — rendering can change things.
- After fixing schema, use URL Inspection in Search Console to request a re-crawl.
- Monitor the Enhancements reports monthly to catch errors as your site grows.
Common mistakes
- Schema that validates in isolation but breaks when the CMS renders the page.
- Never checking Search Console, so errors pile up unseen.
- Expecting rich results instantly — Google must re-crawl and choose to show them.
Add JSON-LD to the page, confirm it renders, then validate with the Rich Results Test and Schema Validator, and monitor Search Console’s Enhancements reports. Testing is what turns markup into real rich results.