Guide · Google
Why Isn't My Website Showing Up on Google?
Your website doesn't show up on Google, even for your own business name. Find which of six causes it is, with a one-minute check for each: not indexed yet, a setting that blocks Google, pages Google can't find, a page that's empty until JavaScript runs, a name shared with someone bigger, or a site that's indexed but ranks low.
Updated 11 min read

On this page
- First: is it missing, or just low?
- Cause 1: Google hasn't found or indexed it yet
- Cause 2: A setting tells Google to stay out
- Cause 3: Google can't find the rest of your pages
- Cause 4: The page is empty until JavaScript runs
- Cause 5: Your name is shared with someone bigger
- Cause 6: It's indexed, it just ranks low
- The checks, in one table
- What the free audit checks
- FAQ
In short
- First find out which problem you have. A
site:search is a 10-second test of whether Google has your site at all, or has it and ranks it low.- A site Google doesn't have is usually new, blocked by one setting, or hard for Google to read. Each has a one-minute check below.
- A site Google has but nobody finds is a ranking problem. For a local search the map comes first, and the map is built from Google profiles, not websites.
You type your business name into Google and your website isn't there. Or you search "plumber in Walnut Creek" and get every company but yours. Those feel like the same problem, but they aren't, and the fix for one does nothing for the other.
This guide walks through the causes in the order worth checking them. Each one has a check you can run in about a minute with a web browser. Where Google documents the behavior, the guide links to it.
First: is it missing, or just low?
Search Google for site: followed by your domain, with no space: site:yourbusiness.com.
- No results at all: Google most likely doesn't have your site. Start with cause 1 and work down.
- Some results: Google has your site. If your homepage is listed but your service pages aren't, go to cause 3. If they're all there, skip to cause 5.
Google notes that site: doesn't necessarily list every indexed page and doesn't rank the results. It's a quick test, not a full count. For a definite answer about one page there's Google Search Console, which cause 1 shows how to set up.
Cause 1: Google hasn't found or indexed it yet
A brand-new site, or a new domain for an old business, starts with nothing. Google says crawling can take anywhere from a few days to a few weeks, and in its own words, Google doesn't guarantee that it will crawl, index, or serve your page.
The one-minute check. How long has the site been live at this address? If it's days or a few weeks and site: shows nothing, this is the likely cause. Run the cause 2 check anyway: it takes a minute, and a new site can be blocked too. If it's been months, something is more likely keeping Google out.
The fix.
- Put your website address on your Google Business Profile and your other listings, so there are links pointing Google to it.
- Ask Google directly. In Search Console, paste your homepage address into URL Inspection and click Request indexing. Do it once: Google says there's a quota, and asking again for the same page doesn't get it crawled faster.
- Submit your sitemap in Search Console (cause 3 covers sitemaps).
Search Console's page indexing report may list pages as Discovered, currently not indexed (Google found them but hasn't crawled them yet) or Crawled, currently not indexed (Google crawled them and hasn't indexed them). Google's report guide says a page that isn't indexed is not necessarily a problem. If it's your homepage, though, keep reading: the causes below are what to rule out.
Cause 2: A setting tells Google to stay out
This is the first thing to rule out on a site that's been live for a while, and the easiest to fix. Two settings do it.
A noindex tag. A line in the page's code, <meta name="robots" content="noindex">, tells Google not to list the page. It's Google's own tool for keeping a page out of search, and it works exactly as designed when it's left on by mistake.
WordPress has a box for it: Settings, then Reading, then "Discourage search engines from indexing this site." When it's checked, current versions of WordPress add a noindex tag to every page. Developers often switch it on while building a site, and nobody switches it off at launch.
A robots.txt block. The file at yourbusiness.com/robots.txt tells crawlers which pages they may read. Two lines block everything:
Google says robots.txt is not a way to keep a page out of Google: a blocked page can still be listed, just without a description. But a file that blocks the whole site keeps Google from reading anything on it, and a noindex tag on a blocked page is never seen at all.
The one-minute check.
- Open
yourbusiness.com/robots.txtin your browser. Look forDisallow: /on its own underUser-agent: *orUser-agent: Googlebot. Other lines in the file can override it, so treat it as a lead and confirm with step 3 before you change anything. - Open your homepage, view the page source (in Chrome, Ctrl+U on Windows or Option+Command+U on a Mac) and search it for
noindex. The one that counts sits in a<meta>tag namedrobotsorgooglebot. - If you've set up Search Console, URL Inspection names a noindex or a robots.txt block when either is the reason. It also catches a noindex sent in the page's headers, which view source can't show.
Cause 3: Google can't find the rest of your pages
Sometimes the homepage is indexed and your service pages aren't. Google finds pages by following links and reading sitemaps.
Links. Google says it can generally only crawl a link if it's a real <a> element with an href. A menu that opens pages with a script, and no actual link, can leave whole sections unfound.
Sitemaps. A sitemap lists the pages you want found. Google says a site of about 500 pages or fewer that links all its important pages may not need one, and that a site on WordPress, Wix or Blogger has likely had one made for it already. You can name it in your robots.txt with a Sitemap: line, which is how Google and other crawlers find it without being told.
That line can go stale. A site moves to a new builder or a new plugin, the sitemap moves, and robots.txt keeps pointing at the old address.
The one-minute check.
- Open
yourbusiness.com/robots.txtagain and find theSitemap:line. Open that address. It should load a list of your pages, or a list of smaller sitemaps that lead to them, not an error. NoSitemap:line isn't a problem by itself. - From your homepage, click through to each service page using only your menu and your page links. If you can't reach a page that way, Google may not either.
- If you've set up Search Console, open Sitemaps and check that yours was read without errors.
Cause 4: The page is empty until JavaScript runs

Some sites send an almost empty page and fill in the text with JavaScript after it loads. Google can read those pages: it renders them in a second step, which can take longer.
AI search is a different story. When Vercel and MERJ tracked the crawlers behind ChatGPT, Claude and Perplexity in late 2024, none of them ran JavaScript.
The one-minute check. View your page source and search it for a few distinctive words you can see on the page. If they aren't there, the page is built in the browser by JavaScript. To see what Google ends up with, use the live test in Search Console's URL Inspection.
The fix. Ask whoever built the site to put the text in the page the server sends. They'll call it server-side rendering or pre-rendering. Some site builders already do it: Lovable says its hosting sends fully rendered pages to search engines and AI crawlers.
Cause 5: Your name is shared with someone bigger
If site: shows your pages but a search for your business name doesn't, check whether your name collides with something else: a national brand, a common phrase, or a business with a similar name in another state.
To see how often a business is missing from a search for its own name, we checked 76 US home-service businesses in eight metro areas in October 2026. We searched Google for each business's name, with the search set to its own city (nationwide for the three whose city we couldn't tell).
25 of 76
businesses didn't have their own website in the top 10 website results for their own name. Signs of a name mix-up were much rarer: Google suggested a different spelling for 2 of the 76 (one only dropped an apostrophe), and showed another business's panel for 1.
So a third of this sample wasn't in the top 10 for its own name, and a shared name is only one explanation. A franchise whose head office outranks it looks the same from the outside, and so does a site Google has little to go on. These are the signs that it's the name.
The one-minute check. Search your exact business name, then your name plus your town.
- Does Google say Did you mean or Showing results for a different name? Google is treating your name as a typo.
- Is the business panel Google shows someone else's?
- Does a business with a very similar name, in your area or another state, take the top results?
The fix. Make your name unmistakable everywhere Google reads it. Use your full business name and your town in your homepage title. Keep your Google Business Profile name exactly as on your signage. Declare your name and type in your structured data (see Which schema type should your business use?) and link your Google profile and other listings from it.
Cause 6: It's indexed, it just ranks low

If Google has your site and shows it for your name, but not for "water heater repair" or "electrician near me", the site isn't missing. It's being outranked.
For local searches, the map pack usually comes first, and it's built from Google Business Profiles. Google says local results are based mainly on relevance, distance and how well-known a business is: how well your profile matches the search, how far you are from the searcher, and prominence, which Google ties to things like how many reviews you have and how many websites link to you.
That's ranking work, not a technical fix, and it's a separate guide:
- How Google ranks the local pack, and where your profile fits.
- Google search optimization for local businesses, for the website side.
Being indexed only means Google knows your site exists. Being found means ranking near the top against every other business nearby.
The checks, in one table
| What you see | Likely cause | One-minute check |
|---|---|---|
site: search shows nothing, new site | Not indexed yet | How long has the site been live? |
site: shows nothing, site has been live for months | noindex or robots.txt block | View source for noindex; open /robots.txt |
| Homepage indexed, service pages aren't | Pages Google can't reach | Open the Sitemap: link; click through your menu |
| Visible text missing from page source | Page built by JavaScript | View source; search it for words from the page |
site: works, name search doesn't | Name shared with someone else | Search your name; look for "Did you mean" |
| Found for your name, not for your services | Ranking, not indexing | Check your Google profile and local pack position |
What the free audit checks
The free audit runs several of these checks on your homepage for you. It flags a noindex tag, a site that doesn't answer crawlers, a missing sitemap, and a sitemap link in robots.txt that leads nowhere. It tells you when your page's text only appears after JavaScript runs, and when robots.txt blocks the crawlers AI assistants use. It also checks your Google profile against your website, so a name or phone number that doesn't match gets flagged.
It doesn't read Google's index for you. Whether Google has a given page is something only Search Console's URL Inspection can say for sure, so start there if site: comes back empty.
FAQ
Either Google hasn't indexed it, or it has and ranks it below where you looked. Search site:yourdomain.com to tell which. No results usually means a new site Google hasn't crawled yet, or a setting telling Google to stay out, such as a noindex tag or a robots.txt block. Results that show up only for site: and not for your name or services mean the site is indexed and the problem is ranking.
Google says crawling can take anywhere from a few days to a few weeks, and it doesn't guarantee that it will crawl or index any page. You can speed up discovery by adding the site to Google Search Console, requesting indexing for your homepage in the URL Inspection tool, and submitting a sitemap. Requesting indexing more than once for the same page doesn't make it faster.
Few pages compete for your exact name, so an indexed site often shows up for it. A search like "plumber near me" puts you up against every plumber nearby. For local searches the map results come first, and Google says local results are based mainly on relevance, distance and how well-known a business is. Your Google Business Profile, your reviews and the sites that link to you carry most of that.
Yes. WordPress has a "Discourage search engines from indexing this site" box under Settings, then Reading. When it's checked, current versions of WordPress add a noindex tag to every page. It's often switched on while a site is being built and never switched off. Uncheck it, then ask Google to recrawl your homepage.
It stops Google from crawling the pages it blocks, but Google says it's not a way to keep a page out of search: a blocked page can still be listed, just without a description. A robots.txt that blocks everything does keep Google from reading your site, though, so a line like Disallow: / under User-agent: * is worth checking for. To keep a page out of Google on purpose, use noindex instead.
Not always. Google says a site of about 500 pages or fewer, with every important page linked from the menu or other pages, may not need one. And if your site runs on WordPress, Wix or a similar system, Google says it has likely made one for you already. If your robots.txt names a sitemap, make sure that address actually opens: a sitemap link that leads nowhere sends Google to a dead end.
Terms used in this article
See how your business shows up
The free audit checks your website, your Google profile and what AI assistants say about you. How the Google check works