Choose a city where a customer can order your service or receive your product. If the company operates in several regions, first decide which territory and pages you want to assess in this project.
The check city sets the conditions for a search measurement. It does not change the company’s address, delivery terms, or the site’s regional targeting in Yandex Webmaster. Before configuring it, compare these details with the pages visitors will see.
To configure it, open “Search positions” → “Change queries and region” → “Find a region.” Select the relevant result and click “Check for region ‘…’.”
Describe the company’s operating territory
List where the products or services are available. For a mobile team, this might be a city and service area; for delivery, a list of territories; for a remote service, a broader market. Use the company’s actual terms of service, which staff can confirm to customers.
If the offer is available in only one city, do not choose a broader territory just to increase the report’s coverage. If the company operates in several regions, first decide which pages and queries belong to each one. One setting does not describe every way the business is present.
Check the service pages for the address, service-call terms, delivery, and contact details. Do not create identical pages by simply replacing the city name without adding useful information of their own. The region you choose should reflect the actual offer, not a convenient way to increase the number of rows being monitored.
Check whether the service depends on the city
A query about a nearby service and a query about how a piece of equipment works reflect different expectations. The first is often tied to where the service is provided; the second may be informational. So the project’s query list should be divided by intent, not just by whether a city name appears in the text.
Yandex explains that regionality may be taken into account for geo-dependent queries. For a working document, it is enough to note why the territory matters for this particular service. There is no need to guess how ranking works based on a single snapshot.
Suppose a company repairs equipment in Kazan and provides remote consultations across the country. The region for local repairs and the target area for consultations are different. The team first assigns the relevant service pages and terms, then chooses which phrases to monitor in one project.
Save the settings before the first measurement
Save the selected region, start date, search engine, device, and query list. For each commercial service, specify the page that explains its terms. This will make it possible to explain later why a particular measurement applied to that territory.
| Setting | What to record | Why it is needed |
|---|---|---|
| Service territory | Actual city and service-call area | Connect search results with customers |
| Check region | The project setting | Recreate the conditions for the snapshot |
| Service page | The URL of the page with the terms | Check the response visitors receive |
| Configuration date | The day this version began | Distinguish a new measurement series |
| Device | Computer | Avoid mixing it with mobile search |
Before saving, ask a staff member to check the settings against this record. If the territory name and the actual service area do not match, resolve the discrepancy before evaluating performance over time. Otherwise, later figures will answer a different question.
Make sure the city matches the page’s terms
Open the found service page as an ordinary visitor would. If the text promises service calls in another city, the monitoring setting will not fix the content. First, make sure the page matches the current offer and contact details.
Also check the contact path. Visitors should understand where their request will go and what limitations the service has. Page checks can reveal availability and issues, but they do not by themselves confirm an actual order or that a message was delivered to a manager.
For assessing how phrases correspond to sections, see the guide to the semantic core. If a project combines different services, do not assign one region by default without discussing exactly what the team intends to compare.
Note the date when the region changes
Changing the city is a significant change to the conditions. Record the last date of the previous setting and the first date of the new one. Comparing two different regions can be a separate study, but it cannot be called an ordinary rise or fall for the previous query.
Do not change the region, query list, and service-page structure all at once without keeping a record. With that many changes, it will be difficult to explain which one is related to the observed result. It is better to mark separate stages of work and their start dates.
A manual search from a staff member’s device may also involve different conditions. reChecker checks monitor search results on computers. If an additional result comes from a phone or another territory, save it separately instead of directly comparing the positions.
Check the saved value
Tell the person who receives the summary when and why the check territory is changing. Specify the last comparable date in the old series and the start of the new one. Without this record, the recipient may mistake a different set of search results for a sudden decline in the site’s performance.
At the end of the configuration, compare the city in the project with the city you recorded before setting it up. If the setting was not saved or the result is for the previous territory, do not present it as the first measurement for the new region. First, confirm the project’s actual state.
Learn more: SERP analysis: what a search engine shows and how to use it.
Check results are available in the website monitoring dashboard.