Tell the developer the exact URL, what happened during the check, and how it should work. Include the report date and how to repeat the check. One task with a clear example is enough to start investigating.
If the problem has not yet been confirmed, ask the developer to investigate it rather than fix a suspected cause. For example, a broken link does not necessarily mean a server failure: the developer should first investigate the link.
Copy the template and fill it in with your details
Задача: исправить [конкретное действие или значение].
Адрес: [страница-источник и адрес, где заметна проблема].
Что получилось: [шаги и результат в браузере или отчёте].
Когда: [дата, время, часовой пояс; дата аудита].
Как должно работать: [нужный адрес, текст или действие].
Проверка после публикации: [те же шаги и страницы; кто подтверждает результат].Attach the relevant part of the report or a screenshot. You can include the full report for context, but highlight one finding in your message. If access to the report is private, agree on how to share it: it is not published automatically.
Example task for a broken link
Fix the “Delivery” link in the menu on example.ru. When clicked from the homepage and /catalog, the browser opens /old-delivery and shows a “not found” page. Checked on October 4 at 11:20 MSK; the same link was flagged in the audit dated October 4. It should go to the active /delivery page. Check whether the same menu is used on other pages. Let us know when the change is published. We’ll verify the link from the homepage, a category page, and a product page.
This describes a specific behavior without prescribing how the code should be changed. After investigating, the developer might fix a shared block or another source of the link. If you don’t know the destination URL, first agree on it with the content owner.
For a page title, specify the exact value or rule, such as the product name followed by the brand. For a form, describe where the submission should appear. For more on structuring a task, see the guide to handing off an SEO finding.
List several URLs for a shared issue
Specify which pages are covered by the task and what has not yet been investigated. For a template issue, include two or three representative URLs, including a possible exception. For example, a standard product page and one with a different set of specifications.
Don’t write “across the whole site” if you have only checked some pages. The daily audit checks up to 100 URLs; a manual run has its own scope. Say which URLs you have already checked and which still need to be investigated.
If you don’t know whether the issue affects a shared template, add a separate request to check. The instructions for investigating audit findings can help you start confirming the issue. When the task is to investigate, finish by explaining what was checked and what information is still missing.
Check the result after publication
Ask the developer to state when the change went live on the production site. Open the original URL and repeat the steps in the task. A check on the developer’s computer or a test domain does not yet confirm that it works for visitors.
For a technical finding, run a new page audit after publication and make sure the relevant URL was checked. For a form, perform the agreed test with the recipient. The overall score does not replace these steps.
The final comment can be brief: “On October 4, after the release at 12:00, the link opens /delivery; checked the homepage, category, and product page; task closed.” If the result differs from the report, include the date and conditions of the manual check. See the instructions for checking after a fix for the full process.