Google not indexing your page? What to fix and when to request indexing

When you open the Search Console page indexing report, the reasons a page wasn't indexed appear as several rows in a single table. Each row shows a page count and a status with a long, often similar name, such as "Crawled - currently not indexed." The answer you get when you search for Google not indexing is usually to submit an indexing request, but this table also contains rows where a request changes nothing.

Some rows only need a single request to move up the crawl order, while others stay the same no matter how many requests you submit until you fix the page or the server. This article splits the reasons shown in the report into two groups, and explains what to fix in each group and when to request indexing.

1. Sort indexing issues into two columns

Separate issues where a request moves the URL up the crawl queue from those that require a page or server fix. PION starts an audit with these two columns, then examines each issue. The page indexing report help puts "The page isn't indexed, but not necessarily because of an error" at the head of the reason list. The state loosely lumped together as Google not indexed is scattered across several rows of this table, and some of them fall outside the scope of action.

Download the URL list for each issue. Submit an indexing request once each only for the URLs you placed in the left column, and move the right column into a fix list organized by reason. Sort the URLs by publication date to see whether pages published on the same day share an issue. If they are clustered, start by checking the template, redirect, and sitemap settings you deployed that day.

2. What to do when a page is discovered but not crawled

"Discovered - currently not indexed" is a state where there is nothing to fix on the page; the crawl order is simply backed up. The help explains this reason as "Typically, Google wanted to crawl the URL but this was expected to overload the site, so Google rescheduled the crawl," and adds "That is why the last crawl date is empty in the report."

The similarly named "Crawled - currently not indexed" belongs to the right column. For this reason the help says "It might or might not be indexed in the future," and explicitly states there is no need to resubmit this URL for crawling. Google has decided not to add the page it already fetched to the index, so resubmitting a request leaves the row unchanged.

A URL not in the report is a case where Google doesn't yet know the address. For adding a property and submitting a sitemap (often called Google indexing registration), along with the actions to take for each status, see Google search registration, confirming site registration, and what to check if it still isn't showing after registering.

3. What to fix for each indexing issue

The right column covers directives that prevent indexing, access restrictions, and response codes. Each needs a different fix.

If the first two rows of the table above overlap on the same URL, resolve robots.txt first. Block search indexing with noindex (updated December 31, 2025) advises "If the page is blocked by a robots.txt file or the crawler can't access the page, the crawler will never see the noindex rule, and the page can still appear in search results."

401 and 403 are separated by the HTTP standard. RFC 9110 defines 401 as "it lacks valid authentication credentials for the target resource" and 403 as "the server understood the request but refuses to fulfill it." Google's help also classifies 403 as a server configuration mistake, stating "Googlebot does not provide authentication credentials, so your server is incorrectly returning this error."

4. Distinguishing the three canonical URL reasons

Three statuses exclude pages because of canonical URLs, but only one requires action. PION distinguishes these statuses at the start of a site audit.

Canonical declarations differ in signal strength by method. How to specify a canonical URL with rel=canonical and other methods (updated July 15, 2026) distinguishes a redirect as "a strong signal that the redirect target should become the canonical URL" and inclusion in a sitemap as "a weak signal that URLs included in a sitemap should be canonical."

Some try to clean up duplicates with the Google URL removal tool, but the same document says "Do not use the URL removal tool for canonicalization" and gives the reason "Using this tool hides all versions of the URL from Google Search."

5. When to request indexing and how often

Submit one indexing request for each URL in the left column. For a URL in the right column, fix the issue first, then submit one request. Ask Google to recrawl your URLs (updated December 31, 2025) limits when to request to "when you have recently added or changed a page on your site," and states "There is a quota for submitting individual URLs, and requesting a recrawl of the same URL multiple times will not get it crawled any faster."

Google index recovery follows the same order. Fix the issue, submit one request, and wait. The reason you submit a request on a URL where you've cleared the noindex directive is the revisit cycle. The noindex document advises "Depending on the page's importance on the internet, it can take Googlebot several months to revisit a page."

After fixing the right column, click Validate Fix on the reason screen. The help advises "Validation typically takes up to two weeks, but it can take longer, so please be patient." If the row remains unchanged after two weeks, check whether the reason name has changed and reassign the group.

The path where a fully indexed page doesn't appear in ChatGPT or Gemini answers is covered in 5 reasons your brand isn't shown in ChatGPT and Gemini.

PION has laid out, in its GEO agency service overview, the scope of its work to get those repaired pages cited in AI answers. To narrow down how many reasons on your site will fall into the right column, start with the indexing and bot-access items in the 5-minute GEO readiness assessment.

Frequently asked questions

What should I do when it says Google isn't indexing?

First split the reasons shown in the report into two groups. For reasons where the crawl order is backed up, like "Discovered - currently not indexed," submit an indexing request once and wait; for reasons where the page or server is the cause (noindex, robots.txt blocking, 401, 403, 404, 5xx, or duplicates), fix it before requesting indexing. When PION audits a site, we split the URL lists by reason into these two columns and then pick out only the ones that need action.

How many times can I submit a Google index request?

Once is enough. Google's documentation advises there is a quota for submitting individual URLs and that requesting a recrawl of the same URL multiple times won't get it crawled any faster. Submit the request right after publishing or editing a page; crawling takes anywhere from a few days to a few weeks.

Can I use the Google URL removal tool to clean up duplicate pages?

For canonicalization, use a permanent redirect or a canonical URL declaration instead of the removal tool. Google's canonicalization document says you should not use the URL removal tool for canonicalization, and gives the reason that this tool hides all versions of the URL from Search. Use the removal tool only for pages you urgently need to take down from search.

Google has indexed fewer pages than I published. Should I request indexing for all of them?

Only the URLs in the left column need a request. The report help advises you should not expect every URL on the site to be indexed, and addresses classified as duplicate or alternate are normally not indexed. Remove those addresses from your published list, then split only the remaining URLs by reason.

If two weeks have passed after submitting an index request and nothing has changed, what's next?

First check whether the reason name has changed and reassign the group. If "Discovered - currently not indexed" has changed to "Crawled - currently not indexed," move it to the right column and fix the body content. If the reason is unchanged, check whether it's included in the sitemap and check internal links, and don't resubmit a request for the same URL.