Which pages should be indexed?
Not every URL belongs in search, so first decide which pages genuinely should be there: services, key categories, guides that answer real questions. Take a small sample of them, ideally from different templates, and check each one’s status code, redirects, robots directives and canonical tag, the basics of technical SEO.
The URL Inspection tool in Search Console shows both the version Google last indexed and a live test of the current page. Compare the two: the problem may already have been fixed, or it may have appeared after the last crawl.
When you find a noindex directive or an unexpected canonical, establish where it comes from: the page’s HTML, an HTTP header or a shared template. And avoid changing rules for the whole site based on the status of a single URL. First confirm that the issue repeats across your sample.
Can Google reach the page?
Find out how a crawler would discover the URL through ordinary links. A sitemap helps, but it does not replace a sensible navigation structure, and a page listed only in the sitemap gets little support from the rest of the site.
Check that the page is linked from a relevant category or service hub, that those links point to the final URL and not to an address that redirects, and that the server responds consistently, without intermittent errors or timeouts. The page indexing report in Search Console gives clues: “Discovered – currently not indexed” means Google knows the URL but has not crawled it yet, while “Crawled – currently not indexed” means it fetched the page and decided not to include it for now.
If the content depends on JavaScript, check what is actually present after rendering; the live test shows the rendered HTML and a screenshot. Text that appears only after a click may not be seen at all.
Is the page a duplicate?
Once access is in order, compare the page with similar URLs on the site. Look for templates repeated without meaningful differences, empty categories and several addresses showing the same content. If Search Console reports that Google chose a different canonical than the one you set, it has probably found exactly such a duplicate.
Decide which page should be the destination for that topic and consolidate deliberately: merge the content, add a redirect or set the canonical, and update internal links to match.
After fixing a specific defect, request indexing for a representative URL and follow the result over the next few weeks. Keep expectations realistic: submitting a URL or passing a technical check does not guarantee that the page will be included in search.
Indexing diagnostic sequence
A template to adapt to your own project.
| Question | Evidence to collect |
|---|---|
| Can the page be discovered? | Relevant internal links and an up-to-date sitemap entry. |
| Can it be fetched? | Final response code, access rules and server behaviour. |
| Is the intended version eligible? | Directives, canonical target and rendered content. |
| Is it worth indexing? | A distinct purpose, supporting evidence and a comparison with duplicates. |
Checklist: indexing
- Inspect a small sample of URLs from different templates.
- Check the final response, directives and canonical for each one.
- Compare the indexed version with a live test in Search Console.
- Confirm that relevant internal links point to the final URL.
- Record each change and follow it up in Search Console.
Example: a new service page outside the index
A new service page returns a 200 status and has no noindex directive, yet it does not appear in search. The diagnosis shows that every internal link points to an old address that redirects to it, and the sitemap still lists the old address as well.
The fix is to update the contextual links and the sitemap to the final URL, check the rendered page and then reassess discovery. A good diagnosis names the actual defect, in this case links to a redirected URL, instead of a vague “indexing problem”. An SEO audit applies the same approach to the whole site.
Common mistakes
- Changing site-wide rules after one URL. Check a sample from several templates first; one odd page rarely justifies a global change.
- Relying on the sitemap alone. A page that is listed in the sitemap but not linked from relevant pages gets little support from the rest of the site.
- Linking to redirected addresses. Internal links and sitemap entries should point to the final URL, not to an address that redirects to it.
- Requesting indexing again and again. Repeated requests do not fix the underlying cause. Find the defect, fix it, then request indexing once.
Questions
How long does Google take to index a new page?
It depends on the site: how often Google crawls it, how well the page is linked and whether it offers something distinct. There is no fixed waiting time. What helps is a clear internal link from a relevant hub, a correct sitemap entry, a fast and stable server and content that is not a near-duplicate of other pages.
What does “Discovered – currently not indexed” mean?
Google knows the URL exists but has not crawled it yet. This often points to weak internal linking, a large number of similar low-value URLs competing for attention or a server that responds slowly. Improve links to the page and reduce duplicates before requesting indexing.
Does requesting indexing in Search Console help?
It asks Google to crawl the page sooner, which is useful after you have fixed a specific defect. It does not guarantee inclusion and does not override problems such as duplicates or a noindex directive. Use it once per fixed page, then check the outcome.
Can a sitemap fix indexing?
A sitemap helps Google discover URLs and understand which ones you consider important, but it cannot make a page eligible or worth indexing. If a page is blocked, canonicalised elsewhere or too similar to others, the sitemap entry will not change that. Technical SEO work usually starts with links and duplicates, not the sitemap.
