Picture two stores selling the same kettle at the same price. Google shows one listing with a star rating under the title and the other with nothing, and an assistant asked for a reliable kettle names the first store and says reviewers praise the fast boil. The kettles are equal. What differs is the evidence around the product, which both systems can read for one store and can't find for the other.
Stars in results come from markup about real reviews
Google's review snippet documentation is precise about where stars come from: an aggregate rating or individual reviews inside structured data for a supported type, and Product is one of them. The markup sits inside the Product object on the product page and states the average rating and the number of ratings or reviews. Google adds conditions that stores break constantly. The reviews must come from customers, they must be visible on the page carrying the markup, and they must be about the product on that page.
The commonest violation is the self-serving rating. A review app injects the store's own score into every page, or the homepage carries an aggregate rating for the business itself. Google's guidelines treat that as ineligible, because an organisation can't rate itself and a store-wide score says nothing about the kettle. Sometimes Google simply ignores the markup, and sometimes the page earns a manual action for structured data that misrepresents what's on it.
Stars on free listings and Shopping ads come from a different place. Google's Merchant Center help documents a product ratings programme, fed by a reviews file you submit or by an approved review aggregator. Page markup doesn't feed it and it doesn't feed page markup, so a store that wants stars in both places needs both. Product schema for search results covers the page side in detail.
Collect reviews the way Google and the law allow
The mechanics are simple and most stores skip them. Ask every buyer after delivery rather than after purchase, using a link that opens that product's review form, and keep the form short. Show the reviews on the product page itself, in the page's HTML, so Google and an assistant's crawler read them as part of the page and not as a widget that loads after a click.
You can't cross two lines here. Google's review policies prohibit fake reviews and paid-for reviews, and in the US the Federal Trade Commission's rule on fake reviews makes buying or faking them illegal. Publish the negative reviews as well. A page showing only perfect scores looks filtered to a shopper and, in observed behaviour, to an assistant summarising sentiment, while a page with a spread of honest scores and a store reply under the critical ones looks trustworthy.
Reply to critical reviews in public. Your reply becomes content on the page that answers the exact objection the next buyer has.
Customer content gives pages the words shoppers use
User-generated content (UGC) is anything a customer adds to your page, such as a review, a photo, a fit comment or a question. Its search value is in the language. You'd write "stainless steel body", while a customer writes "survived a week of camping in the rain and still looks new". That sentence matches searches and sub-questions no product copy would, and an assistant can quote it when it describes what reviewers think.
UGC counts when it meets three conditions. It lives on your product page, not on a review platform's own domain, where it builds their site instead of yours. It's rendered in the HTML Google receives, which is worth checking on a review widget because some render only after scrolling or clicking. And it's moderated for spam but not edited for substance, because a hand-picked set of customer voices is just marketing in a different font.
Questions and answers deserve their own section on a product page. A shopper asking "does it fit a standard UK plug" and a staff member answering is the same question-and-answer pair that Comparison and FAQ content teaches you to write, except a customer wrote half of it for you.
Brand signals are the web agreeing on who you are
For a Google result with stars, the signal is markup on your page. For an assistant naming you, the observed pattern is different: the brands that get named are described consistently by several independent sources, and a brand that exists only on its own website has nobody vouching for it.
A few parts you control directly, and they're worth doing. Google documents Organization structured data for stating your name, your logo and the other profiles that belong to you through the sameAs property. Put it on the homepage and keep the name identical everywhere. Use the same brand and product names in your feed, on your pages, in marketplace listings and on the manufacturer's site, down to the model number. Write an About page that says plainly what you make, who it's for and where you're based, because an assistant reads that page when it describes you.
The parts you earn decide whether you get named: reviews on retailer sites, a mention in a roundup, a recommendation in a forum thread, a comparison article that includes you. Forum threads show up often among the sources assistants cite for "which should I buy" questions. This is observed rather than documented, though it's consistent enough to act on. The next lesson puts these in priority order.
Frequently asked questions
What is SEO in marketing?
SEO is the practice of making your pages easy for search engines to find, understand and trust, so they show up when people search. This lesson covers the trust side for stores. Real reviews, customer content and consistent brand mentions are what earn stars in Google and get a store named by an AI assistant.
What is user-generated content (UGC)?
UGC is anything a customer adds to your page, such as a review, a photo, a fit comment or a question. It helps SEO because customers describe products in the words other shoppers search with. Those phrases match searches your own product copy never would.
Can I do SEO for my website myself?
Yes, for the parts in this lesson. Paste a product page into the free Schema validator and check that the Product object holds an aggregate rating matching what's visible. Then check that your homepage carries no rating for the store itself. Any fix usually sits in your review app's settings.
How to apply for user-generated content?
You don't apply for it. You collect it. Ask each buyer for a review after delivery with a link to that product's review form, then show the reviews in the product page's HTML. Moderate for spam without editing for substance, and never buy or fake reviews.
What to take away
- Google shows review stars from aggregate rating markup inside Product, and only for real, visible reviews of the product on that page; a store rating itself is ineligible.
- Stars on free listings and Shopping ads come from Merchant Center's product ratings programme, which is separate from page markup.
- Customer reviews, questions and photos add the language shoppers search with and assistants quote, provided they sit on your page and in its HTML.
- Being named by an assistant follows from independent sources describing your brand consistently, which you earn rather than mark up.
Next
Put the page, the consistency and the mentions in the right order in Being the product AI recommends.