Give them the latest completed audit, a list of open tasks, and the project’s current settings. Add the date and the pages checked for each result. Explain separately what has already been fixed, what was intentionally left as is, and what has not yet been checked.
Start with one example. If the site owner has decided that a staff form should be hidden from search, say so explicitly. The new specialist can distinguish an intentional restriction from an accidental error and won’t start changing it without a reason.
Gather reports and settings
Share the latest completed technical audit and, if available, a suitable earlier one for comparison. Include the page coverage. On a large site, a daily automated check of up to 100 URLs does not replace information about the entire catalog.
For rankings, save the region and the set of queries. For AI, save the questions, the observation date, and the answers actually received. Don’t group all sections under a general label such as “data for today”: technical audits, search checks, and model responses have different dates.
Add the main URLs, a list of important scenarios, and the technical contacts. You’ll find the region and query settings in the “Search rankings” tab of the monitoring dashboard. Also save the questions used for AI so the next contractor knows which answers you compared.
Explain findings that have already been reviewed
Add a status to significant findings: confirmed, needs checking, fixed and awaiting a repeat result, or accepted as an exception. The last status must include an explanation from the site owner or team. Otherwise, it can look like an attempt to hide an error.
Don’t replace evidence with “the previous contractor said it was fine.” Include the URL, the date of the check, and the reason for the decision. For example, a page is intentionally blocked from indexing because it contains a staff form; this is verifiable context. The same status on a regular service page calls for a different discussion.
For example: “/account-form is blocked from indexing, as decided by the site owner on 20 September: the form is for staff. /repair should remain available to search engines; this restriction does not apply to it.” Name the person who can confirm the decision.
For a recurring defect, provide different examples of the same template issue, not a list of identical rows. The guide to template errors can help you choose them.
Provide a list of unfinished tasks
| Work | What is already known | What to do next |
|---|---|---|
| Delivery link | /old-delivery is accessible from the menu and returns an error | Replace the link with the current address |
| Card headings | Three URLs have the same Title | Check the template and agree on a naming rule |
| Service form | The success screen appears, but the manager receives no submissions | Check data transmission and storage |
| Brief outage | The time and URL are recorded; the hosting provider has not yet responded | Get an explanation based on the logs |
In your list, add the date, source, and current assignee. Title means the page title, usually visible in the browser tab. If the cause has not been found, say so: the task is to diagnose the issue.
For an unknown cause, record what the previous contractor has already checked: which pages they opened, when they submitted a test, and whom they contacted. Continue the investigation using the guide to audit findings.
Check that the contractor can continue the work
Ask the new contractor to choose the first task and identify the address they need, the required result, and any missing information. For example, for the delivery link, they can first reproduce the navigation, then check other pages in the shared menu and report the publication time.
Agree in advance on how to share results. Don’t assume there is a special “contractor” role or shared account access. If you use a link for shared viewing of the full audit, enable public viewing separately. The report does not become public automatically when it is completed.
Check that notifications are set up for the new recipient under “Settings” → “Where to send notifications.” For email, click “Edit addresses” and check the recipients in the profile. For Telegram, complete the required connection. Then ask the recipient to confirm the first real notification. Share access details separately, and keep the original package of reports and decisions with the site owner. The subscription history states 90 days; save the information needed for the work in your own document instead of relying on indefinite storage.