Free · without registration
Check Schema.org and compare it with the page content
Check your structured data and see what information is documented in the delivered HTML. Unclear assignments are expressly marked.
Check your side
URL retrievals run through Seitenreport. The delivered HTML is evaluated without JavaScript execution. External style sheets and reloaded content are not considered.
Their results
Example: Valid structure with incomplete content
Select “Insert HTML locally” and apply this JSON-LD block. The example organization is fictitious. Alternatively, a public page can be retrieved with appropriate markup.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Beispiel GmbH","url":"https://example.org/"}</script>Expected result
The block can be decoded as JSON and contains the type Organization. If, on the other hand, the closing quote behind the name is removed, a JSON parse error occurs – a problem other than a missing or technically incorrect property.
What the Example Does Not Prove
The technical evaluation does not know all the requirements of each search engine format and cannot confirm the existence of a company. Parsable markup and recognized types do not guarantee rich results or the correctness of the content.
Syntax alone is not enough
Valid JSON-LD may contain information that no longer fits the visible offer. The checker complements the syntax and type check with a document comparison for JSON-LD: name, price with currency, availability, author, publication and change date and address.
How to read the content balance
“Found” means that a suitable document has been recognized in the delivered HTML. ‘Deviation’ is shown only in the case of a clearly contradictory indication. “Not found” is not evidence of false markup. Several products, variants or non-attributable information appear as ‘manually check’.
Microdata and RDFa will still be recognized and listed. The new content comparison is limited to JSON-LD. CSS files, JavaScript and content behind interactions are not executed. A search result with extended representations or an AI designation cannot be guaranteed from this.
Check again after correction
Correct the information in the template or in the CMS and check the published URL again. Use supplementary Googles Test for rich search results, to validate supported search functions.
Frequent questions
Does Content Matching Replace Google’s Rich Results Test?
No. It supplements the examination with references and possible contradictions. It does not reflect all the requirements of individual Google search functions.
Can I check unpublished HTML?
Yes. Inserted HTML is processed locally. The basic local check detects JSON syntax, schema types, microdata and RDFa; the URL check also uses the existing server validator.
Why does “manually check” appear?
In the case of several objects or variants, the parser cannot safely assign an indication. Compare object path, value and visible location.