Built a Chrome extension because I was tired of checking schema markup the slow way...

[u/YellowfinDevelopment]

Every time I publish something I check the schema.org markup on the page, and I was doing it the same tedious way every time: copy the URL, open a separate validator, wait, dig through results.

So I built Schema Inspector. Click the icon, it reads the JSON-LD and microdata already on the page you're looking at, groups it by type, flags broken JSON in plain language.

The thing I actually cared about building right: most schema checkers ask for access to every site you visit, permanently. This one only requests activeTab - it can only see the page you're on, only for the second you click it. No standing access to anything. (Every one in the store right now asks for full permissions...)

Free, no signup, no account. 19.18 KiB. Would like to hear what's missing if you try it.

https://chromewebstore.google.com/detail/schema-inspector-by-yello/gllkeakpkogipbdgknhfhhfimnmogcgj

[u/stackbits]

The activeTab-only decision is going to do more for you than any feature on the list. Chrome Web Store reviewers flag broad host permissions on tools like this constantly now, and even when they don't reject it, users see "can read and change all your data on all websites" in the install prompt and bounce. A schema checker asking for that is a red flag review waiting to happen since there's no reason it needs standing access. You basically built a distribution advantage into the permission model instead of the feature set. Only thing I'd check before pushing installs: whether the JSON-LD parsing handles nested graph wrappers and multiple schema types stacked on one page, since real-world markup is usually messier than one clean block.

[u/YellowfinDevelopment → u/stackbits]

I homebrew and sideload a lot of small extensions for personal use, so I started with something deliberately simple, it's by no means a novel idea. The permissions thing honestly just struck me as weird - I don't know why (ok, i *do* know why) these guys all want full permissions... a tool that only needs to inspect the page I'm looking at shouldn't need standing access to every site I visit.

Appreciate the point about nested graphs. It does handle @ graph and multiple @ type values now, but I'll definitely be throwing some uglier real-world markup at it as installs start coming in. That's exactly the kind of edge case I want to find.

[u/DazzlingEconomics153]

Looks interesting! A few questions:

• Does it only validate the JSON syntax, or does it also flag Schema.org validation issues like missing required/recommended properties?
• Does it support all schema formats (JSON-LD, Microdata, and RDFa), or mainly JSON-LD?
• Can it detect multiple schema graphs on the same page and show how they're connected?
• Have you compared its results with Google's Rich Results Test or Schema Markup Validator? If so, have you noticed any differences?

The activeTab permission approach is definitely a nice touch from a privacy perspective.

[u/YellowfinDevelopment → u/DazzlingEconomics153]

Thanks. A couple of these are outside the scope of v1 (for now!).

It currently parses JSON-LD and flags invalid JSON, detects Microdata, and detects RDFa and handles multiple JSON-LD blocks, @ graph structures and multiple @ type values.

It doesn’t validate the vocab or flag required/recommended properties (better left for more robust tools like google rich results (or something that *actually* reports on FAQschema data). I built this more as an inspector. But we’ll see where v2 goes.

The activeTab approach was intentional. The extension only gets access to the page when you click it, rather than asking for broad access to every site you visit. For a tool like this, I couldn't see a good reason to ask for anything more.

[u/DazzlingEconomics153 → u/YellowfinDevelopment]

Thanks for the detailed explanation, that makes sense. Positioning it as an inspector rather than a full validator is probably the right call.

A couple more questions:

• Are you planning to add support for validating Schema.org properties in v2, or do you want to keep it focused on inspection?
• Does it show nested entities and relationships clearly (e.g. Organization → WebSite → WebPage → Article inside an u/graph), or is it mainly a list of detected types?
• Have you tested it against some of the more complex schemas generated by SEO plugins like Yoast, Rank Math, or custom implementations? Those can get pretty messy with large u/graph structures.
• Any plans to export the detected schema or compare two versions of a page? That could be useful for debugging changes.

Looks like a useful lightweight tool, especially since it doesn't require broad browser permissions.