Guide

How to tell if your website is actually findable.

Search Google for site:yourdomain.com. If it returns one result, or none, search engines cannot see most of your website — and no amount of design work will fix that.

You can diagnose most findability problems yourself in about fifteen minutes, without buying a tool or hiring anyone. The checks below are the same ones a technical audit starts with, and each one tells you something specific.

Run them in order. The first two catch the majority of real problems.

1. Ask Google what it has

Search for site:yourdomain.com — the operator with no space after the colon. Google returns the pages it has indexed for that domain.

If you get a healthy list of your real pages, indexing is not your problem and you can move on. If you get one result, your site is probably a single page with anchor navigation, which means there is exactly one thing for Google to rank no matter how many services you offer. If you get nothing at all, the site may be blocked, brand new, or carrying a noindex tag it shouldn't have.

2. Read the page the way a crawler does

Right-click your homepage and choose View Page Source. That is the HTML your server sent, before any JavaScript ran, and it is close to what a crawler sees first.

Use Ctrl-F to look for a sentence you know is on the page. If you can't find it in the source, your content is being assembled in the browser rather than delivered by the server. Google can usually still render it, but on a slower second pass — and most AI assistants don't run JavaScript at all, so a site built this way can be visible in Google and completely invisible to ChatGPT and Perplexity.

3. Check every page has its own title

Still in the source, find the <title> tag. Then check a second page. If both say the same thing — often just the business name — you have given Google no way to tell them apart.

The title is the strongest single on-page signal about what a page is for, and it's the line people read in results. It should be 50 to 60 characters, lead with the distinguishing words, and mention the brand once at the end if there's room. Over about 70 characters, Google rewrites it almost every time, which means you've lost control of it entirely.

4. Check the canonical

Search the source for rel="canonical". Every page should have one, it should be a full absolute URL, and it should point at itself.

If every page's canonical points at the homepage, every page is telling Google it's a duplicate of the homepage — and they will be treated accordingly. This is a common and completely silent failure. It's also one of the most damaging, because the site looks perfect to a human clicking around it.

5. Look for a sitemap and a robots file

Visit yourdomain.com/sitemap.xml and yourdomain.com/robots.txt directly.

The sitemap should list your real pages — all of them. A sitemap listing five URLs for a fifty-page site is worse than none, because it implies the other forty-five don't matter. The robots.txt should allow crawling and name the sitemap with an absolute URL. Also check it isn't disallowing something important; an inherited Disallow: / from a staging setup will quietly de-index an entire site.

6. Test it on a phone, on mobile data

Turn wifi off and load your site. Most local searches happen on a phone, frequently on a weak connection, and the visitor decides whether to stay in the first few seconds.

Run the same page through Google's PageSpeed Insights and look at the mobile numbers. The thresholds that matter are Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Oversized images are the most common cause of failing the first one, and it's usually the cheapest thing on this list to fix.

7. Check what a broken URL does

Type your domain followed by a nonsense path — yourdomain.com/does-not-exist.

You should get a real 'not found' page. What you must not get is your homepage, or a 'not found' message served with a success status. That second case is called a soft 404, and it means every mistyped or outdated URL pointing at your site looks to Google like a real page with nothing on it. Single-page app setups produce this by default.

Common questions

My site is indexed but doesn't rank. Is that the same problem?

No, and it's worth separating them. Indexed but not ranking is a competitiveness and quality question — is there enough on the page to be the best answer, and do enough other sites reference you. Not indexed at all is a technical problem, and it has to be fixed first because nothing else matters until it is.

How long after fixing something does Google notice?

It varies. You can request a recrawl in Google Search Console for a specific URL, which often takes days rather than weeks. Site-wide changes take longer to work through. Quality assessments are continuous rather than switch-like, so a site recovering from thin content improves gradually.

Do I need paid tools for any of this?

No. Everything above uses your browser, Google Search, and PageSpeed Insights. Google Search Console is free and worth setting up regardless — it's the only place you see the queries you're actually appearing for.

If a check above came back wrong and you'd rather not work out why, send the domain over and you'll get a specific list back. There's no obligation attached, and sometimes the honest answer is that the site is fine and the problem is somewhere else.

Why your Google Business Profile beats your website

Google Business Profile signals account for roughly a third of local pack ranking — more than the website contributes. A complete profile with steady reviews will outrank a better website attached to a neglected one.

Why city pages usually backfire

Near-identical pages get clustered by Google, which picks one and ignores the rest — so fifty city pages earn roughly the ranking value of one, while the site-wide quality signal drags down the pages that were genuinely good.

Why your website loads slowly

In most cases it's images — full-size photos sent to phone screens. It's also usually the cheapest thing on the site to fix, and it's the most common reason a page fails Google's speed thresholds on mobile.

Want to know where you actually stand?

Send over your domain and you'll get back a specific list of what's working and what isn't — including when the honest answer is that nothing needs replacing.