Choose a main service and follow the customer journey: open the page, understand the terms, find a way to get in touch, submit a test inquiry, and receive confirmation from the manager. Use the technical report to check this URL and similar pages.
Suppose a company repairs washing machines in Tula. To start, use the /repair-washers page, the query “washing machine repair Tula,” and the service call form. This ties any report finding to a specific service.
Check the offer and contact details
Choose the main offer the company actually provides. Write down the service page, the related search query, and the contact method. If the service appears at several URLs, confirm which one is considered the primary page and why the others exist.
Open the page from the perspective of a new customer. Is it clear what you do, where you work, how to ask about the price, and whom to contact? Don’t judge the content by word count alone. A long text may not answer a visitor’s simple question, while a short page may contain everything needed to get in touch.
Make sure the phone number, service area, and way to ask about the price are consistent with the company’s information. If the service is now called something else, clarify the text first; don’t change the URL without checking existing links.
Match the region, query, and page
The search project’s region should reflect the actual service area. If you serve one city, don’t mix those observations with an offer for the whole country without explaining why. The company’s address and the location where the service is provided may differ, so explain the decision in the project settings and on the page.
Check whether the city, contact details, and terms are consistent. Example for illustration: a page describes a technician visiting customers in one city, but the form lists only another region. This is a reason to clarify the offer manually, not something an automated audit will necessarily detect.
In an external spreadsheet, write “query → /repair-washers → service call.” The guide to building a semantic core can help you get started. If the home page appears for the query, compare its content with the service page. A different URL, by itself, doesn’t indicate an error.
Review the finding for the relevant URL
Check the completed audit for the relevant URL and when it was run. Findings about links, images, metadata, and page responses may require different people to address them. For a template-wide issue, check several service pages before creating a separate task for every URL.
The subscription’s daily automated audit covers up to one hundred pages. If the catalog of services and publications is larger, the current sample doesn’t confirm the state of the entire site. For an updated section, you can choose a manual audit of a suitable scope. The unlimited number of manual runs included in a paid subscription does not change the package’s page limit.
For example, the report flags a broken “Prices” link. Click it from the service page, save the destination URL, and tell the developer where the pricing information should open. For a template-wide issue, check two other services that use the same block. The guide to URL structure can help you understand the navigation paths.
Test the form with the recipient
Agree on a safe test: what to write, who will receive the inquiry, and how it will be labeled. Fill out the form as a regular user would. Save the confirmation screen, but verify the result with the recipient or in the system that actually stores the inquiry.
If a success message appears but the inquiry doesn’t arrive, that is a separate issue in the submission flow. Checking that a page is accessible does not prove that data was delivered. Likewise, the presence of a verification text confirms only a limited signal for an important URL; it does not submit the form for you.
Use a clear label such as “Website test,” agreed-upon values, and the date. If the manager can’t find the entry, save the screen, the submission time, and where they expected to find it. Pass these details to the person responsible for the form.
Repeat the journey after the fix
Start with the same /repair-washers URL. Check the offer, phone number, link to the pricing information, and form. For a general fix, repeat these steps on the other service pages you gave the developer as examples.
Run a new technical check using the page audit. It should correspond to the published fix and examine the relevant URL. If the report is old or still running, save the manual result first, then wait for the new report.
In the monitoring dashboard, check new findings and the dates of search measurements. Assess search rankings and receipt of inquiries separately: the form may work after the fix while the ranking continues to change for other reasons.
Task completion note: “On the repair page, the pricing link opens the correct URL; the test from 4 October was found by the manager; two other service pages were checked.” If the company’s terms or service area change, update this checklist along with the page content.