Choose a representative page
The homepage is not always the best starting point. If most visitors land on a product page or article, that page deserves its own audit. Note its purpose and the main action users should be able to complete. One page’s result must not be presented as a comprehensive measurement of the whole domain.
Check public access
Open the address without signing into an account. Check for login screens or protections that prevent the engine from reading the expected content. Never submit links containing access tokens or personal information. Ordinary public URL parameters are supported; sensitive parameters are rejected.
Record the conditions
Choose mobile or desktop and note the time, engine and recent changes to the website. Record any banners or personalization experiments that change the display. The report’s preview can help verify the observed content. A good score on an error page is not a useful measurement of your service.
Plan the next check
Before testing, decide where to save the result and who will receive it. Enable local history for later comparison or export JSON. After making a fix, repeat the same scenario. A report is most useful when it supports a decision, an action and a documented check.
Your next action
Choose one page, note what you want to check and save a report. After making a change, use comparison to examine the differences. Review the context before concluding that there has been an improvement.
Open the optimization checklist ↗Sources and scope
This guide suggests a working method. No numerical improvement is guaranteed. To check definitions and explore the audits: official documentation.