Schema.org
Validate JSON-LD, Microdata and RDFa: syntax, entity types, properties and value types. Inspect evidence for each affected entity.
JSON-LDMicrodataRDFa
Loading
Loading
We use cookies to give you a better experience on our site. You can learn more about how we use cookies in our privacy policy.
Check one page for indexing blockers, metadata, links and structured data. Get actionable evidence from the response HTML.
We check the HTML returned by the server. Markup added by JavaScript is not checked yet.
Coverage and limitations
Start with one URL. Fix the findings in the source HTML and run the audit again to verify the changes.
Check websiteInspect the finding, understand the expected value and open the documentation for that specific check.
Report example
robots.noindexReview the evidence in the server HTML and correct the value using the linked documentation.
Documentation for robots.noindexThe actual value shows what the scanner found in the response. A selector or JSON pointer is included when available.
Review access and indexing restrictions first, then metadata and structured data. Check whether each restriction is intentional before changing it.
Publish the change and audit the same URL again. Compare the finding and its evidence with the previous result.
Enter a public page URL: a landing page, article or product page. No access to your CMS is needed.
We check the HTML returned by the server. Markup added by JavaScript is not checked yet.
Start with one URL. Fix the findings in the source HTML and run the audit again to verify the changes.
Schema.org vocabulary checks and Google profile requirements are shown separately, so a valid entity can still have missing rich-result fields.
Validate JSON-LD, Microdata and RDFa: syntax, entity types, properties and value types. Inspect evidence for each affected entity.
Check Breadcrumb, Article, Product snippet and Organization against separate Google profiles, with required and recommended fields.
Formal validation does not guarantee a rich result or a search ranking.
The audit checks one public URL. It does not crawl the site, check backlinks or track search positions.
If a check cannot finish, the report marks its coverage. An unchecked section does not count as a pass.
SEO Scanner checks the response HTML. Use the SSR check to compare it with the page after JavaScript runs.
Compare source and rendered HTMLStart with crawling and indexing, then review page metadata, links and structured data.
Inspect HTTP status, redirects, robots.txt, robots meta and X-Robots-Tag. See access restrictions and indexing directives separately.
<meta name="robots" content="noindex">A noindex directive asks search engines to exclude this page.
Check title, description, H1, language and viewport in the response HTML. Find missing or conflicting declarations.
Review canonical targets and language alternatives, including invalid URLs and conflicting declarations. Cross-page reciprocity is not checked.
Find links without crawlable destinations or useful text and images without alt attributes. Linked pages are not fetched.
Validate JSON-LD, Microdata and RDFa: syntax, entity types, properties and value types. Inspect evidence for each affected entity.
Check Breadcrumb, Article, Product snippet and Organization against separate Google profiles, with required and recommended fields.
Audit a landing page, article or product page to catch technical SEO issues in the HTML your server sends.