Indexation for SaaS marketing sites
Written by Olayinka Olayokun·Published ·Updated ·Verified
Indexation for SaaS is the discipline of getting Google to fetch, render, and keep a marketing URL in its index — diagnosed primarily through Search Console's Pages report and URL Inspection tool.
Summary and key takeaways
Indexation failures hide in Search Console's two worst-named buckets: 'Discovered — currently not indexed' (Google saw the URL, didn't fetch it) and 'Crawled — currently not indexed' (fetched, rejected). On a typical SaaS site, 30–60% of published pages sit in those two buckets at any time. The fix is rarely new content — it's removing the friction Google flagged.
- •Search Console → Pages is the authoritative indexation report — third-party tools approximate it.
- •'Discovered — currently not indexed' usually means thin content, an orphan URL, or a crawl-budget constraint.
- •'Crawled — currently not indexed' usually means duplicate content, thin content, or quality signals below threshold.
- •URL Inspection's 'View tested page → Rendered HTML' is the ground-truth check for what Google actually sees.
- •A clean sitemap (only canonical, 200-status, indexable URLs) is the single fastest indexation lever on a young SaaS site.
In plain English ·SaaS indexation is the practice of using Search Console's Pages report and URL Inspection tool to find which marketing URLs Google has refused to index and why. The two highest-leverage buckets are 'Discovered — currently not indexed' and 'Crawled — currently not indexed'; together they explain most missing pages on a B2B SaaS site.
- 30–60%
- Share of published pages sitting in 'Discovered/Crawled — not indexed' on a typical SaaS site SERPNAUT playbook
- 1–7 days
- Typical indexation lag for an internally-linked new page after URL Inspection submission Search Console help
How this compares
| Bucket in Search Console | What it means | Most common SaaS cause | Fix |
|---|---|---|---|
| Discovered — currently not indexed | Google saw the URL, didn't fetch | Orphan page, no internal links from strong pages | Link from home or top-traffic page; submit URL Inspection |
| Crawled — currently not indexed | Fetched, judged not worth keeping | Thin content, duplicate of another page | Add entity coverage, remove duplication, re-submit |
| Page with redirect | URL redirects but is in sitemap | Stale sitemap entry | Remove from sitemap; ship 301 to canonical |
Part of the Technical SEO for SaaS: The Founder's Checklist guide
Indexation for SaaS is the discipline of getting Google to fetch, render, and keep a marketing URL in its index — diagnosed primarily through Search Console's Pages report and URL Inspection tool.
Most SaaS sites publish content into a system that silently drops 30–60% of it. The drop is invisible in analytics (no impressions, no clicks, no traffic) and visible only in Search Console. Fixing indexation is the highest-leverage technical SEO move on a young SaaS site because every published page becomes eligible for the rankings the content was always going to earn — without writing anything new.
What this chapter covers: pages report, url inspection, sitemap hygiene, internal-link signal, re-submission.
Read Search Console → Pages first
Open Search Console → Indexing → Pages. The top number ('Indexed') is what's currently visible to Google. Below it sits a table of 'Why pages aren't indexed' with named buckets — 'Discovered — currently not indexed', 'Crawled — currently not indexed', 'Duplicate, Google chose different canonical', 'Excluded by 'noindex' tag', and a handful of others.
Open Search Console → Indexing → Pages. The top number ('Indexed') is what's currently visible to Google. Below it sits a table of 'Why pages aren't indexed' with named buckets — 'Discovered — currently not indexed', 'Crawled — currently not indexed', 'Duplicate, Google chose different canonical', 'Excluded by 'noindex' tag', and a handful of others.
Sort by bucket size. The two largest buckets on a typical SaaS site are the two with the worst names — Discovered and Crawled. Together they explain most of the gap between 'pages I published' and 'pages Google ranks'.
'Discovered — currently not indexed' diagnosis
Google found the URL (usually via sitemap) but didn't bother fetching it. On a SaaS site under 5,000 URLs, this is almost never a crawl-budget problem — it's a signal-quality problem. Google sees no reason to spend a crawl request on the page.
Google found the URL (usually via sitemap) but didn't bother fetching it. On a SaaS site under 5,000 URLs, this is almost never a crawl-budget problem — it's a signal-quality problem. Google sees no reason to spend a crawl request on the page.
Fix order: (1) Link the URL from at least two existing high-traffic pages with descriptive anchors; (2) Re-submit via URL Inspection; (3) If still unindexed at day 14, expand the page's entity coverage — Google's preview of the URL has to look more valuable than the alternatives in its queue.
'Crawled — currently not indexed' diagnosis
Google fetched the page, looked at it, and decided not to index. On SaaS sites the cause is almost always one of three: thin content (under ~300 words of unique copy), near-duplicate of an existing page (often a programmatic landing-page template), or boilerplate-heavy (header/footer/CTA dominate, unique body is minimal).
Google fetched the page, looked at it, and decided not to index. On SaaS sites the cause is almost always one of three: thin content (under ~300 words of unique copy), near-duplicate of an existing page (often a programmatic landing-page template), or boilerplate-heavy (header/footer/CTA dominate, unique body is minimal).
Open URL Inspection → View tested page → Rendered HTML and read what Google actually saw. If 70% of the rendered HTML is the same as another rejected page, you have duplication. If the unique body is two short paragraphs, you have thinness. Both are content fixes; neither is fixed by re-submitting.
Sitemap as an indexation lever
Sitemap. xml should contain only canonical, indexable URLs that return HTTP 200. Including 404s, redirects, noindex pages, or alternate-language duplicates trains Google to treat the file as unreliable — and to ignore the URLs that do deserve indexing.
Sitemap.xml should contain only canonical, indexable URLs that return HTTP 200. Including 404s, redirects, noindex pages, or alternate-language duplicates trains Google to treat the file as unreliable — and to ignore the URLs that do deserve indexing.
Re-generate the sitemap automatically from the CMS or routing layer, not by hand. Hand-maintained sitemaps drift within weeks. Verify quarterly by crawling the sitemap with Screaming Frog and filtering anything non-200 or noindex.
The checklist for this chapter
- ✓Search Console → Pages reviewed weekly; bucket sizes tracked over time
- ✓Every 'Discovered — not indexed' URL linked from at least two high-traffic existing pages
- ✓Every 'Crawled — not indexed' URL diagnosed via URL Inspection rendered HTML view
- ✓Sitemap auto-generated and filtered to canonical, indexable, 200-status URLs only
- ✓URL Inspection 'Request Indexing' submitted within 48 hours of publishing any new commercial page
- ✓Quarterly Screaming Frog crawl of the sitemap to catch drift
- ✓Indexation rate (indexed URLs ÷ submitted URLs) tracked monthly — target >85%
Where this chapter sits in the guide
rendering — a page Google can't render correctly is also a page it can't index. Read the javascript rendering for saas: ssr, ssg, and the empty-shell bug chapter →
every other discipline — content without indexation produces zero ranking signal. Read the related guide →
Search Console's Pages and URL Inspection — third-party crawlers approximate; only GSC is authoritative. → Google Search Console
ranking — indexation is the precondition for ranking, not a ranking factor itself. → Search engine indexing
the Googlebot crawler, which decides what to fetch and re-fetch on its own schedule. → Googlebot
Quick answers about saas indexation: why your pages aren't in google
- Why are my SaaS pages not getting indexed?
- The two most common causes on a B2B SaaS site are (1) thin or boilerplate-heavy pages Google fetched and rejected ('Crawled — currently not indexed') and (2) orphan URLs Google discovered via sitemap but never bothered fetching ('Discovered — currently not indexed'). Both surface in Search Console → Pages, and both are fixable without new content.#
- Does a small SaaS site need to worry about crawl budget?
- Sites under ~5,000 URLs almost never hit crawl-budget limits. If you have 200 pages and Search Console shows 'Discovered — currently not indexed', the cause is signal quality, not crawl budget. Don't waste a sprint optimising for crawl budget you don't have.#
- How long should I wait before a new page is indexed?
- Submit the URL in Search Console URL Inspection within 48 hours of publishing. Indexation typically lands in 1–7 days when the page is internally linked from a high-traffic existing page; 2–4 weeks when it's orphaned. Pages still unindexed at day 30 are flagged by Google for a reason — diagnose, don't wait.#
- Can I force Google to index a page?
- No, but you can stack signals: submit via URL Inspection, link from at least two high-traffic pages on the site, ensure the page is in sitemap.xml, and check it has unique entity coverage Google can't find on a stronger page. If those four are true and Google still rejects it, the page is thin — the answer is depth, not pressure.#
Questions about saas indexation: why your pages aren't in google
- Paste the URL into Search Console URL Inspection. The status panel shows 'URL is on Google' or 'URL is not on Google' plus the last crawl date and any blocking reasons. The `site:` operator in Google itself is faster but less reliable — Search Console is authoritative.
- Search Console Pages report buckets and their meanings. Google — Page indexing report
- Crawl budget guidance from Google for large sites. Google Search Central — Crawl budget
- URL Inspection tool for live indexation diagnosis. Google — URL Inspection tool
This chapter is one node in the founder-led playbook. To see which nodes your specific URLs are bleeding traffic from, get a founder-grade SEO audit of your URLs. Same six disciplines, applied to the pages you actually own.
Related concepts
Adjacent entities this chapter touches on. Each is a separate concept worth knowing even if it isn't a chapter on its own.
- Crawl budget
- The number of URLs Googlebot will fetch per site within a given window. Rarely the bottleneck below ~5,000 URLs on a SaaS site.
- noindex meta tag
- The per-page directive that keeps a fetched URL out of the index. The correct tool for hiding thin pages — robots.txt does not deindex.
- IndexNow
- A URL-change ping protocol supported by Bing and Yandex but ignored by Google. Marginal benefit for a SaaS site under 5,000 URLs.
- Sitemap protocol
- The XML schema Google uses to discover canonical URLs. A clean sitemap is the single fastest indexation lever on a young SaaS site.
What's changed on this page
- First published with the Discovered vs Crawled diagnostic framework and the >85% indexation-rate target.
- Added Search Console URL Inspection screenshots and clarified the difference between crawl budget and signal quality on sub-5,000-URL sites.
- Added Googlebot and Google Search Console as named entities in the predicates and added neighbouring-concept block (noindex, robots.txt, IndexNow).
Olayinka Olayokun
Founder, SERPNAUT and Invoicemonk
Written by Olayinka Olayokun. I run SERPNAUT, a founder-led SEO service for B2B SaaS, and Invoicemonk, the SaaS I grew from zero to 300+ organic visits and a paying customer in 28 days using the same playbook. Everything below is what worked on my own URLs and on the audits I've shipped since.
More chapters in this guide
Indexation is the precondition for everything downstream — ranking, traffic, conversion. Get the Pages report clean before investing in topical authority work; otherwise every cluster you ship inherits the same indexation drag. The next cluster covers rendering, which is the most common cause of the indexation problems this chapter diagnoses.
See the full guide at technical seo for saas: the founder's checklist. The commercial bridge above is the canonical path from this chapter to your URLs.