Every couple of months I get the same question from a law firm owner. “Our SEO guy said he can add review schema to our site and we’ll get star ratings showing up in Google search results — is that real?” The answer is “yes, it’s a real Google feature, but no, what the SEO guy is describing almost certainly won’t work the way he’s selling it, and depending on how he implements it, it might get your site a manual action.” This page is the version I wish more firms had read before letting a vendor stuff their site full of self-published review markup.
I’ll cover what review schema is, what Google actually does with it, the difference between third-party verified reviews and self-published rating markup, why Google has cracked down on the self-published version, the legitimate use cases that still work, and the contrarian take — most “review stars on my site” implementations don’t show in Google and the ones that do work require infrastructure most firms don’t have. There’s no shortcut. The work to get star ratings in search results is mostly the work to get real Google reviews on your Google Business Profile.
What review schema actually is
Schema markup is structured data — extra code embedded in a webpage that tells search engines specific facts about what’s on the page. Schema.org is the consortium that maintains the vocabulary. For reviews, the relevant schema types are Review (a single review of something) and AggregateRating (a summary of multiple reviews, with an average rating and a review count). The markup is typically in JSON-LD format and embedded in the page’s HTML head.
The theory behind review schema is straightforward. The site embeds machine-readable data about reviews on the page. Search engines parse the data. When the page appears in search results, the search engine has the option to display a “rich result” — a snippet with stars, average rating, and review count visible to searchers. The rich result is more visually prominent than a regular result, which improves click-through rate. Everyone benefits — the searcher sees more relevant information, the site gets more traffic, the search engine produces a better experience.
The theory works as described — for products, recipes, books, movies, and a few other categories where review schema has been broadly supported. For law firms it works differently, and the difference is important.
What Google requires (and doesn’t require) — third-party verification
In 2019, Google updated its rich results guidelines to add a specific restriction on review schema for what they call “LocalBusiness” and “Organization” page types — which includes law firms. The change — Google no longer displays rich review results for self-published review markup on a business’s own site. If a law firm publishes Review schema with five reviews and a 5.0 AggregateRating directly in the firm’s own page code, Google will not show stars in search results for that page. The markup is technically valid. Google’s algorithm just ignores it for rich result purposes.
The reason — Google decided that businesses self-publishing their own reviews creates an unreliable signal. A business can manufacture any review schema it wants, with any rating it wants. The integrity of the rich result depends on the underlying review data being verifiable. Google’s standard for verifiability is “third-party platform that aggregates real reviews and exposes them via API or widget” — Google’s own GBP being the canonical example, but also Yelp, Avvo, BBB, Trustpilot, and similar platforms.
The practical implication — adding Review schema with self-published data to a law firm’s site does nothing in search results. The vendor selling this implementation is selling something that doesn’t function for the intended purpose. The firm doesn’t see star ratings appear. The vendor’s monthly fee continues. The firm doesn’t know why nothing happened because most firms don’t have the tooling to verify what’s happening with their structured data.
Most “review schema for law firms” implementations are technically valid code that produces nothing. The schema is real. The output is zero. The invoice is monthly.
When self-published review markup gets you in trouble
Worse than “doesn’t work” — self-published review markup that Google decides is manipulative can trigger a manual action. Google’s Webmaster Guidelines list “structured data spam” as a specific manual action category. If Google’s quality team reviews the site and determines the schema is being used to misrepresent the page (for example, claiming reviews that don’t exist, manufactured ratings, schema-stuffing across pages that aren’t actually reviewed), the site can receive a manual penalty. The penalty typically removes the page from rich result eligibility and, in worse cases, can affect rankings.
The pattern that draws manual actions — perfect 5.0 AggregateRatings with implausibly high review counts, review markup on every page including practice pages and blog posts that don’t have reviews, fake reviewer names and dates, markup that contradicts the visible content on the page. The Google quality team sees these patterns when reviewing sites for various reasons (spam reports, automated flagging, periodic spot-checks). The pattern most likely to draw a manual action is “law firm site with Review schema on twenty pages, perfect average ratings, no visible reviews matching the markup.”
The fix once a manual action is in place — remove the offending schema, file a reconsideration request through Search Console, wait for Google to review. The process takes weeks. The site is partially or fully suppressed in search during the review. The recovery is rarely complete — Google’s trust in the site as a source is diminished after a structured data violation.
The risk-reward is bad. Self-published review schema doesn’t produce stars in search. It does occasionally produce manual actions. Skip the practice entirely.
What does work — third-party verified review widgets
The legitimate version of review-rich-results for law firms exists but works through a different mechanism. Third-party platforms that aggregate verified reviews (Google’s own GBP being the primary example) expose those reviews via API. If a firm embeds those reviews on its own site using the official platform’s widget or API, the reviews displayed are real, the data is verifiable, and Google generally treats it as legitimate.
The specific implementations that work — Google’s own GBP review widget (officially supported, displays real reviews on the firm’s site, doesn’t generate self-published schema). Trustpilot’s verified review widget for businesses that have a Trustpilot presence. Bazaarvoice and similar enterprise verified-review platforms (typically overkill for law firms). Birdeye and Podium’s review display widgets, which pull from real review platforms and embed via their official tooling.
The key distinction — the widget is pulling real reviews from a verified third-party source. The page is displaying real reviews, not manufactured schema. The schema, if any, is generated by the third-party widget and references the verified source. This is structurally different from the firm or its SEO vendor writing static Review schema into the page’s source code.
Even with these legitimate implementations, the rich result outcome for law firms is inconsistent. Sometimes star ratings appear in search results for the firm’s own pages. Often they don’t. The rich result decision is at Google’s discretion and the algorithm weighs various factors. The honest framing — implementing verified third-party reviews on the firm’s site is good for conversion and user trust regardless of whether stars appear in search. The search snippet outcome is an occasional bonus, not the primary justification.
The Google Business Profile path — where stars actually come from
The way most law firms actually get star ratings displayed in Google search is not through schema on their own site at all. It’s through their Google Business Profile. The GBP listing, when it appears in search results (in the local pack or in the knowledge panel for branded searches), already displays the firm’s star rating and review count. Google generates that display from the verified review data on the GBP itself. No schema on the firm’s site is involved.
For most law firm prospects, the search journey works like this — the prospect searches “[practice area] lawyer [city]” or similar. The search results show the local pack (three GBP listings with star ratings and review counts), plus organic results below. The prospect’s eye goes to the local pack first — star ratings, review counts, photos, all visible. They click into a firm’s GBP, see the full review profile, and either call or visit the firm’s website.
The implication — investment in GBP reviews produces visible star ratings in Google search. Investment in self-published review schema on the firm’s own website does not. The same dollar spent on review velocity for GBP (see Google review strategy for law firms) produces a vastly better outcome than the same dollar spent on schema markup. For the GBP-specific tactical work see Google Business Profile for law firms.
Schema that does help law firms — the legitimate stack
Self-published Review schema doesn’t help. But other schema types do help law firm sites, and there’s a legitimate role for structured data in legal SEO. The core stack that I recommend for law firm pages — Organization or LegalService schema for the firm overall (with address, phone, hours, areas served). Person schema for each attorney with bio page (with credentials, education, professional memberships). BreadcrumbList schema for navigation. Article schema for substantive blog content and deep-dive pages. FAQPage schema for pages with multiple Q&A blocks.
The AggregateRating sub-property of Organization or LegalService schema is the one that gets misused. The schema technically allows a business to publish its own AggregateRating. Google’s policy says this won’t trigger rich results when self-published. Some vendors still include it because “it might help someday if Google changes its policy” — which is essentially gambling against Google’s documented direction. I leave it out of my client implementations because the upside is zero and the downside (slight risk of manual action) is non-zero.
For the broader schema-for-law-firms treatment see schema markup for law firms and the answer page on what schema markup do law firms need.
The rich snippet realities — what actually shows up
For a law firm site, the realistic rich snippet outcomes from a clean schema implementation are — FAQ rich results on pages that have FAQ schema and substantive Q&A content (these still work in 2026, though Google has reduced their prevalence). Breadcrumb display in search results when BreadcrumbList schema is implemented. Knowledge panel population for the firm’s brand searches when Organization schema is complete and consistent with other data sources. Sitelinks for navigational queries on the firm’s brand name.
What doesn’t show up — star ratings on practice pages from self-published Review schema. Average ratings on the firm’s own pages from self-published AggregateRating. Review snippets in organic results from schema embedded by the firm or its SEO vendor.
The honest framing — the rich results that do work for law firms are useful but modest. FAQ rich results bring some incremental click-through. Breadcrumbs improve the visual cleanliness of the search snippet. Knowledge panels enhance the firm’s brand presence. None of these are dramatic. The most impactful thing a firm can do for search visibility is still the foundational work — practice page quality, citation cleanliness, review velocity on the GBP. Schema is supporting infrastructure, not a substitute.
The contrarian take — most schema-for-reviews advice leads to manual actions
The SEO industry has a persistent narrative around review schema that’s been wrong since Google’s 2019 policy change and remains wrong. The pitch — “add review schema to your site and get stars in Google search results, instantly improving your click-through rate.” Variations on this pitch are sold by hundreds of SEO vendors, plugin developers, and “rich snippet experts” every day. The implementation is real. The result is not. The downside is occasionally severe.
The reason the bad advice persists — the implementation is easy. The vendor can deploy review schema across a client site in an afternoon. The schema validates in Google’s structured data testing tool. The vendor can take a screenshot of the validation tool and show the client “look, the schema is working.” The client doesn’t notice that the stars never actually appear in real search results because the client isn’t checking, and when they ask, the vendor says “Google is still processing — give it more time.” The fee continues. The result never arrives.
The cases where it goes worse — the vendor gets aggressive with the schema. They add Review markup on every page. They generate fake reviewer names to populate the schema. They publish a perfect 5.0 AggregateRating with 200 reviews on a firm that has 30 reviews. The site gets a manual action. The firm’s rankings drop. The vendor blames “Google’s algorithm changes” and continues billing. The firm pays an audit-and-fix engagement to recover.
The honest version of the advice — for review-related search visibility, invest in GBP reviews. Use a legitimate third-party widget if you want to display reviews on the firm’s site. Don’t self-publish Review or AggregateRating schema. The schema that does help (Organization, Person, FAQ, Breadcrumb) is worth implementing carefully. The schema that doesn’t help (self-published Review markup) is worth skipping entirely.
If you’ve already had bad schema implemented — the cleanup
For firms that have had a vendor install aggressive review schema and want to clean it up, the process is straightforward. Audit every page’s schema using Google’s Rich Results Test (free tool — search for it). Identify Review and AggregateRating markup that doesn’t correspond to real verified reviews. Remove or replace through the WordPress theme, Yoast/Rank Math settings, or wherever the schema is being generated. Test again. Submit the affected URLs for re-indexing through Search Console.
If a manual action has been issued for structured data spam, the additional step is filing a reconsideration request through Search Console explaining the changes made and confirming the offending schema has been removed. Google’s review of reconsideration requests typically takes one to four weeks. The site may or may not be restored to its prior search visibility depending on the severity of the violation and Google’s discretion.
For most firms the cleanup is preventative rather than reactive — most don’t get manual actions for review schema because Google doesn’t catch every instance. But the schema isn’t producing benefits either way, and cleaning it up reduces the long-term risk. Better to have honest schema or no schema than ambitious schema that’s drawing the wrong attention.
A note on AI Overviews and search evolution
Google search results have changed substantially with AI Overviews and the shift toward generative answers. Review snippets and traditional rich results matter less than they did three years ago because more search journeys now end in an AI-generated summary rather than a click to a website. The shift doesn’t change the underlying schema policy — self-published review markup still doesn’t produce rich results and still occasionally produces manual actions — but it does change how much the result matters.
The implication for law firm SEO investment — the marginal value of getting a star rating in a traditional rich result is lower in 2026 than it was in 2019. The marginal value of having a strong GBP, complete Organization schema, real reviews from real clients, and substantive practice pages that AI Overviews can reliably cite is higher. The shift is toward “be the source the AI cites” rather than “get the prettiest snippet in the search results.” Schema still matters because it helps Google understand the page accurately, which helps the AI cite the page accurately. But the schema isn’t the destination. The substantive work behind the schema is.
Summary — what to do and what not to do
Do — implement Organization or LegalService schema correctly for the firm. Implement Person schema for each attorney’s bio. Implement BreadcrumbList for navigation. Implement FAQPage on pages with substantive Q&A content. Use Google Business Profile as the primary review presence and let GBP-generated star ratings appear in search results naturally. If you want to display reviews on the firm’s own site, use a legitimate third-party widget (Google’s own, Birdeye’s, Podium’s, etc.) that pulls verified reviews.
Don’t — self-publish Review or AggregateRating schema on the firm’s own site with manufactured data. Don’t let a vendor install aggressive review schema with the promise of stars in search results. Don’t pay for “rich snippet optimization” as a standalone service. Don’t run review-gating services or otherwise manipulate which reviews end up on which platforms. Don’t expect schema markup to substitute for the actual work of producing real reviews from real clients.
The work behind a strong review presence is the work of running a firm clients want to recommend, plus the discipline of asking for reviews consistently, plus the patience to let the GBP profile build over years. Schema is housekeeping on top of that work. It’s not the work itself.
Adjacent topics
For the practical review generation strategy that produces the underlying reviews see Google review strategy for law firms. For the bar-rule compliance frame see ABA rules on soliciting client reviews. For the platform-by-platform breakdown see managing reviews across platforms. For the deeper schema treatment see schema markup for law firms and what schema markup do law firms need. For the GBP foundation work see Google Business Profile for law firms.
For the broader frame on what actually moves cases see the legal SEO authority page, the local SEO guide, and our approach.
If you want a second set of eyes
The free audit I offer includes a schema review on the firm’s site. If there’s self-published Review or AggregateRating markup, I’ll flag it and tell you what risk profile it represents. If the legitimate schema (Organization, Person, FAQ, Breadcrumb) is missing or misconfigured, I’ll tell you what to add and where. If you’re paying a vendor for “rich snippet optimization” and it isn’t producing anything, I’ll tell you that too. No deck. No upsell.
— The owner, PHX Search Co.