How Do You Use Google Search Console for a Small Business Website?

Google Search Console is the closest thing you get to a report card from Google itself. It shows which searches bring up your site, which pages Google has indexed, and what’s stopping others from showing up.

It’s free, and you don’t need to be technical to get value from it. Here’s how to set it up and which parts are worth your time.

What does Search Console tell you that Analytics doesn’t?

The two tools answer different questions, and owners often mix them up.

	Google Search Console	Google Analytics 4
Covers	Google Search only	Every source: search, social, email, direct
Shows	Searches, impressions, clicks, ranking position, indexing problems	Visits, pages viewed, key events such as calls and bookings
Answers	”Can people find me on Google, and for what?"	"What do visitors do once they’re here?”
Best for	Spotting SEO problems and opportunities	Measuring leads and sales

You want both. Our GA4 guide for small businesses covers the Analytics side.

How do you verify your site?

Start at Google Search Console and add a property. You’ll be offered two types:

• Domain property. Covers every version of your site: with and without www, http and https, and any subdomains. It’s verified by adding a DNS record where your domain is managed. This is the one we recommend.
• URL-prefix property. Covers only one exact address, such as https://www.example.com/. It can be verified in more ways, including an HTML file, a meta tag, or your existing Google Analytics or Tag Manager setup.

If you don’t know where your DNS is managed, it’s usually your domain registrar or your host. On our hosting and domains page we explain how we handle domains for clients, which makes this step simpler.

One rule: the business should own the property. If a designer sets it up, they should add you as an owner, or verify it under your account and add themselves as a user.

How do you submit a sitemap?

A sitemap is a file that lists the pages on your site you want Google to know about. Most modern platforms generate one automatically. Common addresses are /sitemap.xml or /sitemap-index.xml; try them in your browser.

In the Sitemaps report, enter the sitemap address and submit it. Within a while, the report should show a success status and a count of discovered pages.

A sitemap helps Google find pages. It doesn’t force Google to index them. Google’s own sitemap documentation covers formats and limits if you ever need to build one by hand.

How do you read the Performance report?

The Performance report is where most of the useful information lives. It shows four numbers:

• Clicks: how many times someone clicked through to your site from Google Search.
• Impressions: how many times one of your pages appeared in results someone saw.
• Average CTR: clicks divided by impressions.
• Average position: roughly where your pages appeared in results, averaged across all the searches that showed them.

Below the chart, switch between Queries (what people searched) and Pages (which of your pages showed up). You can filter by date, device and country, and compare date ranges.

Three patterns worth looking for:

1. High impressions, low CTR. People see the page but don’t click. The title and description probably don’t match what they searched. Rewriting them is often the quickest win you’ll find.
2. Position roughly 8 to 20. The page is close to the first page but not there yet. More useful content and better internal links to the service page can help.
3. Queries you didn’t expect. If people find you for a service you don’t have a page for, that’s a hint you may need one. Our guide to building SEO service pages walks through what to put on it.

Treat average position with care. It’s an average across many different searches, locations and devices, so a single number hides a lot. Watch the trend, not the exact figure.

What does Page indexing tell you?

The Page indexing report (sometimes just called Pages) splits your URLs into indexed and not indexed, with a reason for each group of pages that aren’t.

Not every page should be indexed. Here’s how to read the common reasons:

Reason you may see	What it usually means	Usually a problem?
Page with redirect	The old URL points somewhere else	No, if the redirect is intentional
Alternate page with proper canonical tag	Google is using a different version you pointed to	No
Excluded by ‘noindex’ tag	The page asks not to be indexed	Only if it’s a page you want in Google
Not found (404)	The page doesn’t exist	Only if it used to get traffic or links
Duplicate without user-selected canonical	Google sees near-copies and picked one itself	Sometimes; check which version won
Crawled, currently not indexed	Google saw it but chose not to index it yet	Worth a look if it’s an important page
Server error (5xx)	Your server failed when Google visited	Yes, tell your host or developer

The fix is different for each reason. A page set to noindex by accident needs that setting turned off. A thin page that Google crawled but didn’t index usually needs more useful content, not resubmission.

After a site rebuild, this report is where redirect mistakes show up first. Our guide to redirecting everything that moves explains how to avoid most of them, and it’s a big part of how we handle a website redesign.

When should you use URL Inspection?

URL Inspection checks one page at a time. Paste a URL into the search bar at the top of Search Console and it tells you whether the page is indexed and which version Google treats as the main one (the canonical).

Use it when:

• You’ve published a new page and want to request indexing.
• You fixed a problem on an important page and want Google to look again.
• A page isn’t showing up and you want to know why.

The test live URL option checks the current version of the page rather than the last crawl, which helps confirm a fix actually went live.

What else is worth a glance?

A few other reports earn a quick look:

• Core Web Vitals. Shows how real visitors experience your pages’ loading, responsiveness and visual stability, using LCP, INP and CLS. Smaller sites sometimes see “not enough data”. Our post on website speed covers how to improve these.
• Links. Shows which sites link to you and how your own pages link to each other. Useful for spotting important pages with few internal links.
• Enhancements and structured data reports. If you’ve added schema, these show errors Google found. Pair them with testing your schema directly.
• Manual actions and Security issues. These should be empty. If they’re not, deal with them first.

How often should you check?

For most small businesses:

• Monthly: Performance report (queries, pages, CTR), plus a look at Page indexing for important pages.
• After any launch, redesign or URL change: check Page indexing and Sitemaps weekly for the first several weeks.
• When you get an email alert: read it, then decide whether it affects pages that matter.

Folding this into a regular website maintenance checklist keeps it from slipping. If you’d rather not do it yourself, monitoring Search Console is part of our website care service.