Crawl and landing pages

What does Robots.txt blocked mean in Google Merchant Center?

Robots.txt blocked issues usually mean Google cannot crawl the product page or key resources because the site is blocking access.

What it means

If important pages or page assets are blocked, Google may not be able to verify the landing experience or product data reliably.

How FeedIQO helps monitor it

FeedIQO helps teams connect crawl-block issues to landing-page availability, product eligibility, and recurring deployment changes so the problem stays visible after the immediate fix.

Fix workflow

Use a structured check, fix, and follow-up process

These lists are meant to keep the page useful without pretending the same fix works for every store.

Common causes

  • Robots rules were written too broadly
  • Staging or protection rules were deployed to production paths
  • Asset or script paths needed for rendering are blocked

How to check it

  • Inspect the live robots.txt file and the exact blocked paths
  • Review recent deployment or SEO plugin changes
  • Check whether key rendering assets are blocked as well as the page URL

How to fix it

  • Update robots rules so product pages and needed assets are crawlable
  • Retest the affected URLs after the change is deployed
  • Monitor for recurring blocked-path patterns if automation manages robots rules
Related resources

Keep moving through the Merchant Center workflow

These links connect the error explanation to the feed, disapproval, and health-check workflows that usually matter next.

Related guides

Landing Page Not Available

See a closely related Merchant Center issue or glossary page.

Landing Page Not Available

Product Url Mismatch

See a closely related Merchant Center issue or glossary page.

Product Url Mismatch

Feed Issue

See a closely related Merchant Center issue or glossary page.

Feed Issue

Related tools

Free product feed audit

Request a manual audit when error patterns point back to feed quality.

Free product feed audit

Related features

Product feed audit

Review the feed workflow that often sits underneath Merchant Center errors.

Product feed audit

Product disapproval monitoring

Track product-level consequences when the error affects approvals.

Product disapproval monitoring

Merchant Center health checker

See how this error type fits into the broader account health picture.

Merchant Center health checker
FAQ

Questions teams usually ask about this issue

The answers stay general on purpose because Google can evaluate different stores and catalogs differently.

FAQ

Yes. Broad disallow rules, copied staging settings, and plugin changes are common reasons the issue appears unexpectedly.

Not always. It is also worth checking whether related assets or redirects are still affecting Google’s view of the page.