If many pages are missing from Google, treat indexing as a site-wide publishing and diagnosis problem—not a race to submit every URL. Build an inventory of pages you actually want in Search; compare discovery, crawl, canonical selection and index outcomes by page type; repair the largest coherent cause before requesting recrawls. Google explicitly says a crawl request cannot guarantee inclusion or a fixed timetable.
Define what success means for each URL group
Separate service pages, articles, product or category pages, filtered URLs, redirects and removed pages. A published, unique service page may be a target for indexing; a duplicate parameter URL, checkout page or retired page may not be. Therefore “indexed URLs divided by every URL ever seen” is not a useful standalone success metric. Maintain a list of preferred canonical URLs and record whether each should be discoverable, indexable, consolidated or removed. A sitemap should list the absolute URLs you prefer Google to show; Google describes submission as a hint and says a single file must stay below 50,000 URLs or 50 MB uncompressed. See its sitemap construction and submission guide.
Consider a site with articles, product filters and expired campaign pages. If filters intentionally canonicalize to category pages, their absence from the index is not a publishing failure. If core service pages are unknown to Google, inspect whether navigation and related pages actually link to them. If thousands of removed campaign URLs still appear in the sitemap, correct the inventory and their real response behavior before trying to raise an aggregate indexing percentage.
Diagnose the pipeline in the right order
- Discovery: are valuable pages linked from relevant crawlable pages and present in the intended sitemap? Google can discover URLs through links as well as sitemaps. An orphaned service page needs a meaningful route from navigation or a relevant topic page, not merely a new timestamp.
- Fetch and rendering: sample the public response, robots.txt access,
noindexin HTML and response headers, server errors and the rendered main content. A site-wide CDN rule blocking Googlebot or an accidental template-levelnoindexdeserves priority over a single weak article. - Canonical and content: compare redirect destination, internal links, sitemap URL, declared canonical and Google's selected canonical. Similar pages with little distinct value may consolidate even if technically indexable. Check whether the main content actually differs by product, language or service intent.
- Outcome: inspect representative URLs rather than assigning a single cause to every exclusion. Google's URL Inspection documentation distinguishes the indexed result from a live test: the latter cannot check all quality issues or predict duplicate selection and is never an indexing guarantee.
Match the intervention to the pattern
Many URLs “Discovered – currently not indexed”: verify the sitemap is accessible, the URLs are linked and the host is stable; compare the useful URLs with low-value variants you may be generating. Don't equate every delayed crawl with a penalty. Many “Crawled – currently not indexed”: inspect representative rendered pages and canonical choices, then improve content that merely repeats another page or lacks a clear audience. Many “Duplicate, Google chose different canonical”: resolve conflicting signals and decide whether those duplicates should exist. Sudden errors after a release: compare response headers, robots rules, redirects and template output before editing articles. These are investigative branches, not promises that one change will produce indexing.
Review content credibility as part of that decision. Google's helpful, reliable, people-first guidance asks for original information, clear sourcing and substantive answers. It describes E-E-A-T as experience, expertise, authoritativeness and trustworthiness, while expressly saying E-E-A-T itself is not a specific ranking factor. Show real authorship, sources and limitations where readers need them; there is no official “trust pre-review,” numeric E-E-A-T score, ORCID shortcut or guaranteed fast-indexing window. If a page's only change is a new date, the underlying answer has not improved.
Use the right discovery tool and stop at its boundary
For a few high-priority pages you manage, use Search Console URL Inspection to examine the indexed and live versions and request indexing after a real fix. For many URLs, submit the sitemap in Search Console or reference it in robots.txt; keep <lastmod> aligned with significant updates rather than republishing today's date on every page. Google's recrawl guide explicitly divides these two cases. Search Console's sitemap API submits a sitemap, but it is not the Indexing API.
Google restricts its Indexing API to pages with JobPosting or BroadcastEvent embedded in VideoObject. It is not a route for normal blogs, product pages, company pages or service pages. Its notification status reports that a notice was received, not that a page was indexed. Do not route ordinary URLs through batches, multiple accounts or a vendor promising an API shortcut. For a particular missing blog article, use the single-post indexing checklist; for deciding when the sitemap changes, use the sitemap update guide.
Measure progress without confusing stages
Keep a periodic table by page type: intended canonical URLs, valid URLs present in submitted sitemaps, inspected samples by exclusion reason, last crawl when available, indexed canonical pages, and impressions/clicks for indexed pages. Compare like-for-like cohorts over time; Search Console counts and reports have coverage and timing limits, so don't add sitemap index and child-file discovered counts as though they were unique pages. This sitemap-count reconciliation guide explains that particular reporting trap.
A post moving from “unknown” to “crawled” has gained discovery, not necessarily index inclusion; a page moving to the index has not necessarily earned rankings or enquiries. After a technical fix, test a small representative group, observe Google's next crawls and only then assess the wider pattern. If a URL is indexed but receives no relevant impressions, move to the query and content problem rather than submit it again. For broader commercial SEO work, the SEO service overview explains the site's scope without turning the indexing report into a ranking promise.