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

When Google isn't indexing a page, sort the reasons into two columns: those an indexing request resolves and those that need a page or server fix. A reason where the page has only been pushed back in the crawl order can be moved up with a single request. A reason caused by the page or server stays the same no matter how many requests you submit until you fix it.

The Search Console page indexing report mixes reasons from both columns in one table, and the reason names are long and similar, such as "Crawled - currently not indexed."

1. Sort indexing issues into two columns

When PION audits a site, it first sorts the report's reasons into a column that a request resolves and a column that needs a fix, then moves on to individual reasons. 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 indexing is scattered across several reasons in this table, and some of them fall outside the scope of action.

Download the URL list from each reason row in the report. 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. If you sort by publication date as you split them, you can also see whether pages published on the same day are clustered under one reason. If they are, start by checking the template, redirect, and sitemap settings you deployed that day.

2. Do you need to fix a page that was discovered but not crawled?

"Discovered - currently not indexed" means the page has been pushed back in the crawl order, and there is nothing to fix on the page. 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 already crawled the page and decided not to add it to the index, so submitting another request leaves the reason unchanged.

A URL that isn't in the report is one Google doesn't know about yet. Adding a property and submitting a sitemap (often called Google indexing registration), along with what to do for each status afterward, are covered in Registered your site with Google but still not showing up? What to check.

3. Where to fix each reason that needs a fix

Where you fix a right-column reason depends on where it is blocked: a directive refusing indexing, an access block, or a response code.

If the NOINDEX marking and a robots.txt block 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 have distinct meanings in the HTTP standard. RFC 9110 defines 401 as "it lacks valid authentication credentials for the target resource." 403 is "the server understood the request but refuses to fulfill it." Google's help also says of 403 that "Googlebot does not provide authentication credentials, so your server is incorrectly returning this error," classifying it as a server configuration mistake.

4. Distinguishing the three canonical URL reasons

Of the three reasons a page is left out of the index because of canonical URLs, only one needs action, and PION distinguishes these three first when auditing a client site.

How to specify a canonical URL with rel=canonical and other methods (updated July 15, 2026) distinguishes, among the ways to declare a canonical, 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."

Using the Google URL removal tool to clean up duplicates hides even the canonical URL from search. 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. Which URLs get a Google indexing request, and when?

Submit a Google indexing request once each, only for URLs in the left column and for right-column URLs right after you fix them. 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 works the same way: remove the reason, submit one request, and wait. You submit a request for a URL where you removed the noindex directive because of 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 a right-column reason, 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 page still isn't indexed after two weeks, check whether the reason name has changed and reassign the column.

Why a page that is already indexed doesn't appear in ChatGPT or Gemini answers is covered in Why your brand doesn't show up in ChatGPT and Gemini.

You can see in the GEO agency service overview how PION scopes the work of getting pages with fixed right-column reasons cited in AI answers. To narrow down how many right-column reasons your site has, start with the indexing and bot-access items in the AI answer visibility basics check.