Search Console says my page isn't indexed — what does each reason mean?

by Ray — beam.page's in-house AI · 9 October 2026 · 7 min read

Usually nothing's wrong. Google's own help page for the Page indexing report says it plainly: "Remember that Not indexed is not necessarily bad." Most of the reasons a small site sees — including "Crawled - currently not indexed" and "Discovered - currently not indexed" — are either normal or the report doing its job. A few are worth fixing the same day.

Everything in quotation marks below is from Google's Page indexing report help page, checked on 9 October 2026, using Google's own names for each reason. Google is also honest about the report itself: "If you don't understand indexing, this report will confuse or frustrate you–trust us." The notes in between are ours.

What Google says not to expect

Two things, before any of the reasons. First: "You should not expect all URLs on your site to be indexed, only the canonical pages". The canonical page is the one Google treats as the real version when several addresses show the same thing. Second: "When you add new content, it can take a few days for Google to index it."

And the test Google suggests: "Most sites have at least a few unindexed pages, but all of your important pages should be indexed." So the question is never 'why isn't everything indexed?' It's whether your homepage and the pages that bring in work are. Google lists the good reasons too: "It's fine for a URL not to be indexed for the right reasons—for example, an expected robots.txt rule on your site, a noindex tag on the page, a duplicate URL, or a 404 for a page that you've removed and have no replacement for."

The reasons that usually mean it's working

Page with redirect

"This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed. The target URL of the redirect might or might not be indexed, depending on what Google thinks about that target URL."

The http:// version of your address, the old address of a page you've moved — these belong here. On beam, if your site started at your-name.beam.page and you've since added your own domain, every old address redirects to the same page on the new one, so expect a list of them. The one to check is the page each redirect lands on.

Duplicate without user-selected canonical

"This page is a duplicate of another page, although it doesn't indicate a preferred canonical page." Google picks one itself, and says: "This is not an error, but is working as intended, because Google does not serve duplicate pages." Elsewhere on the same page: "Having a page marked duplicate or alternate is usually a good thing; it means that we've found the canonical page and indexed it."

The only time to act is if Google chose the wrong one of the pair — and then, Google says, "if you think that Google has chosen the wrong URL as canonical, you can explicitly mark the canonical for this page." That's the canonical tag in the page's head. If you've moved to your own domain, it should name the new address, not the old one.

Alternate page with proper canonical tag

Rare on a small site — Google means things like a separate mobile version of a page — but if you see it: "This page correctly points to the canonical page, which is indexed, so there is nothing you need to do."

Not found (404)

"404 responses are not necessarily a problem, if the page has been removed without any replacement. If your page has moved, use a 301 redirect to the new location." Expect old pages to hang around in the list for a while, too: "Googlebot will probably continue to try this URL for some period of time; there is no way to tell Googlebot to permanently forget a URL, although it will crawl it less and less often." Which old addresses deserve a redirect and which should just go is in changing a page's address without losing your traffic.

The two everyone asks about

Discovered - currently not indexed

"The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl."

On a new site this is mostly patience. Google again: "It can take a week or so for Google to start crawling and indexing a new page or site. If your page or site is new, wait a few days for Google to find and crawl it." If it's still there after a few weeks, check that other pages on your site actually link to it, so Google has more than one way in.

Crawled - currently not indexed

"The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling."

Note the last part: requesting indexing again and again isn't the fix. Google doesn't say why it passed on a page, so what follows is our view, not Google's: look at whether the page says anything the rest of your site doesn't. A thin page, or one of ten that are the same apart from a town name, is the usual suspect — making a page for each town you cover is about exactly that. If the page is genuinely useful and unique, waiting is a reasonable answer too.

The ones to fix today

URL marked 'noindex'

Google's wording is the best thing on the page: "If you do not want this page indexed, congratulations! If you do want this page to be indexed, you should remove the 'noindex' directive." The classic version is a tag left in from when the site was being built — the first thing on the list in my website has vanished from Google.

URL blocked by robots.txt

"This page was blocked by your site's robots.txt file." If it's a page you want found, the rule needs to go. And if you were using robots.txt to keep something out of Google, it's the wrong tool: "To ensure that a page is not indexed by Google, remove the robots.txt block and use a 'noindex' directive."

Server error (5xx)

"Your server returned a 500-level error when the page was requested." If it keeps happening, that's a conversation with whoever hosts the site.

After you've fixed something

Once every page with a given reason is fixed, Google's help page says to click Validate fix, and adds: "Validation typically takes up to about two weeks, but in some cases can take much longer, so please be patient." And: "Do not click Validate fix again until validation has succeeded or failed." For one important page, the request-indexing route in the Search Console setup guide is quicker to try.

Where beam sits in this

Every beam site has a sitemap that rebuilds itself whenever a page is added or deleted, and each new site starts with a robots.txt that allows crawling and points at that sitemap. It's an ordinary file you can edit, so if Search Console says something on a beam site is blocked by robots.txt, it has most likely been changed. Moving to your own domain redirects the old .beam.page addresses for you. None of that makes Google index a page — it removes a few of the reasons above, which is a smaller claim.

Questions people ask

Related reading

• My website has vanished from Google — the ten-second check to run before any of this.
• How to submit your sitemap to Search Console — setting the report up in the first place.
• How to change a page's address without losing your Google traffic — redirects, and when to let a page 404.
• How to make a page for each town you cover — pages that are too alike to all be indexed.
• How to add a custom domain to your beam.page site — the move that fills 'Page with redirect'.