Schema markup is the machine-readable layer underneath your content — the part that tells search engines and AI systems what your page actually means, not just what it says. But most people have never looked at it. Not on their own site, and certainly not on anyone else's.
That's a problem. Because if you can't see what's there, you can't fix what's broken.
This guide covers three ways to check schema markup on any website — from quick browser tricks to proper tooling — and what to look for when you do.
The quick and dirty: View source
The most basic approach is right-clicking any page and selecting "View page source," then searching for application/ld+json. This finds JSON-LD schema blocks directly in the HTML.
It works. But it's slow, hard to read, and tells you nothing about whether the markup is actually valid or complete. For a quick sanity check on a single page it's fine. For anything more than that, it isn't.
Google's Rich Results Test
Google offers a free tool at search.google.com/test/rich-results. Paste a URL and it shows you which schema types it detected and whether they're eligible for rich results in Google Search.
The limitation: it only checks a subset of schema types — the ones Google uses for rich results. It won't show you Organization, WebSite, BreadcrumbList, or dozens of other types that matter for AI visibility. And it doesn't tell you anything about property completeness. A schema block can pass the Rich Results Test and still be nearly empty.
The proper way: A dedicated schema viewer
The fastest and most complete option is a browser extension built specifically for this. One click, any page, full picture.
We built the enhancely Schema Viewer as a free Chrome extension for exactly this reason. Install it, browse to any page, click the icon — and you see every schema type on that page, every property, every value. Expanded, readable, no source code required.
What you actually see
Take the screenshot: 11 entities, 93 properties filled. WebPage, Organization, WebSite, BreadcrumbList, Article — and a FAQPage with 5 expanded Question entries, each with a filled acceptedAnswer. That's a well-structured page from a machine perspective.
The pink checkmark in the top right? That confirms enhancely is correctly deployed and generating the markup automatically.
What you're looking for when you check a page:
- Types present — Is there an Organization type? A WebPage? If it's a product page, is there a Product type with Offer and AggregateRating? Missing types mean missing signals.
- Properties filled — A schema type with only a name property is technically valid but practically useless. The value is in the depth: how many properties are populated, and are they populated correctly?
- FAQPage — Often overlooked since Google removed the visual FAQ rich result for most sites. But AI systems like ChatGPT, Perplexity, and Google AI Overviews love explicit question-answer pairs. A filled FAQPage is a direct signal that your page answers a specific question.
What to do if markup is missing or thin
That's the part most guides skip. Seeing the problem is one thing. Fixing it across hundreds or thousands of pages is another.
Manual schema implementation at scale is not realistic. The markup needs to stay accurate as content changes, cover all relevant types, and pass validity and compliance checks before it goes live. That's what enhancely automates — crawling, generating, validating, and deploying schema markup across your entire site, without touching your content.
The extension is the diagnostic. enhancely is the fix.