"Indexing request rejected": why and how to fix it

What it means

Before Google queues a page, it runs a quick check for indexing errors. Google's help says you cannot request indexing if the live test finds the page can't be indexed.

So the rejection is about the page as it is now. It is not about the daily limit. That message is Quota exceeded.

Where it shows: In the message that opens after you click Request indexing.

Common causes

1. The page has a noindex rule.
2. robots.txt blocks the page.
3. The page does not load for Google: a 404, a 5xx error, a 403, a redirect error, or a soft 404.
4. The page needs a login.
5. A problem with the whole site, such as a server Google can't reach, stops the test.
6. The test hit a temporary error, such as Internal error. Google's help says to wait a bit and try again.

How to check which cause applies

1. Click Test live URL. The verdict and the Availability section show the problem.
2. Read Crawl allowed?, Page fetch, and Indexing allowed? in the live result.

How to fix it

1. Fix the problem the live test names.
2. Click Test live URL until it says URL is available to Google.
3. Click Request indexing again.

With CrawlCoach

CrawlCoach reads Google's reason for each page it checks and groups the missing pages by it. So you can fix blocks such as noindex and robots.txt on many pages before you ask Google for anything. Google makes the final call on what it indexes.

Related Page indexing reasons

• Excluded by 'noindex' tag: A noindex rule on the page tells Google to leave it out.
• Blocked by robots.txt: Your robots.txt file stops Google from visiting the page.
• Soft 404: The page loads, but Google thinks it looks like an error or an empty page.

Questions

Sources

Checked on October 8, 2026. Google can change its tools and wording after that date.

• Search Console Help: URL Inspection tool
• Search Console Help: Inspect and troubleshoot a single page