How to Get a SaaS Site Indexed by Google

To get indexed by Google, a page needs to be reachable, allowed, linked from somewhere Google can crawl, and good enough for Google to want to keep. Submitting a URL in Search Console can prompt a crawl, but it doesn't force indexing. So if pages on your SaaS site aren't indexed, find out which of those four conditions is failing, and fix that.

Google says plainly that it doesn't guarantee to crawl or index every page. Having some pages left out is normal, particularly thin or duplicate ones. Your goal is for every page that matters to be in, with no concern about the rest.

Start by finding out what's actually happening

Open Search Console. If you haven't set it up, do that first and add a domain property, which covers every subdomain and protocol. That matters for SaaS sites, since a blog or docs site may sit on its own subdomain.

Then use two reports:

• URL Inspection tells you about a single URL: whether it's indexed, when it was last crawled, and which canonical Google chose.
• Page indexing tells you about the whole site: which URLs are in, which are out, and why.

Don't rely on a site: search. It can be useful for a quick look, but it isn't a complete or accurate count of what's indexed.

What each status means and what to do

The reason Search Console gives determines the fix, so read this before you change anything.

Status	What it means	What to do
Discovered - currently not indexed	Google knows the URL but hasn't crawled it yet	Improve internal links, and check for floods of junk URLs
Crawled - currently not indexed	Google read the page and didn't keep it	Improve the page, merge it, or accept it
Excluded by "noindex" tag	The page asks to be left out	Remove the tag if that's wrong
Blocked by robots.txt	Google can't crawl it	Fix the rule if the page should be crawled
Alternate page with proper canonical tag	Another page is the main version	Usually correct
Duplicate, Google chose different canonical than user	Google disagreed with your choice	Check your signals
Soft 404	The page looks empty or like an error	Add real content, or return a true 404
Page with redirect	The URL redirects elsewhere	Expected for old URLs
Not found (404)	The page doesn't exist	Fine if deliberate, otherwise fix links or redirect
Server error (5xx)	Your server failed when Google visited	Check logs and hosting

Say you run a 12-person SaaS that sells appointment software, and your new "for physiotherapists" page isn't showing up. If it's "Discovered", Google hasn't bothered to fetch it, so the page probably needs links. If it's "Crawled", Google fetched it and chose not to keep it, so more links alone may not help, and you need to look at the content.

Fix the access problems first

Access problems are the most damaging, and they're usually the fastest to fix.

Stray noindex tags. Check for tags left over from staging, or a CMS setting left on. Our meta robots guide covers where they hide, including HTTP headers.

Robots.txt blocks. A rule intended for your app, such as Disallow: /app, can also match paths such as /app-integrations. Search Console's robots.txt report shows what Google fetched.

Firewall and bot protection. Security rules can block or challenge Googlebot, so that it gets an error or an interstitial. Your browser won't show this. Use the live test in URL Inspection to see what Google receives.

JavaScript-only content. If your page sends an empty shell, Google has to render it to see anything, and rendering failures can leave the page looking empty. JavaScript SEO for React and Next.js shows how to test this.

Login walls. Google generally can't crawl behind a login. Public docs behind an authentication check, for instance, won't be indexed, even if you assumed they would be.

A wrong canonical. A template pointing everything at the homepage tells Google that those pages are duplicates. See our canonical guide.

Help Google find the page

Google mainly finds pages through links. If a page has none, submitting it in a sitemap might get it discovered, but it sends a weak signal about its importance.

Add internal links from strong pages. A new use-case page should be linked from your solutions menu, related feature pages and relevant blog posts. This is usually the single most useful thing you can do, since it costs nothing and helps with both discovery and importance. Avoid orphan pages, those with no internal links at all. Look at our internal linking strategy.

Keep your sitemap clean. Include only canonical, indexable URLs that return a 200. A sitemap full of redirects teaches Google not to rely on it. Our XML sitemap guide has the details, including how to submit it.

Use URL Inspection to request indexing for a handful of important pages after publishing. It's useful for the odd page, but it's limited, and it doesn't scale. Repeated requests for the same URL won't speed anything up.

Earn some external links. For a new domain, even a few relevant links, such as from a partner or a directory listing, help Google to find your site and decide it's worth visiting. See SEO for a brand-new SaaS domain.

When the problem is quality

"Crawled - currently not indexed" is the status that frustrates people most, as there's no setting to change. It often means that Google doesn't see enough value in keeping the page. That's a particular risk for SaaS sites with sets of programmatic pages.

Going back to the appointment software company: suppose it generates 200 pages, one per profession, swapping only the profession's name. Google might index a few, then ignore the rest. That's a reasonable response, since the pages say nearly the same thing. Here are the options:

• Add something specific to each. Real workflows, terminology, integrations or templates relevant to that profession.
• Consolidate. Keep the 20 that you can make truly useful, and redirect the others.
• Publish in stages. Launch fewer, confirm that they're indexed and useful, and then add more. Our programmatic SEO guide covers this.

Be aware of the wider risk. Google's scaled content abuse policy covers large volumes of low-value pages, however they were made. Quality problems in one area can also affect how your site's other pages are treated.

A page can also be good and just duplicative. If you have three posts on one topic, Google might only want one. Merging them may help more than improving each. It's worth remembering that sometimes a page is unindexed because it doesn't need to exist.

How long does indexing take?

There's no fixed time. A well-linked page on an established site can be indexed quickly, whereas a page on a new domain may take much longer. If a page has been out for several weeks, it's better to investigate than to wait, and the status will tell you where to look.

For posts in particular, see how to get new SaaS blog posts indexed faster.

A routine that catches problems early

Add three small habits to your release process:

1. After each launch, inspect your new pages about a week later.
2. Each month, read the page indexing report for changes, and check that your money pages haven't moved to "not indexed".
3. After each deployment, run an automatic check that your pricing and main feature pages return a 200 with no noindex. Accidental noindex is a serious problem, and it's cheap to detect.

Indexing also matters for AI search. Google says that a page has to be indexed and eligible to appear with a snippet to be shown as a supporting link in its AI features, so this work comes before any AI optimization.

If your indexing report keeps surprising you, book a call with Comppound and we'll look at it with you.