Open “History,” find the check from before the site change, and select the address you worked on. Then compare it with a new check. History helps you reconstruct the previous state if the record shows the date, the pages checked, and the finding itself.
With a subscription, history is stored for 90 days. If you need the report for a long-running project or work approval, save the necessary information somewhere you control in advance. A public link does not replace your own record of which fix was checked and when.
Identify the result you are looking for
You may be looking for the original state before improvements, confirmation of an old finding, or information to pass on to a contractor. These tasks require different parts of the document. Do not forward a large report without explaining what the recipient should take from it.
If the question is about whether a service is available today, a historical result is not enough. If you need to reconstruct which addresses were checked before a migration, the old report may be your main working source.
State your goal in one sentence in a short note. For example: “We’re checking which canonical (the primary version of a page’s address) was recorded for the category before the template change.” This framing connects the history to a specific signal and helps you find the right record.
Check the date and crawl scope
Find the audit date and the list of pages included. Viewing it today does not update the results of an old run. Do not relabel the report as showing the current state just because the link opens.
Check whether the address you need was included. If the report covers only the homepage, a separate service page is outside the confirmed scope. The average score for checked pages does not show the status of every URL that existed on the site.
The subscription’s daily automated audit covers up to one hundred pages. Manual runs have a selected package size. These limits also matter for old documents: you cannot describe a page’s absence from the sample as absence of a problem.
Find the same page
The old address may have been removed, redirected, or renamed. Compare the path and purpose, then open the final URL. A similar heading on a new section does not automatically make it the same object being monitored.
Material on URL structure can help describe the transition. Record the old address, the current address, and the agreed relationship between them. If the service’s purpose has changed, treat it as a separate version, not simply a new result for the old page.
If the domain or template has changed, separately clarify which signals are still comparable. You can retain historical figures, but the overall conclusion “there are fewer errors” requires understanding what was actually checked at both points.
Record the changes in a table
Consider a sample report for a category from before a migration. The site now has a new structure. An external table helps separate past facts from current questions.
| Old audit record | What is historically confirmed | What to check now |
|---|---|---|
| Address was accessible | Response on the run date | Current final URL |
| Duplicate title found | State of the checked pages | New template and sample |
| Service was not included in the audit | No result was recorded | Run a separate check |
| Canonical pointed to a different path | Recorded directive | Purpose of the current page |
Do not add facts to the historical column that were not in the report. A blank row is not proof that the previous state was correct.
Confirm the result with a new check
Start with pages that matter to the business and those where the finding may still apply. Specify the list so the new sample includes the objects you need. Do not treat a new homepage audit as confirmation of an old task concerning a category.
In a technical audit, choose the run scope based on what you are investigating. With an active paid subscription, included manual audits can be run without a monthly quota, but the scope of the individual package and parallel-work limits still apply.
For a local check of the result, a suitable sample is enough if you state its limits honestly. Checking a few examples of a template does not entitle you to automatically claim the status of all unknown URLs.
Save the information before the retention period ends
Subscription history is retained for ninety days. Do not promise a customer permanent access to all past results. If you need the materials for a handover or a long-term case, arrange authorized storage for them in advance.
Save the date, URL, and relevant findings in a working document. If you use an export, open the file you receive and check that it contains this information.
The team’s working archive should have clear labels: project, date, scope, and purpose. Do not store private URLs and client information alongside public materials without access controls. History is useful only when it can be found and read correctly.