Google Merchant Center 404 Product Errors: Fix Guide 2026
404 product errors in Google Merchant Center are among the most common issues merchants ignore until they become a serious problem. A handful of 404 errors causes a handful of disapprovals. But hundreds of 404 errors, left unmanaged across a large catalog, signals feed neglect and can accelerate a formal account review. Here is how to find them, fix them, and prevent them.
Why 404 Errors Happen in GMC
A 404 error means the URL in your product feed points to a page that does not exist. Google's Shopping crawler visits each product landing page URL to verify the product data matches the feed. When it arrives at a URL and gets a 404 Not Found response, it records the error and eventually disapproves that product.
The most common sources of 404 errors: products deleted from your store that were not removed from the feed, URL changes (handle edits, slug changes, platform migrations), seasonal products that were taken offline without feed cleanup, and feed imports from third-party suppliers that include product data for items you no longer carry.
How to Find All 404 Products in Your GMC Account
In Merchant Center, navigate to Products > Diagnostics. Filter the issues list for "404" or "page not found." Export the full results to a spreadsheet. The export includes the product ID, title, and the URL that returned the 404. This gives you a complete working list for remediation.
For large catalogs, also run a bulk URL check using a tool like Screaming Frog or a simple Python script that reads the export spreadsheet and sends HEAD requests to each URL. This lets you batch-verify 404 status across thousands of URLs in minutes rather than checking them individually in the GMC interface.
Fixing 404 Errors: The Right Approach for Each Case
1. Products Deleted from Your Store
If the product genuinely no longer exists and you have no plans to bring it back, the fix is simple: remove the product from your feed. In your next feed upload, omit the product entirely. GMC will process the absence and delete the product from your product list. If you submit a full feed (all products), removing the item from the feed file is sufficient. If you use incremental feeds, submit a deletion entry for that product ID.
Do not redirect the 404 URL to a category page as a workaround. GMC's crawler will follow the redirect, arrive at the category page, and flag a data mismatch because the page content does not match the product data in the feed. The mismatch creates a new disapproval reason on top of the 404.
2. Products with Changed URLs
If you renamed a product handle, changed your URL structure, or migrated platforms, your old product URLs return 404 but the products still exist. The fix is to update the link attribute in your feed to match the new URL. Do not rely on 301 redirects from old URLs to new URLs as a permanent solution. Update the feed to contain the correct, final URL directly.
After updating the feed, trigger a manual fetch in Merchant Center to process the new URLs immediately rather than waiting for the next scheduled fetch. The crawler will visit the new URLs, verify they return 200 and contain the correct product data, and restore the products to approved status.
3. Seasonal or Out-of-Stock Products Taken Offline
Some merchants take product pages offline entirely when a product is out of stock, rather than keeping the page live with an "out of stock" status. This creates 404 errors in GMC. The correct approach is to keep the page live and update the availability attribute in your feed to "out of stock." This tells Google the product exists but is not available, which is a valid state and does not cause disapprovals.
Taking pages offline creates a much worse outcome than marking them out of stock. Once a product page returns 404, the product gets disapproved and must go through the full re-approval cycle when it comes back in stock. Keeping the page live with updated availability is far less disruptive to your active product count.
4. Supplier Feed Products You No Longer Carry
If your feed comes from a supplier or third-party data source, it may include products your store does not actually stock. Those products will not have pages on your site and will return 404. You need to filter the supplier feed before it reaches GMC, removing any products that are not on your store. Set up a feed rule in Merchant Center or a pre-processing script that excludes products without a valid, live URL on your domain.
5. Platform Migration URL Drift
Migrating from one e-commerce platform to another (Shopify to WooCommerce, Magento to Shopify) almost always changes URL structures. If you built a new store and redirected traffic but did not update your GMC feed, every product URL may now be returning 404. After a platform migration, regenerate your entire feed from the new platform and upload it as a replacement, not an addition to the old feed.
Scan Your Entire Product Feed for 404 Errors
Our audit tool identifies every product with a 404 URL, groups them by error type, and gives you a step-by-step remediation plan.
Run Free AuditPreventing 404 Errors Long-Term
The best prevention is syncing your feed deletion process with your product deletion process. When you delete a product from your store, remove it from the feed in the same workflow. Most e-commerce platforms that generate feeds automatically handle this correctly, but custom integrations and supplier-fed catalogs often do not.
Run a weekly 404 check against your feed URLs using an automated script. This catches errors before they accumulate and before GMC's crawler processes them into disapprovals. A cron job that exports your current feed, checks each URL for a 200 response, and emails you a list of non-200 URLs takes less than a day to set up and prevents hours of remediation work later.
If your account already has a suspension on top of these 404 issues, clean the feed completely before appealing. A feed with active 404 errors during an appeal review signals that the underlying issues have not been resolved. Review the full GMC suspension checklist and the appeal process guide to make sure your account is fully clean before submitting.
For stores with frequent product turnover, also review how your product policy compliance holds up when URLs change, since some policy violations are triggered by page content mismatches that arise during URL transitions.
Frequently Asked Questions
Why do my product URLs return 404 in Google Merchant Center?
404 errors in GMC usually happen when a product URL in your feed points to a page that no longer exists. Common causes include deleted products that were not removed from the feed, a URL restructure that changed product slugs without updating the feed, or a platform migration where the URL format changed.
How long does Google Merchant Center wait before disapproving a 404 product?
Google does not disapprove a product the first time it encounters a 404. The crawler retries over several days before marking the product as disapproved. Based on common patterns, products tend to get disapproved after 3 to 7 days of consistent 404 responses.
Should I use a 301 redirect for deleted products or remove them from the feed?
Remove deleted products from the feed. A 301 redirect for a product that no longer exists typically sends the user to a category page or homepage, which does not match the product data in your feed. GMC sees the mismatch as a potential misrepresentation issue. Remove the product from your next feed submission instead.
What happens if I have hundreds of 404 products in my GMC account?
A large number of 404 products signals poor feed hygiene to Google. If your total disapproved product rate exceeds a significant percentage of your catalog, it can contribute to a broader account review. The immediate fix is to remove all 404 products from your feed in bulk, then fix the URL issues and re-add the products correctly.