Google Search Console is Google's free tool for seeing how your website performs in Google Search: which pages are indexed, which queries show your site, and how many people click through. For a local service business in the Twin Cities East Metro, the St. Croix Valley or western Wisconsin, it is Google's free report on how your site performs in Google Search.

This guide covers the parts that matter for an owner: property types and verification, sitemaps, linking Search Console to Google Analytics 4, the Performance report and what its numbers mean, indexing checks, the Core Web Vitals report, and a few filters that help a local business.

Set up Google Search Console: property types and verification

Search Console starts with a property, which is the site you want data for. Google offers two types, and the choice decides what the data covers. Per Search Console Help, a Domain property includes the root domain, all of its subdomains, all paths and multiple protocols. A URL-prefix property includes only URLs that begin with the exact prefix you enter, protocol included.

Scroll to see all columns

Property typeWhat it coversVerificationBest fit
DomainRoot domain, every subdomain, every path, http and httpsA DNS record (for most sites)The default for a business that owns its domain
URL-prefixOnly URLs that start with the exact prefix you enterSeveral methods, listed in Search Console HelpOne section of a site, or no access to DNS

For most owners the Domain property is the better choice, because a quote form on book.example.com and your main site on www.example.com both show up in one place. The tradeoff is DNS access. Verifying a Domain property means adding a record at the company that hosts your DNS, which is often a registrar or a service such as Cloudflare. If a former web designer holds that login, recovering it is the first job. If you cannot get DNS access, a URL-prefix property is the fallback.

Verify the property under the Google account that the business owns, not a contractor's personal account. Add a second owner from the business so that access survives a staff change.

Submit a sitemap and check it

A sitemap is a file that lists the pages on your site. Google's sitemap overview says a sitemap does not guarantee that every item will be crawled and indexed. It also says that sites of about 500 pages or fewer, if they are linked together well, might not need one. Most local service sites fall under that size, but submitting one is still a fast way to see how Google reads your site.

Per the Sitemaps report help, you need owner permissions on the property. Confirm Googlebot can fetch the sitemap URL, paste it into the Add a new sitemap box in the Sitemaps report, and submit it. The report then shows a status of Success, Has errors, or Couldn't fetch, plus how many pages were discovered. If the status is not Success, click the row for the error detail.

Google Search Console integration with Google Analytics 4

Search Console and Google Analytics 4 answer different questions. Search Console covers what happens before a visitor reaches your site: queries, impressions and clicks in Google Search. Analytics covers what happens after: sessions, engagement and conversions. Linking them puts both views side by side. Our Google Analytics setup guide covers the Analytics side.

The Analytics Help page on Search Console links sets the requirements. To create the link you need the Editor role on the Analytics property and must be a verified owner of the Search Console property. In Admin, open Search Console Links, choose Link, pick your Search Console account, then select the web data stream for your site. A link cannot be edited. To change it, you delete it and create a new one.

Once linked, Analytics offers two Search Console reports. Google notes that the Search Console collection of reports is unpublished by default, so open Library in Analytics and publish it first. Per that page, Google Organic Search Queries shows search queries with Search Console metrics, and Google Organic Search Traffic shows landing pages with Search Console and Analytics metrics together. The second report is the useful one for a service business, because it ties a landing page to what visitors did next.

The Data Studio connector

For a monthly report you can send to a business partner, Search Console also connects to Data Studio (formerly Looker Studio). Google's connector documentation describes two table types: Site Impression, which aggregates by site, and URL Impression, which aggregates by page. A single data source uses one of the two, so a report that shows both needs two data sources. You need at least view permission on the property and must sign in with the same Google account.

Read the Performance report: impressions vs clicks and average position

The Performance report is where most owners spend their time in Search Console. It is built from four numbers, and Search Console Help defines each one.

  • Impressions: how many times your site appeared in Search results. Per that page, the chart counts by property, so two results from your site for one query count as a single impression.
  • Clicks: the number of times a user clicked your site from Google Search results.
  • CTR: the click count divided by the impression count.
  • Average position: the average position of the topmost result from your site.

What impressions vs clicks tells you

A page with many impressions and few clicks is being shown but not chosen. That is a prompt to look at the title and description that searchers see, or at whether the query really matches the page. A page with few impressions is not being shown for much, and the fix is different: the page may not match any real search, or it may not be indexed. Reading the two numbers together keeps you from treating every low click count as the same problem.

What average position can and cannot say

Average position is an average across many searches, and it can hide a lot. The same Help page defines it as the position of the topmost result from your site. It does not explain how position is counted for map results or other Search features, so we do not read a position figure as a map ranking. Read it as a rough direction for one query or page, and check the actual results page for a term that matters. Google also notes that some queries are hidden to protect user privacy, so the table omits some queries.

A monthly routine

  1. Set the date range to the last full month and compare it with the month before, using the Compare option in the Date filter.
  2. Look at the Pages tab first. Note which pages gained or lost clicks.
  3. Open the Queries tab for the pages that moved and read the actual search terms.
  4. Write down one change to make, such as rewriting a title or adding a missing service page.

Check indexing with Page indexing and URL Inspection

If a page is not indexed, it cannot appear in results, whatever the Performance report says. The Page indexing report sorts URLs into Indexed and Not indexed. Google's report help says Not indexed is not necessarily bad, because a URL can be left out for a legitimate reason such as a robots.txt block or a duplicate page. Check the reason listed for each URL. The goal Google states is to get the canonical version of every important page indexed.

The URL Inspection tool looks at one page at a time. It shows Google's indexed version of the page, and its live test fetches the URL in real time. You can ask Google to index a URL, but the tool's help page says submitting a request does not guarantee that the page will appear in the index, and daily limits apply. Use it after you publish a new service page or fix an error, then check back rather than resubmitting.

Core Web Vitals report

The Core Web Vitals report shows how your pages perform for real visitors. Per Search Console Help, it uses field data from the Chrome User Experience Report and covers three metrics: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. A URL group takes the status of its worst metric, and the report lists only indexed URLs and only a sample of them. A small site may show little or no data. If so, that is a limit of the report, not a sign that nothing is wrong.

Use Search Console for local search: filters and the Business Profile

Many local searches name a place or a service. Search Console's advanced filters let you add a Queries filter set to Queries containing a string, or to a custom regex for several values at once. Three filters are worth saving:

  • Your service area names. An illustrative plumber, Birchline Plumbing, might filter for "stillwater" or "woodbury" to see whether searches that name those cities reach its service pages.
  • "Near me." A filter on "near me" shows which pages appear for those searches.
  • Your own business name. Separate it from the rest. Someone searching your name already knows you, and mixing those clicks with searches for a service hides how well new customers find you.

Search Console does not report the profile's calls, direction requests or views; those are in the Business Profile performance report. Per Business Profile Help, that report shows profile views, calls, directions, website clicks and, where they apply, messages and bookings. In our measurement, clicks on the profile's website link do show up as Search Console clicks on the page it links to, so check the Pages report for that URL before reading its total as organic traffic. Keep the two reports side by side and do not add their numbers together. Our local SEO guide for the Twin Cities explains how the two fit together.

Search Console reports activity, not revenue. To connect it to booked jobs, pair it with call tracking and form tracking, as covered in our guide to tracking marketing ROI for a service business. Reporting is also a core part of our SEO, GEO and AEO work. If you would like help setting it up, contact McKinney Creative Ventures.