Use Search Console to understand which searches expose your website and which pages people reach. Then connect that observation to the services you want to sell. A monthly review should finish with a small set of page or technical changes, not a screenshot of a rising line.
Keep the reporting window and filters consistent. Record the date, country, device and page group being reviewed so a later comparison uses the same basis. Search data can show a discovery pattern; it does not tell you on its own whether the resulting enquiry was qualified or became a job.
Start with the right property and a clear question
Confirm that the report covers the website you intend to review. A domain property and a specific URL-prefix property can have different scope. Note any recent domain move, tracking change or major release before interpreting a change in the trend.
Choose a business question, such as whether the new window-replacement page is reaching people looking for installation rather than repairs. Begin with that page or service group. Looking at the entire website first can hide a useful change behind unrelated branded searches or seasonal work.
Keep the search measures separate
The Search results report includes clicks, impressions, click-through rate and average position. Compare like-for-like page and query views. Average position is an aggregate, not a fixed placement every homeowner sees, and a high click-through rate on a branded query does not establish broad non-branded demand.
Write the interpretation next to the numbers. If a page gains impressions for the wrong service, the next action may be to clarify its scope. If the page attracts suitable queries but few visits, review how the title and description present the answer, along with the search results themselves.
References: Google Search Console: Search results performance ↗
Sort opportunities into four work queues
Separate pages that cannot be discovered correctly from pages that need a better answer. Review unexpectedly excluded priority pages with the person responsible for the technical setup. An intentional noindex on a private portal is not a content problem to fix.
For accessible pages, choose between improving the existing destination, adding supporting evidence, or covering a genuinely different question. Do not create a second page for every slight wording variation in the query list. Several related queries may belong in one helpful explanation.
- Access: the intended public page is unavailable or unexpectedly excluded.
- Relevance: the page appears for work the business does not offer.
- Clarity: the right question appears, but the title or answer needs attention.
- Evidence: a useful page lacks an example, comparison or process detail.
Bring the findings back to the office
Compare the search observations with enquiries, consultation notes and service demand. A page can receive fewer visits while sending more appropriate projects, or more visits while creating unsuitable calls. Record what the office can verify instead of assigning a source when it is unknown.
Keep a change log with the page, reason, owner and release date. Review the following period alongside seasonality and other marketing activity. The useful output is a defensible next action, not a claim that one edit caused every change in the chart.
Common questions
Does Search Console show signed jobs?
- No. Use it for search discovery and page performance, then connect suitable enquiries and jobs through your own analytics, intake and CRM records.
Should we publish a blog for every query in the report?
- No. Group related questions by intent. Improve an existing page when it already serves the task, and add a guide when it answers a distinct question.