How Do I Add Review Schema to a Webflow Page?

How do I get star ratings to show up for my page in Google?

You add review schema, which is structured data that tells Google about ratings and reviews on a page. When the page qualifies, Google can show star ratings in the search result. The catch is that not every page qualifies, and reviews about your own business usually do not.

I add schema for clients as part of my SEO and AEO work, and review schema is one of the most misunderstood types. People expect stars on their homepage and get nothing, because Google has strict rules about who can show reviews about themselves.

This guide explains what review schema does, which pages can actually earn stars, and how to add it to Webflow the right way. I will be honest about the limits, because a tutorial that ignores them just wastes your time.

What is review schema, and what does it do?

Review schema is code, usually written in JSON-LD, that describes a rating for a specific thing. It uses the Review and AggregateRating types from schema.org. It tells search engines what was reviewed, the score, how many reviews there are, and who wrote them.

The point is to turn plain text on a page into data a machine can read. A human sees "4.8 out of 5 from 120 reviews." Without schema, a search engine just sees words. With schema, it sees a clear rating value, a review count, and the item being rated.

When Google trusts that data and the page type is eligible, it may show a star rating in the search result. That is called a review snippet, and it can make your listing stand out. Getting there depends heavily on the page type, which is the next thing to understand.

Will review schema put stars on my homepage or services page?

No, in almost all cases it will not. Google does not show star ratings for reviews that a business publishes about itself. If your homepage or services page uses LocalBusiness or Organization schema and the reviews are about your own business, that page is not eligible for the star review snippet.

This is called the self-serving review rule. Google explained it in a 2019 update and reaffirmed it in a December 2025 update to its review snippet documentation. The rule covers testimonials you collect yourself and reviews pulled in through third-party widgets, like a Google or Facebook reviews embed.

So marking up your glowing client testimonials will not earn you stars on your own site. I know that is disappointing. It also explains why so many people add review schema, pass the test, and still see no stars. The page type was never eligible in the first place. My guide on LocalBusiness schema for local SEO covers what that schema can and cannot do.

Which pages can actually earn review stars?

Pages that review an eligible type of thing can earn stars. Google lists supported types including Product, Recipe, Book, Course, Event, Movie, and SoftwareApplication. The classic example is a product page where you collect and display reviews for that specific product.

The Product type is the big exception to the self-serving rule. If you sell a product and collect reviews for it, you can mark up that product page with review data, and it is fully allowed. The same goes for a recipe site summarizing visitor ratings on a recipe page.

So the honest answer is that review stars are for things you offer that fit these types, not for your brand as a whole. If you run an online store, review schema on product pages is a real opportunity. If you run a services business, the star snippet route is mostly closed, and your energy is better spent elsewhere.

What does review schema look like in JSON-LD?

In JSON-LD, review schema is a small block of code that names the item being reviewed and its rating. For an aggregate rating, the key parts are the item type, an AggregateRating object with a ratingValue and a reviewCount, and the best and worst possible scores. For a single review, you also name the author and the review body.

In plain terms, you are telling Google four things. What is being rated, the average score, how many ratings make up that average, and the scale, such as out of five. If any of those are missing or do not match what a visitor can see on the page, Google may ignore the markup or flag it.

The most important rule is that the schema must match the visible content. If your page shows a 4.8 rating from 120 reviews, your schema must say the same. Inventing a rating, or marking up reviews that a visitor cannot actually see on the page, breaks Google's guidelines and can get your rich results removed.

How do I add review schema to a Webflow page?

You add the JSON-LD code to the page's custom code, inside the head section. Webflow lets you paste custom code at the page level, so the schema loads only on the page it describes. For a CMS template, you can build the code so it pulls the right values for each item.

Here is the flow I use. First, write or generate the JSON-LD block with the correct item type and rating values that match the page. Next, open the page settings in Webflow and find the custom code section for that page. Then paste the JSON-LD into the head code area and save. Finally, publish the site so the code goes live, because it will not be read on an unpublished preview.

For a store built on the Webflow CMS, you can place the schema in an embed inside the product template and bind the rating fields to CMS values. That way each product page carries its own correct data. If you collect and show those reviews on the page, my walkthrough on building a CMS review section with star ratings pairs well with this schema.

How do I test that my review schema works?

You test it with Google's Rich Results Test and then watch Google Search Console. The Rich Results Test checks your page or code and tells you if the review markup is valid and eligible for a rich result. It will also show warnings for missing recommended fields.

Paste your live page URL into the Rich Results Test, or paste the code directly. If the tool sees a valid review snippet, you are on the right track. If it reports that the item is not eligible, that is usually the self-serving rule at work, not a coding mistake. Reading the message carefully saves a lot of guessing.

After the page is live, Google Search Console has reports that show which pages have valid structured data and which have errors. I check these regularly, because schema can break when a template changes. If you want a deeper process, I wrote about auditing structured data errors in Webflow.

Why does review schema still matter for AI search even without stars?

Review schema still matters because it feeds clean, structured facts to AI answer engines and search systems, not just to the Google star snippet. When you clearly label a rating, a count, and the item, you make it easy for any machine to quote your data accurately.

AI answer engines like ChatGPT, Perplexity, and Google's own AI features read the web and summarize it. Structured data helps them understand your page without guessing. A well-marked product rating is far easier for a model to cite correctly than a number buried in a paragraph.

This is why I still recommend review schema on eligible pages even when the star snippet is uncertain. The goal is not only the stars. The goal is to be the clearest, most machine-readable source on your topic, so both search engines and AI tools trust and repeat your numbers.

What mistakes should I avoid with review schema?

The biggest mistake is marking up self-serving reviews and expecting stars. The second is schema that does not match the visible page. Both break Google's guidelines and can lead to no rich result, or worse, a manual action against your structured data.

Another common error is adding review markup to the wrong page type, like putting a rating on a generic services page that uses Organization schema. It will not earn stars, and it clutters your code. Match the schema to what the page actually is and what a visitor can actually see.

Finally, do not set and forget. Ratings change, review counts grow, and templates get edited. Stale or broken schema is a quiet problem that only shows up when your rich results vanish. A quick check after any change keeps your markup honest and working.

Should you add review schema to your site?

Add it if you have eligible pages, like product or recipe pages, where you collect and display real reviews. Skip the star chase on your homepage and services pages, because self-serving reviews will not earn stars. Spend that effort on schema types that fit and on content quality.

If you run a store, start with your best selling product pages and make sure the schema matches the reviews shown there. Test with the Rich Results Test, watch Search Console, and expand from there. That is a clean, honest path to real review snippets.

If you are not sure which of your pages are eligible, or you want your schema set up so both Google and AI engines trust it, this is the kind of work I do every day. I am happy to review your setup and point you to the wins that are actually available. Let's connect.