How to Embed Facebook Reviews on Your Website: 3 Easy Methods

Most articles about embedding Facebook reviews are quietly out of date, because they describe a feature Facebook removed. In 2018 Facebook stopped collecting 1 to 5 star ratings on Pages and replaced them with Recommendations: a customer taps recommends or does not recommend, writes a short comment, and that is the whole input. There is no star value in it. Everything about putting Facebook social proof on your website follows from that. You are not embedding star reviews, because there are none to embed. You are embedding a set of yes answers with text attached, and the interesting question is how to show that on a page next to a Google widget that really does have stars, without inventing a precision your customers never gave you.

Why There Are No Facebook Star Ratings to Embed

Because Facebook removed them. In 2018 the platform switched Pages from star reviews to Recommendations, and the input a customer gives changed from a number between one and five to a binary answer plus a comment. Facebook's reasoning at the time was that a written recommendation carries more useful signal than a middle-of-the-road star count, and the format has stayed that way since.

The change also removed the middle. Under stars a customer could give three, which reads as fine but unremarkable. Under Recommendations there is no three: they either recommend you or they do not, which makes the set more decisive and, for a website, easier to summarise honestly.

It is worth being precise about the vocabulary, because the interface still uses both words in places and every third-party article uses them interchangeably. What customers leave today are recommendations. What some of them left before 2018 were star reviews, and those older ones still exist on the Page.

So What Is the Rating on Your Page?

A derived figure rather than an average of stars people chose. When Facebook made the switch it kept a rating on the Page but changed what feeds it, taking legacy star reviews together with newer recommendations into account rather than reflecting a star value from each recent customer.

That distinction matters when your website shows a Facebook rating next to a Google one. The Google figure is the mean of numbers customers picked. The Facebook figure is a summary of a mixed set, part of which is binary. Displaying them side by side as though they were the same measurement overstates what the Facebook number is.

The safe approach is to show the Facebook figure exactly as the Page shows it, labelled as Facebook, and to lean on the count rather than the decimal. Forty-one people recommend this business is a claim a visitor can check in one click, and it does not depend on anyone agreeing what a Facebook 4.8 is an average of.

How Do You Show a Yes or No Recommendation on a Website?

Lead with the text. A recommendation without its comment is just a tally, and the comment is the part that persuades: it names the service, the problem, the person who fixed it. On a card the text carries the weight that stars carry on a Google card.

Keep the recommendation visible as a recommendation. A small recommends marker, or a thumbs-up glyph beside the name, tells the visitor what kind of endorsement they are reading and costs one line of layout. Silently rendering every yes as five gold stars asserts something the customer did not say, and it is the most common mistake in hand-built Facebook sections.

Use the count as the headline. Thirty-eight of forty people recommend us is stronger than a manufactured 4.75, because it is the shape of the underlying data and it survives a click-through to the Page.

If Facebook is one platform among several on your site, this is also the argument for badging every card by source. A visitor who can see which card came from where will read the Facebook cards on Facebook's terms without you having to explain the format.

What Are the Three Ways to Get Recommendations Onto Your Site?

Copy them by hand. Open your Page, take the recommendations you want, and rebuild them as cards with the person's first name, the recommendation marker, the date and the text. Free, immediate, and frozen from the moment you publish, which on Facebook is a slightly bigger problem than elsewhere because people delete and edit their own posts freely.

Use the Graph API. It can return a Page's ratings and recommendations, and it is the most gated route of any platform in this series. The next section covers what that involves.

Use a review widget. Connect the Page, choose a layout, paste one line of HTML, and the widget keeps up with new recommendations without an app, a token or a review process. This is the route that exists precisely because the API route is closed to most people.

Why the Graph API Is Not the Shortcut It Looks Like

Because it is owner-only and gated end to end. To read a Page's ratings you need a Facebook app, a Page access token for a Page you administer, the relevant permissions granted, and the app has to pass Facebook app review before it can be used in production. There is no public anonymous endpoint that returns any Page's reviews the way some platforms allow.

App review is a real process with a real failure rate, and it is not a one-time cost. Permissions get re-reviewed, tokens expire and have to be refreshed, and a change on Facebook's side can break an integration that has been working for a year. For a business that just wants recommendations on a page, that is a maintenance commitment out of all proportion to the outcome.

The API also hands you the binary. Recommendations come back as recommends or does not recommend, so every question in the display section above is still yours to answer in code after you have finished the paperwork.

One thing the Graph API is genuinely good for: if you already run a Facebook app for something else and have the tokens in place, pulling the recommendation count for an internal dashboard is a small job. It is the website widget use case where the overhead does not pay.

How Do You Build the Facebook Reviews Widget?

Connect your Facebook Page, preview your real recommendations, and choose from over 100 layout styles across slider, marquee, grid, list, masonry and badge families. Because recommendation text does the persuading here, the text-forward layouts tend to work better for Facebook than the compact star-led ones that suit Google.

No Facebook app, no access token, no app review. That is the practical difference between this route and the previous section, and it is why most businesses end up here.

The embed is one line of HTML and goes into WordPress through a Custom HTML block, Squarespace through a Code block, Wix through the HTML iframe element, Shopify inside a theme section, Webflow through an Embed element and Framer through an Embed component. Free plan, unlimited widget views.

Do not confuse this with the Facebook Page Plugin, which many guides recommend by mistake. The Page Plugin embeds your Page timeline: posts, likes and a follow button. It is a social widget, not a reviews widget, and a visitor looking for proof will find your last three posts instead.

Where Do Facebook Recommendations Belong?

On pages where the audience is already a Facebook audience. If your traffic arrives from a Page, a local group or a Facebook ad, the recommendation cards are familiar in format and the wordmark is doing recognisable work. If your traffic arrives from search for a B2B product, Facebook proof is the weakest card in your hand and something else should hold that space.

Recommendations suit the longer section rather than the tight badge, because the value is in the text. A three-card row where each card has room for two or three sentences will outperform a compact strip that shows a rating and truncates every comment to a line.

And place them where the objection they answer actually appears. A recommendation that describes a callout at nine on a Sunday belongs beside your emergency service copy, not on the homepage in a rotation with forty others.