The short answer
"Not indexed" is not automatically a problem. Google says "Don't expect every URL on your site to be indexed" and asks you to focus on your key pages1. Check which of your important pages are affected, look up each reason below, fix the cause on every affected URL, check one with the URL Inspection tool, then click Validate fix.
Step 1: decide which pages should be indexed
The Page indexing report sorts the URLs Google knows about on your site into Indexed and Not indexed, and lists the reasons in a table headed "Why pages aren't indexed"1. On a typical B2B site, the Not indexed total includes many URLs you never wanted in Google: redirected old URLs, tracking parameter variants, thank-you pages, tag archives, staging leftovers. A large number there is not, on its own, a sign that anything is wrong.
- Filter to your sitemap. At the top of the report, switch from "All known pages" to "All submitted pages", which shows only URLs listed in a sitemap you submitted1. If your sitemap lists only pages you want indexed, which it should, this view shows the problems that matter.
- List your pipeline pages. Services, solutions, industries, pricing, demo, case studies, your main guides. Any of these appearing under a Not indexed reason is worth fixing first.
- Click a reason to see example URLs. The example list is capped at 1,000 rows and "isn't guaranteed to show all URLs in a given status"1, so for a single important page, use the URL Inspection tool instead.
If your site has no Search Console property yet, our Search Console quick wins guide covers the setup and the settings to check first.
Every reason, and what to do about it
These are the reasons Google documents for the Page indexing report, using its exact names1, grouped by what they usually mean.
Usually expected: check, then leave alone
| Reason | What Google says it means | What to do |
|---|---|---|
| Page with redirect | A non-canonical URL that redirects to another page; it is not indexed, but the target may be | Nothing, if the redirect is intended. Check the target is indexed |
| Alternate page with proper canonical tag | The page points to a canonical page that is indexed | Nothing; this is working as designed |
| Not found (404) | The URL returned a 404 | Fine if the page was removed with no replacement. If it moved, add a 301 redirect to the new URL |
| Duplicate without user-selected canonical | Google treats the page as a duplicate and picked another URL as canonical | Inspect the URL to see Google's choice. If it is wrong, declare your preferred canonical; if the page is not a duplicate, make its content clearly distinct |
These need a quick look rather than a fix. The one to watch is "Not found (404)" on a URL that still gets links or used to get search traffic: redirect it to the closest equivalent page.
Blocked by a setting: fix if the page should be indexed
| Reason | What Google says it means | What to do |
|---|---|---|
| URL marked ‘noindex’ | Google found a noindex directive when it tried to index the page | Remove the noindex meta tag or X-Robots-Tag header, check with URL Inspection, then request indexing |
| URL blocked by robots.txt | Your robots.txt file blocks Google from crawling the page | Unblock it if the page should be indexed. To keep it out of Google, allow crawling and use noindex instead |
| Blocked due to unauthorized request (401) | Googlebot was asked to log in | Remove the login requirement for public pages, or verify Googlebot and allow it |
| Blocked due to access forbidden (403) | The server refused the request. Googlebot never sends credentials, so Google says the server is returning this error incorrectly | Check firewall, bot protection and CDN rules; allow signed-out visitors or verified Googlebot |
| URL blocked due to other 4xx issue | Another 4xx error not covered above | Inspect the URL to see the exact response |
On B2B sites, these are the causes we would check first:
- A noindex left over from staging. A site or a set of templates built behind a noindex, and launched without removing it. Some CMSs have a site-wide "discourage search engines" setting that adds it to every page.
- Landing page tools with their own settings. Pages built in a separate landing page or marketing automation tool can have their own "hide from search engines" option, separate from your main CMS.
- Bot protection and geo-blocking. A security rule that challenges unfamiliar traffic can serve Googlebot an error. Google's report names "a misconfigured firewall or DoS protection system" among the causes of server connectivity errors1.
Do not use robots.txt to keep pages out of Google. Google says robots.txt "is not a mechanism for keeping a web page out of Google"3, and a noindex rule only works if the page is not blocked by robots.txt, because Google has to crawl the page to see it4. Google also warns that using JavaScript to remove a noindex "may not work as expected": "If you do want the page indexed, don't use a noindex tag in the original page code"6.
Server and redirect errors: fix promptly
| Reason | What Google says it means | What to do |
|---|---|---|
| Server error (5xx) | The server returned a 500-level error | Check server health and the host status in the Crawl Stats report; check that a firewall or DoS protection rule is not blocking Googlebot |
| Redirect error | A redirect chain that is too long, a redirect loop, a redirect URL that is too long, or a bad or empty URL in the chain | Trace the redirect with a debugging tool and point it straight at the final URL |
| Soft 404 | The page looks like a "not found" page but returns a success code | Return a real 404 for missing pages, or add substantial content if the page is real |
Soft 404s tend to come from thin pages, for example an empty job listings page, a "resources" filter with no results, a case study template published before its content. If the page is real, give it enough content that it is clearly not an error page.
Canonical choices: confirm Google picked the right URL
| Reason | What Google says it means | What to do |
|---|---|---|
| Duplicate, Google chose different canonical than user | You declared a canonical, but Google thinks another URL is a better canonical | Compare the user-declared and Google-selected canonicals in URL Inspection. A declared canonical that is not similar to the page will not be chosen |
Canonical signals stack. Google lists, in order of strength, redirects, rel="canonical" annotations and sitemap inclusion5. Make them agree: the canonical tag, the URL in your sitemap, and the URL your internal links use should all be the same, including the protocol and trailing slash. Google advises against specifying different canonical URLs for the same page with different methods5.
Not indexed yet: the two that need judgement
| Reason | What Google says it means | What Google says to do |
|---|---|---|
| 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 the URL for crawling |
| Discovered - currently not indexed | "The page was found by Google, but not crawled yet." Typically, crawling was expected to overload the site, so Google rescheduled it | No specific fix given |
Google gives no checklist for these, so what follows is our practical reading, not Google's guidance. For a pipeline page stuck in "Crawled - currently not indexed", ask whether the page adds something Google does not already have elsewhere on your site or the web:
- Is it nearly the same as another page, such as one of several industry pages with the name swapped? Merge them, or make each one specific.
- Is it short or mostly boilerplate? Add the substance a buyer needs: what you do, for whom, how, and evidence.
- Does anything link to it? Add links from related pages in context. Our guide to internal linking for B2B websites shows how.
"Discovered - currently not indexed" on a small B2B site is worth checking against the Crawl Stats report: slow or failing server responses would fit Google's explanation that crawling was expected to overload the site1. If the server looks healthy, strengthen internal links to the page and make sure it is in your sitemap.
Warnings: indexed, but with a problem
Two statuses appear under the report's "Improve page experience" table. They do not stop indexing1.
- Indexed, though blocked by robots.txt. The page is indexed despite the robots.txt block, so its snippet is likely to be limited. If you want it out of Google, remove the block and use noindex; if you want it in, unblock it.
- Page indexed without content. Google indexed the URL but could not read its content, which Google says may be cloaking or a format it cannot index. Inspect the page.
Step 2: check the fix with URL Inspection
Before telling Google you have fixed anything, check one affected page with the URL Inspection tool2.
- Read the indexed result. It shows the version Google last indexed, not the live page: when it was last crawled, whether the fetch succeeded, whether indexing was allowed, and both the user-declared and the Google-selected canonical2.
- Click Test live URL. This fetches the page now, so you can confirm the noindex is gone or the server returns 200. Google notes that even "URL is on Google" does not guarantee the page will appear in Search results2.
- Request indexing for important pages. There is a daily limit on requests, and you cannot request indexing for a page the live test finds non-indexable2. For many URLs, submit an updated sitemap instead.
Step 3: validate the fix
Once every affected URL is fixed, open the reason in the Page indexing report and click Validate fix. Google's process1:
- Fix every instance first. Validation stops as soon as Google finds one URL that still has the issue.
- Do not click Validate fix again while a validation is running.
- "Validation typically takes up to about two weeks," and can take longer. You get a notification when validation succeeds or fails.
- If validation fails, fix the remaining URLs and start a new validation.
Record the date and the URLs you changed. If a pipeline page comes back into the index, you will want to compare its search performance before and after, and the B2B website SEO audit checklist covers the baseline to record.
A routine for lean teams
- Monthly: open the Page indexing report on "All submitted pages" and look for any new reason affecting pipeline pages.
- After every launch or migration: inspect the home page, one page of each template and any redirected section; check robots.txt and noindex settings.
- When publishing a key page: add it to the sitemap, link to it from at least one related page, then inspect it a few days later.
- Keep the sitemap clean: list only canonical, indexable URLs that return 200, so the submitted view stays meaningful.
Where Artiweave fits
Artiweave works from the same two sources this guide uses, a crawl of your site and your Search Console data, and proposes specific changes to existing pages with that evidence attached. A marketer approves, edits or rejects every change before it is published.
Frequently asked questions
Is it bad to have lots of pages not indexed?
Not necessarily. Google says not to expect every URL to be indexed. Redirects, canonical alternates and removed pages are expected to appear as not indexed. What matters is whether pages you want in Google are affected.
How long does it take for a fixed page to be indexed?
Google does not give a fixed time. Google says the Validate fix process typically takes up to about two weeks.
What does "Crawled - currently not indexed" mean?
Google crawled the page but has not indexed it, and it may or may not do so in future. Google says there is no need to resubmit the URL. If it is an important page, make sure it offers something distinct and is linked from related pages.
Should I use robots.txt to keep a page out of Google?
No. Google says robots.txt is not a mechanism for keeping a page out of Google. Use a noindex rule, and make sure robots.txt does not block the page, or Google cannot see the noindex.
More in this section: B2B website SEO, Search Console quick wins and the B2B website SEO audit checklist.
Sources
- Google Search Console Help: Page indexing report (accessed 3 November 2026)
- Google Search Console Help: URL Inspection tool (accessed 3 November 2026)
- Google Search Central: Robots.txt introduction and guide (accessed 3 November 2026)
- Google Search Central: Block search indexing with noindex (accessed 3 November 2026)
- Google Search Central: How to specify a canonical URL with rel="canonical" and other methods (accessed 3 November 2026)
- Google Search Central: Understand JavaScript SEO basics (clarified 15 December 2025; accessed 3 November 2026)
Find the pipeline pages Google is missing.
Artiweave proposes specific changes from evidence, your team approves each one, and approved changes are published with automatic rollback. It is in private beta.