WooCommerce SEO Health Check

2. How the Health Score Is Calculated

The score starts at a 30-point baseline and adds points for each detected element: Product schema (+25, the single largest factor, since it's the prerequisite for any rich result), price schema (+15), availability schema (+10), an Open Graph image (+10), a canonical tag (+10), and a title tag length in the 30-60 character range that Google typically displays without truncation (+5) — capped at 100. The weighting reflects real impact: Product schema alone is worth more than every other factor combined because without it, none of the richer search features (price, stock, rating display) are possible regardless of how well-optimized everything else is.

3. How to Use This Scanner

1. Paste the full URL of a live WooCommerce product page (not the catalog or category page — this checks the individual product template).
2. Run the scan and review which of the five checks passed or failed.
3. For any "MISSING" result, check which SEO plugin your theme/store uses (Yoast, RankMath, SEOPress, or WooCommerce's own basic output) and confirm Product schema generation is actually enabled for the product post type.
4. Re-scan after making a fix to confirm the change took effect — plugin caching can sometimes serve stale HTML to the first request after a settings change.

4. Common WooCommerce Product SEO Mistakes

• Relying on a theme's built-in, incomplete schema. Many page-builder themes output partial Product schema (name and image, but no price or availability) that passes a casual glance but fails to qualify for rich results.
• Duplicate canonical issues on variable products. Product variation URLs (with query-string attribute selections) should canonicalize back to the parent product page — a missing or self-referencing-incorrectly canonical here creates duplicate-content signals across what search engines see as many near-identical URLs.
• Missing og:image on out-of-stock or seasonal products. Products with dynamically swapped feature images (seasonal variants, sold-out placeholders) sometimes fall back to a generic image or none at all in the Open Graph tag specifically, even though the on-page image looks correct.
• Title tags that don't fit Google's display width. Titles well over 60 characters (common when a plugin auto-appends "| Store Name | Category" to every product title) get truncated in search results, often cutting off the actual product name.

5. Who Should Use This Tool

Store owners auditing their own catalog for missed rich-result opportunities, agencies performing a WooCommerce SEO audit for a client, and developers verifying that a new theme or SEO plugin configuration is actually outputting schema correctly before rolling it out store-wide.

6. Limitations

This scanner checks the raw server-rendered HTML only — it does not execute JavaScript, so schema or meta tags injected client-side after page load won't be detected even if a real browser (or Google's renderer) would see them. Detection uses pattern matching for key schema properties rather than a full JSON-LD parse-and-validate pass, so it can miss subtle structural errors that a dedicated validator like Google's Rich Results Test would catch. A passing score here means the basic elements are present and detectable — it is not a guarantee of rich-result eligibility, which Google ultimately decides algorithmically.