AI AI Tools Guidebook
Indie Dev & Website Building

Discovered Not Indexed: A Strategy Guide for New Indie Sites

Why Google leaves new indie-site URLs in the Discovered bucket and the multi-week strategy that actually moves them out — authority, internal links, content depth, and realistic timelines.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

You see “Discovered — currently not indexed” in Search Console and instinctively assume something is broken. It is not. The status means exactly what it says: Google learned about your URL (from your sitemap or a link) but has not bothered to crawl it. Here is why, and what actually moves URLs out of this bucket. (If you just want quick triage steps for the error, see Fix the Search Console error — quick triage.)

Background

There are two key Search Console “not indexed” buckets you must not confuse. “Crawled — not indexed” means Google read the page and rejected it. “Discovered — not indexed” means Google has not read it yet. The first is a quality verdict; the second is a priority decision driven by crawl budget and your site’s perceived importance. The fixes are completely different.

How to tell

  • Search Console says “Discovered — currently not indexed” for URLs that have been in your sitemap for over a week.
  • The URLs in question are real, valid, and on the same site as URLs that did get indexed.
  • Affected pages are newer or deeper in your site structure (more clicks from homepage).
  • You recently published 50+ pages and only a handful got picked up.

Quick verdict

This is not a technical problem; do not waste time on robots/sitemap/canonical tweaks. Treat it as a crawl budget + authority signal. Strengthen internal links to affected URLs, reduce thin / duplicate pages that are eating your crawl budget, and accept that for a new site it can take 4-12 weeks for the long tail to be crawled.

Step by step

  1. Confirm the URLs really are in this bucket. Open Pages report, click the row, copy 3 example URLs. Inspect each — the live test should pass with no issues.
  2. Check internal linking. In your codebase or with a crawler, count internal links to each affected URL. Anything under 2-3 inbound internal links is a Google signal that the URL is low priority.
  3. Audit thin / low-value URLs across the site. If your site spawns lots of nearly-empty pages (paginated archives, tag pages with 1-2 articles, near-duplicate templates), they are eating crawl budget that could go to your real content. Cull or noindex them.
  4. Improve discoverability: link to affected URLs from the homepage or a high-traffic article. The most efficient way to get Google to crawl a deep URL is to link it from a URL it visits often.
  5. For a small set (5-10) of important affected URLs, use URL Inspection -> Request indexing. This jumps the line for that URL specifically. Do not do this for hundreds at a time.
  6. Wait 30-60 days. New sites and large content additions take a real amount of time to clear. If after 60 days the bucket has not shrunk meaningfully, the issue is site authority — focus on inbound links and content depth.

Common pitfalls

  • Confusing this with “Crawled — not indexed”. They have different causes and different fixes. Read the bucket label carefully.
  • Re-submitting your sitemap daily. Sitemap submission does not influence crawl priority — internal links and external links do.
  • Spamming “Request indexing” on dozens of URLs. Google rate-limits and the long tail will not move.
  • Adding structured data hoping it changes priority. Structured data is about appearance, not crawl scheduling.
  • Panicking on a 30-day-old site. Brand-new domains routinely have most of their content sit in “Discovered” for 1-2 months while Google figures out if the site is worth crawling fully.

Who this is for

Indie content sites that just published a batch of articles and are watching only some get indexed. Also bloggers post-redesign or post-migration with new URLs.

When to skip this

If you are seeing this on URLs that returned 200 last week and 404 today, the bucket is misleading you — it is actually a redirect / 404 issue. Use URL Inspection live test to confirm.

FAQ

  • How long until Google crawls a “Discovered” URL?: For an established site: days to a week. For a new site: 2-8 weeks. For the long tail of a new site: sometimes 3+ months. Internal and external links accelerate it.
  • Is “Discovered — not indexed” worse than “Crawled — not indexed”?: Different problems. Discovered = priority issue. Crawled = quality issue. Discovered is usually easier to fix because the content might be fine — you just need to signal it is worth crawling.
  • Will increasing publishing frequency help?: Sometimes counterproductive. If you 10x output without 10x quality, your crawl budget gets spread thinner. Steady cadence + high quality + internal linking beats volume.
  • Can I force Google to crawl by submitting via IndexNow or similar?: IndexNow works for Bing and Yandex; Google does not use it. For Google, the practical levers are sitemap + internal links + URL Inspection requests for a small number of critical URLs.

Tags: #Indie dev #SEO #Google #Search Console #Indexing #Troubleshooting

Related Articles