Download the affected-products CSV
In Merchant Center, open Products → Needs attention, filter for Product page unavailable, and download the affected-product list. Keep Google’s product IDs unchanged.
Product page unavailable
Trace unavailable product pages to the submitted feed rows.
Cross-reference Google’s affected-products CSV with the source feed, inspect the exact landing-page URLs, and separate bad feed values from real crawl failures.
Open the feed that supplied those offers
Select the CSV or TSV that generated the affected products. FeedPatch audits the file locally and keeps original source-row numbers; it does not upload your catalog.
Match each Google ID to its source row
Add the affected-products CSV to the ID-list slot. Review matched and unmatched IDs, then inspect the link and mobile_link values on the exact matched rows.
Test the URL that was actually submitted
Check the complete submitted URL on desktop and mobile. Look for a wrong product or variant path, missing http or https, invalid characters, authentication, or a redirect that lands somewhere unexpected.
Separate feed errors from crawl failures
A correct-looking URL can still fail with 404 or 5xx responses, unreachable robots.txt, DNS problems, firewalls, geo-restrictions, repeated redirects, or timeouts. Use your server and hosting evidence to diagnose those failures.
Fix the source, re-upload, then verify
Correct the original product data or site configuration, re-upload once through your normal method, and monitor Needs attention. After the issue is fixed, Merchant Center can run an automatic review or you can request a website check.
Product boundary
Locate the submitted row here. Diagnose the crawl at its real source.
FeedPatch can match affected product IDs to source rows and expose their submitted URL fields. It cannot simulate Googlebot or AdsBot, diagnose your server or DNS, modify your store, or perform Merchant Center’s review.
Run the free feed auditOptional repair export
Locate affected URLs free. Upgrade for the corrected full-feed download.
FeedPatch Pro applies safe, reviewable formatting normalizations after you identify the correct source rows. It does not crawl pages or alter your store.
$79USD
per year
per year
- Free affected-ID and source-row matching
- Full-feed safe normalization export
- Source feeds up to 100 MB
- 14-day refund policy
Frequently asked
Before changing a product link.
Why does Merchant Center say Product page unavailable when the page opens for me?
Google may have received a crawl error from a different device, location, request path, or moment than your browser. Check the exact submitted URL and server-side crawl evidence instead of assuming one successful visit proves universal access.
What does the free FeedPatch matcher return?
When the affected-products export and source feed share product IDs, it returns exact source-row numbers, matched and unmatched counts, and a downloadable match map for review.
Can FeedPatch tell whether Googlebot can crawl my store?
No. FeedPatch can inspect feed fields and map affected IDs to source rows. It cannot simulate Google’s crawlers, inspect private server logs, resolve DNS, or change your store configuration.
Should I change every product URL at once?
Start with the affected rows and verify the failure type. Change URLs only when the submitted value is wrong; site-wide crawl failures may need a server, robots, DNS, firewall, or hosting fix instead.
Official references
Use Merchant Center and your server evidence as the final authority.
Google: Fix Product page unavailableAffected-products download, URL cross-reference, correction, and review workflow.Google: Product crawl issuesCommon robots, response, DNS, firewall, redirect, and timeout failure modes.Google: Link [link] specificationLanding-page URL format, crawlability, domain, and redirect requirements.
Published by the FeedPatch team, the developer of the tool described here. Checked against Google Merchant Center Help on September 5, 2026. FeedPatch is independent and is not affiliated with Google.