2,000 pages “Discovered — currently not indexed”: not a technical bug
Diagnosing a programmatic-SEO indexation problem as crawl budget and authority, and the recovery plan that followed.
For a Dubai real estate platform, we built an Astro programmatic-SEO site of about 2,200 city and property pages in 7 languages. A few weeks later, Search Console showed roughly 2,000 of them as "Discovered — currently not indexed."
The first reaction on any team is to look for a technical fault: a stray noindex, a bad canonical, a broken sitemap. I checked all of those. They were fine.
What "Discovered" actually means
"Discovered" means Google knows the URL exists but hasn't decided it's worth crawling yet. That's not a rendering or markup problem. It's a question of priority, and two things drive it:
- Crawl budget. A young domain that suddenly publishes thousands of URLs doesn't get thousands of crawls.
- Authority. If the pages have few internal links pointing at them and similar content, Google has little reason to prioritise them.
The recovery plan
Internal linking. Every property page linked to its city, every city linked to its neighbours, so no page was more than a few clicks from the homepage.
Hub pages. City and area hubs that actually aggregate useful content, giving crawlers a clear path and giving deep pages inherited importance.
Locale parity. Each of the 7 locales had the same structure and correct hreflang pairs, so translations reinforced each other instead of looking like duplicates.
The lesson
When thousands of pages aren't indexed, check the technical basics first, but don't stop there. With programmatic SEO the bottleneck is often whether Google thinks the pages matter, not whether it can read them.