AggregateRating schema implementation for Yandex requires strict adherence to specific property fields to ensure star ratings appear in search results. By placing the required itemReviewed, ratingValue, and ratingCount properties inside the main schema container, you allow Yandex bots to parse your review data accurately. Incorrect nesting or missing mandatory fields are the primary causes for rich snippet failures, which can limit your organic visibility.
Why is your AggregateRating schema not showing in Yandex?
Search crawlers often ignore schema markup when the code structure lacks necessary parent-child relationships. If your rating data is not associated with the main product or content item using the itemReviewed property, the search engine cannot verify what the rating belongs to. This often happens when developers separate the star rating visual element from the product title in the HTML hierarchy.
In a typical account, we observe that developers often forget to link the AggregateRating object back to the Product object. Without this explicit link, the crawler sees a collection of numbers without context. It is essential to ensure that your JSON-LD script is correctly scoped, ideally within the same HTML block as the product name and price, to avoid ambiguity during the parsing process.
What are the mandatory fields for Yandex rating schema?
To ensure your markup is valid, you must include specific fields that satisfy the crawler requirements. Missing these fields will lead to validation errors in your dashboard, preventing the display of rich snippets. These values must reflect the real data on your page, as search engines compare the markup against the visible text presented to human users.
- ratingValue: A numerical value representing the score, usually on a 1-5 scale.
- ratingCount: The total number of reviews that contributed to the average score.
- bestRating: The maximum possible score, typically set to 5.
- worstRating: The minimum possible score, typically set to 1.
When configuring these fields, avoid using placeholder data or hardcoded averages that do not change. If your system does not have a ratingCount, do not set it to zero, as this can trigger validation warnings. Instead, ensure the schema logic is absent until the first user review is posted, or use a default state that correctly indicates the lack of data.
How do you validate structured data for search engines?
You should use the official structured data validator provided in Yandex Webmaster tools to test your code. This tool simulates how the search engine reads your page and highlights specific lines where syntax or attribute errors occur. It is a solid practice to test your markup after every major template update, as CSS or JavaScript changes can occasionally break the visibility of the underlying HTML.
For example, if you are running a Shopify or WooCommerce store, a plugin update might inadvertently modify the class names or IDs that the schema relies upon. By running a weekly check, you identify these regressions before they impact your click-through rate. Always verify that the rendered HTML contains the schema, not just the raw source code, because some modern frameworks inject markup dynamically via JavaScript.
Schema validation is not a one-time setup. As your product catalog grows, you must ensure that new pages follow the same strict formatting rules to maintain visibility.
Alien Road SEO team
How Alien Road applies this
At Alien Road, our process for fixing schema issues involves a thorough audit of the site’s rendering pipeline. We identify where the rating values are generated, typically within the product template files. Our team ensures that the JSON-LD or Microdata is injected into the document head or alongside the product metadata, ensuring that the hierarchy is logical and easy for crawlers to follow.
- Audit existing product templates to locate rating injection points.
- Map database review counts to the mandatory ratingCount field.
- Run the validator tool to check for schema nesting errors.
- Monitor the Webmaster dashboard for indexing status updates.
In a typical engagement, we begin by crawling the top 50 landing pages to extract existing schema samples. We then compare these against the Yandex guidelines to spot inconsistencies. Once the technical fix is deployed, we track the ‘Rich Snippet’ report in the search console to confirm the changes have been indexed and that the star ratings are appearing for the target keywords.
Can incorrect rating values harm your search performance?
Displaying inaccurate or spammy rating data can lead to manual actions or the exclusion of your rich snippets. Yandex expects the displayed stars to reflect the actual reviews on the page. If a user clicks your result expecting a 4.8 rating but finds no reviews, the discrepancy may hurt your brand credibility and organic traffic, potentially triggering a quality review of your site by the search engine.
Consistency is the best defense against these issues. If your store has 10 reviews, ensure the schema says 10. If the average is 4.2, ensure the markup says 4.2. Avoid attempts to manipulate the schema to show higher numbers than what is actually displayed on the product description page, as automated systems are quite good at cross-referencing your markup with the text on the page.
We always advise our clients to prioritize data accuracy over high rating figures. Search engines value consistency above all else when evaluating markup quality.
Alien Road SEO team
Where to start this week
Start by identifying three high-traffic product pages that currently lack rich snippets. Use the validator to check if the AggregateRating object is present and if it contains the required ratingValue and ratingCount properties. Once you fix these, submit the URLs for re-indexing in your webmaster console to see the results in the coming days. By focusing on these three pages, you can quickly verify that your technical implementation is correct before rolling it out to the rest of your catalog.