Save the original URL and the exact finding. After the fix, run a new check on that page and make sure the finding is gone and the required content is still accessible. Then prepare a link to the result.
Suppose a developer updates the menu after a category is renamed. A good report will show the old link, the page with that menu, and the route to the correct section after the fix. The statement “everything is fixed” alone is not enough for a manager or another team member to verify it.
Choose a fix to verify
Start with a narrowly defined task. “Improved the store's SEO” covers too many events. “Updated menu links after renaming a category” defines the scope: specific link sources, the old address, the new section, and the visitor's expected route.
State why the task came up. In a sample store, the “Kitchen Chairs” category was renamed, but some pages continued to link to the old path. Visitors encountered an extra redirect or a missing document. This is observable behavior; you do not need to claim in advance that it caused lost sales to explain it.
Keep a separate list of other changes made during the same period. If prices changed, products were added, and an advertising campaign was launched at the same time, these events will matter when assessing subsequent metrics. They do not prevent you from accepting the link fix, but they limit what you can say about the commercial outcome.
Save the previous result
Record the date, the source page address, the link's destination, and the response chain received. Attach the data from the specific check and, if needed, an HTML snippet. Readers should be able to understand the issue without trusting the caption “it was bad before.”
State the scope of the sample. If the old path was found on the homepage and two product pages, confirm those specific pages. The assumption that the site uses a single menu generator does not prove that every site template was checked. Identify the hypothesis and how it will be checked further separately.
Save the original measurement before the fix, if available. Do not reconstruct past responses from memory after the release. If there is no old report, state that limitation honestly and use any saved task or snippet as a different type of evidence, not as a complete previous audit.
Describe the change made
State what was changed in the implementation: the source of the menu route, the values of an imported field, or the output template. “Fixed errors” does not explain the link between the cause and the result. For the sample case, “updated the path in the shared navigation generator” is more useful.
State when the change was published and whether any separate cache-related actions were needed. The task date, commit date, and date the change went live on the public site may differ. A repeat check run before release does not confirm the state seen by visitors.
Do not attribute automatic changes to someone else's site to the service. reChecker performs diagnostic checks and displays results; the project team changes the template. Make the roles clear in the write-up: the tool detected or confirmed the issue, the developer made the change, and the person responsible accepted the work.
Rerun the check on the required page
Use the previous addresses and check the same condition after publication. For a menu, check the link's destination and the final document. Add current neighboring categories to the sample to make sure the shared rule did not break their routes.
If the new audit covers different URLs, first identify the overlap. The status of pages not included in the rerun remains unknown. A higher score on a new sample does not automatically close the previous task. The comparison process is covered in the technical audit guide.
A regular subscription audit is limited to up to 100 pages of the site. Manual full runs are available in packages of up to 25, 100, 500 and 1 000 pages. With an active paid subscription, included manual checks can be run without a monthly quota. The page limit and the limit on simultaneous tasks still apply.
Prepare a short table
Do not fill the table with general assessments. Link each item to an observation and a verifiable outcome. Sample for a renamed category:
| Stage | Row content | What it proves |
|---|---|---|
| Before | The menu on the test product page leads to the old path | A specific outdated route is documented |
| Change | The shared source of the route was updated | The team's action between checks is described |
| After | The same product page leads directly to the correct category | The new behavior of the selected page is confirmed |
| Limitation | Archive pages were not included in the sample | The result for the archive as a whole remains unknown |
Screenshots are useful as illustrations, but keep exact values for addresses and statuses. Do not show a successful new product page in place of the previously problematic one without explaining the substitution. For a migration, check separately what happened to the old URL and whether internal links are up to date.
Give access to the required report
A working analysis may contain addresses, a client's name, and task details. Agree on which information can be disclosed before publication. A specialist's permission to run a check does not replace the owner's permission to use the project in public materials.
Publishing a detailed reChecker report requires a current preview and explicit confirmation. Indexing can be enabled separately and depends on the preparation conditions; it does not guarantee that the report will appear in search results. For a full audit, at the top of the completed result, click “Share report” → “Create public link”, then “Copy public link”. This access is opened separately from detailed publication; check what it contains. The process for granting and revoking access is described in the guide to report access.
Open the approved material without signing in and read every section, including addresses and limitations. If you used fictitious URLs instead of real ones, note this in the write-up. Do not present a sample table as documented client metrics or assume that material already made public is fully private.
More: How to prioritize items in an SEO audit report.
Check results are available in the site monitoring dashboard.