Shop::Wildberries::Suggest - Wildberries Search Suggestions Parser
Wildberries Suggest Parser Overview
Wildberries search suggestions parser. With the Shop::Wildberries::Suggest parser, you can automatically collect keyword databases from the search suggestions of the Wildberries marketplace by query. Using the Shop::Wildberries::Suggest parser, you can easily and quickly parse Wildberries suggestions by query.
The Wildberries suggestions parser solves one of the main SEO tasks, namely, fast automated obtaining of an extended semantic core. Wildberries search suggestions allow you to cover the maximum number of phrases, especially when using the Parse to level function.
Thanks to the multi-threaded work of A-Parser, the processing speed of requests can reach 10000 requests per minute, which on average allows you to receive about 20000 - 50000 results per minute.
You can use automatic query multiplication, substitution of subqueries from files, enumeration of alphanumeric combinations and lists to obtain the maximum possible number of results. Using results filtering, you can immediately clean up the result by removing all unnecessary garbage (using minus-words or filtering by type of suggestion).
The A-Parser functionality allows you to save the parsing settings of the Shop::Wildberries::Suggest parser for further use (presets), set a parsing schedule, and much more.
Saving results is possible in the form and structure that you need, thanks to the built-in powerful Template Toolkit template engine, which allows you to apply additional logic to the results and output data in various formats, including JSON, SQL, and CSV.
List of collected data
- Number of results per query
- Suggestions for the query
- Type of suggestion (suggest/category/brand)
Capabilities
- Ability to filter keywords when parsing in depth
- Ability to use the Parse to level function
Use cases
- Collecting keyword databases
Query examples
- Search phrases should be specified as queries, for example:
adidas
майки и футболки
смартфон Xiaomi
Query substitutions
You can use built-in macros to automatically substitute subqueries from files, for example, we want to add some list of other words to each query, specify several main queries:
скидка
акция
распродажа
In the query format, specify a macro for substituting additional words from the Keywords.txt file. This method allows you to increase the variability of queries many times over:
$query {subs:Keywords}
This macro will create as many additional queries as there are in the file for each original search query, which in total will give [number of original queries] x [number of queries in the Keywords file] = [total number of queries] as a result of the macro's operation.
For example, if the Keywords.txt file contains the substitutions above, then in the end, there will be 9 queries:
adidas скидка
майки и футболки скидка
смартфон Xiaomi скидка
adidas акция
майки и футболки акция
смартфон Xiaomi акция
adidas распродажа
майки и футболки распродажа
смартфон Xiaomi распродажа
Result output options
A-Parser supports flexible result formatting thanks to the built-in Template Toolkit template engine, which allows it to output results in any form, as well as in a structured form, such as CSV or JSON.
Exporting a list of suggestions
Result format:
$results.format('$suggest\n')
Example result:
adidas кроссовки
adidas для женщин
adidas кроссовки мужские
adidas terrex
adidas superstar
adidas originals
adidas terrex кроссовки мужские
Кеды и кроссовки
Дезодоранты
adidas
Output of the query, suggestions for the query + type of suggestion
Result format:
$query:\n$results.format('$suggest - $type\n')
Example result:
adidas кроссовки - suggest
adidas для женщин - suggest
adidas кроссовки мужские - suggest
adidas terrex - suggest
adidas superstar - suggest
adidas originals - suggest
adidas terrex кроссовки мужские - suggest
Кеды и кроссовки - category
Дезодоранты - category
adidas - brand
Output of suggestions to a CSV table
The built-in tools.CSVline utility allows you to create correct tabular documents ready for import into Excel or Google Sheets.
Result format:
[% FOREACH i IN results;
tools.CSVline(i.suggest);
END %]
File name:
$datefile.format().csv
Initial text:
Подсказки
In the General result format, the Template Toolkit template engine is used to output elements of the suggest array in the results loop.
What is the general result format?
In the results file name, simply change the file extension to csv.
To make the "Initial text" option available in the Task Editor, you need to activate "More options". In "Initial text", write the column names separated by commas and make the second line empty.
Saving in SQL format
Result format:
[% FOREACH p1.results;
"INSERT INTO serp VALUES('" _ query _ "', '"; suggest _ "', '"; type _ "')\n";
END %]
Example result:
INSERT INTO serp VALUES('adidas', 'adidas кроссовки', 'suggest')
INSERT INTO serp VALUES('adidas', 'adidas для женщин', 'suggest')
INSERT INTO serp VALUES('adidas', 'adidas кроссовки мужские', 'suggest')
INSERT INTO serp VALUES('adidas', 'adidas terrex', 'suggest')
INSERT INTO serp VALUES('adidas', 'adidas superstar', 'suggest')
INSERT INTO serp VALUES('adidas', 'adidas originals', 'suggest')
INSERT INTO serp VALUES('adidas', 'adidas terrex кроссовки мужские', 'suggest')
INSERT INTO serp VALUES('adidas', 'Кеды и кроссовки', 'category')
INSERT INTO serp VALUES('adidas', 'Дезодоранты', 'category')
INSERT INTO serp VALUES('adidas', 'adidas', 'brand')
Dumping results to JSON
Result format:
[% result.${query} = {
totalcount = p1.totalcount
suggests = []
};
FOREACH i IN p1.results;
result.${query}.suggests.push(i.suggest);
END %]
Initial text
[% result = {} %]
Final text
[% result.json %]
Example result:
{
"adidas": {
"suggests": [
"adidas кроссовки",
"adidas для женщин",
"adidas кроссовки мужские",
"adidas terrex",
"adidas superstar",
"adidas originals",
"adidas terrex кроссовки мужские",
"Кеды и кроссовки",
"Дезодоранты",
"adidas"
],
"totalcount": 10
},
"майки": {
"suggests": [
"майки женские летние",
"майки мужские летние",
"майки детские",
"майки спортивные",
"майки для мальчика",
"майки женские",
"майки женские бельевые турция",
"Майки"
],
"totalcount": 8
}
}
To make the "Initial text" and "Final text" options available in the Task Editor, you need to activate "More options".
Parse to level option
The option instructs the parser to substitute the received results into the query queue in depth up to the specified level, for example:
- If the 1st level is specified, the parser will add all the results obtained from the source query to the queries
- If the 2nd level is specified, the parser will add all the results obtained from the source query + all the results obtained from the queries from the 1st level to the queries
- etc.
Since there will most likely be duplicates in the results, it is recommended to enable query uniqueness so that the parser does not do unnecessary work (does not parse the same thing twice).
Possible settings
| Parameter name | Default value | Description |
|---|---|---|
| Follow suggests | All | Select the type of suggestions to be substituted into queries when using Parser to level (All/Suggest/Category/Brand), multiple selection is supported |