Read the report as someone seeing your website for the first time. They should be able to understand the date of the check, the pages checked, and the findings. Review internal URLs, details of unfinished work, and instructions for the person doing the work separately before publishing.
Start by listing the information you can show external readers. Then check the published link without signing in to an account. An approved text and an accessible report are two separate conditions to verify.
Decide what the public report is for
Make a list of what you want to explain to external readers. For example: a link to an image file that does not exist was found on a selected product page; the path source was fixed; a follow-up check found a working image. The developer's contract cost or the history of discussions about responsibility are not needed for this explanation.
A working list may include the person doing the work, the release deadline, costs, an agreed compromise, and open questions. These details are useful to the team, but publishing them requires separate permission. They do not become public technical facts merely because they are recorded alongside audit results.
Separately identify data that comes from outside reChecker: sales, inquiries, the contents of requests, and budgets. Do not present these as technical report metrics. The data owner decides whether to add this information to the article, and its source must be stated clearly.
Review the content piece by piece
This matrix helps assess usefulness and possible disclosure before granting access. It does not describe automatic removal of fields from a completed report.
| Sample store information | For a public explanation | For internal work |
|---|---|---|
| Check date and crawl scope | Needed to understand the result | Needed to compare runs |
| Public product page URL | May be included after approval | Needed to reproduce the issue |
| Technical finding and confirmation | May be included with limitations | Needed for the task and to verify the result |
| Developer's name and contract cost | Usually not needed by readers | Discussed with the team |
| Customer contact details and request contents | Not included without a separate basis | Shared according to the project's working rules |
| Assumption about sales growth | Not presented as a proven result | Checked against separate data |
For each row, record the decision and who approved it. Do not use the word “anonymous” if the company can easily be identified from the domain and description.
Review page URLs
A public report may contain the main URL and a list of pages checked. Seeing the domain is not enough: read the paths and parameters. A route can reveal a future promotion, a new product range, or a project name known only to the team so far.
The meaning of a URL may remain sensitive even after contact fields are removed. For the sample store, URL /catalog/new-collection-preview/ reveals an unreleased collection. This is a reason to reconsider publication, even though the URL contains no person's name or contract number.
Do not edit only the link label while leaving the original URL as its destination. If the prepared report reveals unsuitable information and the current interface does not let you produce an approved version, keep it private. You can prepare a separate public explanation, clearly identifying any sample URLs that have been changed.
Explain the scope of the check
Readers need to know the scope, date, and actual volume checked. If the audit ended after checking only some of the discovered URLs, do not shorten that to “the site was checked.” Specify which templates are represented and which areas were not included in the sample. An unchecked section does not automatically receive a positive assessment.
For a subscription, the daily audit covers up to 100 pages of the connected site. Manual full checks have packages of up to 25, 100, 500, and 1 000 pages. The name of a larger package does not prove that all pages were processed successfully: unavailability and discovery limitations still matter.
Limitations do not invalidate a finding on a specific product page. They define the limits of the conclusion. You can confirm that an image path was fixed on selected products without declaring the entire media library fixed. This approach is discussed in the guide to SEO audit priorities.
Add explanations for readers
Potential customers benefit from knowing what was checked, what the error was in plain language, and how it was confirmed. Developers need exact states, URLs, and reproduction conditions. Managers often need only a short summary with the decision and the person responsible. One public document does not necessarily replace all three formats.
Publishing a detailed reChecker report requires a preview and explicit approval. A share link for a full audit opens the audit through a separate mechanism. Assess both options based on their actual contents, rather than assuming that the word “share” means access is limited to the client.
Choosing whether to make something public and allowing it to be indexed are also different things. Disallowing indexing does not prevent someone from forwarding an accessible URL. For information intended for one recipient, agree on an appropriate private channel for sharing it, and do not publish it just to make the link convenient.
Check the link from outside
After preparing the material, ask a team member unfamiliar with the project to read it. They should understand what was measured, when it happened, and why a particular action was proposed. If they have to guess the scope of the check, add an explanation; if they see unnecessary details, revisit the matrix.
Check the document without your own authorization. Read the sections on pages, findings, and limitations, not just the top-level score. Compare the published version with the approved preview. If there are several domains, make sure the link is for the selected store.
You can clarify the purpose of regular monitoring on the site monitoring page. It helps continue the work after publication, but the public material remains a description of specific data. The current account status and a dated analysis should not be treated as interchangeable.
Read more: How to conduct an SEO audit of a website: a step-by-step guide.