You can build a Yelp-style review site on WordPress with a directory plugin that supports listings, star ratings, written reviews and business owner claims, on a theme that makes it look like a real product. The hard part is not the software. It is trust: stopping fake reviews, letting owners reply without letting them edit the truth, and publishing review markup the way Google’s rules allow. This guide covers the structure, the plugins, the moderation and the legal basics.
Product details here were checked on each vendor’s own site in October 2026. Plugin features change often, so confirm anything that affects your plan on the vendor page.
In this guide
- What a Yelp-style site actually needs
- Which WordPress plugin should run the reviews
- How to structure a review: stars, text and photos
- How to prevent fake reviews
- How owner replies and disputes should work
- How review schema and Google’s rules apply
- How moderation works day to day
- How claiming listings fits in
- Local SEO pages that bring searchers in
- Legal basics
- How to design the site with Reign, step by step
- Questions people ask
What does a Yelp-style review site need?
A Yelp-style site is a business directory where the public, not the business, writes the reviews. It needs five parts: business listings, a review form with a star rating, a way for owners to claim and answer, moderation, and search pages that work by place and category.
Everything else is decoration. If you want a deeper look at what makes a directory worth running as a business, read what makes a directory worth running. If you only want to add reviews to an existing community, how to add business reviews and ratings to your community is the shorter job.
One honest warning before you start. Yelp has years of reviews, millions of visitors and a large trust and safety operation. You will not copy that on day one. What you can build is a review site for one city, one industry or one community, where you know the businesses and the reviewers. That focus is the reason a smaller site can win.
Which WordPress plugin should run the reviews?
Pick the plugin whose review features match your plan, then check the ones you need on its own page. Four options are worth a look: Listora, GeoDirectory, Directorist and HivePress. We make Listora, so we list it first and say so. The others each have real strengths.
| Plugin | Reviews and ratings | Claims | Maps | Best fit |
|---|---|---|---|---|
| Listora (made by Wbcom) | Reviews with owner reply. Multi-criteria reviews described in its restaurant playbook. Rating criteria sets and photo reviews need a paid licence, check the product page. | Owners claim a listing with proof and an admin approves it | Near Me with radius, drag the map to search that area, clustered results | Sites built on a block theme or Reign, where one product should cover submission, claims and reviews |
| GeoDirectory | Reviews in the base plugin. The MultiRatings and Reviews add-on adds several rating categories such as service, quality and price, and images in reviews | Claim Listing Manager add-on, with an owner-verified badge | Maps in the base plugin, marker clustering as an add-on | Directories that want many add-ons |
| Directorist | Reviews in the core plugin | Claim Listing is a paid extension | Google Maps or OpenStreetMap | Sites that want a visual form builder and many extensions |
| HivePress | Ratings and reviews listed on its comparison table | Claim listings listed, including charging for claims | Geolocation and radius search listed | Sites that may grow into a marketplace, bookings or classifieds |
Sources are on each vendor’s page: listora.org, GeoDirectory, Directorist and HivePress. HivePress’s own page describes its review feature only in a comparison table, so check its demo before you commit.
When is each one the better pick? GeoDirectory is the better pick if you want the widest range of add-ons and a plugin with a long list of add-ons. Directorist is better if your team likes a drag-and-drop builder and you want a plugin that works with several page builders. HivePress is better if reviews are one piece of a site that also takes bookings or sells things. Listora is the better pick if you want a block-based plugin that works with Reign and runs the whole flow, from submission to claim to reply, in one place. For a wider comparison, see the best WordPress directory plugins.
Whichever you choose, test the review form as a stranger on your phone before you build anything else. If it is awkward for you, it will be awkward for the person who just finished dinner and wants to say so.
How should a review be structured?
A good review has a star rating, a written comment, an author name and, where possible, photos. Each part does a different job. Stars let people scan. Text gives the reason. The name makes the review accountable. Photos prove someone was there.
Star ratings
Use a five-point scale. It is the scale readers expect, and it is the default scale Google’s review snippet guidelines use for rating values. Decide whether you want a single overall rating or several criteria. A restaurant can have food, service, ambiance and value. A plumber might have punctuality, price and quality of work. Listora’s restaurant playbook describes multi-criteria reviews of exactly that kind, and GeoDirectory’s MultiRatings and Reviews add-on does something similar.
More criteria give richer data, but they make the form longer, and long forms get fewer reviews. Start with one overall rating and one or two criteria that matter in your niche.
Written text
Google recommends only accepting ratings that come with a review comment and the author’s name. That is also good practice for trust. A bare five-star click is easy to fake and tells a reader nothing. Set a minimum length, perhaps a sentence or two, and show a prompt such as “What should the next customer know?”
Photos
Photos make a review credible, and they make fakery harder, because a fake reviewer needs a convincing picture. Listora’s photo reviews need a paid licence, check the product page. GeoDirectory’s MultiRatings and Reviews add-on supports images in reviews. If you take photos, set a size limit and moderate them as carefully as text.
To confirm the structure works, submit a review as a test user and check that the stars, comment, name and any photo all appear on the listing, and that the average rating on the listing card updates.
How do you prevent fake reviews?
You cannot stop all of them. You can make them expensive enough that most people do not bother, and catch the rest. Fake reviews come from three places: bots, the business itself or its friends, and competitors writing bad ones. Each needs a different defence.
Google’s guidelines are blunt about the standard. Reviews must not be fake or undisclosed incentivized reviews, meaning ones that are not based on a genuine experience, or written in exchange for a benefit without clear disclosure. Treat that as your house rule too.
Stop the bots
Require a logged-in account to review. Add a CAPTCHA or similar check. Listora’s submission flow ships with a honeypot, rate limits, a keyword blacklist and a URL-density cap, and it can use reCAPTCHA, Turnstile or Akismet once you add keys. Those protections are described for listing submissions on its site, so test your review form separately rather than assuming they cover it. Whatever plugin you use, rate-limit by account and by IP address, and block links in review text by default.
Slow down the insiders
Business owners and their friends are the larger threat on most small sites. Useful rules include:
- Block the listing owner from reviewing their own business, and flag reviews from accounts that share an IP address or email domain with the owner.
- Allow one review per account per business, with an edit window rather than unlimited rewrites.
- Hold the first review from a brand-new account for a human check.
- Watch for bursts. Five new five-star reviews in an hour on a quiet listing is a signal worth a look.
Catch the competitors
A flood of one-star reviews on one listing, from new accounts, is the pattern. Give owners a way to report a review, and give your moderators a queue where reported reviews sit above everything else. Never delete a review just because an owner asks. Check it against your written rules first.
Write the rules down
Publish a short review policy. Say what counts as a review (a real visit or purchase, one per person), what is not allowed (reviews of your own business, paid reviews, hate speech, private information) and what happens when a rule is broken. A published policy is also your defence when someone accuses you of bias.
How should owner replies and disputes work?
Let the owner reply publicly, once, under the review. Do not let them edit, hide or delete the review. That single rule is what separates a review site from a brochure site.
Listora lists reviews with an owner reply. Whatever plugin you pick, check that only the claimed owner can reply, and that the reply is clearly labelled as coming from the business.
Set a dispute path
Owners will dispute reviews. Some disputes are fair. A reviewer may have the wrong business, or describe something that never happened. Plan for this:
- The owner clicks “report” on the review and picks a reason, such as not a genuine experience, wrong business, or breaks the policy.
- The review stays visible while it is under review, unless it breaks a hard rule such as hate speech or private information.
- A moderator reads the report, the review and the owner’s reply, and decides within a stated time.
- Both sides get a short message with the outcome and the rule that decided it.
Keep a log of every decision, with the date and the moderator’s name. If a dispute reaches a lawyer, that log is what you will want.
To confirm the flow works, create a test owner account, claim a test listing, reply to a test review, and report another. Check that the reply is labelled, that the report lands in the queue, and that the owner cannot change the review text.
How does review schema work, and what does Google allow?
Review schema is structured data that tells search engines a page contains reviews or a rating. Google’s review snippet guidelines say what can be marked up and what cannot. The most important rule for a site like yours is about self-serving reviews.
Here is what Google’s review snippet documentation says. If the entity being reviewed controls the reviews about itself, its pages that use LocalBusiness or any other Organization structured data are ineligible for the star review feature. An example it gives is a review about entity A placed on the website of entity A. Ratings for local businesses must be sourced directly from users, and the page says not to rely on human editors to create, curate or compile ratings information for local businesses.
What that means for you is simple. A business that puts its own testimonials on its own page and marks them up as reviews of itself is not eligible. Your site is different, because the reviews on your listing pages come from independent users, not from the business being reviewed. Do not blur that line by letting owners paste reviews in.
The required properties
For a Review, Google’s page lists the author, the item reviewed with its name, and a review rating with a rating value. For an AggregateRating, it lists the item reviewed, the average rating value, and at least one of a rating count or a review count. The default scale is five points. If you omit best and worst rating, the defaults are 5 and 1.
The content rules
- The review content you mark up must be readily available to users on the marked-up page.
- Review information must be about a specific item, not a category or a list of items.
- If you include several individual reviews, also include an aggregate rating of them.
- Do not aggregate reviews or ratings from other websites.
The last rule matters if you were thinking of pulling in someone else’s reviews to fill an empty site. Do not. Your listing pages should only mark up reviews written on your own site.
What a plugin will and will not do
Check what your plugin outputs by testing a listing in Google’s Rich Results Test. Listora’s site does not describe schema for general listings, only for jobs, so confirm output for your own listings before you rely on it. GeoDirectory and Directorist do not mention schema on the pages we checked, so test those too. If your plugin does not output valid markup, an SEO plugin or a small custom function can add it. Even when markup is valid, Google decides whether to show stars, and it makes no promise to do so.
To confirm it worked, paste a listing URL into the Rich Results Test, check that Review or AggregateRating is detected with no errors, and that the numbers match what a visitor sees on the page.
How should moderation work?
Moderation works best as a small, fast queue with written rules, not as a heroic effort. You need three things: a place where flagged and new reviews wait, a clear rule for each decision, and a person responsible for clearing the queue on a schedule.
For a general approach to running a queue, our community moderation guide covers roles, warnings and escalation. For a review site, add these specifics:
- Pre-moderate or post-moderate? Pre-moderation holds every review until a human approves it. It is safer on a new site with few reviews. Post-moderation publishes at once and removes problems later. Many sites pre-moderate first reviews from new accounts and post-moderate everyone else.
- Decide what you remove. Remove personal information, threats, hate speech, spam and reviews of the wrong business. Do not remove a review only because it is negative.
- Tell people why. A one-line message naming the rule keeps trust, and it stops the same mistake from happening twice.
- Keep reviews and listing approval separate. Listora sends new listings for approval at the final submission step. Reviews need their own rule, so set one.
At small scale one person can handle the queue. At a few thousand reviews, add a second moderator, a daily check, and a rule for how long a report may sit. A review site where complaints go unanswered for a week loses its owners first and its readers second.
How does claiming a listing work?
Claiming lets a business owner prove they own a listing, so they can update its details and reply to reviews. It is also where most directories earn money. The claim is a trust step, so make it hard to fake.
Listora lets an owner claim an existing listing with proof, and an admin approves the claim. GeoDirectory’s Claim Listing Manager add-on does a similar job and adds an owner-verified badge. Directorist lists Claim Listing as a paid extension, and HivePress lists claim listings, including charging for claims. For what makes a directory profitable and how claimed and paid listings fit together, read our guide to claims and paid slots.
What proof to ask for
Ask for something only the real owner can supply. A business email at the listing’s own domain is the cheapest check. Other options are a utility bill or business licence, a phone call to the number on the listing, or a postcard with a code. Pick the lightest option that works for your niche, and keep a note of what each owner supplied.
What a claim should allow
A claimed owner can edit details, add photos, post updates and reply to reviews. They should not be able to remove reviews, change star ratings or turn off the review form. Write that down in your owner terms, so nobody is surprised.
If you charge for claims or for featured placement, keep a basic ownership claim open to every owner. Charging for the right to reply to reviews makes your reviews look bought, and readers notice.
To confirm it worked, claim a test listing from a second account, upload fake proof, approve it as admin, then check that the owner can edit and reply but cannot touch reviews.
What local SEO pages does a review site need?
A review site needs one page per business, one page per category, and one page per place, linked together. Those three page types match how people search: a business name, “dentist near me”, or “best pizza in Leeds”.
Build the pages in this order:
- Listing pages. Each has a unique title, address, hours, photos, the reviews and the average rating. Thin pages with only a name and phone number will not rank.
- Category pages. “Italian restaurants”, “emergency plumbers”. Add a short intro written by a person, then the list.
- Location pages. City or neighbourhood pages that list categories within them.
- Category by location pages. “Italian restaurants in Leeds” is where much of the search demand sits.
Search is what makes these pages work. Listora describes Near Me with a radius, a map you can drag to search that area, and results on a clustered map, which suits “near me” queries. Check any plugin you choose for filters in the URL, because a filtered view people can link to and search engines can crawl is worth more than one hidden behind a script.
Local search has its own habits. Our posts on local SEO for restaurants and the difference between local and organic SEO are useful background. Keep the business details on each page consistent, add a sitemap, and avoid duplicate pages for the same business.
For a worked example of a vertical directory on Reign, see the restaurant directory build. If your listings are for sale rather than for review, the classifieds directory guide is the closer match.
What legal basics apply to a review site?
The rules depend on where you and your users are, so check your local rules and talk to a lawyer before you launch. This section is a list of topics to ask about, not legal advice.
Review platforms have their own legal duties. Those can cover how you handle fake or paid reviews, what you must tell users about how reviews are collected and ranked, how you respond to complaints about defamatory content, and how you treat personal data in reviews and accounts. The rules differ by country and sometimes by state.
Questions to put to a lawyer:
- What happens if a reviewer says something false and damaging about a business, and who is responsible for it?
- What notice and takedown process should we publish, and how fast should we act?
- What must we disclose about incentives, such as discounts for leaving a review?
- What privacy notice, consent and data retention rules apply to reviewers’ accounts and photos?
- What do our terms need to say about who owns reviews and photos, and what we may do with them?
Practical steps that help in any country: publish terms of use and a review policy, keep a log of moderation decisions, never write or buy reviews yourself, and label any sponsored placement clearly. Google’s guidelines on incentivized reviews point the same direction.
How do you build the site with Reign, step by step?
Install Reign, import a demo, set up the directory plugin, configure reviews and claims, then build your category and location pages. The steps below assume a fresh WordPress install.
Step 1: Install Reign and import a starting layout
Reign is a WordPress community theme by Wbcom Designs. It has five header layouts, colour tokens and dark mode, with no code needed, and a Demo Installer for importing a starting site. Install the theme, run the Demo Installer, and pick a directory-style demo or the closest layout you can find.
To confirm it worked, open the front page and check that the header, footer and colours load, and that the site looks right at 390 pixels wide.
Step 2: Install the directory plugin
Install your chosen plugin from the vendor’s site. Reign styles Wbcom’s own plugins without an add-on. It also has a paid add-on for GeoDirectory, which you need only if you run that plugin. For Directorist and HivePress, check the result on a staging copy and adjust the colours until the cards match your brand.
To confirm it worked, create two test listings in different categories and view them on the front end.
Step 3: Define categories and fields
List your categories and the details a reader needs for each, such as hours, price range, phone number and service area. Keep the list short at first. You can add categories later, but reorganising hundreds of listings is slow.
To confirm it worked, submit a listing through the front-end form as a normal user and check that every field you set up appears on the listing page.
Step 4: Switch on reviews and set the rules
Turn on reviews, require a login, set a minimum length for the comment and decide whether first reviews wait for approval. If you use rating criteria, add the two or three that matter in your niche. Block the owner from reviewing their own listing.
To confirm it worked, post a review from a test account, then check that it appears (or waits in the queue, if that is your rule) and that the average rating updates.
Step 5: Set up claims and owner replies
Switch on claiming, decide what proof you require, and write the owner terms. Test the whole path from claim to approval to reply.
To confirm it worked, claim a listing from a second account and reply to a review as that owner.
Step 6: Seed the first reviews honestly
An empty review site looks dead. Do not invent reviews, because that breaks both Google’s guidelines and your own rules. Instead, invite real customers. Email the businesses you listed and ask them to invite their customers. Add the businesses yourself, then ask friends who really used them to write honest reviews. Fewer real reviews beat many fake ones.
To confirm it worked, check that each early review comes from a real, distinct account, and that none was written by you on behalf of someone else.
Step 7: Build the category and location pages
Create the category, location and category-by-location pages from the earlier section, with a short human-written intro on each. Add them to the menu and the sitemap.
To confirm it worked, search your own site for a category plus a place, and check that the result page lists the right businesses, shows their ratings and is linked from the menu.
Step 8: Test it as three people
Walk through the site as a visitor looking for a business, as a reviewer writing a review on a phone, and as an owner claiming and replying. Fix anything awkward before you invite real users. For a worked example of the design side, see the listings site built with GeoDirectory and Reign.
If you want members to talk to each other as well, such as a local group for reviewers, you can add BuddyNext, the Wbcom community plugin. It is optional, and the directory runs without it. Try BuddyNext or open the live demo if that sounds useful. Wbcom’s directory plugin is Listora, which runs on its own.
Questions people ask
Can I build a Yelp clone on WordPress?
Yes, a smaller one. A directory plugin gives you listings, reviews, search and claims, and a theme gives you the look. What you cannot copy is Yelp’s audience, so aim at a single city, trade or community where you can get the first hundred real reviews.
How do I stop businesses from posting fake reviews about themselves?
Require accounts, block owners from reviewing their own listing, flag accounts that share an IP address or email domain with the owner, and hold first reviews from new accounts for a check. No rule is perfect, so keep a report button and a moderation queue.
Will Google show star ratings for my listings?
Maybe. Valid markup makes your pages eligible, but Google decides what to show. Reviews must be written by independent users on your site, and pages where the reviewed business controls its own reviews are not eligible, according to Google’s review snippet guidelines.
Can I import Google or Yelp reviews into my site?
Do not mark up reviews copied from other sites. Google’s guidelines say not to aggregate reviews or ratings from other websites. The terms of the source site may also forbid copying, so read them first.
Do I need a lawyer?
For a real launch, yes, at least for an hour. Review platforms have their own legal duties, and the rules on defamation, takedowns, disclosures and personal data vary by place. Check your local rules before you go public.
Reign is the design layer behind this build. It gives a review site a clean, branded look that works on a phone, so the directory feels like a product rather than a plugin demo. See the Reign theme page for features and demos.