Skip to content
FAQ topic 12 answers

Magento Schema Validator FAQ

Which schema types matter for Magento, JSON-LD vs Microdata, why Google’s tester says valid but Search Console flags errors, how often to revalidate, whole-site validation, “missing recommended” meaning, errors blocking rich results, vs Google’s Rich Results Test, dynamic Offers, score formula, VideoObject / Course / HowTo support, when to hire a full-site auditor.

All 12 answers

Which Schema.org types actually matter for a Magento store?

Choose types that describe the actual page: for example, Product and its real offer on a product page, BreadcrumbList for a breadcrumb trail, or Article for an article. Organization and Person describe genuine identities. A service page does not require Article simply to claim expertise. Check the current requirements of the intended consumer. FAQPage remains a Schema.org type, but Google FAQ rich results were retired in May 2026.

References: Google structured-data introduction; Google Search documentation updates.

Was this helpful?

JSON-LD vs Microdata vs RDFa, which should Magento use?

Google supports JSON-LD, Microdata and RDFa and recommends JSON-LD. JSON-LD can be easier to maintain separately from layout HTML, but existing correct Microdata or RDFa is not automatically obsolete. Inspect the theme and installed modules before adding another emitter. A syntax change cannot correct a wrong price, invented review or inconsistent entity.

References: Google structured-data introduction; Google structured-data guidelines.

Was this helpful?

Why does Google’s Rich Results Test say my schema is valid but Search Console flags errors?

First compare the same URL, store view, page state and feature. A test and a Search Console report may reflect different observations or processing times. Inspect the complete rendered markup, current feature requirements and the specific reported issue. This checker assesses one typed node with fixed top-level profiles, so it cannot explain every difference between Google tools or verify the visible page. A clean test also does not guarantee a search appearance.

References: Google structured-data guidelines; Schema.org Markup Validator.

Was this helpful?

How often should I revalidate my Magento schema?

Recheck representative pages after changes to a theme, output module, catalog data, store-view setup or cache behavior. Prioritize the affected templates and values rather than relying on a universal daily schedule. After deployment, inspect the actual URL and relevant Search Console reports. Keep the test evidence tied to the deployed version and investigate a change before assigning a cause.

References: Google structured-data guidelines.

Was this helpful?

Can I validate my whole site with this tool?

This form checks a pasted JSON snippet; it does not crawl your website. For a graph or array, the current implementation selects the first typed node rather than validating every entity. Isolate a node for a focused first pass, then inspect the complete page with an appropriate external validator. A whole-site audit also needs representative URLs, template ownership, store contexts and a review of visible values.

References: Schema.org Markup Validator; Google structured-data guidelines.

Was this helpful?

What’s a “missing recommended” warning, do I need to fix it?

Here, missing recommended means a field from this tool's fixed profile is absent. It is not automatically a Google requirement or a Schema.org error. Read the relevant feature documentation and supply only genuine applicable data. Do not invent product identifiers, reviews or dates to improve a score. Existing empty values and absent properties may also receive different treatment under these local rules.

References: Schema.org data model; Google structured-data guidelines.

Was this helpful?

Do all “errors” actually block rich results from appearing?

No. An error label belongs to the validator and rules that produced it. This checker can flag a local profile requirement that does not match the current Google feature you need. Conversely, it does not inspect every nested entity or visible-content policy, so passing its checks is not approval. Google feature requirements, page accessibility and content quality need their own review.

References: Google structured-data guidelines.

Was this helpful?

How is this different from Google’s Rich Results Test (search.google.com/test/rich-results)?

This tool parses JSON and applies an embedded registry of 15 top-level profiles. It does not query the current Schema.org vocabulary, recursively validate all graph nodes, check every enum or resolve entity references. Google's Rich Results Test addresses currently supported Google features; Schema.org Markup Validator addresses broader vocabulary markup. Use the tools for their different purposes. Google no longer shows FAQ rich results, even though FAQPage remains a Schema.org type.

References: Schema.org Markup Validator; Google Search documentation updates.

Was this helpful?

Can I validate my Product JSON-LD if my offers block is dynamic (price changes per customer group)?

Check the markup generated for the relevant store, currency and visitor context, then compare it with the visible offer. This tool can examine the pasted top-level Product shape, but it does not run Magento pricing, inspect customer-group rules or validate nested offers completely. Use actual public page evidence and the current Product feature guide; a local score cannot establish whether every price or cache variant is correct.

References: Google Product snippet guide; Google structured-data guidelines.

Was this helpful?

What’s the 0-100 score formula?

The current implementation starts at 100, subtracts 25 for each profile error, 5 for each warning and 3 for each absent recommended field, then limits the result to the range 0 to 100. These are local heuristic weights. The colored score display and its thresholds are not Google metrics, a probability, merchant approval or a rich-result eligibility threshold. Read each finding and complete the checks the tool does not perform.

References: Google structured-data guidelines.

Was this helpful?

What about VideoObject / Course / HowTo / Recipe / Event?

Course, HowTo, Recipe and Event have embedded profiles in this checker; VideoObject does not. A type outside this registry can still be valid Schema.org vocabulary. With Auto-detect it receives structural checks only; selecting a known expected type can apply that fallback profile. Read mismatch warnings instead of treating the result as vocabulary approval. The available dropdown is not a list of current Google search features. Check the current documentation for your content and intended consumer rather than assuming that a profile, sample or passing score establishes feature support.

References: Schema.org data model; Google Search documentation updates.

Was this helpful?

When should I hire someone to audit the whole site instead of using this tool?

Consider a broader review when multiple modules emit conflicting entities, store or price variants disagree, a deployed page differs from the source template, or a Google report needs investigation beyond a snippet. Define the affected templates, examples and acceptance checks first. The useful outcome is a traceable correction to the responsible output owner, followed by rendered-page verification, rather than a promise to reach a particular checker score or search appearance.

References: Google structured-data guidelines.

Was this helpful?
Kishan Savaliya Online 10 AM to 7 PM IST Chat on WhatsApp