How to Fix Landing Page Disapprovals in Google Merchant Center

Landing page disapprovals vs. misrepresentation

Landing page technical disapprovals are about whether Google can access your page at all. Misrepresentation is about what your page says (deceptive claims, missing policies). Technical disapprovals are fixable with infrastructure changes — no appeal needed.

The five types of technical landing page disapprovals

1. Hard 404 — page not found

The URL returns HTTP 404. Most common technical disapproval.

How it happens: Deleted product not removed from feed; URL structure changed without 301 redirects; out-of-stock products generate different URLs.

Fix: Restore the page, add a 301 redirect, or remove from feed. Setting availability: out_of_stock doesn’t help — Google still needs to crawl the URL.

Page is behind a login wall, membership gate, or paywall.

Fix: Shopping feeds should only include publicly accessible product pages. Create a public version with public pricing, or exclude gated products.

3. Robots.txt blocking

Your robots.txt disallows Googlebot from crawling product pages.

How to check: Visit yourdomain.com/robots.txt. Test specific URLs in Search Console’s robots.txt tester.

Common problematic rules:

User-agent: *
Disallow: /products/   ← blocks all product pages

User-agent: Googlebot
Disallow: /            ← staging config left in production

4. Redirect chains (2+ hops)

Feed URL redirects to another URL, which redirects again. Google tolerates a single 301; chains of 2+ get flagged.

Fix: Update intermediate redirects to point directly to final destination. Update feed with final canonical URL.

How to check: Tools like httpstatus.io show full redirect chains.

5. Soft 404s

Page returns HTTP 200 but content signals the product doesn’t exist (empty page, “Product not found” message, generic category page).

Fix: Dead URLs should return 301 (to related product) or proper 404/410. Don’t let dead URLs return 200 with empty content.

Diagnosing at scale

Export all link values from your feed.
Run async HEAD requests. Look for: 404/410, slow 200 (possible soft 404), redirect chains.
Fix 404s first (binary problems).
Consolidate redirect chains.
Investigate slow pages (server rendering, queries, CDN).

After fixing

In Merchant Center: Products → Feeds → “Fetch now” to force re-fetch.
Submit updated sitemap in Search Console.
Allow 24–48 hours for reprocessing.

Prevention

Before site migrations: audit URLs, set up 301 redirects, update feed before/after migration
After product deletion: remove from feed first, then delete page
Check robots.txt after any site config change
Weekly sample check of 50–100 product URLs