Implementation guide · 15 minute read · By Trevor Fenner
Some links below are affiliate links. Purchases through those links support SEO Paradise. Read our disclosure.
Google Search Console indexing confuses almost every store owner the first time they open it. You see a gray bar of “not indexed” pages that is bigger than the green bar of indexed ones, and your stomach drops. I get it. At first glance, that chart looks like something is badly broken.
Usually nothing is broken. A big share of the not indexed list is Google doing its job. It is skipping redirects, duplicates, filtered URLs, and pages you told it to skip. The real skill is separating those normal statuses from the few that actually cost you traffic.
This guide is the overview. It covers the Page indexing report, the URL Inspection tool, sitemaps, requesting indexing, and the validation flow, based on Google’s own documentation. If one status in particular is driving you crazy, we have a separate deep fix guide for crawled, currently not indexed. Shopify owners should also read our Search Console setup guide for Shopify.
One promise up front. Nothing in Search Console guarantees indexing. Google says so in plain language in its own help pages. What you can do is remove the blockers, send clear signals, and make pages worth indexing.
| Status | Usually normal? | First action |
|---|---|---|
| Page with redirect | Yes | Confirm the redirect is intended and internal links point to the final URL. |
| Alternate page with proper canonical tag | Yes | No action unless the canonical points to the wrong page. |
| Not found (404) | Often | Ignore removed pages. Fix only important URLs that should exist. |
| Noindex (URL marked noindex) | Depends | Check whether the noindex was intentional. |
| Crawled, currently not indexed | Sometimes | Improve page value and internal links on pages that matter. |
| Server error (5xx) | No | Fix with your host or platform, then validate. |
Where indexing lives in Search Console
Three tools in Search Console handle indexing. Each answers a different question, and mixing them up is how people waste hours.
- The Page indexing report answers “how many of my pages are indexed, and why are the others not?” It works at the site level.
- The URL Inspection tool answers “what does Google know about this one URL?” It works at the page level.
- The Sitemaps report answers “did Google read the list of URLs I want indexed?” It works at the sitemap level.
Start with the report to find patterns. Use URL Inspection to confirm a pattern on 2 or 3 example URLs. Use sitemaps to tell Google which URLs you care about most. That order saves a lot of guessing.
How to read the Page indexing report
Open Search Console, choose your property, and go to Indexing, then Pages. Google’s Page indexing report documentation describes a chart of indexed and not indexed URLs, a table called “Why pages aren’t indexed,” and a second table for pages that are indexed but could be improved.
The filter at the top is the part most people miss. By default the report shows all known pages, which means every URL Google has found anywhere, including old links, parameter URLs, and pages you deleted years ago. You can switch it to all submitted pages, unsubmitted pages only, or a single sitemap.
Switch to all submitted pages first. Those are the URLs you told Google matter. Problems there deserve your attention before anything in the unsubmitted pile.
Click any row in the “Why pages aren’t indexed” table to see example URLs. Google limits that example table to 1,000 rows, so it may not list every affected URL. For a big store, export the examples and look for patterns in the paths, like /collections/ with filter parameters or old /products/ URLs from a previous theme.
Submitted vs indexed
Your submitted count will almost never match your indexed count. That gap is not a penalty. Submitting a URL in a sitemap tells Google it exists and that you consider it important. It does not force Google to index it.
Google’s sitemap guidance is blunt about this. Submitting a sitemap is a hint, and Google may not use it to decide which URLs to crawl. The Sitemaps report also says that being listed does not guarantee a page will be crawled or indexed.
So what is a healthy gap? There is no official number. For a small business site with 40 service and blog pages, I would expect almost every submitted page to be indexed once the site has been live for a few months. For a store with 3,000 products where many are near duplicates from the same supplier feed, a larger gap is common and often a content quality signal rather than a technical bug.
If you sell high-ticket products, that second case is worth thinking about. Copying supplier descriptions word for word across hundreds of products gives Google little reason to index every page. The high-ticket dropshipping guide explains why fewer, better product pages usually win in this model.
What each status means
Here is every common reason in the “Why pages aren’t indexed” table, in plain English, based on Google’s descriptions. I have grouped them by the type of fix they need.
Server and redirect problems
Server error (5xx) means your server returned a 500 level error when Google asked for the page. Redirect error means the redirect chain was too long, looped, created a URL that was too long, or pointed to a bad or empty URL. Both are real technical problems. Fix them first because they can block pages you want indexed.
Pages you blocked on purpose or by accident
URL blocked by robots.txt means a robots.txt rule stops Google from crawling the page. Google notes the page can still be indexed if other pages link to it. The noindex status (Google’s help page calls it URL marked noindex) means the page carries a noindex directive. On Shopify stores, apps and theme settings sometimes add noindex without the owner knowing, so check these carefully.
Missing or restricted pages
Not found (404) means the URL returned 404. Google says this is usually fine when the page was removed and has no replacement. Soft 404 means the page looks like a “not found” page to Google but returns a normal success code. Empty collection pages and out of stock product pages with almost no content often land here.
Blocked due to unauthorized request (401) means the page needs a login. Blocked due to access forbidden (403) means the server refused access, and Google notes that Googlebot never sends credentials, so this is likely a server misconfiguration. Other 4xx issues cover the remaining client errors.
Pages Google found but did not index
Crawled, currently not indexed means Google visited the page and decided not to index it for now. Google says it may be indexed later and you do not need to resubmit it. Discovered, currently not indexed means Google knows the URL exists but has not crawled it yet, sometimes to avoid overloading your site. These are the 2 statuses people stress over most. Our crawled, currently not indexed fix guide covers the diagnosis step by step.
Duplicates and canonicals
Alternate page with proper canonical tag means the page points to another canonical page that is indexed, which is what you want. Duplicate without user-selected canonical means Google chose a different page as canonical, and Google describes this as working as intended. Duplicate, Google chose different canonical than user means Google ignored the canonical you declared and picked another URL. That last one deserves a look, because it can mean your signals are mixed.
Redirects
Page with redirect means the URL redirects somewhere else, so only the target can be indexed. After a site migration or a URL cleanup, this list can grow into the hundreds. That is expected.
Indexed with warnings
The second table lists pages that are indexed but have a problem. Indexed, though blocked by robots.txt means Google indexed the URL without crawling it, often showing a limited snippet. Page indexed without content means the page is in the index, but Google could not read its content. Both are worth checking on important pages.
Which statuses are normal
Google says directly in the report documentation that not indexed is not necessarily bad. Here is the short list of statuses I usually leave alone on a healthy site.
- Page with redirect, when the redirects are intended.
- Alternate page with proper canonical tag.
- Duplicate without user-selected canonical, when the duplicates are variants you do not need indexed.
- Not found (404) for pages you removed on purpose.
- Blocked by robots.txt or noindex, when you set those blocks on purpose for cart, account, search, or filter pages.
The test is simple. Ask whether you want that URL to appear in Google. If the answer is no, and Google is not indexing it, the report is showing you a good outcome. Keep that in mind before you spend a weekend “fixing” a chart that was fine.
Using the URL Inspection tool
Paste any URL from your property into the search bar at the top of Search Console. The URL Inspection tool documentation explains that the default view shows the most recently indexed version of the page, not the live version.
The top line gives you one of a few verdicts. URL is on Google means the page is eligible to appear in results, though not guaranteed to. URL is on Google, but has issues means it is eligible but something like structured data has a problem. URL is not on Google means it cannot appear, and the Page indexing section explains why.
Open the Page indexing section and read these fields in order:
- Discovery shows the sitemaps that list the URL and a referring page Google may have used to find it.
- Last crawl shows when Google last crawled the page and whether it crawled as a smartphone or desktop.
- Crawl allowed shows whether robots.txt permits crawling.
- Page fetch shows whether Google could retrieve the page.
- Indexing allowed shows whether a noindex blocks indexing.
- User-declared canonical and Google-selected canonical show whether Google agrees with your canonical.
Then click Test live URL. The live test fetches the page right now, so it confirms whether your fix is live. Google lists some important limits. The live test does not check sitemaps or referring pages, does not check duplicate or canonical status, and does not check manual actions or quality guidelines. A clean live test means the page can be fetched. It does not mean the page will be indexed.
Requesting indexing and its limits
After a live test, you can click Request indexing. This asks Google to crawl the URL again. It is useful for a new page, a page you just fixed, or a page with a major update.
It has limits. There is a daily quota for individual URL requests. Google’s guide to asking Google to recrawl URLs says that requesting a crawl does not guarantee inclusion in search results, instantly or at all. It also says that crawling can take anywhere from a few days to a few weeks, and that requesting a recrawl several times for the same URL will not make it faster.
So use the button with intent. I use it for a handful of important pages after a real change, like a new category page or a rewritten buying guide. For anything bigger than a few URLs, I rely on the sitemap and internal links instead. Pressing the button every morning on the same page is a pain in the butt and it does nothing.
Sitemaps that help Google
A sitemap is the cleanest way to tell Google which URLs matter. Google’s sitemap building guide sets a limit of 50MB uncompressed or 50,000 URLs per sitemap file. Larger sites split into several files under a sitemap index.
A few rules from that guide matter in practice. Google uses the lastmod value only when it is consistently and verifiably accurate. Google ignores priority and changefreq. List the canonical version of each page, not redirected or duplicate URLs.
To submit, go to Indexing, then Sitemaps, paste the sitemap URL, and click Submit. The Sitemaps report documentation lists 3 statuses. Success means Google processed it with no errors. Has errors means Google fetched it but found problems, though parseable URLs are still queued. Couldn’t fetch means Google could not load the file.
Shopify builds the sitemap for you. The Shopify sitemap help page says the file lives at your root domain as sitemap.xml and links to child sitemaps for products, collections, blogs, and pages. It also notes that Google cannot read the sitemap while your store is in private mode, so remove the storefront password before you submit. If you are still choosing a platform, Shopify handles this part well out of the box.
One last trick. After you submit a sitemap, filter the Page indexing report by that sitemap. Now you see the indexing status for exactly the URLs you care about, without the noise of every old URL Google ever found.
How to prioritize fixes
You cannot fix everything at once, and you should not try. Score each status group on 3 questions, then work from the highest total down.
| Question | 0 points | 3 points |
|---|---|---|
| Do the affected URLs earn money or leads? | Filter, tag, or old URLs | Core service, category, or best selling product pages |
| Did you intend this outcome? | Yes, the block or redirect is on purpose | No, it is a surprise |
| Is the count growing? | Flat or shrinking | Rising week over week |
Here is a filled example for a small Shopify store. Server error (5xx) on 12 collection pages scores 3, 3, and 3 for a total of 9, so it goes first. The noindex status on 4 blog posts that should rank scores 2, 3, and 0 for a total of 5. Page with redirect on 300 old product URLs scores 0, 0, and 0, so it waits forever.
If you need help finding the technical cause behind a high score, run an audit. Our SEO audit checklist covers the usual suspects. For stores, the common Shopify SEO issues guide goes deeper.
The validation flow
Once you have fixed every instance of an issue, open that row in the Page indexing report and click Validate fix. Google first checks a few sample pages. If the problem is still there, validation stops right away. If the samples pass, Google rechecks the known affected URLs.
The status moves through a few stages. Not started means you have not asked. Started means Google is checking and has not found remaining problems yet. Looking good means every URL checked so far is fixed. Passed means all known instances are gone. Failed means too many pages still have the issue, so fix them and start a new validation.
Google says validation typically takes up to about 2 weeks and sometimes much longer. Do not click Validate fix again while one is running. Google can also notice a fix during normal crawling without a validation request, in which case you may see N/A.
Only validate issues you actually fixed. Clicking Validate on a status like page with redirect, when the redirects are intended, just gives you a failed validation and a false sense of urgency.
A monthly indexing routine
Indexing is not a one time project. Here is the 30 minute routine I recommend once a month for a small business site or store.
- Open the Page indexing report and filter to all submitted pages. Note the indexed and not indexed counts in a simple sheet.
- Scan the “Why pages aren’t indexed” table for any reason that is new or growing since last month.
- Open 2 or 3 example URLs from any new reason and run URL Inspection on them.
- Score the new issues with the priority table above and fix the top 1 or 2.
- Click Validate fix on anything you fixed.
- Check the Sitemaps report for errors.
- Request indexing for any brand new pages that matter, up to a handful at a time.
Log the numbers each month. Trends tell you far more than any single snapshot. Our SEO report template has a spot for this. The SEO monitoring guide explains what else to watch.
Before you worry about indexing at all, make sure the business underneath is set up properly. A clean domain, real contact details, and proper policies support trust with customers and search engines alike. The business formation checklist covers that foundation for store owners. And if you want someone to look at your Search Console with you and build a fix list, that is part of what we do in Ecommerce Paradise coaching.
I have been running online stores since October 2010, and this report is still part of how I review the Shopify stores we build and manage at Ecommerce Paradise. It is not exciting work. It is the kind of boring habit that keeps a site healthy.
Frequently asked questions
How long does Google take to index a new page?
Google’s URL Inspection documentation says indexing typically takes a day or so but can take much longer, up to a week or two in some cases. Its recrawl guide says crawling can take a few days to a few weeks. There is no guaranteed timeline.
Does Request indexing guarantee my page gets indexed?
No. Google says submitting a request does not guarantee the page will appear in the index. It only asks Google to crawl the URL again. There is also a daily quota on these requests.
Why does Search Console say my page is not indexed when I can find it in Google?
The report and the inspection results can lag behind the live index. Data in the indexed result comes from the last crawl. Run URL Inspection on the specific URL for the most current view, and check that you are looking at the exact same URL, including https and trailing slash.
Should I worry about a high number of not indexed pages?
Not by itself. Redirects, canonicalized duplicates, intentional noindex pages, and removed 404 pages all count as not indexed. Filter to submitted pages and focus on reasons that affect URLs you actually want in Google.
What is the difference between crawled and discovered, currently not indexed?
Crawled means Google visited the page and chose not to index it for now. Discovered means Google knows the URL but has not crawled it yet. Our crawled, currently not indexed guide covers how to diagnose and fix both.
Related SEO guides
Trevor Fenner publishes practical SEO guides through SEO Paradise, part of Ecommerce Paradise. His articles cover search strategy, content planning, on-page optimization, and technical foundations for business websites.