Almost every founder I work with has Google Analytics installed. And now there is Google Search Console.
If you’ve ever looked at a traffic drop in Analytics and thought “okay, but why” – Search Console is the why. Here’s what it actually does, how it’s different from Analytics, and how to get it running on your own site today.
What Google Analytics Actually Does
Analytics tracks what happens once someone’s already on your website. How long they stayed, what they clicked, which pages they bounced from, whether they came from Instagram or an email or a Google search. It’s brilliant at telling you what people do after they arrive.
What it can’t tell you is what happened before that – what someone typed into Google, whether Google’s even showing your page properly, or why your organic traffic moved. Analytics only knows “Organic Search” as a source category. It doesn’t know the search itself.
What Google Search Console Actually Does
Search Console is Google talking to you directly about how it sees your website. It shows you:
- The exact words people typed into Google before landing on your site
- Whether your pages are actually indexed – meaning Google can find and show them at all
- Any errors stopping Google from crawling your site properly
- How your site performs on mobile and page speed
It’s the piece that sits before Analytics in the customer journey – and it’s the only place you’ll find any of this information. Nowhere else shows you real search terms, for free, tied to your own site.
Side by Side, in Plain English
| Google Analytics | Google Search Console | |
|---|---|---|
| What it watches | What happens after someone lands on your site | What happens before someone lands on your site |
| In one line | “What are people doing on my website?” | “How does Google see my website?” |
| Shows you | Time on page, bounce rate, click-throughs, where traffic came from | The exact search terms used, indexing status, crawl errors, mobile issues |
| Good for | Understanding behaviour and conversions once someone’s on-site | Understanding your visibility in Google, and fixing anything stopping people finding you |
| The gap it fills | Doesn’t explain why organic traffic changed — just that it did | Doesn’t track what happens after the click — just the click itself, and what led to it |
| Rough analogy | The camera inside your shop, watching what customers do once they’ve walked in | The window display and the street outside — who’s looking in, and whether they can even see the shop |
The short version: Analytics is behaviour on-site, Search Console is visibility in Google. You want both, because Analytics alone can’t diagnose a search traffic problem – only Search Console can.
Why This Actually Matters (Not Just in Theory)
Say your organic traffic drops 30% one month. Analytics shows you the drop – 800 visits down to 560 – and that’s the end of the story it can tell you.
Open Search Console instead, and now you can actually diagnose it:
- Your Performance report might show you’ve dropped from position 4 to position 11 for your main keyword – still ranking, just buried on page two where nobody scrolls.
- Your Pages report might show a batch of posts suddenly marked “Excluded” – a site update quietly added a “noindex” tag, and Google stopped showing pages that used to bring in traffic.
- Or rankings haven’t moved at all, but impressions stayed flat while clicks fell – meaning people are still seeing you in results, they’re just not clicking. That’s a title or meta description problem, not a ranking one.
Three completely different problems, three completely different fixes. Analytics alone would’ve just shown you a number going down. Search Console turns “something’s wrong” into “here’s exactly what, and what to do about it.”
How to Set It Up
Head to search.google.com/search-console and sign in with the Google account you use for your site – ideally the same one linked to your Analytics, if that’s already set up.
Click Add property, and this is where most people freeze, because Google asks you to choose between two property types. Here’s the plain-English version:
Domain Property vs URL-Prefix: What’s the Actual Difference
Think of your website as having a few different “doors” people could technically walk through: www.yoursite.com, yoursite.com without the www, the old http:// version, the current https:// version. To Google, each of those is technically a different address, even though to you it’s all just “my website.”
- URL-prefix property watches one specific door – exactly the address you type in, exactly as typed. Traffic on a slightly different version of your URL won’t show up here.
- Domain property watches the whole building – every door at once (www, non-www, http, https, and any subdomains like
blog.yoursite.com) – under one unified view.
The trade-off is in how you prove ownership. URL-prefix lets you verify with something simple sitting on your website – a file, a code snippet, or your existing Google Analytics connection. Domain property can only be verified one way: a DNS record, because DNS is the one place that owns the entire domain, subdomains included.
If you’re not sure which to pick: start with whichever’s easiest for you to verify today, then add the other one later – you’re allowed both on the same account, and most people end up wanting both eventually.
Setting Up a URL-Prefix Property
- Choose URL-prefix and enter your site’s exact address, including
https://. - Pick a verification method: an HTML file upload, an HTML meta tag, or — the fastest if you’ve already got Google Analytics running — verify instantly through that with zero code.
- Click Verify.
Setting Up a Domain Property
- Choose Domain and enter just your bare domain –
yoursite.com, nohttps://, nowww. - Google gives you a TXT record to copy.
- Log into wherever your domain is registered (not your website host – your domain registrar) and find the DNS settings.
- Add a new TXT record: leave the subdomain/host field blank so it applies to the root domain, paste Google’s verification string into the content field, and save.
- Back in Search Console, click Verify. DNS changes can take anywhere from a few minutes to a few hours to take effect, so if it fails the first time, wait and try again.
If someone else – a web developer or agency – manages your DNS, this is the one step you’ll need to hand off. Everything else you can do yourself.
Once You’re Verified
Submit your sitemap – go to Sitemaps in the left-hand menu, type sitemap.xml after your domain, and hit Submit. A sitemap is just a map of your pages, telling Google what exists so it can find it faster.
Then check two things, once a week, and nothing more:
- Performance, filtered to the last 7 days, sorted by clicks – see what’s actually working
- Pages / Indexing – scan for anything marked “Excluded” that shouldn’t be
That’s it. Ten minutes a week, and you’ll know more about how Google sees your site than most people running paid ads ever will.
Go set up Google Search Console!
Analytics tells you what people do once they’ve found you. Search Console tells you whether they can find you at all, and exactly what they searched to get there. Most sites only have half the picture running. If you’ve only ever set up Analytics, Search Console is the free ten-minute job that fills in the rest.
And if untangling what any of this actually means for your site isn’t how you want to spend your afternoon – that’s genuinely what I do for clients. Reach out and I’ll take it off your plate.
Comments +