Search Console statuses

These are the reasons Google shows after a crawl. None of them is fixed by asking an API to index the URL. Fix the page, the robots rule, or the response the page returns.

• Crawled – currently not indexed

  Google fetched the page and chose not to index it. The fix is the page, not a resubmit button.

• Discovered – currently not indexed

  Google knows the URL and has not crawled it yet. Discovery is not a bug to force.

• Excluded by noindex tag

  A meta robots tag or X-Robots-Tag told Google to keep the URL out of the index.

• Page with redirect

  Google is indexing the destination, if anything. The URL you submitted is not the one that stays.

• Duplicate without user-selected canonical

  Google found copies and you did not say which URL is the one to keep.

• Alternate page with proper canonical

  The canonical points at another URL, and Google is respecting that.

• Duplicate, Google chose different canonical

  You declared a canonical and Google picked another URL anyway.

• Soft 404

  The URL says 200, and the page looks empty or like an error.

• Blocked by robots.txt

  Googlebot is not allowed to crawl the path. An index request cannot override that.

• Blocked due to access forbidden (403)

  The server refused Googlebot. robots.txt saying Allow does not undo a 403.

• Server error (5xx)

  Google got an error instead of a page. Fix the response, then let the next crawl happen.

• Not found (404)

  The URL is gone. Restore it or stop linking to it.

• Lovable, v0, and Bolt pages that Google never sees

  A polished client render can still ship an empty document to Googlebot.

• Cloudflare blocking AI crawlers

  A managed robots.txt or a bot rule can stop AI crawlers even when Googlebot is allowed.