sciencePublic example report

WooCommerce product SEO report example

A sample ShopGox report for a WooCommerce product page with SEO plugin metadata, schema plugin overlap, review proof, and cache-rendered drift checks.

Scan your product pagearrow_forward Open WooCommerce scanner

67Audit score

Good baseline with schema conflicts

If the priority fixes were completed, this sample report would project a score range of 81-87.

Sample Context

What this example represents

This page demonstrates report output using desensitized fixture data. It is public and indexable, while private user reports stay under noindex `/report/*` URLs.

Example page

Fictional variable skincare product

Platform

WooCommerce with SEO and review plugins

Scan mode

Rendered page, plugin markers, and structured-data inventory

Data boundary

Fictitious public sample, not a real merchant scan

Score Summary

The report starts with explainable score dimensions

The score is only useful when it points to the evidence and repair path behind the number.

Search visibility

Title, meta description, and canonical signals are generally healthy.

Machine-readable facts

Schema exists but plugin overlap creates ambiguous product facts.

AI crawler access

Crawl access appears available for the public product URL.

Platform confidence

WooCommerce and WordPress runtime markers are visible.

Product Signal Matrix

Visible facts versus machine-readable facts

The sample separates what shoppers can see from what crawlers and AI shopping systems can reliably parse.

Visible

7/7

Structured

5/7

Product factVisibleMachine-readableEvidence source

Title

Botanical Repair Serum

check_circleDetectedcheck_circleStructured

SEO plugin + rendered DOM

Description

Lightweight daily repair serum

check_circleDetectedcheck_circleStructured

meta description

Price

$42.00

check_circleDetectedcheck_circleStructured

Offer schema

Brand

Lumen Demo

check_circleDetectedradio_button_uncheckedRendered only

visible product detail

Image

Product gallery image

check_circleDetectedcheck_circleStructured

Product JSON-LD

SKU

LUM-SERUM-DEMO

check_circleDetectedradio_button_uncheckedRendered only

WooCommerce product meta

Structured data checks

This section audits product, offer, review, breadcrumb, and related structured signals without publishing product markup for the sample itself.

Pass

Warn

Fail

Product schema

Product structured data exists, but duplicate sources make brand and SKU confidence lower.

warningWarning

Product nodes

Multiple detected

JSON-LD inventory

Brand

Visible only

Rendered DOM

Offer schema

Price and currency are represented in structured Offer data.

check_circlePass

Structured price

$42.00 USD

Product/Offer schema

Review schema

Visible review proof exists, but plugin output should be checked for alignment.

warningWarning

Review schema

Partial

Review plugin output

Breadcrumb schema

BreadcrumbList and visible product category path are aligned.

check_circlePass

BreadcrumbList

Present

Rendered JSON-LD

Platform Diagnostics

WooCommerce specific findings

The platform section explains what the scanner would inspect for the storefront technology involved.

Pass

Warn

Fail

SEO plugin metadata

SEO plugin title, description, and canonical output are present.

check_circlePass

SEO plugin signals

Detected

Rendered HTML

Schema plugin conflict

Multiple schema emitters may create conflicting product facts.

warningWarning

Product nodes

Multiple detected

JSON-LD inventory

Variable product schema

Variable product SKU and brand values are visible but not fully structured.

warningWarning

Visible SKU

Detected

WooCommerce DOM

Cache-rendered metadata drift

No major drift is shown in the sample, but cached metadata remains a release QA point.

infoInfo

Rendered attributes

Stable

rendering comparison

Priority Fixes

What the sample report would fix first

Each fix ties evidence to impact, recommendation, confidence, and expected score movement.

3 prioritized fixes

Fix 1highschema conflict

Choose one authoritative product schema source

Impact

+7-10

Confidence

86%

Evidence

Multiple product schema emitters can be detected in the sample inventory.

Impact

Conflicting product facts reduce confidence for search engines and AI shopping agents.

Recommendation

Keep one plugin or theme layer responsible for Product schema and disable overlapping product markup in secondary plugins.

Implementation target

WooCommerce SEO/schema plugin settings

Fix 2mediumproduct facts

Add brand and SKU to the structured product layer

Impact

+5-8

Confidence

84%

Evidence

Brand and SKU are visible but not consistently machine-readable.

Impact

AI comparisons may miss brand attribution and variant identity.

Recommendation

Map WooCommerce product attributes or custom fields to the product schema source.

Implementation target

WooCommerce product attributes and schema plugin field mapping

Fix 3mediumtrust

Verify review schema matches visible review content

Impact

+3-6

Confidence

76%

Evidence

Review proof is visible, but structured review alignment is partial.

Impact

The page may show trust signals to shoppers that crawlers cannot safely interpret.

Recommendation

Use a review plugin configuration that emits review data only when it matches visible review content.

Implementation target

WooCommerce review plugin schema settings

Run The Real Scan

Replace the fixture data with your product URL

A real ShopGox scan will inspect your rendered page, structured data, platform signals, crawler access, and priority fixes for the submitted URL.

Start a scanarrow_forward

FAQ

About this public example report

These questions are visible on the page, so the page can safely emit matching FAQPage structured data.

Why does WooCommerce often show schema conflicts?

Themes, SEO plugins, schema plugins, and review plugins can all emit product markup unless one source is made authoritative.

Does this page mark up a real WooCommerce product?

No. It is a public report sample and does not emit Product, Review, or AggregateRating JSON-LD for the fictitious product.

What should I scan on WooCommerce?

Start with a high-value product URL, especially if it uses variable products, review plugins, or multiple SEO/schema plugins.

More Examples

Compare another public report

Use these samples to see how the report changes by platform, crawler behavior, and schema risk.

Scan your pagearrow_forward

Shopify

Shopify Product Schema Audit Example Report

See a public ShopGox example report for a Shopify product page with visible product facts, schema gaps, platform diagnostics, and priority fixes.

Score 64arrow_forward

Magento

Magento AI Crawler Audit Example Report

Review a public ShopGox example report for a Magento product page covering AI crawler access, configurable product signals, localized schema, and priority fixes.

Score 58arrow_forward

Custom/headless

Headless Commerce Rendered HTML Drift Example Report

Explore a public ShopGox example report for a headless commerce product page where rendered HTML, source HTML, API data, and crawler-readable facts drift.

Score 52arrow_forward