--- title: "SaaS Indexation: Why Your Pages Aren't in Google" description: "How to diagnose and fix the 'Discovered — currently not indexed' and 'Crawled — currently not indexed' buckets that swallow most B2B SaaS pages before they ever rank." url: "https://serpnaut.xyz/playbook/technical-seo-for-saas/indexation-for-saas" verifiedAt: "2026-06-09" canonical: "https://serpnaut.xyz/playbook/technical-seo-for-saas/indexation-for-saas" --- # SaaS Indexation: Why Your Pages Aren't in Google > TL;DR — 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. 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. ## Key takeaways - 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. ## Definition 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. ## Why it matters 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. ## 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. 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. 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). 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. 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. ## Quick answers ### Why are my SaaS pages not getting indexed? (https://serpnaut.xyz/playbook/technical-seo-for-saas/indexation-for-saas#qa-not-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? (https://serpnaut.xyz/playbook/technical-seo-for-saas/indexation-for-saas#qa-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? (https://serpnaut.xyz/playbook/technical-seo-for-saas/indexation-for-saas#qa-how-long) 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? (https://serpnaut.xyz/playbook/technical-seo-for-saas/indexation-for-saas#qa-force-index) 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.