SCAN TROUBLESHOOTING

Find out why an automated product scan cannot read your store.

Three public products · No account or card

Check HTTP blocks, inaccessible sitemaps and JavaScript-only product data before changing the catalog.

Measured evidenceCatalog-level diagnosticsImplementation-ready findings

A failed scan needs an access diagnosis

An automated scan must retrieve the storefront before it can inspect product information. A request can fail even when the store works in your browser. Check the response before deciding that the catalog has no products.

The useful evidence is the requested URL, time, response status and whether the returned page is a storefront or a security challenge. Keep security identifiers and customer details private.

Work through the response

Response First check Next action
HTTP 401 or 403 Authentication or a firewall challenge Ask the store owner to review scanner access
HTTP 404 The exact submitted URL Confirm a current public storefront or product URL
Timeout or 5xx Store and network availability Retry after the underlying fault is resolved
HTTP 200 with no product data Returned HTML and product links Check whether data appears only after JavaScript runs

A browser succeeding while a server receives a challenge is evidence of different access treatment. Repeatedly changing the scan URL does not repair that restriction.

Check discovery separately from page quality

A sitemap can help a scanner find products, but a reachable sitemap is only the first step. A product URL still needs to resolve to the intended product page. If the sitemap lists only categories, inspect links on a public category page and check a small product sample manually.

If a store loads catalog content after JavaScript runs, compare its initial response with the rendered browser page. A response-only checker cannot measure fields it never receives.

Use a manual fallback

Choose three live physical products from one category. Record the visible name, SKU, material, available options, price conditions and delivery information. Mark structured data and feed settings as unverified until you can inspect those sources directly. A manual review can still produce a useful implementation brief while access is being resolved.

Try the Product Schema Checker for one accessible product URL, or contact Lumen with the scan error and storefront URL. You can also start a free scan once public access is available.