Google has clarified how review and rating markup must be used. This is not a penalty update. It is a rulebook update. If your stars vanish from search, your traffic takes a direct hit. This guide explains what Google really means, why they did it, and how Indian and global websites can fix their structured data in a clean and predictable way.
The Real Problem Google Is Solving
Google has been drowning in confusing review markup for years.
Every website wants a five star badge. Every product wants a shiny yellow rating. Everyone abuses plugins that promise instant reviews.
The problem is simple.
One page.
Three different schemas.
Two different ratings.
One confused search engine.
Google finally stepped in because the review ecosystem became a circus.
Fake reviews. Imported reviews. Invisible reviews. Brand controlled reviews.
Indian problem examples
• Restaurants embedding Google Business reviews and marking them up as their own.
• Small ecommerce sites importing Amazon reviews via a plugin.
• Local gyms posting reviews written by their own staff members.
• Recipe blogs mixing FAQ schema with Review schema inside a HowTo block.
Google looked at all this confusion and basically said:
Clean your markup. Stop reviewing yourself. And please stop confusing me. I am not your intern.
Breaking Down Google’s Rules In Simple English
Here is what Google clarified, without jargon.
Rule 1
Talk about one item on one page.
If the page is about a book, the review must be about that book.
Not books in general. Not a list of ten books.
Rule 2
Use one method to show what is being reviewed.
Do not include a Review block and then separately include an AggregateRating block pointing to another item.
Google sees that as double signalling.
Rule 3
If many people rated one item, use AggregateRating.
Example. A mobile phone with 2122 ratings on your website.
Use Product as the parent type.
Nest AggregateRating inside it.
Rule 4
Reviews must be clearly visible to users.
If your structured data says four point six stars from ninety two users, your page must show those details.
Google does not accept invisible ratings.
Rule 5
A rating must have a reviewer name and a review comment.
Do not add an anonymous five star rating.
Google wants transparency.
Rule 6
Do not review categories.
You cannot add review schema to a page titled Best Laptops Under 30000.
Google will reject it because you are reviewing a list, not an item.
Rule 7
If you have multiple individual reviews, include an overall aggregate rating.
Google wants consistency.
Rule 8
Do not copy reviews from other websites.
If you import Zomato reviews and mark them up as your own, Google will remove your snippet.
You can display them, but never mark them up.
Rule 9
Local businesses cannot mark up reviews about themselves.
If you are a restaurant and your website contains self-controlled reviews, you cannot get star snippets.
This rule exists because nearly every small business misuses these plugins.
Common Mistakes Indian Websites Make
Mistake 1
Using Review schema inside FAQ schema.
Google cannot decide what the user is reviewing.
The question, the house, the food, or the entire website.
Mistake 2
Adding rating data that is not visible on the page.
Visible to Google but not to the user is not allowed.
Mistake 3
Using LocalBusiness markup with self-written reviews.
This is a direct violation.
Mistake 4
Importing reviews from Amazon, MakeMyTrip, Swiggy, or JustDial.
Google sees this as syndication.
Mistake 5
Using multiple top level schema types on the same page.
Google reads it as multiple items being reviewed.
Case Studies That Explain This Clearly
Case Study 1. Indian Ecommerce Brand
A D2C cosmetic brand in Bangalore imports Amazon reviews via a plugin.
Their page shows five star ratings.
Their schema marks it up as their own rating.
Google removes their review snippet within two crawls.
Traffic to their product pages drops by twelve percent.
Reason. They did not collect ratings directly. They borrowed them.
Case Study 2. Global Recipe Blog
A food blogger in Hyderabad shows 18 genuine reviews for a pasta recipe.
Each review has the author name, comment, and rating.
The page uses Recipe as parent type, with Review and AggregateRating nested properly.
Google accepts the data and shows stars.
CTR increases by fourteen percent.
Case Study 3. Indian Local Restaurant
A restaurant in Hyderabad uses a plugin to embed Google Business reviews.
They mark them up with LocalBusiness schema.
Google flags it as self-serving.
Star snippet disappears completely.
Reason. A business cannot mark up reviews about itself.
The Correct Schema Structures (Explained Without Code Jargon)
Product Page
Parent type: Product
Inside it:
• Name
• Description
• Review (optional, if you have individual reviews)
• AggregateRating (if multiple reviews exist)
Recipe Page
Parent type: Recipe
Inside it:
• Ingredients
• Instructions
• Review
• AggregateRating
Book Review Page
Parent type: Book
Inside it: Review
ItemReviewed must clearly be the specific book.
Local Business Page
Parent type: LocalBusiness
Must not contain self-written reviews.
Only factual information about the business.
Course or Service Page
Parent type: Course or Service
Review can exist only if reviewers are real and independent.
Checklist For SEOs And Developers
Use this before publishing any review content.
- Is the page about one clear item
- Is the rating visible on page
- Does each rating have a name and comment
- Is the aggregate rating real and shown to users
- Is the review collected directly, not imported
- Is the schema nested cleanly under one parent type
- Is the review about a product or service, not a category
- Does the schema avoid duplication or conflicting signals
If any answer is no, Google may remove your star snippet.
Impact On CTR, Rankings, And AI Summaries
Review stars improve click through rate across Indian ecommerce and service categories.
Losing them creates a measurable drop.
Google AI Mode also prefers pages with clear, non-conflicting schema.
Your visibility in AI summaries improves when markup is consistent and trustworthy.
This update does not change ranking directly.
It changes visibility.
Visibility affects clicks.
Clicks affect overall performance.
Roadmap To Fix Your Site In One Week
Day 1
Audit all pages with Schema Validator.
Identify pages with multiple parent types.
Day 2
Clean the schema.
Remove duplicate blocks and incorrect nesting.
Day 3
Make all reviews visible on page.
Add reviewer name and comment.
Day 4
Fix all category pages.
Remove review schema from list pages.
Day 5
Fix all LocalBusiness pages.
Remove self-controlled reviews.
Day 6
Rebuild AggregateRating sections.
Ensure they match what users see.
Day 7
Test again and request recrawl.
Final Thoughts:
Google is not trying to punish anyone.
They are trying to reduce noise.
When your schema becomes clean, predictable, and honest, your stars stay stable, your visibility stays strong, and Google trusts your content more than your competitors.
Discover more from Rudra Kasturi
Subscribe to get the latest posts sent to your email.