A bigger number should lead to a better question. If search impressions rise, which services and locations are appearing? If inquiries rise, are they the projects the company wants? If estimates rise, can the team follow them through to a clear decision?
A useful report keeps these questions connected without pretending they are interchangeable. The goal is enough reliable information to decide what deserves attention next.
One journey, different measures
Follow the opportunity
Read the stages together, while preserving what each number means.
- 01
Visibility
Search impressions: is the business appearing for relevant searches?
- 02
Visit
Search clicks: are people choosing a result and reaching the site?
- 03
Inquiry
Calls and forms: are relevant people starting a conversation?
- 04
Estimate
Qualified opportunities: has the team gathered what it needs to quote?
- 05
Won work
Confirmed commitments: which opportunities became the work the company agreed to do?
Read the search measures in context
Google Search Console reports clicks, impressions, click-through rate, and average position for a selected view. Impressions describe appearances in search results; clicks describe visits from those results. CTR is clicks divided by impressions, while average position summarizes the topmost result from the site. These measures describe search activity, not signed construction contracts.
Keep the date range, search type, and filters with the comparison. Look at queries, pages, geography, and devices when they help explain the totals. Google notes that search results vary with context, and recent report data can be preliminary. A screenshot without its period and settings leaves the reader guessing.
Use the report to decide
What changed? What should you inspect?
| Pattern you observe | Useful question | A place to inspect |
|---|---|---|
| Visibility grows; relevant clicks do not. | Are the searches and result descriptions aligned with the work you want? | Queries, service pages and result titles. |
| Relevant visits grow; inquiries do not. | Can the buyer judge fit and reach you easily? | Phone experience, proof, call buttons and the actual form route. |
| Inquiries grow; estimates stall. | Who owns qualification, and what information is missing? | Lead assignment, service fit, access details and next actions. |
| Won work grows; delivery becomes strained. | Can the team support the new commitments? | Capacity, scheduling, handoffs and customer expectations. |
Diagnostic prompts, not proof of a single cause. Validate the explanation with the people doing the work.
Illustrative owner review
Ten requests are not ten projects
Imagine a concrete contractor with ten requests in its tracker. Three are outside the work area, two need access details, two estimates await a decision, and three became won work. Keep those categories visible. Do not report ten projects or treat every estimate as booked revenue.
The next useful improvement may be clearer service-area copy and a better qualification question. More traffic is one possible action; the record should help the owner judge whether it is the right one.
Compare periods you can explain
A 28-day view and a calendar month do not cover the same dates. Keep comparisons clear and record changes that may affect the story: new pages, a tracking change, a shift in service demand, or a change in the area being served. If a starting point is an upper bound, preserve the bound instead of converting it into a precise baseline.
S&N’s story separates the team-supplied first-month search update from early business opportunities. That is the right distinction to keep. Visibility can be part of the account without being presented as a calculation of project revenue or evidence that every future engagement will perform the same way.
Keep a useful project record
The six details worth capturing
- Source, when known; keep unknown sources marked unknown.
- Requested service and work area.
- Project fit and the reason for a poor-fit classification.
- The responsible person and next action.
- Estimate and decision status.
- Won work and any delivery constraint the owner needs to see.
Turn reporting into an operating habit
Run a focused owner review
Bring search data, the inquiry tracker, and one observation from the person handling estimates. Avoid turning the meeting into a tour of every dashboard.
- Name one meaningful change and show the period and evidence behind it.
- Ask what may explain it. Separate what is observed from what the team is inferring.
- Follow a few inquiries through the process to check the explanation.
- Choose one improvement and define what would show it is helping.
- Assign a person and a review date. Keep the decision next to the report.
A useful report ends with an informed next action, not a larger collection of screenshots.
