Start by checking whether the site is available, then open the latest completed audit and review new findings. If nothing urgent comes up, check tasks for which a contractor has already reported a fix. You do not need to reread the entire old list of issues every day.
Different sections update on different schedules. So the date next to a result matters more than the date you logged in: yesterday’s report may describe a version of the site that has already changed today.
Check availability first
Start with the selected project and the latest availability check result. Look at the status and measurement time. If the site opens in your browser now, but the latest result reports an outage, compare the times rather than immediately assuming the message is wrong. A brief incident may have ended before you checked.
If there is an alert, open the main address and an important page in a new tab. Note which address appears in the browser bar, what you see on the page, and whether the problem happens again. If the check was run a while ago or its status is unknown, do not call the site available based only on an earlier green status.
If there is an outage, save the URL, time, and what you see now. Scheduled checks run every five minutes, so a brief issue between measurements may go unnoticed. The status values are explained in the availability monitoring guide.
Open the latest completed audit
Check the date of the completed audit and its coverage. A report that is still running is not a newly confirmed status for all pages. If only the previous result is available, comparisons should use its date. After a major site update, that report may no longer reflect the published version.
Review new and recurring findings, then resolved ones. Do not start with the overall score: one important issue on a contact page may need more attention than several similar findings in an archive. For each significant change, you need a URL or group of pages to determine its scope and which users the problem affects.
The daily audit checks up to 100 pages. After changing a large catalog, check whether the relevant addresses were included. If not, choose a suitable manual audit or open those pages separately.
Decide what to do next based on a specific signal
| What you saw | What to do | What to record |
|---|---|---|
| The site does not open | Open the main address and an important page, then contact the technical contractor | URL, time, browser message |
| The same incorrect heading appears on three product cards | Compare the cards and send examples to the developer | Three URLs and the expected title |
| The score has gone down | Open the findings that changed | Which check changed and where |
| A new audit is running | Wait for the result; check any urgent issue manually | What is already known and what is pending |
For example, yesterday the developer was asked to fix the delivery link. Today it is still flagged in the old report. Check when the fix was published and click the link on the site. If the new audit has not finished yet, do not create a duplicate task: add the result of the manual check to the existing record.
Review search changes alongside the date
Rankings are tied to specific queries, a region, and a measurement time. During a brief daily review, look for significant changes in important queries, then open the page found. If the result URL has changed, check whether the same document now answers the query.
Different groups update daily, weekly, or monthly. Do not compare a figure from an old monthly group with today’s daily measurement as if they were simultaneous results. Similarly, competitor comparisons use saved Yandex search results, not a live view in your browser.
If the position or URL found for an important query has changed, save the query, region, date, and address. The SEO monitoring guide covers the basics.
Finish your review with one record
An external spreadsheet or your usual task tracker will work for recording decisions. For example: “04.10, audit dated 03.10, incorrect Title on three product cards; examples sent to the developer; response expected 05.10.” Here, Title means the page title set by a meta tag and usually visible in the browser tab.
On a quiet day, it is enough to note: “Reviewed the latest results; no new problems on the checked pages.” During an outage, the record should include the contact person you reported the problem to. If the result is unknown, specify the next step: wait for the audit or check the URL manually.
The next time you open the reChecker dashboard, start with these unfinished actions. Set aside a separate day for detailed planning: the main purpose of a daily review is to notice what is new and check a fix that has already been promised.