Discovered, currently not indexed means Google found your URL, usually in your sitemap or through a link, and decided not to crawl it yet. No fetch happened. Google has not read the page, judged it, or rejected it. The page is in a queue, and on a new site with little authority that queue can hold a URL for weeks. It is the most common status on freshly launched vibe coded sites, and it is also the most misread, because owners treat it as a verdict on the content when Google has not seen the content. This article explains why the crawl gets postponed, what actually moves a page up, what people do that changes nothing, and how to tell when the status is hiding a different problem.
Why Google delays the crawl
Google's own explanation is that the page was found but the crawl was postponed because fetching it might overload the site, or because the site is not yet important enough to justify the crawl. For a small site on a fast host, overload is never the reason. Priority is. Google assigns a crawl budget by how much it trusts the domain and how often the domain produces pages worth fetching. A brand new domain with twenty URLs in a sitemap and no links from anywhere has almost no budget, so the homepage gets crawled and the rest wait their turn.
Three things make the wait longer on AI-built sites specifically.
- The sitemap is often the only path to the page, because the builder wired the navigation with buttons and click handlers instead of anchor links. Google found the URL in a list, not on a page it trusts.
- The sitemap has no lastmod dates, or every date is the same, so Google cannot tell which pages changed and has no reason to prioritise any of them.
- The site has dozens of near-identical pages, such as a location page per city with the same paragraph, which tells Google the rest of the queue is probably not worth the trip. Every thin page you add lowers the priority of the good ones.
Confirm it is really this status
Open Google Search Console, go to Pages under Indexing, and click the row that says Discovered, currently not indexed. The list shows every affected URL and the date Google last checked. Then paste one of those URLs into URL Inspection at the top of the screen. The result should say URL is not on Google, with Crawl showing no crawl date and Indexing showing the discovered status. If instead you see a crawl date, the page has moved to a different status since the report was generated, and you should read that status instead. The report lags the inspection tool by days.
While you are in URL Inspection, read two more lines. Referring page tells you where Google found the URL. If it says the sitemap and nothing else, the page has no internal links Google knows about. User-declared canonical should be the page itself. If it points somewhere else, stop here and read the section at the end about hidden faults.
What actually moves a page up the queue
- Link to it from pages Google already crawls. Your homepage is crawled first and most often. A real anchor link from the homepage to the waiting page is the strongest signal you can send. Check it is an a tag with an href, not a button. View Page Source on the homepage and search for the path; if it is not in the file, the link does not exist as far as Google is concerned.
- Request indexing in URL Inspection. Paste the URL, wait for the check, click Request Indexing. This puts the page in a priority queue. It is rate limited, so use it on the pages that matter, not all fifty. One request per page is enough; repeating it does nothing.
- Give the sitemap a lastmod date for that URL and set it to the day you last changed the page. Google reads lastmod. It ignores priority and changefreq, so do not bother with those. Resubmit the sitemap in the Sitemaps report after the change.
- Cut the pages that do not deserve a crawl. If you have thirty thin pages that say the same thing, Google spreads its small budget across all of them. Remove or merge the weak ones and the strong ones get fetched sooner. Return a 410 or 404 for the removed URLs and take them out of the sitemap.
- Get one link from another site. A directory listing, a partner, a supplier page, a local association. A single mention from a real website in your field does more for crawl priority than anything you can do inside your own domain, because it is the signal Google uses to decide the domain is worth budget at all.
A correct sitemap entry looks like this. The date is the thing that matters.
<url>
<loc>https://yourdomain.com/services/pricing</loc>
<lastmod>2026-09-12</lastmod>
</url>What does nothing
Clicking Validate Fix on the status report does nothing on its own. Validation asks Google to re-check the URLs over the following days and weeks, and it reports Passed when Google confirms a page is now indexed, but it does not force the crawl. That is why people see Validation passed on some URLs and the rest still sitting in Discovered: the ones that passed were crawled in the normal course of things, the ones that did not were never fetched. Validation is a progress bar, not a lever.
The Indexing API is not a route either. Google only honors it for job posting and broadcast event pages, and requests for ordinary pages are ignored. IndexNow pings Bing and Yandex, and Google does not read it. Resubmitting the same sitemap five times a day does nothing, because the file has not changed. Adding the page to Google Business Profile, posting it on social media, or buying an indexing service does not force a crawl; the last of those is a bot that clicks Request Indexing for you.
The recipe for a stuck page, in order
- Add a text link to the page from the homepage or the main navigation, with anchor text that describes the page.
- Add a link from the two most related pages on the site, inside the body text.
- Set the page's lastmod in the sitemap to today and resubmit the sitemap.
- Request indexing once in URL Inspection.
- Check the Pages report again in ten days. Not tomorrow. The report will not have moved.
Stuck in Discovered for more than a month?
Send me your sitemap URL and your Search Console Pages screenshot. I will tell you whether it is a link problem, a budget problem, or a content problem, and what to change this week.
When it is not a queue problem
If the page has been in Discovered for more than two months, has a homepage link, and has been requested twice, look harder. Sometimes the status is hiding a different fault. A page whose canonical points at the homepage will never leave the queue, because Google already has the URL it thinks is the original and has no reason to fetch a declared copy. A page on a site that returns a 200 for made-up paths may be lost among thousands of soft duplicates that all look equally unimportant. Both are covered in Why is Google not indexing my pages?. And if your site was built with Lovable before May 2026, check which rendering stack you are on first, because on the older build Google may be discovering a URL whose only content arrives after JavaScript, and it will not spend budget on a page whose stored copy is an empty shell.
One more thing. Discovered is a much better status than Crawled, currently not indexed. Discovered means Google has not read the page yet. Crawled means it read the page and walked away. If you are in Discovered, the page still has every chance, and the fix is links and patience rather than a rewrite.
Questions people also ask
Is Discovered, currently not indexed a penalty?
No. It is a scheduling status. Google has recorded the URL and not fetched it. Penalties appear under Manual Actions in Search Console, and this is not one.
Why does validation say Passed but the page is still not indexed?
Validation reports on the sample of URLs Google happened to recrawl. Passed applies to the URLs that were fetched and indexed in the normal course of crawling. The rest were never fetched, and validation has no way to make Google fetch them. Use the five levers above instead.
Will Discovered, currently not indexed go away on its own?
On an established site, usually yes, within a few weeks. On a new domain with no links, it can sit indefinitely, because nothing ever raises the page's priority. Add the links and it moves.
Does the status affect the pages that are already indexed?
No. It says nothing about the indexed pages. It does say something about the site's crawl budget, and a long list of Discovered URLs is a hint that the site has more pages than Google thinks it needs. Cutting thin pages helps the whole site.
Should I delete pages stuck in Discovered?
Only if they do not deserve to exist. A page that answers a real question and is linked from the homepage should stay. A page that was generated to fill out a menu and says nothing specific should go, and removing it speeds up the rest.
