All posts

Not on Google? Here is why.

Website not showing up on Google? The cause can usually be found with Google’s own free tools: a tag that tells Google not to index your pages, a crawl block, a site that is too new, or pages Google sees as duplicates or too thin. Here is how to diagnose it and fix it properly.

For businesses Google
cannot seem to find.

Find the cause. Then fix it.

Website not showing up on Google: the short answer and the fix

A page can only appear in Google after three things happen: Google finds the address, crawls the page and decides to add it to its index. When your website is not showing up, one of those steps has failed or has not happened yet. Ranking comes after that, and it is a separate problem.

The quickest way to find out which step failed is Google Search Console, the free tool Google provides for site owners. Its Page indexing report lists every known URL that is not indexed, with a reason, and the URL Inspection tool shows how Google sees one specific page. Most causes become visible quickly once you look there.

The usual culprits are mundane: a noindex tag left over from development, a robots.txt rule that blocks crawling, a site that is simply too new, content that only appears after scripts run, or pages Google considers duplicates or too thin. Each has a specific fix.

  • New site: verify it and submit a sitemap.
  • Noindex tag: remove it from pages that belong in search.
  • Robots.txt block: allow crawling of the pages that matter.
  • Duplicates: one canonical address per page, redirect the rest.
  • Thin pages: give each a distinct purpose and real content.

Live for months. Still invisible?

Why a perfectly good website can stay invisible in search

Most owners notice it indirectly. A customer says they could not find you, or a search for your company name shows directories and social profiles but not your own site. The site works fine in the browser, so nothing looks wrong.

The underlying issue is that a website can look complete to people and still send the wrong signals to a crawler. A setting meant to keep the test site private went live with the real one. The text only appears after scripts run, so the crawler receives an almost empty page. Or several versions of the same page exist, with and without www or with tracking parameters, and Google spends its attention on the copies.

There is also a quality threshold: Google does not promise to index every page it finds. Service pages that repeat the same text with a different city name, or product pages copied from a supplier, often end up crawled but not indexed. Nobody receives an error message, so the problem can persist for months.

Start with access. Not with guesses.

What you need before you diagnose indexing problems

The essential step is verifying your site in Google Search Console. A domain property, verified with a DNS record, covers every version of your domain at once: http and https, with and without www, and any subdomains. If you cannot edit DNS, a URL prefix property verified with an HTML tag or file also works, but it only covers that exact version of the address.

You will also need access to whatever controls the technical setup: the content management system, the hosting or deployment platform and the domain’s DNS settings. Many indexing fixes are a single setting or a single line, but someone has to be able to change it.

Finally, list the pages that matter most: usually the home page, each service or product category, the contact page and a few articles that answer real questions. Not every URL on a site deserves to be indexed, so start with those.

  • Owner or full user access to Google Search Console.
  • Access to the CMS, the hosting platform and the DNS settings.
  • The current robots.txt file and XML sitemap, if they exist.
  • Bing Webmaster Tools too: other search engines and AI tools keep their own indexes.

Crawl, render, then index.

How crawling, rendering and indexing work, and where each one breaks

Crawling is controlled by robots.txt, a plain text file at the root of your domain that tells crawlers which paths they may fetch. A common misunderstanding is that blocking a page there keeps it out of search. It does not reliably do that: Google can still index the address if other pages link to it, just without reading its content. To keep a page out of the index, it must be crawlable and carry a noindex directive.

Indexing is controlled per page, by a robots meta tag in the HTML or an X-Robots-Tag header sent by the server. Many platforms offer a single checkbox, often labelled something like “discourage search engines”, that adds noindex to every page. Canonical tags tell Google which address is the main version of a page, and Google treats them as a strong hint rather than a command. When the canonical points somewhere unexpected, the page you care about may be passed over.

Rendering is where modern sites often slip. If the server sends an empty shell and the text is assembled by JavaScript in the browser, Google has to render the page before it can read it, which can be delayed and occasionally fails. Server rendering or static generation puts the full content in the first response, which is also what many AI crawlers need, since a lot of them do not run scripts at all.

Status codes matter too. A missing page should return a 404, not a friendly message with a 200 status, which Google reports as a soft 404. Redirects should point straight at their final destination, and pages behind a login are never indexed.

Fix it once. Then keep watching.

A step-by-step process to get your website indexed by Google

Begin with the Page indexing report in Search Console and group the URLs that are not indexed by reason. Ignore those meant to be excluded, such as redirects and admin pages, and focus on the pages that should be in search.

Use the URL Inspection tool on each important page. It shows whether the page is indexed, which canonical Google selected and, through the live test, what the rendered HTML looks like to Googlebot. If the rendered page is missing your main text, the problem is rendering, not content.

Fix causes in order of impact: site-wide blocks first, then individual pages, then quality. After a fix, request indexing for a few key URLs and submit an XML sitemap that lists only live, indexable addresses. Reprocessing can take days or a few weeks, so validate the fix in the report and give it time.

Pages reported as discovered or crawled but currently not indexed rarely need a technical fix. They need a reason to exist: distinct content, a clear purpose and internal links from relevant pages. Merging several weak pages into one strong page often works better than rewriting each of them.

How we approach it.

How Walhallah handles indexing as part of agentic search optimization

We start with a technical SEO and indexability audit: what Google has indexed, what it skipped and why, checked against the pages your business actually depends on. That tells us whether the issue is a setting, the way the site is built or the content itself, and we say so plainly when the fix is small.

Where the cause sits in the build, our engineers fix it at the source: server-rendered pages, correct status codes, one canonical address per page, clean sitemaps and structured data that matches what is on the page. Where the cause is content, we work on clear service pages and an information architecture that search engines and AI assistants can understand and verify. Technical SEO and structured data are also part of every website we build, so indexing is designed in rather than repaired later.

Questions. Answered.

How long does it take for a new website to show up on Google?

There is no fixed time. A new site with a verified Search Console property, a submitted sitemap and a few links from other websites is often discovered within days, but indexing every page can take weeks. If nothing is indexed after a few weeks, check for blocking settings instead of waiting longer.

Why does Google show my business profile but not my website?

Your Business Profile and your website are indexed separately. A profile can appear in maps and local results while the site itself is blocked, new or not seen as relevant for that search. Link the website from the profile and check the site in Search Console to see whether its pages are indexed.

Does requesting indexing guarantee my page will appear in Google?

No. Requesting indexing asks Google to crawl the page sooner, but Google still decides whether to index it, and being indexed is not the same as ranking. Use it after a real fix, for a handful of important pages, rather than as a routine step for every update.

Is a site: search a reliable way to check if my pages are indexed?

It is a useful first check, but the results are approximate and incomplete. For a definitive answer on one page, use the URL Inspection tool in Search Console. For the whole site, use the Page indexing report, which also tells you why pages were left out.

My website is indexed but does not rank. What should I do?

Then the problem is relevance and competition rather than indexing. Check which searches your pages already appear for in the Performance report, and make each page answer one clear question better than the competing results. That is ongoing SEO work rather than a technical fix.

Hard to find? Let’s fix that.

Tell us what you’d like to build or improve.