Google Merchant Center Redirect Issues: Fix Guide 2026
Redirect issues are one of the more subtle causes of product disapprovals in Google Merchant Center. They do not always show up as obvious errors. Sometimes a product appears approved in GMC but is quietly failing data verification because the page it redirects to does not match what is in the feed. This guide covers every redirect scenario that causes GMC problems and the correct fix for each.
Why Redirects Cause GMC Problems
When Google's Shopping crawler visits a product URL from your feed and receives a redirect response (301, 302, or meta refresh), it follows the chain to the final destination. The problem is that GMC verifies product data against the content of the final page, not the URL you submitted in the feed. If the final page content does not match the product attributes in your feed, that mismatch becomes a disapproval reason.
Beyond data mismatches, long redirect chains create timing problems. The crawler's total time budget for visiting a product URL includes every hop in the redirect chain. A 5-hop redirect chain that takes 2 seconds per hop uses 10 seconds before any product data is even loaded, which can push the total past GMC's timeout threshold.
Redirect Issues That Cause GMC Disapprovals
1. Redirect Chains (Multiple Hops)
Redirect chains build up over time, especially on stores that have changed platforms, restructured URLs, or installed and removed marketing apps that added their own redirect layers. Each URL change that uses a redirect rather than updating references adds another hop. After several migrations, a product URL might redirect through 4 or 5 intermediate URLs before reaching the actual page.
Audit your product URLs with a tool that shows the full redirect chain. Screaming Frog, Redirect Checker, or a curl command with verbose mode all show every hop in the chain. Update your feed to use the final destination URL directly. Then clean up the intermediate redirects on your server to prevent the chain from growing again.
2. HTTP to HTTPS Redirect Plus Other Redirects
If your feed uses HTTP URLs (without the S) and your site redirects HTTP to HTTPS, that redirect is the first hop. If your site also redirects from non-www to www (or vice versa), that is the second hop. Add one more redirect for a URL change and you are already at three hops before you reach the actual product page. Each of these redirects is technically correct, but the accumulation causes the same problems as intentional redirect chains.
The fix is simple: always use the exact canonical HTTPS URL in your feed, including the www or non-www prefix that your site uses as the canonical version. Eliminate the HTTP-to-HTTPS and www-to-non-www hops by starting the feed URL at the final form.
3. Redirects to Mismatched Pages
When a product URL in your feed redirects to a page with different content, such as a category page, a homepage, or a different product, GMC detects the mismatch between the feed data (specific product title, price, GTIN) and the destination page. This triggers a misrepresentation flag, which is one of the most common causes of both product disapprovals and account suspensions.
Never redirect a product URL to a generic page as a "soft 404." If a product no longer exists, remove it from the feed. If it still exists at a different URL, redirect to the correct specific product page and also update the feed URL to match. The destination page must contain the specific product data that the feed entry describes.
4. Temporary 302 Redirects Used as Permanent Fixes
A 302 redirect signals to Google that the move is temporary. If you changed a product URL permanently but set up a 302 redirect from the old URL to the new one, GMC's crawler treats the old URL as still canonical and expects the product data to be there permanently. Over time, Google's association of the product with the correct URL can drift, causing verification failures.
Use 301 redirects for all permanent URL changes, without exception. Audit your redirect configuration and replace any 302 redirects on product URLs with 301 redirects. Then update your feed to use the new final URL directly, at which point the redirect becomes irrelevant and you can remove it.
5. App-Injected Tracking Redirects
Some marketing apps, affiliate tracking systems, and UTM-tagging tools wrap product URLs in tracking redirects before they reach the destination. If your feed generation pulls product URLs from a tracking system rather than your store's native URL structure, the feed may contain tracker URLs that redirect through a third-party domain before reaching your product page.
GMC requires that product URLs lead directly to your domain. A feed URL that starts with a third-party tracking domain and redirects to your store is grounds for disapproval and can contribute to a misrepresentation review. Use your store's native product URLs in the feed. Apply tracking parameters as query strings appended to the direct URL, not as separate tracking redirect layers.
How to Audit Your Feed for Redirect Issues
Export your product feed to a spreadsheet or text file and extract all link attribute values. Run each URL through a redirect-checking tool or a script that follows redirects and records the final URL and the total hop count. Flag any URL with more than one hop and any URL where the final destination does not match the submitted URL exactly.
For Shopify stores, URL changes made through the Shopify admin automatically create 301 redirects. The redirect list can be found under Online Store > Navigation > URL Redirects. After a platform migration or major URL restructure, this list can contain hundreds of entries. Clean up old redirect chains here and update your feed to use current URLs.
If your account is under a GMC suspension, fixing redirect issues is part of the required cleanup. Reviewers check that feed URLs resolve directly to the correct product pages without redirect chains or mismatched destinations. The suspension checklist covers the full set of issues to clear before submitting an appeal.
Find Redirect Issues in Your Merchant Center Account
Our audit tool scans your feed URLs for redirect chains, 302 misuses, destination mismatches and tracking redirect layers that cause product disapprovals.
Run Free AuditRedirects and Misrepresentation Risk
The most serious consequence of redirect issues is not the crawl error itself but the misrepresentation flag it can trigger. When a product URL redirects to a page with different pricing, a different product, or a page that lacks the required structured data, Google's policy team sees a disconnect between what your feed advertises and what users actually land on.
This is the same pattern flagged in misrepresentation suspensions. Even if the redirect was unintentional, the data mismatch is treated as a policy issue, not a technical one. That means fixing the redirect alone is not sufficient. You may also need to address a pending misrepresentation review through the GMC appeal process.
The rule that prevents this entire class of problems: every link attribute in your feed should return a 200 response directly, load the specific product page it describes, and have pricing and availability that exactly matches what is in the feed. No redirects, no detours.
Frequently Asked Questions
Do redirects cause product disapprovals in Google Merchant Center?
Yes, in several scenarios. Long redirect chains can cause crawl errors if GMC's crawler times out or exceeds its redirect-follow limit. Redirects that lead to a page with different product content than what is in the feed cause misrepresentation flags. The safest approach is to use the final destination URL directly in the feed.
Does Google Merchant Center follow 301 redirects?
GMC's Shopping crawler does follow 301 redirects, but it flags the discrepancy between the URL in your feed and the final URL it lands on. Persistent 301 redirects indicate that your feed data is out of date. Google recommends always using the final canonical URL in your feed rather than relying on redirects.
What is the difference between a 301 and 302 redirect in GMC?
A 301 is a permanent redirect, signaling that the URL has moved permanently. A 302 is a temporary redirect. For GMC product URLs, both types are followed, but 302 redirects are treated as temporary. If your product URL consistently uses a 302, GMC may not update its internal association of the product with the destination URL, causing data verification problems.
How many redirects will Google Merchant Center follow before giving up?
Google's Shopping crawler typically follows up to 5 redirects in a chain before stopping. If your product URL requires more than 5 hops to reach the final page, the crawler records a crawl error and the product gets disapproved. Keep redirect chains to a single hop or update your feed to use the final URL directly.