When Google discovers new pages but does not index them, first separate discovery from crawling and indexing. Inspect representative URLs for response, robots access, noindex, canonical, rendering and sitemap consistency. Then assess internal discovery, duplicate inventory, page usefulness and server capacity. Request indexing only after a material cause is fixed.
This is a technical SEO and SEO strategy issue. An indexing request cannot make an inaccessible, duplicate or low-value page deserve inclusion.
Google says crawling and indexing take time, depend on many factors and are not guaranteed by submitting a sitemap Source: Google Search Central.
Confirm the exact Search Console state
Use the Page Indexing report and URL Inspection for several affected pages. Record discovery source, last crawl, crawl allowance, fetch result, indexing permission, declared canonical and Google-selected canonical.
Do not treat every excluded URL as the same issue. “Discovered, currently not indexed,” “Crawled, currently not indexed,” duplicate and blocked statuses imply different next checks.
Verify the live HTTP response
Test the final URL without authentication and through the complete redirect path. It should return a stable 200 for indexable content. Check 5xx, 429, timeouts, redirect loops and soft 404 behaviour.
Google notes that crawl delays can result from serving-capacity problems and will reduce activity when servers struggle Source: Google Search Central.
Check robots and noindex controls
Review robots.txt, robots meta tags and X-Robots-Tag headers. Inspect rendered HTML, not only source templates. Check environment variables, CMS visibility, staging controls and security middleware.
Do not block a URL in robots.txt while relying on a noindex tag that Google cannot crawl to see. Remove accidental restrictions from the public version.
Google's minimum technical requirements include allowing Googlebot access and returning indexable content with a successful status Source: Google Search Central.
Resolve canonical conflicts
Compare the page's self-canonical, internal links, sitemap URL, redirects and alternate versions. Check parameters, print views, location variants and copied landing pages.
If Google selects another canonical, decide whether the pages are genuinely duplicates. Consolidate variants or make intended independent pages materially distinct.
Do not canonicalise a new page to a category or old post while expecting it to index separately.
Test rendering and content delivery
Inspect rendered HTML for the main answer, headings, links, metadata and structured data. Check failed JavaScript, blocked resources, hydration errors and client-only content. Compare desktop and mobile.
Important content should be available reliably without waiting for user interaction. Validate that consent tools do not replace the page with an empty shell for crawlers or first visits.
Strengthen internal discovery
Link new pages from relevant hubs, service pages and established articles where a reader would benefit. Use crawlable anchors and ensure the page is not reachable only through site search or JavaScript controls.
Keep important pages within a reasonable click path. Update navigation and related-content systems. Remove links to obsolete URL variants.
A sitemap assists discovery but does not replace a coherent internal architecture.
Audit sitemap quality
Include only canonical, indexable, successful URLs. Use accurate last-modified dates for meaningful changes. Remove redirects, errors, noindex pages and parameter duplicates.
Submit the correct sitemap to the verified property and monitor processing. Split large inventories logically when diagnosis benefits.
Google says sitemaps can help it learn about URLs but do not guarantee indexing Source: Google Search Central.
Assess uniqueness and searcher value
Compare each page with other site pages and current search results. Does it answer a distinct useful task with original information, evidence, experience or decision support? Is it a thin variation generated from a template?
Google notes that crawled pages may still not appear when there is insufficient value or user demand Source: Google Search Central. Its people-first guidance asks whether content is substantial and satisfying Source: Google Search Central.
Do not add filler merely to increase word count.
Reduce duplicate URL inventory
Crawl the site for filters, tags, internal searches, parameters, pagination, archives and campaign copies. Decide which should be indexed, canonicalised, noindexed or prevented from being created.
Large unnecessary inventories can consume server and crawl attention. Google recommends managing URL inventory and crawl priorities Source: Google Search Central.
Fix the system that produces duplicates rather than submitting individual URLs forever.
Check content publication quality
Confirm the page is complete, fact-checked, publicly useful and not an accidental placeholder. Remove lorem ipsum, empty filters, unavailable products and near-empty location pages.
Add clear authorship, primary sources, local context and update ownership where relevant. Make the title and opening accurately match the task.
Avoid publishing hundreds of pages before the template and evidence quality are proven.
Review site-wide quality patterns
Compare affected template, folder, date, author and content type with successfully indexed pages. Check whether the problem began after a release or rapid publication wave.
If many pages across the site decline, assess the whole site rather than editing one URL repeatedly. Check manual actions, security and spam issues.
Segment brand-new pages from previously indexed pages that disappeared.
Use indexing requests proportionally
After fixing a representative page, use URL Inspection to validate and request indexing where appropriate. Submit updated sitemaps. Avoid repeated daily requests for unchanged URLs.
Google cannot provide a guaranteed schedule for crawling or indexing Source: Google Search Central. Give systems time to process the fix and watch the page group.
Indexing APIs are limited to specified content types and are not a general solution for ordinary pages.
Monitor the cohort after release
Track discovery, crawl date, canonical selection, indexing, impressions and conversions for the affected cohort. Annotate fixes and compare similar pages.
Measure how many eligible URLs become indexed, not the total number submitted. Investigate new patterns and server logs.
Noindex or retire pages the business cannot maintain responsibly rather than treating index count as the goal.
My take: fix the page system, not the submission button
My take is that indexing problems often expose a publication system that creates pages faster than it creates distinct value, clean signals and internal support. The durable fix lives in templates, inventory and editorial criteria.
If your business needs a practical starting point, inspect ten excluded URLs from the same template and identify the first shared technical or value failure before editing them individually.
Frequently asked questions
Does discovered but not indexed mean Google penalised the page?
No. It can reflect crawl timing, capacity, inventory, duplication or value assessment. Diagnose the evidence.
Will submitting the sitemap again force indexing?
No. A sitemap helps discovery but does not guarantee crawling, indexing or ranking.
How long should a new page take to index?
There is no guaranteed timeline. Site signals, discovery, capacity and page value all affect processing.
Should I delete every unindexed page?
No. Improve necessary pages, consolidate duplicates and retire pages without a valid user purpose.
Make every indexable page earn its place
If your business needs a systematic diagnosis, get in touch for technical SEO and SEO content strategy.
Related guides
For further background, read our seo audit guide and search intent. The javascript seo glossary explains the terminology used in those guides.