Before starting an update, save the URLs and the results you will compare the new version against. Otherwise, after publication, the team may disagree about whether the issue existed before and which pages were checked.
A brief note in the task, a relevant report, and a few example pages are enough. This is not a website backup or a promise that reChecker includes a snapshot of the entire system. Arrange technical backups separately with the person doing the work.
Choose the URLs the change could affect
First, clarify the scope of the work. “New catalog” is too broad; “we’re changing the title and price in the shared product-card template” makes it possible to choose examples. A template is shared markup that the site uses to display multiple pages.
For this update, choose a problematic product card, a working product card, and a special case—for example, a product with a size selector. Record why each URL is needed. That way, the complex case won’t be replaced after publication with a convenient, simple page.
If sections are structured differently, agree on separate examples. Clarify what is being published now and what will come later. A practical preparation checklist is in the pre-release check article.
Save the specific “before” state
Below is a sample note for a product-card update. Replace it with your own URLs and values:
| What to save | Example |
|---|---|
| Change | Fixing product-card titles; the price must stay the same |
| Problematic URL | /catalog/chair, tab title “Catalog” |
| Working URL | /catalog/table, tab title “Table — Store” |
| Special case | /catalog/chair-large, product with a size selector |
| Source | Audit 04.10; all three URLs are included in the check |
| Manual check | 04.10 at 09:20 MSK; prices and size selection work |
| Expected result | Different product names in the titles; prices and size selection are preserved |
A screenshot is useful when it shows an important detail; copying the entire page into the task is not necessary. For a disputed finding, first check that the issue can be reproduced. Otherwise, it is unclear what exactly you are fixing.
Check the audit date and the relevant URLs. The daily automated check covers up to 100 pages; a recent general report does not mean the selected product card was included.
Note settings that affect the comparison
If you will evaluate rankings, save the query set and region. If you change the region at the same time, the before-and-after comparison has a different condition. Don’t attribute a search difference solely to the development work.
For AI-related questions, record the questions and the period covered by the answers received. For an important page, record its URL and the required text. If an editor replaces that text, agree when to update the setting: the disappearance of an intentionally changed phrase is not the same as a page failure.
In Website Monitoring, sources have different dates. Don’t call the whole set a “snapshot as of today” if the audit is recent but the search result is a week old. Label the date next to each item you save.
Agree on the check and add the result alongside it
Before publication, name the person who will check the result and define the completion criteria. In the product-card example, the criteria are a new result for all three URLs and a manual price/size check. An increase in the overall score does not replace these items.
After publication, add the time and repeat the check on the same variants on the main domain. Keep the original entry. Add this next to it: “06.10 at 11:00 MSK: product names appear in the titles on all three URLs; the price and size selection work.”
If a URL was not included in the new audit, run a separate suitable check. If either side of the pair fails, the task is still open. Share the necessary sources with the person checking in the agreed way: a private report does not become accessible to another person just because you sent them a link.