New Website Not Ranking on Google? A Practical 30-Day Fix Plan

A three-month-old SaaS site can have a submitted XML sitemap and still show “not indexed” pages in Google Search Console—the practical situation discussed in the Reddit thread that prompted this guide. If your new website not ranking on Google, this workflow helps you identify whether the problem is discovery, indexing, or rankings, then gives you a concrete 30-day plan for fixing the real bottleneck.

Google finding a URL, adding it to its index, and ranking it for a useful query are three different outcomes. Sitemap submissions and indexing requests can help discovery, but they do not create page-one rankings. Google’s SEO Starter Guide says its recommendations can make it easier for search engines to crawl, index, and understand content; it does not promise rankings, and helpful people-first content still has to compete with other results.

Start by separating discovery, indexing, and ranking

The phrase “my website is not ranking” often hides three different issues:

1. Google cannot discover the URL. The page may not be in the XML sitemap, have no crawlable internal links, or be unavailable to Googlebot.
2. Google discovered the URL but did not index it. Search Console may show statuses such as “Crawled - currently not indexed” or “Discovered - currently not indexed.”
3. Google indexed the URL but ranks it poorly. The page can be on Google yet receive few impressions, rank beyond page 5, or fail to appear for the query you expected.

This distinction changes the fix. In the Reddit example, the site was a new SaaS website around three months old and Search Console showed pages as not indexed. That is first an indexing diagnosis, not proof that the site has a ranking problem.

Before changing titles, building backlinks, or repeatedly requesting indexing, choose five representative URLs: the homepage, one product or feature page, one pricing page, one article, and one excluded page. This small sample is enough to reveal whether a site-wide template or architecture problem is affecting the whole site.

Use Google Search Console URL Inspection first

Google’s official URL Inspection tool documentation describes it as a way to inspect a page’s indexed version and test a live URL. Inspect each of your five sample URLs, then record what Search Console actually reports rather than relying on a Google search alone.

For every URL, record these five details:

• Whether the URL is currently in Google’s index.
• Whether Google can crawl the live URL.
• The last crawl date, if Search Console provides one.
• Your declared canonical and Google’s selected canonical.
• The exclusion reason, warning, or failure shown for that page.

“URL is on Google” means Google has indexed that URL. It does not mean the page ranks for your preferred keyword, in your country, or on every device. A site: search for a distinctive URL fragment can be a rough secondary check, but URL Inspection is the stronger page-level diagnostic.

If a page is not indexed, do not assume the Request indexing button is the remedy. Google’s documentation presents it as a way to ask for a recrawl after a meaningful fix, not a guarantee of inclusion. Request it once after resolving the underlying issue; repeated requests do not make blocked, duplicate, thin, or poorly connected pages more useful.

For a broader walkthrough, see our guide on how to index your website and get new and updated pages found.

Check the XML sitemap, but only include indexable canonical URLs

Google’s sitemap guidance describes sitemaps as a way to tell Google about pages and files you think are important. A sitemap is a hint, not an instruction to index every listed URL or rank it above competitors.

In the Sitemaps report in Search Console, check these specifics:

• Does the submitted sitemap load successfully?
• Does its URL count look plausible for the public site?
• Are the important canonical URLs present?
• Are redirects, error pages, staging URLs, parameter URLs, or noindex pages included by mistake?
• Does the sitemap use the same preferred URL format as navigation and canonical tags?

For a new SaaS site, the sitemap may include the homepage, product pages, feature pages, public comparison pages, and substantive articles. Include documentation and help pages only when they are public, useful to searchers, intended to rank, and self-canonical. Private docs, login-only pages, duplicate installation instructions, internal release notes, and deliberately noindex support content should not be added just because they exist.

For example, /features/automation?source=nav should normally not be in a sitemap if its canonical is /features/automation. List the final 200-status canonical URL, and use that same version in internal links.

Sitemap monitoring can tell you when a URL already present in a monitored sitemap is added, removed, or changed. It cannot identify a valuable URL that your CMS never put into the sitemap. To catch that separate omission, reconcile a product-content inventory—such as your CMS export or release checklist—against the sitemap at least once per month.

Resolve crawl and indexing exclusions before chasing rankings

Search Console’s Page indexing report groups URLs by indexing status and exclusion reason. Labels can change, so use the live explanation in Search Console and inspect a representative URL rather than treating any label as a permanent diagnosis.

Common technical causes

These are common reasons website pages are not indexing:

• `noindex` directives: Check both the meta robots tag and the HTTP X-Robots-Tag header. A template setting can accidentally exclude an entire page type.
• Robots.txt blocking: If you block Google from crawling a page you want indexed, Google may be unable to evaluate its content properly.
• Redirects and 404s: Sitemaps should list final, live, 200-status canonical URLs—not redirects, removed pages, or soft 404s.
• Canonical conflicts: Google may choose another canonical when pages are substantially similar or when sitemap, internal-link, and canonical signals disagree.
• Server and rendering failures: A 5xx response, timeout, login wall, or broken JavaScript rendering can prevent reliable crawling.

“Crawled - currently not indexed” does not mean Google is waiting for another submission. It means Google crawled the URL but did not index it at that time. Our recommendation is to review unique value, query purpose, internal links, and duplication before asking for another crawl.

Ten city pages where only the city name changes are often less useful than one substantial service-area page with local examples, pricing context, FAQs, and original proof. That is a content and site-quality problem, not merely a submission problem.

Build internal links that show Google which pages matter

Google’s SEO Starter Guide recommends making links crawlable and using descriptive anchor text. In practice, a valid sitemap with no meaningful internal links leaves both users and crawlers with weak signals about which pages matter most.

Start with core commercial pages. A SaaS homepage should normally link to its principal product, feature, use-case, pricing, and public documentation pages. Supporting articles should link back to a relevant product or feature page where that connection genuinely helps the reader.

Use this internal-link checklist:

• Link to each priority page from at least one crawlable, indexed page.
• Use descriptive anchor text, such as “automated sitemap monitoring,” instead of repeating “click here.”
• Avoid burying priority pages four or five navigation levels deep.
• Add contextual links in relevant articles, not only footer links.
• Repair links that point to redirects, removed URLs, or non-canonical parameters.

For example, an article about publishing new landing pages can link to a feature page about monitoring sitemap changes. That gives readers a useful next step and makes the topical relationship clearer than a generic homepage link.

Our guide on automatically submitting new pages to Google without chasing every URL explains how URL discovery operations fit alongside, rather than replace, sound site architecture.

If pages are indexed, diagnose why they rank poorly

When Search Console confirms that a URL is indexed, stop treating indexing as the primary issue. In the Performance report, filter by that page and review impressions, clicks, queries, average position, country, device, and a date range long enough to contain useful data.

Three patterns are especially useful:

1. No impressions: The topic may have little search demand, Google may not see the page as relevant yet, or the page may be new and weakly connected.
2. Impressions but few clicks: The title, snippet, query match, or search-result competition may be limiting clicks.
3. Impressions with positions around 30, 50, or lower: Google is associating the page with queries, but competing pages may better satisfy intent or have stronger evidence and authority.

Do not overread average position. It is an aggregate across queries, devices, locations, and individual ranking events. Instead, identify the actual queries producing impressions and compare your page with the first 5 to 10 results for those queries.

A product page targeting “best CRM for agencies” competes with review sites, established vendors, comparison content, and list articles. A page that only says “our CRM is great for agencies” may be indexed but fail to meet the research-heavy intent. It may need agency workflows, a comparison table, pricing clarity, implementation details, case studies, and an honest explanation of who should not choose it.

Match search intent with useful, original content

Google’s SEO Starter Guide emphasizes helpful, reliable, people-first content. Our practical test for SEO for a new website is simpler: can the page complete the searcher’s job better than a generic summary or a competitor’s existing page?

Search the target phrase before optimizing. Classify the result page: product pages, how-to guides, categories, templates, local listings, videos, or comparison articles. Those result types are evidence of what Google currently interprets as the likely intent.

Improve the page, not just keyword placement

For each priority URL, review these elements:

• Primary intent: Is the query informational, commercial, transactional, or navigational?
• Specificity: Does the title and opening section answer the main job clearly?
• Original evidence: Can you add screenshots, workflows, data, customer outcomes, or expert explanation?
• Completeness: Does the page cover the decisions a visitor needs to make?
• Readability: Do useful headings, descriptive titles, and clear navigation make the answer easy to scan?

Avoid publishing 20 shallow posts for slight variations of the same phrase. One strong guide on sitemap monitoring should not become five near-duplicates for “XML sitemap checker,” “sitemap monitor,” and “monitor XML sitemap” unless each page serves a materially different search intent.

Content quality is not a fixed word count. A definition might need 600 useful words; a competitive “best software” query may need original research, comparisons, and ongoing maintenance. What varies is the level of evidence needed to be more useful than the pages already ranking.

Build authority with relevant links and real proof

Backlinks are not the first fix when pages are blocked, noindexed, or absent from internal navigation. Once the technical foundation and intent match are sound, however, a new domain often needs external signals before it can compete for difficult searches.

For a SaaS company, relevant links and mentions can come from integration directories, partner pages, industry newsletters, practitioner communities, podcasts, original research citations, and tools people voluntarily reference. The useful question is not “how many links?” but “would this audience plausibly use this reference?”

Avoid buying large volumes of irrelevant directory links. A small number of editorially relevant references to genuinely useful pages can be more valuable than a large volume of links with no audience fit.

Also build proof on your own site: a real company page, contact details, transparent pricing where appropriate, support and security information, product screenshots, customer examples, and author information for expert-led content. None guarantees rankings, but each gives users more reason to trust a young site.

Use submission and monitoring tools within their real limits

Manual requests in Search Console and sitemap submission are appropriate ways to surface newly published or materially updated public pages to Google. For ongoing operations, tools can reduce the chance that a change in a sitemap goes unnoticed—but they cannot determine whether a page deserves indexing or rankings.

There is an important Google-specific limit. Google’s Indexing API documentation restricts API use to pages with JobPosting structured data or BroadcastEvent pages embedded in a VideoObject for livestreams. It is not a general-purpose API for ordinary SaaS feature pages, blog posts, documentation, or comparison pages.

Indexa can monitor a sitemap locally for additions and updates, and it can notify IndexNow-supported search engines such as Bing through their supported endpoints. For ordinary Google web pages, use a submitted sitemap, crawlable internal links, and Search Console’s manual request where appropriate. Indexa should be treated as operational discovery support, not as a Google ranking promise or a workaround for Google’s API eligibility rules.

For the distinctions between submission routes, read Submit URL to Google and Bing: Search Console vs IndexNow.

A 30-day SaaS plan: work from a release inventory, not just a sitemap

A standard technical checklist is useful, but new SaaS sites commonly fail at the handoff between publishing and SEO. The sharper workflow is to trace one real release from source to search visibility: planned URL, production URL, canonical, internal link, sitemap entry, Search Console status, impressions, and the query it should answer.

Imagine a SaaS launches /features/automated-reporting on day 8. The page is live and canonical, but the CMS sitemap has not refreshed. On day 10, the page has no navigation link, so it is neither in the sitemap nor supported by internal links. A sitemap monitor cannot see that missing URL; the release inventory can. Add the canonical URL to the sitemap, link it from the feature hub and one relevant article, then inspect it in Search Console.

Days 1-3: Establish facts

Inspect five representative URLs in Search Console. Create a spreadsheet with one row per URL and columns for release source, sitemap presence, canonical, internal links, indexing state, target query, and next action. Label each row as a discovery, indexing, or ranking issue.

Days 4-10: Fix technical and architecture blockers

Remove unintended noindex directives, correct robots.txt rules, replace redirecting sitemap URLs, and align canonicals. Reconcile the sitemap with your CMS or release inventory so you can find pages never added to the sitemap, then add contextual links from the homepage, navigation, and relevant articles.

Days 11-20: Improve three high-value pages

Choose three pages with clear business value. For each, inspect the current search results and write down the dominant intent, missing decision information, and one original proof element to add. For the automated-reporting page, that could mean a workflow screenshot, supported data sources, export limits, a comparison with manual reporting, and a use-case example for an agency.

Days 21-30: Measure and choose the next bottleneck

Review Search Console impressions, query matches, and indexing status. Publish one useful supporting asset, such as a template, benchmark, checklist, or comparison, and promote it to a relevant audience. Then decide based on evidence: fix crawl coverage if pages remain undiscovered, improve value if pages are excluded, or improve intent match and authority if indexed pages receive impressions without competitive positions.

FAQ

Why is my new website not ranking on Google?

A new site may not be discoverable, may be excluded from Google’s index, or may be indexed but not considered the best result for its target queries. Start with URL Inspection in Google Search Console, then check canonical URLs, sitemap coverage, internal links, keyword intent, content quality, and relevant backlinks in that order.

Why are my website pages not indexing?

Common causes include noindex directives, robots.txt blocks, redirects, soft 404s, canonical conflicts, server errors, weak internal links, and pages Google considers duplicative or low value. Use URL Inspection and the Page indexing report to find the reason attached to a specific affected URL before submitting another indexing request.

How can I check whether Google has indexed my pages?

Use URL Inspection in Google Search Console for the strongest page-level answer. It reports whether Google has indexed the URL and can show crawl, canonical, and indexing details. A site: query can provide a quick clue, but it is not a complete or authoritative replacement for Search Console data.

How do I get a new website to rank?

First make priority pages crawlable, canonical, present in the sitemap where appropriate, and linked internally. Next, build pages that match the actual intent behind the target query and include original evidence competitors lack. Then earn relevant mentions and links through useful resources, partnerships, and visible expertise in your market.

What should I do if my sitemap is submitted but my pages still do not rank?

A submitted sitemap is a discovery hint, not a ranking lever. Confirm indexing with URL Inspection. If the page is indexed, use Search Console Performance data to identify the queries generating impressions, compare the page with current results, improve intent match and content quality, and strengthen internal links and relevant authority signals.