The owner can open the page
The reported URL loads while you are signed in or browsing from the office. A fresh session, another device or a different network hits an error, a challenge or a redirect that hides the product.
Google Merchant Center
Find out why Google can’t reach a product page that opens for you
Merchant Center flags a product page as unavailable, yet it opens for you. A saved session or different request path can hide the failure. We check the exact submitted URL and access rules, then test changes before you review products.
Discuss this problemHow We Help
We start with the reported issue and the affected products. After storefront changes, your feed may still point to an older product URL. We compare those paths and look through the server and security logs available. The work focuses on the specific access failure. We coordinate with the people who run your storefront and hosting, because either system may control the response Google gets.
Signs This Is the Problem
Errors affect selected products
Some submitted links point to old paths, unavailable variants or pages with different publishing settings. Similar products work, so a quick look at the storefront homepage tells you little about the affected URLs.
Issues return after a correction
An edited product looks fine in a manual check, then gets another issue. Intermittent server failures, changing access rules or a rebuilt feed may bring back the same condition after that first test.
What We Investigate
Follow the submitted URL
We inspect the exact product link sent to Merchant Center, including parameters and redirects. We compare where it ends up with the intended product and any separate mobile link your feed actually uses.
Inspect access and response evidence
We review relevant server errors, crawler instructions and security rules with your hosting owner. Request tests help identify status codes, redirect loops or challenge pages. Logs give stronger evidence of what happened to actual crawler requests.
Check device and session differences
We compare typical desktop and mobile visits in fresh sessions. We look into product publishing, regional behavior, cookies and page rendering where they explain why you see a working page and another visitor doesn't.
What We Repair
Correct the source of bad links
We repair feed link generation or storefront redirects when the submitted URL is wrong. We make the fix in the source that produces the links, so the next product update doesn't bring back an old address.
Repair the verified access failure
We address the confirmed hosting, storefront or access-rule problem with its owner. Changes stay limited to what the evidence shows, and we review them against your site's existing security requirements before they go live.
Recheck and document the outcome
We test the affected URLs after the fix and review the current Merchant Center issue status. Google controls later checks and eligibility decisions. We document open issues and a process for looking into new examples.
How We Verify the Fix
- Each sampled submitted URL reaches the intended published product page through an understood redirect path.
- Fresh desktop and mobile sessions can reach typical affected pages without hitting the reported failure.
- Relevant server or security logs show the reviewed requests getting the intended response after the change.
- A rebuilt feed keeps the corrected links, and Merchant Center issue status is recorded separately from site test results.
Questions About This Work
Does a working page mean Google will approve the product?
Not by itself. Page access is one part of product eligibility. Other feed or policy issues may remain after the landing page works. We confirm the access fix and review the reported status, while Google's checks and decisions determine whether the product becomes eligible to appear.
Can you fix this with Merchant Center access alone?
Maybe not. Merchant Center access helps us find affected items and submitted links. Fixing the cause may also take access to your storefront, feed integration, hosting or security settings. We work out who owns what early and coordinate changes with the person responsible for each system.
Should we remove our site's security protection?
Not as a starting point. We inspect the evidence before changing access rules. A product URL problem may have nothing to do with security settings. If a rule blocks legitimate access, we review a limited fix with your site owner and check how it behaves alongside your existing protection.
Useful Platform Documentation
Tell Us What Is Happening
Tell us your storefront and hosting platforms. Share one public product URL and a redacted Merchant Center issue screenshot, so we can compare the reported failure with the submitted landing page.
Explore Google Merchant Center More problems in Google Merchant Center
Ready to Get Started?
Tell us about your project and we'll get back to you within 24 hours.