A new SaaS website can be missing from Google for two different reasons: its important pages are not indexed, or they are indexed but do not appear for the searches you tried. Open Google Search Console and inspect the exact homepage URL before changing anything. A blocked page needs a technical fix; an indexed page needs a better match to the query. Neither indexing nor a ranking can be forced.
We run LaunchAF, which offers free founder tools, so weigh that accordingly. Google's documentation linked below was checked on October 23, 2026. Search Console labels and features can change; use the current report for your own property as the source of truth.
Key takeaways
- Check the exact URL in Search Console's URL Inspection tool. A Google search for your brand is not a reliable indexing report.
- Separate discovery, crawling, indexing, and ranking. Each stage has a different fix.
- A sitemap and a crawl request help Google find URLs; neither guarantees an index entry.
- Check robots rules,
noindex, canonicals, server responses, and rendered content before rewriting copy. - If the page is indexed, work on a specific searcher's problem and measure queries in Search Console instead of chasing one broad term.
First, find out: not indexed, or indexed but not ranking?
Set up a Search Console property for the domain and verify ownership. Inspect the precise URL you want people to find, including https, the host, and the final path. Search Console's URL Inspection help distinguishes the information Google has in its index from a live test of what it can fetch now. A live test that succeeds is useful, but it does not mean the page has already been indexed.
Look at Page indexing, Crawl allowed?, Indexing allowed?, Page fetch, and the Google-selected canonical. Then open the Page indexing report to see whether the same problem affects other important URLs. Do not treat every excluded URL as a defect: redirects, duplicates, and private pages often should stay out. Focus on your homepage, product page, and a small number of useful public pages.
| Symptom | What it tells you | Start here |
|---|---|---|
| URL Inspection says the page is not on Google | Diagnose discovery, access, noindex, canonical, or content issues | Fixes 1 to 7 |
| "Discovered - currently not indexed" | Google knows the URL but has not crawled it yet | Fixes 1 and 7 |
| "Crawled - currently not indexed" | Google fetched the URL but has not indexed it | Fixes 5 and 6 |
| A different URL is Google-selected canonical | Google is treating another version as representative | Fix 4 |
| URL Inspection says indexed, but your test query finds nothing | Indexing is not the same as ranking for that query | Fixes 8 and 9 |
Those two "currently not indexed" phrases are Google's report labels, not diagnoses of your copy. A page can also change state between the report's last update and a fresh inspection.
You can try site:yourdomain.com as a rough spot check, but do not count its results as your indexed-page total. Google's site: operator documentation says its results are not exhaustive and directs site owners to URL Inspection when a URL does not show. The exact URL in Search Console is the better starting point.
The 10 reasons a new SaaS site is missing from Google
1. Google has not discovered the page
Why it happens: A new domain may have no links from sites Google already crawls. Its key page may also be absent from navigation or a sitemap. Google says a new site with few external links is a case where a sitemap can help discovery, but even a submitted sitemap is only a hint.
How to check: Inspect the exact URL. If it is not known to Google, compare your live sitemap with the pages you actually want indexed. Click from the homepage to the product page using ordinary links. A form button that changes the screen without a crawlable URL is not a substitute for a link.
The fix: Add important public pages to a valid sitemap, submit it in Search Console, and link them from a sensible menu or related page. Google's sitemap submission guide describes the reporting you get after submission. A relevant external mention can also give Google another path to the site; it is not an indexing guarantee.
2. robots.txt blocks Googlebot
Why it happens: A staging rule such as Disallow: / can survive a production launch. It can also block only the folder containing your product pages, which is easy to miss if you check the homepage alone. Google's robots.txt guide explains that a disallow rule prevents crawling, not necessarily every appearance of a bare URL in search results.
How to check: Read yourdomain.com/robots.txt and inspect the affected page's "Crawl allowed?" field. Test the actual path and Googlebot user agent with our robots.txt tester. The tester evaluates rules you provide; it cannot see a private firewall decision or Google's crawl queue.
The fix: Narrow or remove the unintended rule, then live-test the URL in Search Console. Do not use robots.txt to hide a page you want Google to read, and do not assume removing a block makes indexing immediate.
3. A noindex instruction is still present
Why it happens: A site can return HTTP 200 and look perfect in a browser while its HTML says <meta name="robots" content="noindex"> or its response sends an X-Robots-Tag: noindex header. This often comes from a staging environment, CMS setting, or inherited template. Google's noindex documentation describes both supported forms.
How to check: Use URL Inspection's "Indexing allowed?" field, inspect the rendered HTML, and inspect response headers. Our free SEO checker reports the robots meta tag or X-Robots-Tag it observes along with status, canonical, and sitemap signals. It is a site snapshot, not a replacement for Google's own index data.
The fix: Remove noindex only from pages that should be public. Make sure Googlebot can crawl the page to see the change: Google's guide warns that blocking a URL in robots.txt can prevent the crawler from reading its noindex directive.
4. Google chose a different canonical URL
Why it happens: HTTP and HTTPS versions, www and non-www hosts, parameters, or nearly identical pages can split your signals. A canonical tag may point to an old staging domain or to a different product page. Google chooses a representative URL for duplicate content and treats your preferred canonical as a signal, not a command.
How to check: In URL Inspection, compare the user-declared canonical with the Google-selected canonical. Follow the URL through redirects and inspect the page source for a single sensible rel="canonical". Check that internal links and the sitemap use the same preferred URL. Google's canonical guidance recommends consistent internal linking.
The fix: Redirect deprecated variants to the preferred live URL, fix mistaken canonical tags, and align navigation and sitemap URLs. Do not add noindex to every duplicate merely to force your preference. Google may still choose a different canonical after the change.
5. The useful content is missing when Google renders the page
Why it happens: Google can render JavaScript, but a page that initially returns only an app shell may depend on a failing API call or a blocked script before its product explanation appears. Google's JavaScript SEO guide explains the crawl, render, and index stages and recommends crawlable links with href attributes.
How to check: Inspect the page with Search Console's live test and view the tested HTML or screenshot. Compare it with what a visitor sees. Are the product name, use case, pricing or access status, and primary link actually present? Check whether important JavaScript or API requests fail for a visitor without an account.
The fix: Put essential product facts in accessible HTML, fix the failed request, and link important pages with normal URLs. Server rendering or prerendering can simplify this, but a JavaScript site is not automatically unindexable. Avoid changing a noindex directive only after JavaScript runs; Google says it may skip rendering a page it has already seen as noindex.
6. Google crawled the page but did not index it
Why it happens: "Crawled - currently not indexed" is a status, not proof of a penalty. Google may decide not to index a page that adds little beyond another page, is mostly a signup wall, or cannot show its useful content after rendering. Google's Page indexing report says not every "Not indexed" URL is an error.
How to check: Inspect the live page and a comparable indexed page. Can a stranger learn something distinct from this URL without signing in? Is the answer to the page's main question visible, current, and specific? Check the Google-selected canonical before assuming the issue is quality; duplicate handling may explain the status.
The fix: Improve the page for its intended reader, remove near-duplicate versions, and connect it from a relevant page on your site. Do not manufacture a pile of keyword variants. If a page is deliberately private or redundant, leaving it out of the index may be correct.
7. The server or security layer interrupts Googlebot
Why it happens: A site can load for its founder yet return a 5xx error, redirect loop, login challenge, or bot-protection page to Google. Google's crawl troubleshooting guide names blocked content and site availability as reasons Google may miss pages.
How to check: URL Inspection shows "Page fetch" problems; the Page indexing report can show server and redirect errors. Check your server and CDN logs for the affected URL and user agent. A generic online fetch is useful as a comparison, but it cannot prove exactly what Googlebot received.
The fix: Correct the broken response, remove an accidental challenge on public pages, and make sure the final URL returns useful content. Retest in Search Console. If the host intermittently fails, fix reliability before requesting another crawl; repeated requests to an unstable page do not solve the underlying problem.
8. Almost nobody links to or mentions the new site
Why it happens: Google discovers URLs through links and sitemaps. Its sitemap overview specifically notes that a new site with few external links can be harder to discover. Even when indexed, a new page has little history or independent context for broad, competitive queries. That does not imply a special new-site penalty.
How to check: Review Search Console's indexed URLs and search queries alongside your actual public mentions. Can a buyer find an accurate reference outside your own site? Is the destination URL a working page? Separate a real published profile from a submission still waiting for review.
The fix: Earn a small number of relevant public references by helping a community, publishing a useful resource, or listing the product where its buyers browse. The first 100 backlinks guide treats this as relationship and asset work, not a bulk form-filling target.
9. The page is indexed, but the query is a poor fit
Why it happens: Indexing makes a page eligible for search; it does not make it rank for every phrase. "Project management software" is a very different task from "client approval workflow for a two-person design studio." A new SaaS page may answer the narrow question clearly yet never show in your own broad, personalized test.
How to check: If URL Inspection confirms indexing, open Search Console's Performance report. Look at the queries that actually generate impressions and the pages they reach. Search for the brand plus the domain to investigate name ambiguity, but do not interpret one manual search as a universal position.
The fix: Describe the product's category, buyer, and job in natural language. Build a useful page for a real question, with a title that says what that page offers. Our meta tag and SERP preview can help draft a title and description; it does not determine Google's indexing or guarantee how a snippet appears.
10. A security issue or manual action affects the site
Why it happens: This is less likely for an ordinary new SaaS than a crawl or indexing issue, but it is worth checking, especially on a previously owned domain. Search Console's Manual actions report covers human-reviewed spam-policy actions. Its Security Issues report covers signs of hacking or harmful behavior.
How to check: In Search Console, open Security & Manual Actions, then each report. Google says it sends messages for detected manual actions. An empty report is useful evidence against this specific explanation; it does not certify that every page deserves a ranking.
The fix: If a report names an issue, follow its own remediation instructions and request review where that report offers it. Do not send a reconsideration request for a normal "Crawled - currently not indexed" status; that status alone is not a manual action.
How long does Google take?
Google's recrawl documentation says crawling can take days to weeks and explicitly says a request does not guarantee inclusion. Its crawling and indexing FAQ does not promise when or whether an individual URL will be indexed. A founder who publishes on Monday should not treat a missing Tuesday result as proof something is broken.
After fixing a blocker, request indexing once and monitor it. Google says repeated recrawl requests for the same unchanged URL will not get it crawled faster. For a group of pages, submit a clean sitemap and link the pages from relevant places on your own site. Those steps improve discovery, not certainty.
Record the change date and last crawl date so you do not judge a fresh fix against an older crawl. Once indexed, shift attention to query and page fit.
How do links and launch listings help a new site get found?
A public listing can make a new URL easier to discover and give a buyer another way to encounter the product. A relevant mention from a community, partner, or editor has a reason to exist beyond its link attribute. Google's documentation describes links as one discovery path; it does not promise that one link, including a followed directory link, will index or rank a page.
Choose places whose readers might use your SaaS. Our free launch-platform comparison explains differing review, queue, and badge conditions. A reviewed LaunchAF submission is one possible public profile, but the free route requires a badge and review and currently shows a 35-to-40-day expected publication window at submission. It is not a quick indexing fix.
The directory SEO guide explains why mass-submitting to weak listings is different from earning useful references. Google's spam policies include low-quality directory links among link-spam examples. Prioritize accurate descriptions and a reachable product page over the number of submission receipts.
A 14-day plan
These days are a work schedule, not a prediction of when Google will index you.
| When | What to do | What to record |
|---|---|---|
| Days 1 to 2 | Verify Search Console, inspect the homepage and one product page, record their index status and Google-selected canonical | Exact URLs, current status, last crawl |
| Days 3 to 4 | Fix robots.txt, noindex, redirects, server errors, or missing rendered content if inspection revealed them | Change date and before/after live test |
| Days 5 to 6 | Publish or correct the sitemap; link important pages from navigation and relevant body copy | Submitted sitemap URL and key internal paths |
| Days 7 to 9 | Rewrite one weak page to answer one real customer question; make the title and visible copy agree | Query, page URL, original and revised promise |
| Days 10 to 12 | Seek a few genuine references from relevant communities, partners, or reviewed listings | Public URLs, not merely submitted forms |
| Days 13 to 14 | Reinspect the URLs, compare last crawl dates, and review early impressions without claiming causation | Remaining blocker and the next sensible check |
If Search Console already confirms that your key page is indexed, skip the technical repair days. Spend them talking to customers about the words they use and making the page useful for one of those searches.
What not to do
- Buy links or an "indexing service" that guarantees Google inclusion or a ranking.
- Submit the same vague description to hundreds of unrelated directories.
- Show Googlebot a different page from the one a person sees, or hide keyword text from visitors.
- Keep clicking "Request indexing" on an unchanged URL and call it an SEO plan.
- Turn a deliberate privacy page into a public page simply to increase your indexed count.
Frequently asked questions
How long does it take Google to index a new website?
Google gives no guaranteed indexing date for a new website. Its recrawl guidance says crawling may take days to weeks, and a crawl request does not guarantee inclusion. Inspect the exact URL in Search Console and fix a documented blocker before worrying about a calendar estimate.
Why is my SaaS site indexed but not ranking?
An indexed SaaS page is eligible to appear, but it may not answer the query you tested as well as other pages. Check its actual impressions and queries in Search Console, then compare the page's promise and content with the searcher's need. A broad query with strong competitors is not a useful pass-or-fail test for a new product.
Does submitting a sitemap guarantee indexing?
Submitting a sitemap does not guarantee that Google will crawl or index every listed URL. Google calls sitemap submission a hint and says internal and external links are other discovery paths. Keep the sitemap accurate, then use URL Inspection to diagnose important pages individually.
Is there a Google sandbox for new sites?
Google has not documented a special "sandbox" rule that every new SaaS must wait out. Its indexing FAQ says newness itself commonly explains why a site has not been indexed yet, and that timing depends on several factors. Check the evidence in Search Console rather than assuming a hidden penalty.
Can a launch-platform backlink help Google find my site?
A live link on a public launch profile can be another path by which Google discovers a new SaaS URL. It does not force indexing, ranking, or referral traffic, and a submitted but unpublished listing is not a backlink. Choose a relevant audience and verify the live page after publication.
Why does my site show in Google but not in ChatGPT?
Google indexing and appearances in ChatGPT answers are different processes. A site can be indexed in Search and still be absent from one AI answer or prompt. Our ChatGPT visibility guide explains that separate diagnosis; the Claude, Gemini, and Perplexity guide covers their different search experiences.
The bottom line
Do not fix a ranking problem as if it were an indexing problem, or vice versa. Open Search Console, run URL Inspection on your exact homepage URL, and write down what it says. Then run the free SEO checker for a second look at the page's access and metadata signals, fix the first real blocker, and recheck after Google has had a chance to crawl the change.