Your New Website Is Live but Invisible on Google. One Setting Is Usually Why.

A boiler-servicing engineer in Cavan built himself a website last spring. Nothing fancy. A few pages, a booking form, the areas he covers, all so he could stop answering the phone with his arm halfway inside a combi boiler. Six weeks after it went live, he did what every owner eventually does. He typed his own business name into Google.

Nothing. Not on page one. Not on page three. He searched the town, then the service, then his own name again. His site was nowhere. As far as Google was concerned, it did not exist.

He assumed the worst. Bad site. Wasted money. Maybe he needed to pay someone for this "SEO" thing everyone talks about. The real answer took about ninety seconds to find and about ten seconds to fix. His whole site was carrying a single instruction that told every search engine to stay away. Somebody had ticked a box.

Being live and being found are two different things

Publishing a website puts it on the internet. It does not put it in Google. Those are separate events, and the gap between them is where a lot of new sites quietly die.

Google finds pages by crawling. A program called Googlebot follows links, reads your pages, and decides whether to add them to the index, which is the library it searches when someone types a query. No crawl, no index. No index, no appearance in results, no matter how good the site is.

Sometimes a brand new page is simply waiting its turn. That is normal, and if a single page has been live for a couple of weeks without showing up, the usual cause is patience rather than a fault. We covered that specific situation in why a new page can go live and still not get indexed. This article is about the other case. Not a page that is waiting. A whole site that has been told, in plain machine language, that it is not welcome.

The checkbox that hides your entire site

Open a WordPress dashboard and go to Settings, then Reading. Near the bottom sits an option labelled "Search Engine Visibility", with a checkbox beside the words "Discourage search engines from indexing this site".

Tick that box and WordPress adds one line to the code of every page on the site:

<meta name='robots' content='noindex,nofollow' />

That line is not a suggestion Google weighs up. It is a directive. As the WordPress core team documented when they reworked this behaviour in version 5.3, the setting stopped relying on a robots.txt block and started outputting a proper noindex tag instead, precisely because it is the more reliable way to keep a page out of results. So-what for the business owner: that one line is a polite note pinned to your front door telling every search engine to turn around and leave. And they do.

Here is how it gets left on. A developer or an agency ticks that box on purpose at the start of a build, so the half-finished site does not get crawled and indexed while it is still a mess of placeholder text. That is correct practice. The problem is the handover. The site goes live, the invoice goes out, and nobody unticks the box. The owner is now paying for a shopfront on a street that no map will show.

I will admit we did this to ourselves once. During a migration a few years back, we moved a client's site across and handed it back with the visibility setting still carried over from the staging copy. Live and invisible for the best part of a week before anyone spotted it. We rewrote our deployment checklist that afternoon, and "confirm the site is crawlable in production" has been a hard gate on every go-live since.

Why "SEO just takes time" is the wrong diagnosis

When a site is nowhere to be found, the reflex is to assume search is slow and to wait it out. Waiting is the right call for a genuinely new page on a healthy site. Waiting does nothing at all for a site carrying a noindex tag, because the delay is not the problem. The instruction is.

Google is explicit about this. Its Search Central documentation states that when Googlebot crawls a page and reads the noindex tag, Google will drop that page entirely from search results, regardless of whether other sites link to it. Read that again. Regardless of links. You could have twenty local directories pointing at your homepage and it would still not surface, because you have overruled all of them with one line of code.

The trap is that this failure looks exactly like slow SEO from the outside. No results, no traffic, no enquiries. The owner-operator concludes that demand is low, or that the market is quiet, or that they need to spend money they do not have on marketing. The Cavan engineer took no online bookings for six weeks and assumed people simply preferred to ring. They could not ring a site they were never shown.

The other ways a site goes dark

The Reading checkbox is the common culprit, but it is not the only one. If the box is unticked and the site is still missing, check these three.

• A stray noindex from an SEO plugin. Tools like Yoast or Rank Math can set a noindex on individual pages or, occasionally, across a whole post type. A setting that was right during testing can get left in place.
• A blocking robots.txt. A line reading Disallow: / tells crawlers to stay out of everything. There is a subtlety worth knowing here, and it catches people out.
• A "coming soon" or maintenance plugin. These throw a holding page in front of every visitor, Googlebot included, and many keep the real site noindexed while active.

The robots.txt subtlety is this. Blocking a page in robots.txt does not reliably remove it from Google, and it can make things worse. Google's own guidance is clear that for a noindex tag to work, the page must not be blocked by robots.txt, because if the crawler cannot reach the page it never sees the noindex instruction in the first place. Block and noindex at the same time and you get the worst of both: Google cannot read your removal request, yet may still list a bare URL it found through an external link. Pick one lever. For keeping a live site out of results, noindex is the correct one. For a site you want found, neither should be blocking it.

How to check if your site is blocked, in five minutes

You do not need a developer for this. Work through it in order and stop at the first thing that is wrong.

1. Inspect the setting. Go to Settings, then Reading, and confirm "Discourage search engines from indexing this site" is unticked. This alone solves most cases.
2. View the page source. On your production homepage, right-click, choose "View Page Source", and use find to search for the word noindex. If it appears in a robots meta tag, something is still setting it.
3. Verify in Search Console. In Google Search Console, paste your homepage into the URL Inspection tool. You want "Indexing allowed?" to read Yes. If it reads No, Search Console will name the exact directive stopping it.
4. Check robots.txt. Visit yoursite.ie/robots.txt in a browser and look for Disallow: /. That single line blocks the whole site.
5. Deploy the fix, then request indexing. Once the site is clean, use the URL Inspection tool and click "Request Indexing" to push Google to recrawl sooner rather than waiting for it to come around on its own.

Two of those steps use Google Search Console, which is free and is the closest thing to a dashboard for how Google sees you. If you have never set it up, it is worth the twenty minutes before you spend a cent on anything else.

One honest caveat before you expect miracles

Fixing the block is fast. Recovery is not always. Google has to recrawl the site before it acts on the change, and its documentation is candid that it may take weeks, and for less prominent pages sometimes months, before Googlebot revisits. Requesting indexing nudges that along but guarantees nothing. So untick the box today and check back over the following fortnight, not the following afternoon.

There is also a fair point to make in the checkbox's defence. It exists for a good reason. A genuine staging environment, or a site that is still being built, absolutely should be noindexed, because the last thing you want is Google indexing half-written pages and stray test content. The setting is not the enemy. Leaving it switched on in your production environment is. If you are running a separate staging environment to test changes safely, that copy is exactly where a noindex belongs.

What a site that launches ready actually looks like

The deeper issue is that indexability should never be left to memory. On a healthy setup, going live and being crawlable are the same event, the noindex lives only where it belongs on staging, and you have a straightforward way to verify the production site is open to Google. That is the standard. Any platform worth using should meet it without you having to think about a checkbox.

This is one of the quiet advantages of building the site yourself on a properly managed platform rather than inheriting a configuration from someone who has moved on. With Web60, you describe your business and the AI builds a live WordPress site in about a minute, deployed into a production environment that is visible to search engines from the start, with a separate staging environment for the times you genuinely want to keep something hidden. No handover. No forgotten box. Full WordPress underneath, running on Irish infrastructure, with a real support team you can ask if anything looks off. For around four in ten websites on the planet running on WordPress, that combination of full control and a sensible default is worth more than most owners realise.

The point is not the platform. The point is that "is my site actually findable?" should be a question you can answer in five minutes, not a mystery you pay to investigate.

The lesson worth keeping

Being live is not the same as being found. Before you conclude that the market is quiet, that your site is poor, or that you need to spend money you do not have on getting noticed, open the source of your homepage and search it for one word. Nine times in ten, the reason a new site is invisible is not a hard problem in disguise. It is a switch, flipped for a good reason during the build and never flipped back. Check the door is open before you decide nobody is coming in.

Sources