Review Schema Won't Show Your Own Stars

There is a widespread piece of advice that goes like this: add Review and AggregateRating schema to your own website, and Google will show your star rating in search results. Plenty of property managers have paid to have it done.

It doesn’t work, and it can hurt you. Google does not let a business mark up reviews of itself, on its own site, to earn the star feature. Doing it anyway is ineligible for stars and risks a manual action against your site. If your reviews are strong, that’s worth protecting, not gambling on a tactic that Google explicitly disallows.

This post explains the rule, where your local star rating actually comes from, and the schema on your own site that is legitimate and worth doing.

Can you use review schema to show your own star rating?

No. Google’s policy is direct: if the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or any other Organization structured data are ineligible for the star review feature.

The rule is simple: you cannot publish your own star rating through schema on your own website. Review and AggregateRating markup exists for reviews of other entities, a page reviewing a product, a place, a different business, not a business rating itself. For a property manager, self-hosted review schema about your own firm is off the table.

This is not a grey area or a loophole to work around. It’s a stated policy with a manual-action penalty attached. Any implementation that tries to surface your own stars from your own markup is working against Google, not with it.

Does an embedded review widget count as self-serving?

Yes, and this is the version that catches people who thought they were being careful. Embedding a third-party review widget, a Google or Facebook reviews block rendered onto your own page, does not change who controls the reviews being displayed. The entity is still reviewing itself on its own property, so the page is still ineligible.

The distinction people expect to matter, that the reviews are “real” and came from a genuine third-party platform, isn’t the one Google is drawing. The test is control of the surface, not authenticity of the reviews. A widget showing your genuine four-point-eight rating is treated the same as markup you wrote by hand.

Displaying reviews on your site for human visitors is completely fine and often worth doing, because an owner comparing two firms wants to read them. What isn’t fine is attaching structured data that asks Google to promote that rating into the search result.

Where does a local business star rating actually come from?

Local businesses do get star ratings in search. They come from Google’s own review corpus, not from anything on your website.

Your stars appear through the Google Business Profile and local-pack ecosystem. When an owner searches “property management Vancouver,” the map pack and your knowledge panel can show your rating and review count, drawn from the reviews on your profile. Two things drive it.

The volume and recency of your Google reviews

A steady flow of recent reviews on your profile is what feeds the rating Google displays, and recency carries real weight in local ranking, not just in what shows. A firm with two hundred reviews whose most recent is eight months old is losing freshness ground to one with forty and a review from last week. This is a process problem, not a markup problem, and I covered how to build that process in why happy clients don’t leave reviews.

A well-grounded business entity

Google has to be confident that the profile, the website, and the business are one and the same before your reputation on one surface reinforces your position on another. That confidence comes from consistent business information and an explicit link between the two, which is what the schema below is for. Without it, you have a well-reviewed profile and a website Google treats as a separate, unvouched-for thing.

Which schema is worth implementing on your own site?

Dropping the self-review tactic doesn’t mean schema is pointless. The foundational, legitimate piece is LocalBusiness schema for entity grounding, and most property managers I audit don’t have it complete.

It tells Google, in structured form, who your firm is: name, address, phone number, category (RealEstateAgent for a property manager), service area, hours, and, through the sameAs field, the links connecting your website to your Google Business Profile, LinkedIn, and industry listings. It produces no visible star snippet, because that is not what it’s for. What it does is make Google confident your website and your profile are the same entity, which is exactly the confidence that lets your reputation reinforce your organic presence.

The full field-by-field implementation is in LocalBusiness schema for property managers. That’s the schema worth investing in. The stars come from the reviews themselves, on Google.

Do AI search engines use your review markup?

Not in the way people hope. An engine answering “best property manager in Burnaby” is not reading a self-declared rating off your page and treating it as evidence, for the same reason Google doesn’t: a business asserting its own score is not an independent signal.

What does travel is the entity chain. When your sameAs array points at your Google Business Profile, an engine trying to establish who you are can follow that link to the real review corpus, held by a third party, and use what it finds there. So the work that makes you citable in AI answers is the same work described above: complete entity grounding plus a genuine review base on the profile.

This is worth being precise about, because “schema helps you get cited by AI” gets repeated as though any schema will do. The schema that helps is the schema that resolves your identity. Markup asserting your own quality helps nobody and risks a penalty.

What does the manual-action risk actually mean?

A manual action is a human reviewer at Google applying a penalty to your site, as distinct from an algorithm quietly ranking you lower. For structured data violations it usually arrives as a “Structured data issue” notice in Search Console, and the effect is that Google stops trusting your markup, sometimes across the whole site rather than only the offending page.

That last part is what makes this worth taking seriously for a property manager. The markup carrying your entity grounding, the block that tells Google your name, service area, and profile chain, sits on the same pages. A penalty aimed at self-serving review markup can take the credibility of the rest of your structured data with it, which means you lose the thing that was actually working in order to keep the thing that never worked.

Recovery is not complicated but it isn’t instant either: remove the offending markup, request a review in Search Console, and wait. Not adding it is materially cheaper than removing it later.

What should you do instead?

Four steps, in order.

1. Stop, or don’t start, marking up Review or AggregateRating about your own firm. It’s ineligible and carries manual-action risk. If a previous developer added it, have it removed rather than left in place as dormant risk.
2. Build your Google review velocity. Recent, genuine reviews on your profile drive the rating Google displays. That’s the process worth investing in.
3. Implement complete LocalBusiness schema for entity grounding: correct type, address, areaServed, and a populated sameAs chain to your profile and listings. Our schema markup service covers this, including stripping self-review markup a previous developer left behind.
4. Validate what you have. Run the site through the Schema.org validator and Google’s Rich Results Test to confirm your entity schema is clean and to catch self-serving review markup that should come off.

---

If you’re not sure whether your site carries risky self-review markup or complete entity grounding, I’ll check it as part of a free audit, along with where your Google review profile stands against your competitors, walked through with you live. The audit is the next step.