Start with a brief explanation of why you checked the site: after importing products, changing the menu, or applying a new template. Include the date, the pages checked, and the three main findings. The client should understand what was found and what decision is needed now.
Next, prepare a link to the audit and check it without signing in to your account. If the report cannot be opened by everyone who receives the link, share an agreed manual summary through a private channel. Completing an audit does not, by itself, give the client access.
Explain why you checked the site
State the reason for running the audit. After importing products, the question might be: “Were the product images and metadata preserved?” After changing the menu: “Where do the links to the renamed section lead?” This is clearer than explaining every possible audit feature to the client at once.
Specify the domain and section. If the contract covers several sites, avoid saying “our site”: the recipient needs to know exactly which one. Check the project name in the email and in the attached link. Selecting a neighboring domain by mistake can turn even a well-written message into the delivery of someone else’s material.
Clarify from the outset which questions the check does not cover. A technical audit does not confirm that a lead reached a manager or that a visitor completed a payment. If the client asks about sales, suggest a separate check of the relevant user journey and name its data source.
Specify the date and pages checked
Put the measurement date in the first few lines. The date you write the message may be different: the audit was run in the morning, but the discussion started several days later, after the next release. The recipient needs to understand which state of the site the document describes.
List the pages actually checked and any limitations. For a sample handoff, you could list six product pages and a category page. If this is a selected sample, describe it as such. Don’t turn seven successful responses into a conclusion about a catalog with thousands of products.
In reChecker, the daily subscription check is designed for up to 100 pages; manual full audits have their own packages. These limits explain how runs are organized, but the accompanying text should be based on the actual result of the specific check. “Up to 100” does not mean “all 100 were successfully checked.”
Choose a few important issues
Select a few items that require action or approval now. Leave the rest in the detailed document. Prioritize by the page’s role, the confirmed symptom, and the consequences for visitors—not by the number of rows in the issues section.
For a sample store, these could include an unavailable image for an active product, a menu link to an old category, and a template variable in the title (the page name shown in the browser tab). Each row should answer three questions: where the issue was found, what needs to change, and how to verify the result. If the cause is not yet known, identify it as a hypothesis.
Don’t write “this definitely reduces sales” when you measured only technical status. You can explain the practical risk: a person cannot see an image or lands on a missing page. A causal link to revenue cannot be established without a separate check.
Connect the issue to the work
A table is for discussion, not for creating artificial reporting. For example, it might look like this:
| Finding | Action | Confirmation of completion |
|---|---|---|
| The photo for the selected product returns 404 | Fix the path in the import source | The file is available and the photo is visible after a new import |
| The menu leads to an old category | Update the link source | Direct access to the correct section without a redirect chain |
| A CMS variable remains in the title | Fix the template and product data | The correct title appears on the sample product pages |
Add an assignee and deadline to the team’s working document if they have been agreed. Don’t invent them on the client’s behalf. If no one has been assigned yet, honestly state that an owner needs to be chosen rather than promising to fix the issue by a specific date.
Give access to the details
A private result does not become public when the audit is completed. An address copied from your session may require the user to have access. For a full audit, at the top of the completed result, click “Share report” → “Create public link.” Then use “Copy public link.” Publishing details through a separate block uses a preview and explicit confirmation from the owner.
Agree on disclosure of project data before making it public. Anyone who receives a public link can forward it. Do not enable separate permission for indexing automatically just to share the report with a client: access to a document and publishing it for search are different things.
Open the selected address while signed out. Check the project, date, number of pages, and content. If the details cannot be disclosed, use an agreed private method to share a manual summary. Don’t promise built-in protection based on an email allowlist or automatic hiding of client information.
Prepare a short message
Draft the text first and read it separately from the report. The recipient should understand the task without searching for the right paragraph on a long page. Don’t attach several nearly identical links without explaining which one is the main link.
Sample message for training:
We checked the store’s sample product pages after the import on 4 October. The sample includes six product pages and a category; this run does not confirm the whole catalog. We found three items to review: one product photo, an old menu URL, and a variable in the title. The table lists the actions and how to verify the result. We need approval of priorities and assignment of an owner. We’ll run the check again after the fixes are published.
More details: How to prioritize issues in an SEO audit report.
More details: How to conduct an SEO audit of a website: a step-by-step guide.
Check results are available in the website monitoring dashboard.