Why Google won’t index your SaaS site, and how to fix it

Crawling and indexing are different steps

Google first has to crawl a page, which means fetching it. Only then does it decide whether to index it, which means storing it so it can appear in results. A page can be crawled successfully and still be excluded from the index. When Search Console reports a problem, first work out which of the two steps failed.

The URL Inspection tool shows both. Look at whether crawling was allowed, whether the page fetch succeeded, and whether indexing was allowed. The answer to the last question is where most launch-week problems show up.

Cause 1: a leftover noindex directive

Many frameworks and hosting templates ship with search indexing switched off for staging and preview builds. That is sensible before launch, but the setting is easy to forget. If your page sends a robots meta tag or an X-Robots-Tag header containing noindex, Google and Bing will crawl the page and then refuse to index it.

Check the live page, not your local build. View the page source and search for name="robots". Check the response headers for X-Robots-Tag. If either says noindex, change the production setting, redeploy and confirm the live response has changed before asking for indexing again.

Cause 2: Google last saw a redirect

If your domain pointed at a registrar parking page or another host before you connected it, Google may have recorded the old redirect. Search Console then reports the page as a page with redirect. That status describes the last crawl, not necessarily what your site does today.

Once the domain serves your site directly, run Test live URL. If the live test passes, request indexing and Google will replace the old record on its next crawl.

Cause 3: robots.txt blocks the page

robots.txt controls crawling, not indexing. Blocking a page there does not reliably keep it out of results, and it stops search engines from reading a noindex directive on that page. Use robots.txt to keep crawlers away from areas such as APIs, and use noindex for pages you want excluded.

Open yourdomain.com/robots.txt and make sure your public pages are not disallowed. A single Disallow: / line blocks the whole site.

Cause 4: no sitemap, or an empty one

A sitemap lists the URLs you want discovered. New sites have few inbound links, so the sitemap is often the main way search engines find pages beyond the homepage. Some setups generate an empty sitemap while indexing is disabled. Check that yours lists real, canonical URLs that return HTTP 200.

Reference the sitemap in robots.txt with a Sitemap: line and submit it in Search Console and Bing Webmaster Tools.

Cause 5: duplicate hostnames

If www.yourdomain.com, yourdomain.com and your hosting provider’s default address all serve the same pages, search engines see duplicates. Pick one origin. Permanently redirect the others to it and point every canonical tag at it.

A launch-day indexing checklist

Run through this list on the live production URL after every domain or hosting change:

• The page returns HTTP 200 on your chosen origin, and other hostnames redirect to it.
• No robots meta tag or X-Robots-Tag header says noindex on pages you want listed.
• robots.txt allows those pages and links to your sitemap.
• The sitemap lists only canonical, indexable URLs.
• Each page has a self-referencing canonical URL, a unique title and a description.
• Search Console’s live test passes before you request indexing.

Indexing is not ranking

Getting indexed makes a page eligible to appear. It does not guarantee traffic. Requests are not instant either: Google decides when to recrawl, and new sites often wait days or weeks. Ranking depends on whether your pages answer what people search for, which is why useful content matters once the technical basics are in place.

Reachlora’s website audit checks up to three public pages along with robots.txt and your sitemap, and records the evidence behind each recommendation. It is a quick way to catch these problems before you start marketing.