Google keeps a running report on your website: every search it appeared in, the position it held, which listings earned a click, and which pages made it into the index at all. The report is called Search Console. It's free, it's yours, and most small business owners have never opened it.
That's not a knock on owners. Nobody hands you the login when you buy a domain, and no invoice ever depends on reading it. But it means the evidence about how your site performs in search sits in a Google account, already collected, while website decisions get made on gut feel.
This guide covers setup, the reports worth your time, and what each one can and cannot tell you. One habit carries the whole thing: read the evidence before you change anything. (If you're not sure the site is working at all yet, start with this checklist and come back.)
Search Console vs. Google Analytics
The two get confused constantly, and the split is simple. Google Analytics shows what people do on your site after they arrive: pages viewed, time spent, forms submitted. Search Console shows how they found you before they arrived: the searches your site appeared in, and whether anyone clicked.
Analytics is behavior on the site. Search Console is visibility in search. You want both eventually, but diagnosis starts with Search Console, because if nobody is arriving, the on-site data has nothing to tell you.
Setting Up Search Console
Go to search.google.com/search-console and sign in with your Google account, ideally the same one that runs your Analytics.
Google asks you to prove you own the site. There are several ways to do it:
- HTML tag: paste a short snippet into the head of your site
- DNS record: add a record at your domain registrar
- Google Analytics: if Analytics is already installed, Search Console can verify through it
- Google Tag Manager: the same idea, through your existing container
Pick whichever one you can finish without calling anybody. The Analytics route is the usual shortcut, since that tag is already on the site.
Then open Sitemaps in the left menu and submit yours. For most sites it lives at yoursite.com/sitemap.xml. A sitemap hands Google a list of the pages you consider worth indexing, which beats hoping the crawler stumbles onto everything.
Setup ends there. The reports fill in as Google collects data, so a brand-new property starts sparse and gets more useful with time.
Wondering if this applies to your site?
The $500 SEO Health Check includes a written report within 48 hours and a 30-minute walkthrough after delivery.
The One Report That Matters Most
Open Performance, then Search results. For a small business this is the report that earns the visit; the rest are supporting cast. It shows four numbers:
- Clicks: how many times someone chose your listing and landed on your site
- Impressions: how many times your site appeared in results, clicked or not
- CTR (click-through rate): the percentage of impressions that became clicks
- Average position: where your listings tend to sit across the queries you appear for
A round-number illustration, hypothetical on purpose: say a page gets 500 impressions in a week and 25 clicks. That's a 5% CTR. If a clearer title earned 50 clicks from the same 500 impressions, traffic from that page would double without its ranking moving at all. Real numbers are never that tidy, but the arithmetic is the point. Clicks can grow two ways: rank higher, or earn more of the impressions you already have. The second is where you at least hold the pen, since the title and description are yours to write, even if Google sometimes rewrites them.
The report also breaks the traffic down by query, page, country, and device. Each of those is a filter, and the filters are where the diagnosis happens.
The Queries Tab and the Pages Tab
Inside Performance you can flip between Queries, the searches people typed, and Pages, the URLs of yours that appeared for them.
Queries is customer language, verbatim. "Emergency plumber near me." "Roof leak repair cost." Not what you call your services; what buyers call them, with counts attached. When your page says "moisture intrusion remediation" and the queries all say "roof leak," that gap is worth closing.
Pages shows which URLs are pulling the weight. A homepage with heavy impressions and a service page with a better CTR are telling two different stories, and both are useful.
Read both before touching anything. The queries tell you what people wanted. The pages tell you what Google offered them.
The Almost-Ranking Queries
In the Performance report, add a position filter: greater than 7, less than 21. What's left is every query where your site sits low on page one or on page two. Visible enough that Google keeps showing it. Not visible enough that many people click.
That filter is the most useful thing in the tool, because it surfaces evidence of standing rather than potential. Google already shows these pages for these queries. When you're deciding what to improve next, this list beats guessing, and it beats chasing brand-new keywords where you have no standing at all.
The working sequence:
- Filter for positions 8-20 and note which queries have real impression volume
- Find which of your pages appears for each one
- Read that page the way the searcher would: does it actually answer the query?
- Improve what falls short: the title, the description, the content itself
- Come back to the same filter later and compare
No step in that sequence guarantees movement. Google decides rankings; the report just shows you where your effort has the most evidence behind it. And how long changes take to show up is its own question, with its own sequence of signals to watch. The SEO timing guide owns that one.
Reading the Indexing Report
Indexing, in the left menu, shows how many of your pages Google has indexed and, for the rest, the reason it hasn't. A page that isn't indexed can't rank, so a wide gap between the pages you have and the pages indexed deserves a look.
The usual causes:
- Blocked by robots.txt: your site is telling crawlers to skip the page
- Noindex tag: the page itself asks to be left out of the index
- Server errors: Google tried to fetch the page and couldn't
- Orphan pages: no internal links point to the page, so Google never found it
Read the specific reason before reacting, because a scary count is not automatically a problem. I've watched 145 "not indexed" entries turn out to mean nothing at all: GSC Coverage Noise vs. Real Indexing Problems walks through that exact case, noise and all.
If the question you're really asking is bigger, whether Google can find your site in the first place, that's a different diagnosis with its own steps: how to check if Google can find your website covers it.
For a new page you want in the index, paste its URL into the Inspect URL bar at the top and click Request Indexing. That asks Google to recrawl the page. It's a request, not a command. Google decides if and when.
Your Monthly Search Console Check-In
You don't need to live in this tool. Fifteen minutes a month covers the essentials for most small sites, in three reads.
Performance trends. Compare the last 28 days against the 28 before them. If clicks fell, check whether impressions fell too. Fewer impressions points at visibility: rankings slipped, or pages dropped out of the index. Steady impressions with fewer clicks points at the listing itself: your title, your description, or what Google shows around you changed. Two different problems, two different fixes, one comparison to tell them apart.
The almost-ranking filter. Run the positions 8-20 filter again and pick one page worth improving. One page a month is a pace you can keep, and the same filter shows you next month whether the last one moved.
Indexing errors. Open the Indexing report and read any new reasons. Request indexing for pages you've published since last time. For a quick single-page check between sessions, the free indexability checker reads a URL the way a crawler does and reports anything blocking it.
That's the whole habit. Evidence first, changes second, and a calendar reminder so it actually happens.
FAQ
What's the difference between Search Console and Google Analytics?
Google Analytics shows what people do on your site after they arrive: pages viewed, time spent, forms submitted. Search Console shows how they found you before they arrived: the searches your site appeared in and whether anyone clicked. Analytics is behavior on the site. Search Console is visibility in search. You need both to see the whole picture.
How often should I check Search Console?
Once a month is enough for most small businesses, or once a week if you are actively working on your SEO. Daily checking adds nothing, because the reports are not real-time anyway. Regular reads are what catch indexing errors and traffic changes while they are still small.
What do I do if Google can't index my pages?
Start by asking whether the page needs to be indexed at all, because plenty of pages legitimately do not. If it does, read the specific reason listed in the Indexing report. The usual causes are a robots.txt block, a noindex tag, or a server error. Fix the cause, then use Request Indexing to ask Google to recrawl the page.
Should I manually request indexing for every new page?
No. Submitting your sitemap covers routine updates, because Google reads it on its own schedule and discovers new pages through it. Requesting indexing is worth doing for pages that matter, like a new service page, but it is a request to recrawl, not a guarantee of when or whether the page gets indexed.