First, confirm the site is missing rather than ranking low
"Not showing on Google" means two very different things. A site that is not in the index cannot appear for any search, including its own name. A site that is indexed but ranks low appears somewhere, often for its exact name, and is a ranking question rather than an indexing one. The checks below separate the two before anything is changed.
Verify the site in Search Console first if nobody has. The Search Console tutorial
recommends a Domain property, which covers every protocol and subdomain, so that the data is not split between the
address with and without www or between the old and new protocol. Then inspect the home page and a few key pages with
URL Inspection. As the tutorial describes, it shows whether a URL is indexed, which canonical Google chose, when the page
was last crawled and, in the live test, the rendered HTML and a screenshot of what Google's crawler receives now. Open
the Page Indexing report as well: it counts indexed and not-indexed pages and lists a reason for each group of the
latter. Finally, glance at the Manual actions and Security issues reports, which should both read "no issues"; if they
do not, the problem is a policy one, and the guide to Google's spam policies is the
place to start.
| What the checks show | What it means | Where to go |
|---|---|---|
| URL Inspection says the URL is unknown to Google, and the Page Indexing report is empty or nearly so | Google has not discovered the site | The first cause below |
| Pages are known but excluded, with a noindex, robots.txt, authorisation or similar reason | Something tells crawlers to stay out or keeps them out | The second, third and fourth causes |
| Pages are indexed, but the live test screenshot is nearly blank | Content depends on scripts the crawler did not run | The fifth cause |
| Pages are indexed and the property shows impressions | The site is on Google; the check was wrong or it ranks low | The last two causes |
| Pages are known but waiting or declined, with "discovered" or "crawled" reasons | A different problem, already covered | Discovered, currently not indexed or crawled, currently not indexed |
The SEO page checker reads the status code, robots directives and canonical of a single live URL, which is a quick second opinion on the home page before you start.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| URL Inspection does not know the home page; no other site links to it | Sitemap submitted? Any links from other sites? | Google has not found the site yet: no links from other sites and no sitemap | Submit the sitemap, link the site from profiles and partners, inspect the home page |
| Pages are excluded by a noindex rule | Page source and response headers; the content system's visibility setting | A noindex rule or a content-system setting left on from the build | Remove the rule or switch the setting off, then request indexing of key pages |
| Pages are blocked by robots.txt | Read the live robots.txt file | A robots.txt rule that blocks the whole site | Replace the blanket disallow with the intended rules |
| Crawlers get an authorisation error or a holding page | Load the site in a private window; URL Inspection live test | A password, login, holding page or bot protection in front of the site | Remove the gate from the production site |
| Pages are indexed but the screenshot is nearly empty | Live test rendered HTML against the browser | Content and links that appear only after scripts run | Serve the main content and links in the HTML |
| Search Console shows impressions the owner cannot find | Property type; which address was searched; private window | Checking the wrong thing: another host or protocol, a personalised search or the wrong Search Console property | Use a Domain property and search the way a stranger would |
| Indexed pages appear only for the exact business name | Performance report queries | Indexed, but too new and too little known to rank for anything beyond its own name | Build the first links and make pages say what the business offers |
Fix, verify and prevent each cause
Google has not found the site yet
Google finds pages by following links from pages it already knows and by reading XML sitemaps. A new domain that no other site links to, with no XML SitemapA file listing the URLs a site wants search engines to discover and crawl. submitted, can wait unnoticed. The crawling and indexing guide describes discovery as the first stage of a pipeline that continues through crawling, rendering and indexing, and a site has to pass each in turn.
Fix: submit the sitemap in Search Console and confirm it is read without errors; link the site from places that already exist, such as the business's social profiles, the Business Profile, partner and supplier sites and trade memberships; then inspect the home page and request indexing.
Verify: URL Inspection reports the home page as known, then crawled, and the Page Indexing report starts to count pages.
Prevent: make sitemap submission and the first links part of the launch plan, not something done after a complaint that the site cannot be found.
A noindex rule or a setting left on from the build
Content systems often have an option to hide a site from search engines while it is being built, and themes and plugins can add a noindexA robots directive telling search engines not to show a page in their results. rule of their own. When the option is forgotten at launch, every page asks Google to leave it out of results. Google's noindex documentation describes the rule as a way to keep a crawlable page out of results, which is exactly what it then does.
Fix: switch the setting off, remove any noindex in templates and response headers, and request indexing of the home page and the main pages.
Verify: the live test in URL Inspection reports the page as indexable, and over the following recrawls the excluded group in the Page Indexing report empties.
Prevent: keep environment settings out of templates and compare the indexing settings of staging and production before each launch, as SEO checks for staging and releases sets out.
A robots.txt rule that blocks the whole site
A disallow rule for every path, often carried over from a Staging EnvironmentA private copy of a website or tool where changes are tested before release, kept behind access control and out of search and production analytics., stops crawlers fetching any page. Google's robots.txt documentation is clear that the file manages crawling and is not a way to keep pages out of results, so the result is a site Google cannot read rather than a site that is safely hidden.
Fix: replace the blanket rule with the rules the live site actually needs, usually very few. The comparison of noindex and robots.txt disallow explains which control fits which goal and why stacking them fails.
Verify: the robots.txt report in Search Console shows the new file, and URL Inspection reports key pages as crawlable.
Prevent: review robots.txt changes like code. If some URLs were indexed while blocked, the page on indexed, though blocked by robots.txt deals with them.
A password, login, holding page or bot protection in front of the site
A launch held back by a password, a coming-soon page served in place of the real site, or a protection rule that challenges unfamiliar visitors can all keep crawlers out while staff, who are logged in or on an allow list, see a working site. The release checks guide notes that a host behind authentication answers crawlers with an authorisation error, which the Page Indexing report lists as a reason a URL is not indexed.
Fix: remove the gate from the production site, replace any holding page with the real pages, and adjust protection rules so that crawlers reach the content.
Verify: a private browser window shows the real home page, and the live test screenshot matches it.
Prevent: keep access control on staging hosts only, configured on the server rather than in the site's code, so it cannot reach production by accident.
Content and links that appear only after scripts run
Google renders pages, but content that depends on client-side execution can be indexed late or not at all, and links that are not real links may never be followed. A site whose text and navigation exist only after scripts run can look complete in a browser and nearly empty to the crawler, which shows up as a thin index and pages Google declines. The JavaScript SEO guide explains the documented RenderingThe step in which a search engine runs a page's HTML, CSS and JavaScript to build the content a browser would display before indexing it. behaviour and the failure modes.
Fix: serve the main content and the navigation links in the initial HTML, or adopt a rendering approach that does.
Verify: the rendered HTML in the live test contains the page's text and its links.
Prevent: test rendered output before launch with the pre-release checklist in the JavaScript guide.
Checking the wrong thing
Some sites are on Google and the owner simply cannot see them: the search was made in a browser shaped by the owner's own history, the owner searched a generic phrase rather than the business name, the Search Console property covers only one version of the address, or the site moved from one host or protocol to another and the old property shows nothing.
Fix: use a Domain property, search in a private window, and search for the exact business name and for the address itself. The Search Console tutorial explains how to read the performance report with filters rather than site totals.
Verify: the performance report shows impressions, and URL Inspection confirms the key pages are indexed.
Prevent: keep one Domain property for the whole site and give the team access to it, so nobody judges visibility from a personal search.
Indexed, but too new to rank beyond its own name
When the site is indexed and appears only for its name, nothing is blocked: it is a new site with little external evidence of being worth ranking. The discovered, currently not indexed page notes that links from other sites are one of the ways Google discovers URLs and judges how much attention a site deserves.
Fix: make each important page say plainly what the business offers and where, and start the order the link building methods guide gives for a new site: relationship links first, then the directories that matter for the trade and the area, then one asset worth citing.
Verify: the performance report begins to show impressions for searches other than the business name.
Prevent: plan the first links and the strongest pages before launch. If a specific page is indexed but never climbs for its target search, the page on new content that is not ranking takes over.
Prevention: a launch routine that keeps the door open
Most of these causes are launch accidents, and a short routine prevents them. Before launch, protect staging with authentication rather than robots rules, and write down which indexing settings differ between staging and production. On launch day, switch off any "hide from search engines" option, read the live robots.txt file, check the home page's response headers for a noindex rule, load the site in a private window, verify a Domain property and submit the sitemap. In the days after, inspect the key pages, watch the Page Indexing report start to fill, and record each step with its date so a later problem can be matched to a change.
| When | Check | Owner |
|---|---|---|
| Before launch | Staging behind authentication; indexing settings listed for both environments | Developer |
| Launch day | No noindex, no blanket disallow, no holding page; Domain property verified; sitemap submitted | SEO lead or site owner |
| After launch | Key pages inspected; Page Indexing report filling; first links requested | SEO lead or site owner |
| Every release | Directive, robots and status checks on changed templates | Developer and SEO lead |
The technical SEO maintenance playbook turns the release row into a standing routine, and SEO strategy for a launch covers which pages to publish ahead and how to get the rest indexed quickly. For an established site that disappears after a release rather than a new one that never appeared, the page on sudden ranking drops starts from the change log instead. And when the site is indexed but other results still come up first for its own name, the page on not ranking for your own brand name starts from the home page and how plainly the name is stated.
A pottery studio finds its new site (illustrative)
Thuvrell Pottery Studio
Thuvrell Pottery Studio, an invented studio that runs wheel-throwing and hand-building classes, launches a new website with 14 class pages and a booking page on 3 March. Five weeks later the owner still cannot find it on Google, even by searching "Thuvrell Pottery". Search Console has never been set up. After verifying a Domain property, URL Inspection shows the home page is known but excluded by a noindex rule: the content system's option to hide the site from search engines, switched on during the build, was never switched off. The sitemap has never been submitted, and no other site links to the new address. The owner switches the option off, submits the sitemap, requests indexing for the home page and the 3 most popular classes, and asks the local craft guild and 2 clay suppliers to link to the studio. Within 3 weeks the Page Indexing report shows 12 of the 16 pages indexed and the studio appears for its name; a month later the performance report shows its first impressions for "pottery classes" searches near the studio.
Common mistakes
- Requesting indexing before removing the block. A request cannot override a noindex rule, a disallow or a login; fix the cause first.
- Hiding staging with robots.txt. The file manages crawling, not results, and a rule written for staging is how a launched site ends up blocked.
- Judging from a personal search. Search history and location shape what the owner sees; use a private window and Search Console instead.
- Verifying only one version of the address. A property for one protocol or host shows nothing for the other; a Domain property covers both.
- Treating "not ranking" as "not indexed". A site that appears for its name is on Google; the next work is pages and links, not technical fixes.
- Waiting without a sitemap or a single link. Discovery needs a route in; give Google one on launch day.
