If positions haven't improved, say so directly and check which queries and dates were compared. Then show completed website work separately. A fixed link or restored form may be useful, but they don't turn a lack of search growth into a success.
The discussion should end with a decision: which support tasks are complete and what to do next about search. The “Website Monitoring” subscription helps identify and check changes, but it does not guarantee better search rankings.
Check whether the data is actually comparable
Compare the same set of queries in the same region. If you tracked laptop repair a month ago but have now added office equipment maintenance, the average values refer to different sets.
Check the dates of the actual checks. They may differ for queries checked daily, weekly, and monthly. Google is in the daily group; don't expect equally recent data from both search engines for every query.
In the report, state the basis: “For these ten queries in Tula, comparing results from 01.09 and 30.09, there is no noticeable growth.” This is an example phrasing: use the actual dates. If there is no new result, write that there is no data rather than reporting a position of zero. See the SEO monitoring guide for general rules.
Show technical results that can be verified
Don't limit the report to the number of checks or files changed. Choose work with a clear result on the website. The examples below are illustrative:
| Work | Verified result | What it does not prove by itself |
|---|---|---|
| Fixed the link to the returns policy | /returns opens from the menu | Increased sales |
| Gave product card headings different titles | The specified URLs have different headings | Improved positions for all products |
| Restored form submission | The manager received an agreed test request | An increase in inquiries |
Instead of saying “we improved the technical condition,” name the URL, date, and result. If a change has been published but the follow-up check is not complete, keep it in progress. For confirmation, use the fix verification process.
Don't calculate avoided financial losses if you don't know how many visitors were affected. You can show the restored user journey without inventing a financial estimate.
Don't close the discussion about search with a table of fixes
Technical support and promotion address related but different tasks. If the client expected search growth, clarify what was agreed and what work on the pages was actually done.
Check whether the queries match the company's offer. Is there a suitable page for an important query? Does it explain the service terms, price, or ordering method? These are questions for a specific content review, not a promise that fixing any technical error will improve positions.
Data from website monitoring can help raise this question. The team decides on content and promotion. If it only receives reports and does not carry out tasks, that needs to be addressed in how the work is organized, not hidden behind a long list of checks.
Agree on work with an outcome that can be accepted
Instead of saying “positions will improve next month,” propose a verifiable task. For example: “We'll match five queries about office equipment maintenance to pages, note any missing terms, and agree on updates to two pages.”
Specify the person responsible, deadline, and deliverable: a table of queries and pages, agreed changes, and a check of the published text. Search performance can then be monitored afterward, rather than treated as an outcome a contractor can guarantee with a single promise.
A concise response to the client could be: “We see no improvement for the selected queries in September. The returns link and form have been fixed, and the results have been checked. We'll continue the search work separately: by 7 October, we'll match the queries to the relevant pages and present an update plan.” If no work has been completed, don't include it in this response—start with the outstanding tasks.