Right after launch, open the public domain, check the main pages, and submit an agreed test inquiry. Save the first technical audit with its date: later, you can compare fixes against this result.
You can follow the first setup instructions to configure the region, queries, and AI questions. This article covers checking a website that has just been moved from a test address or opened to visitors for the first time.
Check that the primary domain is open
Record the primary domain, the active protocol, and the address visitors should reach. If the site opens at several address variations, check the redirects manually. Complete the move from the test domain before saving the baseline; otherwise, the comparison will show differences between two environments, not changes to one site.
Open the homepage in a new window, then visit the contact page and a service page or product page. Check the final URL and the content. Make sure this is the published site, not a test environment with a similar design.
If the site is still password-protected, record this limitation and check the public version after the restriction is removed. A successful check of the test environment does not show what an ordinary visitor can access.
Choose different page types
Make a short map of the page types. For a service website, these might include the homepage, a service category, an individual service, the contact page, and an article. A store will also have a category page, a product page, and informational pages. Choose examples with different layouts rather than ten nearly identical URLs.
The automated daily audit is limited to crawling up to 100 pages of the connected site. This is a reason to organize the initial check sensibly, not to claim that every large site is checked in full every day. The scope of a separate full audit depends on the selected plan.
Prepare a list of URLs to check before launch. Mark which pages are included in the audit and which you will also open manually. The article about pages to monitor explains the selection criteria. At the first stage, a representative sample matters more than a long list without a clear purpose. Save it with the report so that subsequent acceptance checks cover the same pages.
Review the first completed report
The first completed audit is a baseline set of observations. Check the completion date, the URLs examined, and the report's limitations. If a check was not performed, do not mark it as “all good”: no result is different from a confirmed absence of an issue.
Divide the findings into three groups: issues that prevent the site from opening or being used, issues affecting multiple pages, and issues that need clarification. This order helps you avoid starting the launch process with cosmetic score improvements. The name of an error alone does not show its actual impact on visitors.
It makes sense to review the first report with the developer before making extensive changes. For each selected issue, provide the URL, a reproducible fact, and the expected state. The SEO audit guide provides a detailed sequence. The report itself does not prove that every page on the site is working correctly, especially if some URLs were not crawled.
Confirm the inquiry and record the first tasks
Agree with the recipient on a clearly labeled test. Submit the form, save the response screen, and ask them to find the inquiry in the live system. For a store, separately confirm that the test order was saved using the agreed scenario. Checking the URL and expected text does not perform these actions for you.
Record one example: “example.ru was open on 4 October at 10:00; the first check was completed at 12:00; the homepage, service page, and contact page were checked; the manager found the ‘Launch test’ inquiry; the delivery link needs fixing.” If the audit is still running, leave the result date blank.
Send the developer the first confirmed issues, with URLs and the expected result. Use the technical check for an individual URL, and view new recurring results in the monitoring dashboard.
The history starts with the actual checks performed after setup. Do not record the absence of previous data as the absence of previous issues. After the first fix, repeat the same navigation or action and add the result date to the launch task.