How to investigate a product page unavailable error
Check the exact submitted URL from an unauthenticated public session. A syntactically valid feed link does not prove that Google can retrieve a usable product page.
Reviewed October 4, 2026 · Independent guidance · Manual/live investigation; not a performed scan check
What does this issue mean?
A product page may return an error, redirect to an unrelated destination, require login or display a security challenge. It can also load essential product information only through unreliable client-side behavior. Merchant Center evaluation considers what its crawlers can access, which may differ from the experience of a store administrator.
Why this happens
Typical causes include deleted products, password-protected stores, region blocking, stale URL handles, redirect loops and robots rules. A page can return HTTP 200 while showing not-found content or a bot challenge. Record the final URL and response behavior rather than assuming a successful browser redirect resolved the product-page problem.
How to diagnose and fix it
- Copy the exact feed link and test it without admin cookies or membership access.
- Inspect redirects, status codes, robots rules and any geographic or security restrictions.
- Confirm the final page visibly represents a purchasable offer with the submitted variant, price and availability.
- Correct the source URL or hosting configuration, refresh the feed and monitor subsequent Merchant Center processing.
Before and after example
The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.
Before
Feed link → deleted product → 404After review
Feed link → current public product offer → 200Feed Doctor does not perform live product-page requests in this MVP. Static URL findings are separate from availability diagnostics, and a crawler-specific issue may require server logs or Merchant Center evidence.
Shopify fix
Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies link. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.
Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.
WooCommerce fix
Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.
Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.
Verify the repair before submitting
Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.
Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.
Scan your feed for this issue
Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Live page checks described above are not performed by this scanner.
Check My FeedFrequently asked questions
Does this finding always mean my product is disapproved?
Feed Doctor does not perform live product-page requests in this MVP. Static URL findings are separate from availability diagnostics, and a crawler-specific issue may require server logs or Merchant Center evidence.
Can Feed Doctor fix link automatically?
This MVP does not run the live or account-level checks needed to establish this issue. It supplies static feed diagnostics and this manual investigation workflow.
Should I fix the exported file or my store?
Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.
Do I need to connect Google to scan a feed?
No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.
Related feed issues
- How to fix malformed product URLs in Google Shopping
- How to fix missing product links in Merchant Center
- How to investigate price mismatch in Merchant Center
Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.