Why Google delays indexing bottom-of-funnel pages on new SaaS sites
You launched. You submitted a sitemap. You waited. Your pricing page, use-case pages, and feature comparisons are still stuck in "Discovered – currently not indexed" while a blog post you threw together on day three is already showing in Search Console.
This isn't random. There are clear reasons Google treats transactional pages on new domains differently, and once you understand the pattern, you can work with it instead of against it.
The pattern you're probably seeing
Open Google Search Console on a domain that's less than 6 months old and sort pages by indexing status. The split usually looks something like this:
Gets indexed quickly
Stuck in discovered / not indexed
The pages you most want indexed the ones that convert are precisely the ones Google holds back longest on new domains.
Why Google holds back BOF pages on new domains
There are three overlapping reasons trust, intent signals, and crawl budget prioritisation. They compound each other.
1. Domain trust hasn't been established yet
The credibility gap
Google's crawl and indexing pipeline allocates resources based on how trustworthy and established it believes a domain to be. A new domain even one with a clean structure and fast load times has no track record. No inbound links from credible sites. No click-through history. No dwell time signals.
Informational content (guides, tutorials, glossaries) is lower-risk to index because it's harder to spam and less likely to mislead users into a bad purchase. BOF pages pricing, comparisons, "best X for Y" are exactly the pages black-hat SEO sites use to farm transactional traffic. Google is cautious by design, and new domains get the most scrutiny.
2. High-commercial-intent keywords are more competitive
The intent problem
Google processes intent before it considers whether to index a page at all. Pages targeting queries like "best AI customer support tool" or "ChatRAG pricing" compete in a space where users expect established vendors, G2 review roundups, and known brands. Serving a brand-new domain in those results is a quality risk Google isn't yet willing to take.
Contrast that with a query like "how does RAG work in customer support" that's an informational intent. Users aren't committing to anything. Google is happy to surface a thoughtful explanation from a new domain because the downside of a wrong answer is low. This is why your blog post about the concept outranked your pricing page it's not an accident.
3. Crawl budget prioritisation deprioritises thin pages
The budget problem
Google doesn't crawl everything on every visit. On new or low-trust domains, Googlebot allocates a small crawl budget and spends it on pages that look most valuable. Historically, that means pages with substantive text content, internal links pointing to them, and external links signalling they're worth reading.
A pricing page is often one or two short sections. A use-case page might be a hero, a feature list, and a CTA. By word-count and content-depth signals alone, these pages lose to your longform guides every time. Googlebot crawls the guide, sees value, comes back. It crawls the pricing page, sees thin content with commercial intent, and deprioritises it until trust is higher.
Real-world observations from early-stage SaaS sites
Sitemap submission doesn't accelerate BOF indexing. Submitting a sitemap tells Google the page exists it doesn't override the trust queue. Pages submitted via sitemap on day one of a new domain are still routinely left in "Discovered" for 8–12 weeks if the domain has no external signals. Informational pages from the same sitemap typically index within 7–14 days.
Crawl frequency is domain-level, not page-level. When you publish more content that gets crawled and indexed, Google revisits your domain more frequently. This indirectly benefits your BOF pages not because you tricked the algorithm, but because you raised the overall trust signal of the domain faster.
Internal links from indexed pages do accelerate BOF crawling. When an indexed guide links to your pricing or use-case page like how AI customer support works for SaaS teams, Google follows that link on its next crawl of the guide. This consistently cuts the "Discovered → Indexed" gap more reliably than any sitemap ping or manual URL inspection.
One legitimate external link can unlock a wave of BOF indexing. A single mention in a newsletter, a relevant Reddit thread, or a partner blog pointing to your homepage or a guide has been observed to move 3–5 previously stuck pages into the indexing queue within days. The external signal raises domain authority, and Google re-evaluates the queued pages.
What actually helped (and what didn't)
Based on patterns across early-stage SaaS domains. Your mileage will vary, but these observations are consistent enough to be worth knowing.
✓ What helped
Publishing substantive informational content first
Guides of 1,000+ words on problems your product solves built domain trust before the product pages needed it.
Linking BOF pages from every indexed guide
Adding a contextual internal link ("→ See how we handle this in our use-case overview") at the natural end of a section moved pages faster than any other tactic."
Getting one real external link early
A genuine mention a founder community post, a tool review, a newsletter inclusion acted as a trust unlock that rippled across stuck pages.
Using URL Inspection to monitor (not force)
Requesting indexing via URL Inspection occasionally helped but wasn't reliable. Using it to understand crawl status and spot errors was more valuable.
✗ What didn't help
Re-submitting the sitemap repeatedly
Submitting the sitemap a second or third time didn't change indexing speed at all. It's a signal, not a queue jump.
Adding more keywords to BOF pages
Stuffing more keyword variations into a pricing or use-case page didn't resolve the 'Discovered' status. Trust is the gate, not keyword density.
Creating low-quality articles just for volume
Publishing 10 thin posts to 'show activity' backfired. Googlebot crawled them, found low value, and this arguably slowed domain trust improvement.
Pointing paid social traffic at BOF pages
Traffic from ads doesn't contribute to Google's trust signals. Direct traffic has no meaningful impact on indexing speed.
Where to link your BOF pages naturally
The goal is to let already-indexed informational pages act as bridges to your commercial pages. Here's where those links land most naturally without feeling forced.
End of a how-to guide
If you're building a SaaS support workflow, see how teams use AI customer support agents for this in practice.
→ links to your use-case page
Comparison or "when to use X vs Y" post
If your team is already using documentation to answer support tickets, the use case for an AI support layer becomes obvious.
→ links to your feature or integration page
Glossary or definition page
"RAG-based support systems use retrieval to answer strictly from your content you can see what this looks like as a product."
→ links to your product overview or pricing
Problem-framing post (like this one)
"To see how one SaaS team approaches this for AI customer support specifically, the use-case breakdown gives a concrete example."
→ links to your BOF use-case or landing page
FAQ or community Q&A page
"Teams often ask whether AI support can replace human escalation here's the breakdown of how that actually works."
→ links to your product FAQ or feature comparison
The anchor text should describe what the person will find, not what you want to rank for. "How teams use AI for support" beats "best AI support chatbot" in every scenario on a new domain.
A realistic timeline for new SaaS domains
Information pages start indexing
Blog posts, guides, and definition pages begin appearing in Search Console as indexed. BOF pages show 'Discovered – not indexed'. This is normal.
Crawl frequency increases
If your informational content is substantive and linked internally, Googlebot starts revisiting your domain more often. You'll see crawl stats increase in Search Console.
First BOF pages enter the index
Usually the pages with the most internal links pointing to them and the highest word count. Often the product overview or a detailed use-case page rather than pricing.
Remaining BOF pages index as external signals grow
Once you have a handful of legitimate external links from communities, partners, or press the remaining stuck pages typically move within weeks.
The honest caveat: There is no guaranteed timeline. Domain age, niche competitiveness, content quality, and link acquisition all interact. What you can control is the sequence and the sequence above is the most consistent path.
The short version
Google delays BOF page indexing on new domains because it hasn't established trust in the domain yet not because your pages are broken.
Informational and experimental content indexes faster because the intent risk is lower and the content is harder to spam.
Crawl budget is allocated by trust level. More indexed content → more frequent revisits → faster BOF indexing.
Internal links from indexed pages to BOF pages is the most consistent lever you can pull directly.
One legitimate external link often unlocks a wave of indexing across previously stuck pages.
Re-submitting sitemaps, adding keywords to thin pages, and sending paid traffic to BOF pages don't move the needle on indexing speed.
Experiment updates (live observations)
Update (Day 20): This page was indexed within days of publishing, without backlinks or manual indexing requests. During the same period, multiple BOF pages on the same domain remain in“Discovered – currently not indexed”.
No structural SEO changes were made to BOF pages during this time. The only variable was publishing high-depth informational content and linking to BOF pages contextually.
This reinforces the hypothesis that Google establishes trust at the domain level using informational intent before allocating crawl priority to commercial pages.
Related reading
If this is the context here's what we're building
We ran into this exact indexing problem while building ChatRAG an AI support agent for SaaS teams that answers strictly from your documentation. Writing this guide was part of the strategy: earn trust with informational content, then let it carry the commercial pages. If you're curious what that looks like as a product, the use-case overview explains the approach without the sales pitch.