Substantively updated October 9, 2026. Original publication date retained.
Search Console and Google Analytics answer different questions. Search Console describes your site’s presence in Google Search. Analytics describes measured activity on your site after people arrive, subject to your setup and the data it can collect.
For a small service business, the useful question is how that activity relates to inquiries and booked work. You do not need to master every report. Start with a few definitions, confirm the setup, and keep a record of changes.
Know which tool to open
| Question | Starting point | Important limit |
|---|---|---|
| Is an important page indexed? | Search Console URL Inspection and Page indexing | Being indexed does not guarantee visibility for a particular search |
| Which Google searches show the site? | Search Console Performance | Some queries are omitted for privacy; it is not a complete query log |
| Which channels bring website sessions? | GA4 Traffic acquisition | Collection, attribution settings, and consent affect the data |
| What pages do visitors use? | GA4 Pages and screens | Views alone do not establish useful inquiries |
| How many inquiries succeeded? | A validated GA4 lead event plus business records | Events can be missed, duplicated, or include spam |
| How many jobs were won? | Sales or booking records | Website activity is not the same as a completed sale |
Set up GA4 with the business in control
Create or use an Analytics account controlled by the business. Add a GA4 property with the appropriate reporting time zone and currency, then create a Web data stream for the site.
Follow the stream’s installation instructions for your platform. You may use a supported CMS integration, Google Tag Manager, or a directly installed Google tag. Check for an existing installation first so two methods do not send duplicate events. Google’s Analytics setup guide covers property, stream, and tag installation.
Review the site’s privacy and consent requirements before collection. Test a visit in Realtime and use DebugView when validating specific events. Define a successful inquiry separately from a phone-link or submit-button click; our GA4 event guide walks through that work.
Verify the right Search Console property
Search Console supports two useful website property types. A Domain property covers protocols and subdomains and uses DNS verification. A URL-prefix property covers the specified prefix and offers several verification methods. Choose the scope you intend to monitor and follow the method available to you. Compare the property types.
If someone else controls DNS or the site’s code, have them help with verification. Keep the business’s ownership and the verification method documented so access does not depend on a departing employee or agency.
After verification, inspect a representative public page. Check the Page indexing report for important content that is unexpectedly excluded. Not every unindexed URL is an error; redirects, alternate versions, and deliberately excluded pages may be expected. Google explains the Page indexing report.
Link the tools if the combined reports help
You can use both tools independently. Linking them makes Search Console reports available within GA4, but it does not turn the data into a complete person-by-person journey.
To link, you need the appropriate Analytics Editor access and to be a verified owner of the Search Console property. In GA4, open Admin → Product links → Search Console links, choose Link, select the Search Console property, select the web data stream, review, and submit. This uses a web stream, not the “views” from older Analytics instructions.
The Search Console report collection may need to be published from the GA4 report Library before it appears in navigation. Follow Google’s linking and report instructions.
Read search performance with context
In Search Console’s Performance report, start with the search type, date range, page, and device filters. Keep the same filters when comparing periods.
- Impressions count appearances according to the result type’s rules.
- Clicks count clicks from those results to your content.
- Click-through rate is clicks divided by impressions.
- Average position summarizes the position of your topmost result across the relevant impressions; it is not a fixed rank everyone sees.
Google’s metric definitions explain the differences between result types. Its Performance report guidance also explains anonymized queries and why table totals can differ from chart totals.
If impressions rise while click-through rate falls, the site may be appearing for a wider mix of searches. Inspect queries, pages, devices, and positions before blaming the title. More impressions are not automatically more qualified demand.
Use GA4’s current engagement definitions
GA4 bounce rate is the percentage of sessions that were not engaged sessions. With the default engagement-duration setting, an engaged session lasts longer than ten seconds, has a key event, or has at least two page or screen views. The time threshold can be adjusted. A one-page session can therefore be engaged. Read Google’s engagement and bounce-rate definitions.
Avoid assuming every short visit failed. A visitor may find a phone number quickly, while a long visit may reflect confusion. Read engagement alongside the page’s purpose and meaningful actions.
For source comparisons, distinguish Traffic acquisition, which describes session acquisition, from User acquisition, which focuses on how users were first acquired. Report navigation can vary with the collections configured for your property. Google’s Traffic acquisition guidance explains the difference.
Work through one business question
Consider a hypothetical service page with 1,000 search impressions and 50 clicks in one period. Its click-through rate is 50 ÷ 1,000 = 5%. In a later comparable period, 2,000 impressions and 60 clicks give 3%.
Clicks increased by 20%, even though click-through rate fell. That is a reason to inspect the search mix, not proof that the page got worse or that the business gained 20% more customers.
Next, review visits to that page and validated inquiries in Analytics, then actual inquiry quality in your business records. Do not expect Search Console clicks and Analytics sessions to match exactly: they measure different activity and have different collection and reporting rules.
Choose a response you can test. If the page attracts searches for work you do not offer, clarify scope. If visitors request services you do offer but cannot find the form, improve the contact path. Record what changed before comparing another period.
Make a short recurring review useful
At an interval appropriate to your traffic volume, check important pages, search clicks and queries, acquisition, successful inquiries, and booked outcomes. Compare equivalent periods and consider seasonality and advertising.
Investigate a sudden drop by checking collection and site functionality first. Then inspect Search Console’s indexing, security, and manual-action reports as relevant. Do not assume a ranking penalty from a percentage threshold alone.
Keep someone responsible for Search Console messages and account access. Reports and alerts do not replace testing your own site. In particular, the old Mobile Usability report was retired; use direct phone testing and appropriate performance tools. Google announced that retirement.
End each review with one recorded decision: what you observed, what remains uncertain, and the next check or change. The tools help you investigate; the business result still needs to be measured in actual customer outcomes.