The two numbers you can read
on your phone in a minute

You are standing in a driveway with your phone in one hand and a coffee going cold in the other. You want one thing: is this website doing anything for me, or not. You do not want a call, a login maze, or a PDF full of charts you did not ask for. You want to look, know, and get back to work.

You can. There are two numbers that matter, and both of them fit on a phone screen.

The two numbers

Here they are, plain:

1. Is the phone ringing.
2. Where are the calls coming from.

That is the whole scoreboard. The first number you already own. It is in your pocket right now. Every call log, every text, every "saw your site and need a quote" is the truest measurement there is. No tool reports it because no tool has to. You lived it.

The second number is the one the free Google tools add. When the phone rings, you want to know whether the website had anything to do with it. That is all analytics really answers: someone showed up, and here is the road they took to get to you.

Everything past those two numbers is detail. Useful detail sometimes. But if a report leads with anything other than "more calls, and here is where they came from," someone is dressing up a slow month.

Opening them on your phone

Keep it simple. Open Google Analytics and Search Console in your phone's web browser, signed in the same way you do on your computer.

That is the reliable path, and it always works. Same login, small screen. You do not need to install anything or set up a second thing to check the first thing.

Two tools, two jobs:

• Google Analytics tells you who showed up on your site and where they came from.
• Search Console tells you how you are showing up in Google search itself, before anyone even clicks.

You do not have to master either one. You are reading, not building. (Turning these on for the first time is its own short walk, and it lives in the next chapter.)

Reading Analytics without getting fooled

Open Analytics and you will see visits. Your first honest question should be: are these real people, or junk?

Good news on that front. Analytics quietly throws out traffic from bots and crawlers that identify themselves honestly. It uses Google's own research plus a shared industry list of known bots, and that filter runs by default with no switch to turn it off. So the obvious fake traffic is already gone before you ever see the number. You did not have to do a thing.

Here is the honest catch, and it matters: that filter only catches the bots that admit what they are. The sneaky stuff — fake visits dressed up to look real, run through tricks that hide where they came from — can still slip through. So treat the visitor count as a decent read, not gospel. A number that suddenly triples overnight with no calls behind it is a flag, not a party.

This is exactly why the phone stays the anchor. Visits can be gamed. A booked job cannot.

Where did they come from

Now the good part. In Analytics you can see the road people took to reach you: straight from a Google search, from a link somewhere, typed your address in directly, and so on.

Newer wrinkle worth knowing. Analytics now automatically sorts some visits that came from an AI assistant into their own built-in bucket, labeled something like "AI Assistants" — no setup on your end. So when somebody asks ChatGPT or a similar tool "who does drain work near me" and lands on your site, you can sometimes see that.

That word "some" is doing real work. It only catches a visit when the AI sends along a little tag saying where it came from, and only for tools on Google's own list — a list Google does not fully publish and has already changed once. If the AI sends no tag, or it is a tool Google has not added yet, that visit just shows up as "Direct," same as someone typing your address by hand. So the bucket is a nice bonus, not a full count. Do not treat a low AI number as proof no AI is sending you anyone.

Search Console, and why "today" looks empty

Flip over to Search Console and you might panic: today looks blank or thin. Don't.

Search Console numbers are not live. They typically run a couple of days behind, sometimes longer when Google's own systems hiccup, and the most recent day or two is still preliminary and can shift after the fact. A quiet "today" is normal lag. It is not a broken site and it is not you doing something wrong. Look at the last full week instead of refreshing this morning's empty box.

One more thing to know so you check at the right rhythm: Search Console keeps about the last sixteen months of history and no further. Data older than that rolls off and is gone from the report. So it is a rolling window of roughly a year and a bit — plenty to spot a trend, but not a forever archive. If you ever want a number for your records, screenshot it before it ages out.

Reports are theater

Think about what a monthly report actually is. Someone else picks which numbers to show you, arranges them, and mails you the flattering ones. The metric that went up gets a big chart. The phone that did not ring gets left off entirely.

A report isn't proof. It is a story someone chose to tell you.

You do not need the story. You have the two numbers, and you can read them yourself in under a minute, standing in that driveway. The tools are free, the login is the one you already use, and nobody gets to spin it for you.

The one rule

If you remember nothing else: the phone ringing is the number that matters. Everything on the screen is just there to tell you where the ring came from.

Next: Setting up your numbers