SE::Yandex::WordStat::ByRegion -
Scraper Overview
Wordstat is a Yandex service designed to estimate user interest in various topics and select keywords for SEO optimization and contextual advertising. In addition, with Wordstat Yandex, you can evaluate the seasonality and geographical dependence of search queries.
The Yandex WordStat by region scraper supports automatic query multiplication, so you can be sure that you will get the maximum number of results from the search results. Also, A-Parser can automatically follow related queries to a specified depth.
A-Parser functionality allows you to save scraping settings for future use (presets), set a scraping schedule, and much more. You can use automatic query multiplication, substitution of subqueries from files, enumeration of alphanumeric combinations and lists to get the maximum possible number of results.
Saving results is possible in the form and structure you need, thanks to the built-in powerful template engine Template Toolkit which allows you to apply additional logic to the results and output data in various formats, including JSON, SQL, and CSV.
Accounts
To use the 
SE::Yandex::WordStat::ByRegion scraper, Yandex accounts are required. Accounts can be registered using the 
SE::Yandex::Register scraper or simply by adding existing accounts to the files/SE-Yandex/accounts.txt file in the supported format.
Alternatively, you can enable account registration "on the fly".
Collected data
- Total number of impressions for the query
- Keyword statistics by regions and cities:
- Region/City
- Number of views per month
- Regional popularity in %
Capabilities
- Support for automatic bypass of Smart captcha and the ability to bypass graphic captcha using the AntiCaptcha service or any other supporting their API
- Device type selection
- Ability to choose the authorization method
- Ability to register accounts "on the fly"
- Supports working with extended account format and can answer the secret question (if the answer is in
info). It also uses a saved proxy for authorization (if it is ininfo).
Use Cases
- Estimating the amount of traffic for a keyword by region
Queries
Keywords should be specified as queries, just as if they were entered directly into the Wordstat search form, for example:
test
Output results examples
A-Parser supports flexible formatting of results thanks to the built-in template engine Template Toolkit, which allows it to output results in an arbitrary form, as well as in a structured one, such as CSV or JSON
Default output
Result format:
$query - Total views: $totalcount\nViews by regions:\n$regions.format('$region $count, $popularity%\n')\nViews by cities:\n$cities.format('$city $count, $popularity%\n')
The result shows the number of impressions for the query, keyword statistics by regions and cities, the number of views per month, and regional popularity:
test - Total views: 872855
Views by regions:
Moscow and Moscow Region 147107, 85%
Central 194716, 77%
Northwest 55815, 70%
South 31759, 67%
Volga Region 86006, 66%
...
Views by cities:
Chita 2937, 113%
Saint Petersburg 35713, 73%
Belgorod 2737, 58%
Ivanovo 1773, 55%
Kaluga 2196, 64%
Kostroma 1166, 49%
Output in CSV table
Result format:
[% FOREACH i IN regions;
tools.CSVline(query, i.popularity, i.region, i.count);
END %]
Result example:
"test",88,"Moscow and Moscow Region",1902795
"test",96,"Central",2992864
"test",95,"Northwest",926138
"test",112,South,647140
"test",124,"Volga Region",1927873
"test",64,"West",60975
"test",86,"East",427304
Saving in SQL format
Result format:
[% FOREACH i IN regions;
"INSERT INTO regions VALUES('" _ query _ "', '"; i.popularity _ "', '"; i.count _ "', '"; i.region _ "')\n";
END %]
Result example:
INSERT INTO regions VALUES('test', '88', '1902795', 'Moscow and Moscow Region')
INSERT INTO regions VALUES('test', '96', '2992864', 'Central')
INSERT INTO regions VALUES('test', '95', '926138', 'Northwest')
INSERT INTO regions VALUES('test', '112', '647140', 'South')
INSERT INTO regions VALUES('test', '124', '1927873', 'Volga Region')
INSERT INTO regions VALUES('test', '64', '60975', 'West')
INSERT INTO regions VALUES('test', '86', '427304', 'East')
INSERT INTO regions VALUES('test', '80', '89569', 'South')
INSERT INTO regions VALUES('test', '75', '356560', 'Central')
INSERT INTO regions VALUES('test', '77', '34894', 'North')
Dump results to JSON
Common result format:
[% IF notFirst;
",\n";
ELSE;
notFirst = 1;
END;
obj = {};
obj.totalcount = p1.totalcount;
obj.regions = [];
FOREACH item IN p1.regions;
obj.regions.push({
popularity = item.popularity
region = item.region
count = item.count
});
END;
obj.json %]
Initial text:
[
Final text:
]
Result example:
[
{
"regions": [
{
"count": "1902795",
"popularity": 88,
"region": "Moscow and Moscow Region"
},
{
"count": "2992864",
"popularity": 96,
"region": "Central"
},
{
"count": "926138",
"popularity": 95,
"region": "Northwest"
},
{
"count": "647140",
"popularity": 112,
"region": "South"
},
{
"count": "34894",
"popularity": 77,
"region": "North"
},
],
"totalcount": "10837937"
}
]
See also: Results filters
Possible settings
| Parameter | Default value | Description |
|---|---|---|
| AntiGate preset | default | You must first configure the  Util::AntiGate scraper - specify your access key and other parameters, then select the created preset here |
| AntiGate preset for Login | default | AntiGate preset for login. You must first configure the Util::AntiGate scraper with parameters, then select the created preset here |
| Type | All | Device type selection |
| Accounts | Only from "accounts.txt" | Selection of the method for working with accounts: Always auto register - always automatically register accounts "on the fly", requires selecting a configured preset in the SE::Yandex::Register preset parameter. Auto register if no more in "accounts.txt" - existing accounts from accounts.txt are used first, and if they run out - automatic registration "on the fly" is used, for which you need to select a configured preset in the SE::Yandex::Register preset parameter. Only from "accounts.txt" - use only existing accounts from accounts.txt, and if they run out - wait for the specified time (Wait new accounts in "accounts.txt" parameter) for new ones to appear |
| Wait new accounts in "accounts.txt" | 0 | Waiting time for new accounts to appear in accounts.txt |
| Remove bad accounts | Always, except wrong login/password | Automatic removal of "bad" accounts: Always - always remove. Always, except wrong login/password - always remove, except when Yandex reported that an incorrect login/password was specified. The fact is that Yandex can give such a message when an IP is banned for a perfectly working account, so optionally you can leave such accounts for reuse. Never - never remove. Regardless of the selected option, accounts are not removed in case of proxy/browser errors |
| SE::Yandex::Register preset | default | Selection of a settings preset for SE::Yandex::Register |
| Authorization method | HTTP | Authorization method: HTTP - fast, not resource-intensive. Chrome - slow, resource-intensive, theoretically can extend account life |
| Chrome headless | ☑ | If the option is enabled, the browser will not be displayed |
| Use sessions | ☑ | Use of sessions |
| Do not reset session if authorization passed | ☑ | Do not reset the session on errors if the scraper has already authorized |
| Use Wordstat 2 | ☐ | Use of Wordstat 2 |
| Wordstat 2 parse all table data | ☑ | Allows you to immediately download all 2000 results for a query without going through pagination |