A site changed its design or serves tiny photos, so Google search cards come out thin. The “Statistics” tab shows which site falls short of your requirements and why; AI reconfigures its parser, with rollback.
When you need this:
- Small photos in cards: “Check” shows whether the site or the parser is at fault.
- A site stopped giving specifications: “Reconfigure” builds new selectors and compares them with the old.
- Which site is worse: the “Rating” from 0 to 100.
- No time to check by hand: the most used sites are checked every Monday night.
Where to start: open “Product content search” → “Statistics” and set the “Result requirements”.
What site quality control does
- Sets requirements: the minimum photo size, how many specifications, and whether a description is required.
- Gives each site a status and a rating: “Good”, “Small photos”, “Few specs” and others, with the reason in a tooltip.
- Checks a site on live pages: what the parser takes and which photos the page really has.
- Reconfigures the parser with AI: shows “before → after” and saves only after “Accept”.
- Checks on its own every week: sites with problems get the “Needs attention” label.
How to set result requirements
The “Result requirements” panel sits on the “Statistics” tab above the “Sites” table. The requirements are the same for all sites and all users of the account: they drive statuses, the rating and the list of problems in the check. They do not affect the search itself: a site that falls short still gives data as before.
1
Photo from, px2
Specs from3
Description required4
Save5
Last self-check- Minimum photo width in pixels (800).
- Minimum number of specifications a page must give.
- Whether a description is mandatory for a page to count as good.
- Saves the requirements (not pressed in this shot).
- Line with the date of the last automatic self-check.
| Field | What it sets | Limits | Default |
|---|---|---|---|
| “Photo from, px” | the minimum long side of the first product photo | 200–4000 | 800 |
| “Specs from” | how many specifications a page should give | 0–100 | 10 |
| “Description required” | whether a missing description counts as a problem | yes / no | yes |
Change the values and click “Save”: statuses and the rating in the table are recalculated right away. A number outside the limits is replaced with the nearest limit.
How to read a site's status and rating
In the “Sites” table, status labels appear next to the site address, and two columns show quality in numbers: “Photo, px”, the long side of the first product photo averaged over the site, and “Rating” from 0 to 100. Hover over a label: the tooltip explains the reason with numbers.
1
Small photos2
Needs attention3
Rating4
Photo, px5
Check site- Status label: the site's photos are smaller than required; the tooltip shows the numbers.
- Red label: the site needs attention.
- Rating column: grows from the worst site at the top to the best.
- Average width of the first photo in pixels.
- Stethoscope icon: check the site.
| Label | When it appears |
|---|---|
| “Good” | none of the conditions below applies |
| “Not loading” | 3 or more pages, and more than half of them failed to load |
| “Small photos” | the first photo averages less than “Photo from, px”; measurements from at least 2 pages are needed |
| “Placeholders” | more than 3 discarded placeholders per 10 pages with data: “no photo” images, icons under 200 px and photos the site already gave for your other products |
| “Few specs” | on average fewer than “Specs from” |
| “No description” | a description is found on less than half of the pages with data; only when “Description required” is on |
| “Needs attention” | the weekly self-check found a problem; the tooltip shows the date and the list |
Quality labels, except “Not loading”, need 2 or more pages with data: one page is too few to judge. Sites in “Do not take content from these sites” get no status labels. “Photo, px” counts only searches where photo size was measured; until then it shows “—”. “Photo, px” below the requirement and a rating below 50 are highlighted.
The rating has four parts measured against your requirements:
| Part | Points | Full points when |
|---|---|---|
| Pages with data | 30 | all pages of the site gave data, including those that failed to load |
| Photos | 25 | the first photo is at least “Photo from, px”; if the size was not measured, 3 or more photos per page |
| Specifications | 25 | on average at least “Specs from” |
| Description | 20 | a description on every page with data |
If you clear “Description required”, its 20 points are split among the other parts. The “By pages / By rating” switch in the top row of the tab, next to the period, sorts the table: “By rating” puts the worst sites at the top. The “Need attention” tile counts sites with problems from the last self-check.
How to check a site
In the site row, click the “Check the site” icon (a stethoscope on the right). It opens up to 3 latest product pages of the site from the account's search history and shows what the parser takes versus what each page has. Up to a minute, for slow sites a few minutes. The check changes nothing and is free.
1
Site parser line2
Parser photos3
Best photos on the page4
Problems5
Reconfigure- The line says how the site parser was created and suggests reconfiguring it if the result is poor.
- Parser photos — the number and size of photos the configured parser takes from the page.
- Best photos on the page — what the search itself finds, including larger versions of the photos.
- Problems — what is wrong with each page: small photos, no or very short description.
- Reconfigure — asks AI to build new selectors and compare them with the current ones.
| Report column | What it shows |
|---|---|
| “Name”, “Specs”, “Description, chars” | what the site parser extracted from this page |
| “Parser photos” | how many photos the parser takes and the long side of the first one; the number links to the photos |
| “Best photos on the page” | which photos the page has under the search rules: larger versions, without photos of neighboring products and placeholders. The search takes photos by the same rules, so this is roughly what it will find; for fast drivers, photos are not taken from the page |
| “Problems” | the page's problems against your requirements |
Above the table you see which parser the site has. This decides what you can do next:
- Created by AI auto-setup or set up manually: the “Reconfigure” button is available.
- System parser or fast driver (Rozetka, Hotline): we maintain these; pages and photos are checked, reconfiguring is not available.
- No parser yet: the next search that comes across this site will create it.
| Problem | What it means |
|---|---|
| “The parser takes no photos although the page has them” | the photo selector does not find the gallery; worth reconfiguring |
| “The parser takes small photos; the page has N px and larger” | larger photos exist, and the search already takes them; reconfiguring fixes the parser itself too |
| “The site shows only photos below N px” | the site has no larger photos; reconfiguring will not help |
| “The parser takes only some of the page photos” | the page has 3 or more photos, and the parser takes less than half |
| “The page has no product photo” | the page has no photos or is not a product page |
| “Fewer than N specs”, “No description or a very short one” | the table or description was not found, or the site does not have them; a description under 100 characters counts as missing and is checked only with “Description required” |
| “Name not found” | the name selector did not work |
| “The page did not open” | the site did not return the page just now; try later |
How to reconfigure a site parser and restore the previous one
- In the check report, click “Reconfigure”. AI builds new selectors from the first page and tests them on the same pages, up to two minutes. It spends AI tokens, as parser auto-setup does.
- The report shows side by side what the current parser takes and, in bold, what the new selectors will take, plus a score summary: “The new selectors are better: 18 → 27 points” or “not better”.
- If the new ones are better, click “Accept”: the selectors are saved, and a parser disabled after a failed setup is turned back on. Until you click “Accept”, nothing changes.
Points are counted per page and added up: 10 minus 2 for each problem, plus up to 3 points for specifications (a point for every 10, at most 30). “Accept” appears only when the new selectors score higher. New selectors wait a day for your decision; after that, click “Reconfigure” again.
If the site's data got worse after “Accept”, open the site check again and click “Roll back”: the selectors from before the reconfiguration come back. The button is available for 30 days after “Accept”. More on manual selectors: CSS and XPath selectors.
Weekly self-check
Every Monday night the program checks up to 8 sites that the search took the most pages from over the last 30 days, just like the “Check” button does. It does not change parsers and charges nothing.
- A site gets the “Needs attention” label if a problem occurred on at least half of the checked pages: one failed page out of three does not flag the site. “No parser” and “The search history has no pages of this site” always flag it.
- The label tooltip shows the self-check date and the list of problems; page details are in the “Check” report.
- Below the “Result requirements” panel you see the date of the last self-check or “no self-check yet”.
- The label stays until the next self-check. After “Accept” or “Roll back”, a check starts automatically: the fresh report shows whether the problem is gone.
- The self-check takes sites from the searches of all users of the account, while the table shows only yours, so the number on the “Need attention” tile can be higher than the number of labels in the table.
Scenarios
Cards get small photos from one site
Task: the site has the “Small photos” label, and photos in cards are 300–500 px.
What to turn on: click “Check” in the site row and look at the “Problems” column.
Result: “The parser takes small photos; the page has 800 px and larger”: click “Reconfigure” and “Accept” if the new selectors are better. “The site shows only photos below 800 px”: add the site to “Do not take photos from these sites” or move another site up in “Take photos from these sites first”.
What will not happen: photos in already saved cards will not change.
A site changed its design and stopped giving specifications
Task: the site used to give a full table, and now it has “Few specs” or “Needs attention”.
What to turn on: “Check” → “Reconfigure” → “Accept”.
Result: from the next search the parser takes data with the new selectors. If it got worse, use “Roll back” within 30 days.
What will not happen: a system parser or fast driver cannot be reconfigured this way; contact support.
Your store needs photos of 1200 px and up
Task: the marketplace accepts only large photos.
What to turn on: in “Result requirements”, set “Photo from, px” to 1200 and save, then switch the table to “By rating”.
Result: sites with smaller photos get “Small photos” and drop in the rating; add the best sites for photos to “Take photos from these sites first”.
What will not happen: the search does not discard photos below the requirement: it only highlights sites.
What to do when the check did not help
| What you see | Why | What to do |
|---|---|---|
| “The search history has no pages of this site” | the site's pages have not been taken for a long time or the records were deleted | run a Google search for a few products where this site comes up |
| “The site pages did not open, there is nothing to reconfigure on” | the site is not returning pages right now | try later; if it is always like this, exclude the site on the “Statistics” tab |
| “AI could not build selectors for this page” | the page has no usual product layout or AI did not respond | try later or set up selectors manually |
| “The new selectors are not better” | the current parser already takes as much as the site gives | leave it as is; the problem is the site itself |
| “The new selectors are no longer available (a day has passed)” | more than a day passed between “Reconfigure” and “Accept” | click “Reconfigure” again |
| No “Reconfigure” button | system parser, fast driver, no parser yet, or no pages of the site in the history | for system parsers, contact support; otherwise run a search where this site comes up |
FAQ
Is checking a site paid?
No. Neither “Check” nor the weekly self-check charges for pages. Only “Reconfigure” spends AI tokens.
Do the requirements affect what the search finds?
No. The requirements only give sites a status and a rating. To stop a site from being used, add it to “Do not take content from these sites” or “Do not take photos from these sites”.
Why does the “Photo, px” column show a dash?
Photo size is measured during the search starting from November 2026. Pages from older searches have no size; it will appear after a new search that comes across this site.
What happens if I do not click “Accept”?
Nothing: the parser keeps working with the old selectors. The new ones wait a day and then disappear.
How do I remove the “Needs attention” label?
It is updated by the next weekly self-check. Fix the parser with “Reconfigure” and make sure in the “Check” report that there are no problems.
Where it is and who has access
- Menu
- Base catalog → “AI & content” → “Product content search” → “Statistics” tab
- Access right
- the “Product content search” window in “Group permissions”
- Prepare
- at least one Google search: the sites come from its history
Charts, tiles and excluding sites on this tab are covered in the article on Google search. This article covers everything about site quality.
Related topics
- To set up the search itself, the site lists and the combined card check, see content search through Google.
- To fix a site parser manually, see CSS and XPath selectors.
- To learn how parser runs work, see parser runs.
