Search Console: 11 pages discovered, 0 indexed after 7 weeks. What's the usual cause?

by


I launched a small price-comparison site at the end of July. It tracks current catalogs of guitar models from a handful of major brands and matches them against new stock at independent dealers — roughly 1,250 models across 11 URLs (a home page with the comparison table, five brand pages, and the usual about/methodology/legal pages). Static HTML, no client-side framework. The one rule I built it around: no synthetic data — if a price can't be kept fresh, it links out to a search instead of showing a number I made up.


Build side works. Discovery doesn't. Seven weeks in, a site: query returns nothing and Search Console shows 11 pages "Discovered — currently not indexed" with 0 indexed. The sitemap was read successfully and all 11 URLs were discovered from it, so Google has known they exist since July.


What I've checked so far: robots.txt allows everything and points at the sitemap; canonicals are self-referencing; meta robots is index, follow; a Googlebot user agent gets a 200 with fully server-rendered HTML (the home page is ~17k characters of visible text with 100 rows rendered). Sitemap lastmod follows the data sync date rather than the deploy, and the last data sync was July 26.


Four things I can't tell apart:


  1. Age and links. The domain is 7 weeks old with essentially no external links, and Google has known all 11 URLs since it first read the sitemap in July. Is "Discovered — currently not indexed" just Google deprioritizing a linkless new domain, or does that bucket usually hide a technical reason?

  2. Content shape. Most pages are one table template repeated 88–449 times with different rows. Every value is real, but is "same shape, different data" the pattern Google discounts as thin content? Would you split it into one page per model, or does that turn into a doorway site by definition?

  3. Rendered vs. interactive. Each table server-renders 100–150 rows and filters the rest client-side. Does content behind a filter count for anything, or is what I render the whole story?

  4. Freshness. My lastmod follows the data sync rather than the deploy, so it has sat unchanged since July 26. Does a static lastmod actually hold back recrawling?


Beyond the sitemap and Search Console, I haven't done anything else to push it — there are no links from anywhere real yet. How much of this is just that?


If you've launched a large generated-content site on a fresh domain, I'd love to know what actually moved the needle for you.


20 views

Add a comment

Replies

Best

I don't think any of the four is the cause. The answer is in your own post: there are no links from anywhere real yet, and seven weeks is nothing for a domain with no authority. Sitemap tuning won't change that.

I don't think discovery is the problem here. Eleven pages on a new domain with nothing pointing at them look optional to Google, so it just parks them, and no amount of on-page cleanup moves that. What moves it is other people linking to you or actually searching for those models.

I would just adding 1,250 model pages just to create more indexable URLs. That might multiply the same problem rather than solve it. Your five brand pages already have a clear purpose, so strengthening their unique usefulness seems safer. Could adding model specific insights inside those pages give Google more distinct content?