Testing & Validation

When a Vietnamese electronics exporter deployed Product schema across 200 product pages, they assumed the job was done. A month later, a routine audit revealed that 85% of their schema markup contained critical errors: missing required properties, incorrect data types, and broken references to non-existent pages. Google had been silently ignoring their invalid schema, and none of their products were eligible for rich results. They had spent weeks on implementation but achieved zero benefit. A proper testing and validation process would have caught every issue within hours.

Testing and validation are the essential final steps in any schema markup project. Structured data is code, and like any code, it can have bugs. Schema errors do not typically cause visible problems on your website — your pages still load and your content still displays — so it is easy to assume everything is working. But beneath the surface, invalid schema markup is simply ignored by search engines and AI systems. The only way to know your structured data is working is to test it, validate it, and monitor it continuously.

Using Google's Rich Results Test

Google's Rich Results Test is the primary tool for validating your structured data. You can access it at search.google.com/test/rich-results. Paste a URL or code snippet, and the tool will parse your structured data, identify errors and warnings, and show you which rich result features your page is eligible for. For each schema type covered in this module — Product, Organization, BreadcrumbList, FAQ, and How-To — the Rich Results Test provides specific feedback about whether your implementation meets Google's requirements.

Using the tool effectively means more than just running a single test. Test each unique page template on your site, not just your homepage. A product page template may have different schema requirements than a category page or an FAQ page. When the tool reports errors, read the descriptions carefully — many errors have straightforward fixes like adding a missing required property or correcting a URL format. Warnings are less critical than errors but should still be addressed, as they may prevent your schema from being used in certain features or by certain services.

Beyond the Rich Results Test, the Schema.org validator offered by the W3C provides a more technically rigorous validation. While the Rich Results Test focuses on Google-specific eligibility, the Schema.org validator checks your markup against the full Schema.org specification. This is particularly useful for properties that Google does not yet use for rich results but that are valuable for AI systems and other search engines. For exporters serious about future-proofing their structured data, passing both validators is the gold standard.

Common Schema Errors and How to Fix Them

The most common schema error is the missing required field error. Each schema type has specific required properties — for example, Product schema requires name and offers (or aggregateOffer). When you omit a required field, the entire schema block may be invalid. The fix is straightforward: review the Schema.org documentation for your schema type, identify all required properties, and ensure each one is present with a valid value. Creating a checklist for each schema type you use can prevent these errors from recurring.

Another frequent issue is the incorrect data type error. Schema.org properties expect specific data types — text, URL, number, Boolean, or nested objects. A common mistake is providing a text value where a URL is expected (for example, using a relative path instead of a full URL for the url property) or providing a string where a number is expected (such as including a currency symbol in a price value). Use the Schema.org documentation to verify the expected type for each property, and validate your JSON-LD syntax carefully before deployment.

More subtle errors include mismatched or broken internal references. When you use the @id property to reference a product variant or an offer, the reference must point to a valid @id that exists within the same page's structured data. If you restructure your JSON-LD and accidentally change or remove a referenced ID, the connection breaks and the associated properties are silently dropped. Additionally, watch for stale or outdated information — prices, availability, and shipping details that were accurate when you first implemented the schema can become invalid over time. Regular audits catch these decay issues before they harm your search presence.

Ongoing Monitoring and Maintenance

Schema markup is not a set-it-and-forget-it activity. Search engines periodically update their structured data requirements, your product information changes, and new pages get added to your site. Without ongoing monitoring, schema errors accumulate silently. Google Search Console provides a dedicated Rich Results report that shows the total number of valid items, items with warnings, and items with errors across your entire site. Review this report weekly, especially after making changes to your site structure or product catalogue.

Set up a regular audit schedule that includes checking all pages with schema markup, verifying that prices and availability are current, and testing new page templates before they go live. For larger export websites with hundreds or thousands of product pages, consider using automated testing tools that can crawl your site and validate schema markup at scale. Several third-party SEO tools offer structured data auditing features that can save hours of manual checking and catch errors that might otherwise go unnoticed.

Finally, stay informed about changes in the structured data landscape. Google periodically announces new rich result types, updated guidelines, and deprecated features. Following the Google Search Central blog, the Schema.org blog, and reputable SEO industry publications will help you anticipate changes before they impact your search visibility. For exporters investing in international markets, staying current with structured data best practices is a competitive advantage that directly translates into better visibility with both traditional search engines and emerging AI-powered discovery tools.