Practical guide
Plan your Google workflow
Measure search results for a declared location, language, query, and device profile.
Start with a reproducible sample
Use a fixed keyword set and keep browser language, login state, and result depth consistent.
- Define one target, a permitted task, and the settings that must remain fixed.
- Check the exit IP and location, then run the complete task in the intended client.
- Record valid results, errors, traffic, and timing. Change one setting at a time.
- Scale only after the sample meets your acceptance criteria and the traffic budget.
What makes the test meaningful
Record organic positions and advertising separately, with the query and observation time.
Limits to account for
IP geolocation is only one input to search personalisation. A proxy cannot guarantee identical results for every user in a city.
Example: a declared search-result sample
Create a small keyword set for an authorised visibility study, such as coffee equipment and coffee equipment Chicago. Declare country US, interface language English, desktop browser, signed-out state, and the observation time. Keep the exact query text, including punctuation, so another reviewer can reconstruct what the sample was intended to measure.
Record organic destinations separately from advertising, maps, shopping, and other result blocks. Define a counting rule before assigning positions: for example, count only the ordinary organic web links in the chosen result depth. Preserve each destination URL and visible title, with a permitted screenshot that shows how the result was classified.
Separate location from personalisation
Do not attribute every ordering difference to the exit IP. Browser language, account state, cookies, device profile, query wording, and observation time are additional inputs. Change only the declared geographic setting when comparing regions. If the displayed search location differs from your intended country, record it rather than silently relabelling the sample.
A verification screen or incomplete results page is not an empty search result. Likewise, a paid placement is not an organic rank. Keep redirects and final destination domains, since several visible links can lead to the same website. Avoid presenting a single result page as the experience of every user in a city.
Acceptance criteria for a ranking report
Require query, country, displayed location when available, language, device, account state, timestamp, result category, destination, and counting rule. A comparison is meaningful only when these inputs agree apart from the variable you planned to change. Use repeated permitted observations to distinguish a stable pattern from one page captured at one moment.
Report incomplete observations separately from accepted result sets. If the target cannot be observed under the permitted workflow, stop and reconsider the method instead of trying to bypass a verification. Describe the report as a declared search sample; it does not establish search volume, advertising eligibility, or a guaranteed position for future visitors.
| Task | Starting configuration | Verify before scaling |
|---|---|---|
| Independent regional observations | Chosen country; rotation between samples | Exit-IP location, valid response content, and traffic per result |
| Login or another multi-step session | Continuous session; consistent browser profile | IP continuity, cookies, authentication, and account permissions |
Google: questions before launch
What should I verify when testing Google?
Record organic positions and advertising separately, with the query and observation time.
Should I keep one IP or rotate it?
Use a continuous session for login and other multi-step tasks. Test rotation between independent requests. Verify the exit IP in your application; connection settings and a fixed address are different things.
Does a proxy guarantee access or a successful outcome?
IP geolocation is only one input to search personalisation. A proxy cannot guarantee identical results for every user in a city.
Residential traffic pricing
Choose the plan that matches your workflows
The rate depends on traffic volume. Check the final amount and available payment methods in your dashboard before payment.
