In a monthly client report, show what you fixed, how you verified the result, and what remains to be done. A list of every notification would leave the client to work out the conclusions themselves. Start with a few key facts and decisions.
reChecker provides technical and search data. You prepare the document as agreed with the client; a custom report of the work you have done is not generated automatically. Below is an example that you can shorten into an email.
First, specify the period and scope of the check
State the website, the dates of the work, and the date of each data source. For example: “example.ru, work completed in September; latest technical audit — 30.09”. If the search data was collected earlier, label it separately.
The daily automatic audit checks up to 100 pages. For a large catalog, that is only part of the website. If you ran a manual audit, state the scope you selected and the actual results; do not write “the entire website was checked” without evidence.
Keep data from different websites separate. The total number of errors across five domains does not tell the client what is happening with their store. For guidance on reading an individual source, see the technical audit guide. In the website monitoring dashboard, check the latest results before adding them to the document.
Show completed work on specific URLs
Sample report for an online store:
| Section | What to tell the client |
|---|---|
| Fixed and verified | 12.09 Replaced the outdated return-policy link. /returns opens from the homepage menu and from a product page; checked after publication |
| Published, verification ongoing | 29.09 Updated product page titles. Two URLs have been checked; product variants still need to be compared |
| Problem with cause not yet established | 23.09 A visitor reported a brief catalog error; logs for that time period have been requested |
| Next task | By 05.10, check the product variants and finish the title task |
| Needed from the client | Confirm the final return terms for the /returns page |
This kind of report shows the status of each task. “Updated the titles” without a follow-up check describes an action, not a confirmed result. Do not conflate these statuses.
For important work, include the original URL, date, and verification method. For a technical change, a new audit of the same pages is suitable; for a form, use confirmation that a test submission was received. See the process in the article on verifying fixes.
Answer questions about search and inquiries separately
If the client asks about rankings, specify the queries, region, and comparison dates. Different data groups are updated at different frequencies, so a single dashboard snapshot may contain different dates.
Inquiries, sales, and visits require a separate company data source. A technical audit score does not give you the number of orders. If no such source is available, write: “The fix has been verified; the change in the number of inquiries has not been assessed based on the available data.”
Do not attribute revenue growth to replacing a single link without evidence. You can describe the useful result directly: the required page now opens from the menu. That is enough for a report on this work; a conclusion about sales would require a different comparison.
An unknown result should also have a follow-up. Instead of “data not available yet,” state who will request it or when the next check is expected. If this is not part of the ongoing service, identify it as a question for the client.
Before sending, check the links and next steps
It should be clear which report item each link supports. Dozens of attachments without explanation make verification harder. Keep the relevant sources in the main document; the rest can be stored in a working archive.
A reChecker report does not become public when an audit is complete. Check access using the same mode the client will use to open the link. Agree on how information will be shared; do not publish client data for everyone’s convenience.
In the next-step plan, name the task, URLs, and completion criteria: “check three product page variants, confirm that their titles differ, and close the task.” At the next monthly review, start with that promised step. If it has been postponed, state the reason and the new decision.