Why Isn't My Website Showing Up on Google? (Australian Guide)

"My website isn't showing up on Google" is actually two different problems wearing the same sentence, and they have nothing in common. Either Google hasn't put your site in the index at all — in which case you could rank #1 for every keyword you own and it wouldn't matter, because you're simply not in the competition — or your site is indexed and it's showing up on page 6 for the searches that matter, which is a ranking problem with an entirely different fix.

Most business owners jump straight to "SEO isn't working" without checking which one they're actually dealing with. That's the expensive mistake. If you're not indexed, buying more blog posts or fiddling with meta descriptions does nothing — Google can't rank a page it doesn't know exists. If you are indexed and just ranking badly, that's a content, authority, and site-quality problem, and it's a longer game.

This is the ten-minute diagnostic to work out which one you've got.

Step one: don't trust the site: search

The classic move is to type site:yourbusiness.com.au into Google and see what comes back. It's a reasonable first instinct, but Google itself warns against relying on it. Google's own documentation on search operators states plainly that "the site: operator doesn't necessarily return all the URLs that are indexed under the prefix specified in the query" — and that if a URL doesn't show up in a site: query, the correct next step is the URL Inspection tool, not a conclusion.

So use site: as a rough sanity check only. If it returns dozens of your pages, you're indexed — move to the ranking question below. If it returns nothing at all, that's a signal worth taking seriously, but confirm it properly before you panic.

Step two: the actual indexing check

Open Google Search Console — free, and if you don't have it connected to your site yet, that's the real first problem, because you're flying blind either way. Two reports do the real work.

URL Inspection tool. Paste your homepage URL into the search bar at the top. It'll tell you, directly from Google's own index, whether that exact page is indexed, when it was last crawled, and — if it isn't indexed — why not. This is more reliable than any site: search because it's Google telling you the actual status of that URL, not an approximation from search results.

The Pages report (Search Console calls it "Pages" under the Indexing section; some longer-running properties still show it as "Coverage"). This lists every URL Google knows about and sorts them into indexed and not-indexed, with a reason attached to each excluded page. The reasons that matter for a small business site are almost always one of four:

• "URL marked 'noindex'" — a noindex tag is telling Google, explicitly, not to index the page. Google's guidance confirms this directive is honoured when Google processes the page — it isn't a suggestion.
• "URL blocked by robots.txt" — your own robots.txt file is stopping Googlebot from crawling the page in the first place.
• "Crawled - currently not indexed" — Google visited the page and decided, for now, not to add it. Usually a quality or duplication signal.
• "Discovered - currently not indexed" — Google knows the URL exists but hasn't got around to crawling it yet.

Each of those points to a different cause, ranked below roughly in the order we'd check them.

The causes, in the order they're worth checking

1. The site is new, or something on it changed recently

The boring explanation is usually the right one. Google's own guidance says it "can take a week or so" for Google to start crawling a brand-new site, and "up to a few weeks" before it's fully indexed. If your site launched, or a section of it was rebuilt, in the last fortnight, this is very likely just timing. Check the Pages report again in a week before assuming something's broken.

2. A noindex tag got left on by accident

This is the single most avoidable cause and, anecdotally, the most common one developers and agencies talk about. Most CMS platforms — WordPress especially — have a setting along the lines of "discourage search engines from indexing this site," usually ticked on by default during development so the staging version doesn't get crawled. It's meant to be switched off at launch. It regularly isn't. If your Pages report shows "URL marked 'noindex'" across the board, this is almost certainly it — check your CMS's SEO settings and your page <head> for a stray <meta name="robots" content="noindex"> tag.

3. robots.txt is blocking Googlebot

Visit yourdomain.com.au/robots.txt directly in a browser. If you see a line like Disallow: /, Google is being told not to crawl anything on the site — sometimes left over from a staging environment that got pushed live without anyone checking the file. This one's a five-second fix once you've found it, and rankings usually recover within a couple of weeks of Google re-crawling.

4. Google doesn't know the site exists yet

If you've never submitted a sitemap and the site has no backlinks pointing to it — no directory listings, no partner mentions, nothing — Google may simply not have discovered it. A sitemap isn't mandatory; Google's own documentation on building a sitemap describes it as "merely a hint," not a requirement or a guarantee. But it's a very cheap hint to give, and for a new site with no existing links pointing at it, it's often the fastest way to get discovered. Submit it in Search Console under Sitemaps, then use the URL Inspection tool's "Request Indexing" option on your key pages to nudge things along.

5. A manual action

Rare for a legitimate small business site, but worth the thirty seconds to rule out. Search Console's Manual Actions report will show a green tick if you're clear, or details of the violation if Google has taken action against the site for something like unnatural links or thin, spun content. If you inherited a domain with a chequered SEO history, check this first.

6. The platform isn't rendering properly for Google

Google can crawl JavaScript-heavy sites, but it does it in a second pass, after crawling the plain HTML first — and if the important content on a page only appears after JavaScript runs, that second pass has to succeed for the page to be understood correctly. Some page-builder platforms and heavily plugin-laden setups handle this poorly, serving Google a near-empty shell on first crawl. If URL Inspection shows Google's rendered screenshot of your page looking broken or blank compared to what a visitor sees, that's the platform working against you, not your content.

If you're indexed and still can't find yourself

This is where the two problems split apart. If the Pages report shows your key pages as indexed and URL Inspection confirms it, "not showing up on Google" actually means "not ranking for the searches I care about" — which is a completely different diagnosis. That's a question of content depth, page speed, backlinks, and whether Google's core updates have moved the ground under you. We've written the full diagnostic for that scenario separately: why your rankings dropped, and how to tell if it's an SEO problem or a site problem.

It's also worth being honest with yourself about what you're searching for when you check. Searching your own business name and not finding yourself is a genuine indexing red flag. Searching a broad, competitive term like "plumber Melbourne" and not appearing on page one is not evidence of an indexing problem — it's evidence you're one of several thousand pages competing for that term, and ranking there is earned, not switched on.

The pattern underneath most of this

Nearly every cause above traces back to the same root: something technical happened during a build, migration, or platform change that nobody checked afterwards. The noindex tag left on. The robots.txt pushed live from staging. The JavaScript that renders fine for a person and badly for a crawler. None of these are content problems, and no amount of blogging fixes them. They're the kind of thing that gets caught by a proper technical handover — or missed entirely on a platform where nobody's looking at the raw HTML Google actually receives. If your site's been through a page-builder migration, a rebrand, or a rebuild in the last year and you've never checked the Pages report since, that's worth doing before you write another word of content. Platform-level rendering and crawl issues are also part of what separates a hand-coded build from a template one — nothing renders behind JavaScript that shouldn't be there, because there's no page-builder layer generating it.

If you've worked through the checks above and you're still not sure whether you're dealing with an indexing gap or a genuine ranking problem, run the free audit — it checks the technical fundamentals in under a minute and tells you which category you're actually in before you spend another dollar on content.