Google ignores your structured data when it’s broken.
You won’t get rich results, and you’ll miss free traffic.
Schema Checker is a free browser-based tool that validates structured data against schema.org rules. It checks JSON-LD, Microdata, or RDFa markup and tells you if Google can read it or if it’s broken beyond repair.
What Is a Schema Checker?
Schema Checker is a free browser-based tool that scans your page’s schema markup and highlights errors, warnings, and unsupported types. You paste the URL or code, and it tells you exactly what’s wrong — no login needed.
It supports all major schema types: Article, Product, Event, FAQ, How-to, and more.
If it’s not in schema.org, the tool flags it.
Why It Matters for SEO
Bad schema means no rich snippets.
No rich snippets mean less visibility and lower click-through rates.
Google tested rich results across 100 queries and found they took up to 35% of page one clicks. If your schema’s broken, those clicks go to competitors.
The real issue is most people assume their schema works because the page renders. That’s not how Google sees it.
Here’s what actually happens: you add FAQ schema, but one missing comma turns it into gibberish for Google. No error shows on the page. You think it’s live. It’s not.
Google recrawls most sites every 3-7 days, so broken markup can cost you weeks of missed traffic.
How to Use It
- Go to https://scrawl.tools/tools/schema-checker (no login needed)
- Paste your URL or schema code into the box
- Click “Check” and review the results
It takes under 10 seconds.
The tool is free, and you don’t need to sign up.
What the Results Tell You
You see a clean breakdown: valid schema types, errors, and warnings.
Errors block rich results. Warnings might not, but they’re risks.
If you used `datePublished` but formatted it as “January 1st, 2024,” the tool flags it. Google wants ISO format: “2024-01-01T09:00:00+00:00”.
Missing `@context`? That’s a full error. Google won’t touch it.
The output shows exactly where in your code the issue occurs. You don’t guess — you fix.
Most people miss the context error because their site still displays fine. But for Google, missing context means “skip this.”
3 Mistakes Most People Make
- They validate the home page but ignore product or blog pages
Your homepage might pass, but your articles use a different template. That’s where schema breaks. You need to test every page type.
- They copy-paste schema without checking for dynamic data errors
Say your CMS injects `null` for `aggregateRating` when no reviews exist. That’s not valid JSON. The schema fails.
Most people don’t test after publishing — they assume the template works every time.
- They mix JSON-LD and Microdata on the same page
Google supports both, but using both at once creates conflicts. The Schema Checker flags duplicate entities.
Here’s what actually happens: Google picks one, ignores the other, and you lose control over what appears.
If you’re using schema but not testing it weekly, you’re flying blind.
Changes in CMS, plugins, or templates break schema silently.
Fix broken links that can harm crawlability — use the Broken Link Checker alongside this.
If redirects are mangled, Google might not even reach your schema. Check those with the Redirect Chain Checker.
Test your schema today. It’s free, no login needed, and takes less than a minute.
Go now: https://scrawl.tools/tools/schema-checker
How to Use It Step by Step
- Open the tool: Go to https://scrawl.tools/tools/schema-checker in your browser. No account creation required.
- Choose your input method: You have two options. Either paste your full page URL in the top field, or select the "Code" tab and paste your raw schema markup (JSON-LD, Microdata, or RDFa). The tool works either way.
- Run the check: Click the "Check" button. The scan takes less than 10 seconds for most pages.
- Review the results: The output shows three categories: valid schema types (green), errors (red), and warnings (yellow). Read through each flag carefully.
- Locate the problem: Each error shows the exact line and field where the issue occurs. For example, you might see "Missing required field: @context at line 5." This tells you exactly what to fix.
- Make the correction: Go to your website's code or CMS editor and fix the flagged issue. Common fixes include adding missing fields, correcting date formats to ISO 8601 (2024-01-15T09:00:00+00:00), or removing duplicate schema blocks.
- Re-check your work: Paste the corrected code or URL back into the tool to confirm the error is gone. You should see a clean result with no red flags.
- Test all page types: Don't just check your homepage. Run the same process on your blog posts, product pages, and any other major page templates. Schema breaks often happen on secondary pages while the homepage looks fine.
Common Mistakes to Watch For
- Assuming one valid schema means all pages are fixed: Your homepage might have perfect markup, but your blog uses a different template with its own schema errors. Test at least three pages from each major section of your site.
- Ignoring warnings because they're not errors: Yellow warnings can still hurt your visibility. A missing `url` field in Product schema won't block rich snippets, but it leaves money on the table. Fix warnings, not just errors.
- Forgetting to recheck after plugin or theme updates: Your schema might have passed last month, but a CMS update can change how dynamic fields are populated. Set a reminder to validate quarterly, or whenever you update plugins.
- Using special characters without proper escaping: If your schema contains quotes, apostrophes, or HTML characters in text fields, they need to be escaped or wrapped correctly. The tool will catch this, but many people skip the recheck after fixing quotes.
- Testing only in the Schema Checker and skipping Google's own validator: Schema Checker is thorough, but Google's Rich Results Test (search.google.com/test/rich-results) is the official source. Always verify your final schema there too.
Troubleshooting & Common Questions
Why does my schema pass the tool but Google still won't show rich results?
Schema validity is only part of the equation. Google also checks your page's authority, content quality, and whether the schema type matches your actual content. A valid FAQ schema on a product page, for example, might be ignored because the content doesn't support it. Make sure your schema accurately describes what's on the page.
Can I check schema on pages behind a login or paywall?
No, the tool can't crawl pages that require authentication. In this case, copy your page's full HTML source code (including the schema block), then paste it directly into the tool's "Code" tab instead of using the URL option. This lets you validate the markup without needing the tool to access the live page.
What should I do if the tool shows an error but my CMS says the field is optional?
Schema.org marks some fields as recommended, others as optional. If a field is optional per schema.org specs, the tool flags it as a warning, not an error. You can safely leave optional fields blank. However, if the tool shows a red error, that field is required for that schema type and you must include it or remove the entire schema type.