Most restaurant apps are built to sell tables or ads. A guide written by food lovers is built for a different reason: people who eat in the same town want to know what the others actually thought, and they would like to eat together now and then. Both jobs are small and local, and WordPress handles them well.
This guide sets up three pieces. Listora holds the restaurant listings and the reviews. Eventonomy runs the tasting meetups. BuddyNext gives members profiles and neighbourhood spaces so the guide has a community behind it. Reign is built to work with BuddyNext and every Wbcom plugin, so the whole site shares one design. Free and Pro scope is marked wherever it changes what you can do.
If you are still comparing review-site approaches in general, our walkthrough of a Yelp-style review site on WordPress covers fake-review defence, schema and legal basics. This post stays on the setup of a food lovers’ guide specifically.
What a food lovers’ guide has to do that a review app does not
A review app optimises for volume. A guide made by a group of enthusiasts optimises for judgment. Four differences shape every decision below.
- Reviewers are known. Your reviewers are members with profiles, not anonymous strangers, so a reader can learn whose taste they share.
- The list is curated. You would rather have 80 restaurants described well than 800 scraped from a map.
- Eating together is part of the product. The meetup is not an add-on. It is how reviewers meet each other and how new restaurants get tried.
- Freshness beats size. A closed restaurant still shown as open costs you readers faster than a thin directory does.
Keep those in mind and most settings choose themselves. The rest of this guide goes in the order a member meets the site: a listing, a review, a meetup.
Design the listing around how people pick where to eat
Listora ships a built-in Restaurant listing type, so you do not start from a blank form. Its fields are already the ones diners filter on.
| Field | What it holds | Why it matters in a guide |
|---|---|---|
| Cuisine | A multi-select list (Italian, Japanese, Seafood and so on) | The first filter most people reach for |
| Price Range | Four steps from budget to fine dining | Lets a reader rule places in or out quickly |
| Business Hours | Opening hours per day, with up to three ranges so a lunch break fits | Cards and search show an open or closed state against your site’s timezone |
| Reservations | Yes, No or Online Only | Saves a phone call |
| Delivery and Takeout | Two checkboxes | Useful filters for casual places |
| Menu URL | A link to the restaurant’s own menu | You link out instead of retyping prices that go stale |
| Photo gallery, video, social links | Media and profiles | Makes the card worth clicking |
Those fields come from the plugin’s own type definition. You can edit them in Listora, Listing Types and add your own. The type editor supports text, number, date, choice and map location fields, so a guide that cares about something particular, such as “Vegetarian main courses on the menu”, can add a yes or no field and make it filterable.
Features, categories and locations
Listora keeps three separate ideas apart, and it pays to use all three.
- Categories say what the place is: Bakery, Ramen shop, Wine bar.
- Locations say where it is. This is a hierarchical list, so you can nest neighbourhoods inside a city.
- Features, which Listora’s documentation also calls amenities, are flat attributes such as outdoor seating, step-free access or vegan options. They become checkboxes in the search sidebar.
The documentation suggests keeping the features list to somewhere between 8 and 15 items so the filter panel stays readable. For a food guide that usually means a few access and dietary items plus a couple of atmosphere items. Resist adding a feature for every quirk. A short list that people actually tick beats a long one nobody opens.
A note on dietary information
A listing that says “vegan options” is a member’s observation, not a guarantee. The software does not check what is in a kitchen. Say so on the directory page, and tell anyone with an allergy to ask the restaurant directly before they eat. This is general good practice and not medical advice.
Collect listings without losing control of quality
Members add listings through a multi-step form. Submitting needs a logged-in account, which already filters out a lot of casual spam. A duplicate check runs while the name is typed and warns when a similar listing exists, so you do not end up with three entries for the same corner cafe.
Under Listora, Settings, Submissions you choose the behaviour that matters most to a guide:
- Moderation mode. Manual review holds every new listing as pending. For a curated guide, start here and relax it later if the queue is quiet.
- Edit approval. Require re-approval when a listing is edited if you do not want an owner swapping a description for an advert after it was approved.
- Expiration in days. Restaurants close, move and change hours. Setting an expiry means a listing needs a renewal to stay live, which forces someone to confirm it still exists.
- Image limits. A cap on gallery photos keeps pages light.
Seed the guide yourself first. Add 15 or 20 places you can describe honestly before you invite anyone. A new member who lands on an empty directory leaves, and the quality of the first listings sets the tone for everyone who follows.
Maps are included at no cost. The free plugin uses Leaflet with OpenStreetMap tiles, with a Near Me button and a “search this area” option when someone drags the map. Pro adds Google Maps with marker clustering if you prefer that look or already pay for a key.
Reviews your readers can trust
Listora’s review system is complete in the free version: one to five stars, a written review, helpful votes, a report button, and a public reply from the owner. Several of its defaults suit a guide.
- One review per member per listing. The reviews table enforces it, so nobody inflates a score by posting repeatedly.
- A minimum length. Set one under Listora, Settings, Reviews and one-word reviews stop appearing. Setting it to zero allows star-only reviews, which suit almost nobody here.
- Auto-approve or hold. For a small, known group, publishing straight away is fine. Once strangers can join, hold reviews for approval and use the queue to read before anything goes live.
- Report a review. Flagged reviews show in a Reported by visitors filter in the moderation screen, so you can handle disputes in one place.
What Pro adds to reviews
Pro adds multi-criteria reviews and photo reviews. The documentation gives restaurants Food, Service, Ambiance and Value as the example criteria. For a guide that wants to separate “great food, slow service” from “average food, lovely room”, that split is worth having. Photo reviews let a reviewer attach the plate, which is usually the first thing a reader looks for.
You can run a good guide without either. If you start free and your reviewers keep writing “the food was great but” in the first line, that is your cue.
Write a review policy and pin it
Short and plain wins. A useful policy answers:
- Must you have eaten there? (Most guides say yes.)
- Do you declare a free or discounted meal? (Say yes, and say where to put the note.)
- What gets removed? (Abuse, personal attacks on staff, anything you cannot stand behind.)
- How can an owner dispute a review? (The reply feature, then a contact route to you.)
Post it as a BuddyNext announcement and link it from the review form page. Rules that members can see are easier to enforce than rules you apply quietly.
Working with restaurant owners without selling them the rankings
Owners will turn up. The question is what you let them do.
Claims. Listora’s claim flow is free. A logged-in owner opens a listing, presses the claim button and submits proof of ownership, with an optional document. Every claim waits for an admin to approve it; there is no auto-approve. On approval the owner becomes the author of the listing, can edit it and can reply to its reviews. Approving a claim does not add a verified badge. That is a separate manual step in Pro, so decide in advance what your badge means. Something like “we confirmed this person manages this restaurant” is honest and checkable. “Recommended by us” is a different statement and should be a different label.
Owner replies. Allow them. A restaurant that answers a critical review calmly does itself a favour, and readers notice. The reply is labelled as the owner’s response, so nobody mistakes it for a review.
Featuring. In the free plugin an admin ticks a Featured box on a listing, and the Featured block shows only listings you have flagged. Owners cannot feature themselves unless you set a featured upgrade cost above zero in the credits settings, which belongs to the Pro credits system. If your guide is editorial, keep featuring as your own decision and publish how you choose. If you want to earn from listings, Pro’s pricing plans and credits are how Listora does it, but then say plainly which placements are paid. Mixing the two without telling readers is the fastest way to lose them.
Direct contact. Each listing has a contact form, and every message is saved as a lead the owner can read in their dashboard. That is the route for a diner’s question about a private event.
Tasting meetups with Eventonomy
A tasting meetup is a small event with a venue, a headcount and a few practical questions. Eventonomy’s free plan covers all of it.
Make each meetup bookable
In the event editor choose People register here, then set the options that matter for a dinner:
| Setting | Suggested choice | Reason |
|---|---|---|
| Capacity | The number the restaurant agreed to seat | Only “Going” counts toward capacity |
| Waitlist when full | On | The oldest waitlisted person is promoted automatically when someone cancels |
| Additional guests | Allow, with a limit | Each guest counts toward capacity |
| Close registration before the event | A number of hours that suits the kitchen | Gives the restaurant a final headcount |
| Show remaining spots | On | Creates gentle urgency |
| Do attendees need an account? | Must log in | Ties RSVPs to members and reviewers |
Ask for dietary needs properly
Turn on Custom questions in the registration settings and add one for dietary requirements, with a required flag. Then tick it on the event. The organiser sees the answers alongside the attendee list. Ask for what the kitchen needs and no more. Collect the minimum, keep it for the event, and delete it afterwards where you can.
Let members propose meetups
With member submissions on, any logged-in member can create an event from the front end through the My Events dashboard or the event editor block. Turn on approval so each proposal waits for you, and cap how many events one member can create so one enthusiast cannot fill the calendar. The organiser gets an email when you approve or reject.
Recurring tasting nights
Eventonomy’s free recurrence handles daily, weekly and monthly repeats, so “the last day of each month” patterns need Pro, but “every month on the same date” does not. Be aware of how registration works: one RSVP covers the whole series, and the event page lists the other dates as information rather than a choice. If each evening has its own menu and its own capacity, create a separate event per evening. Editing a recurring event edits the whole series, and there is no “this date only” edit, though you can cancel a single date.
Message the table
Before the night, use the attendee screen to email everyone marked Going, or Going plus the waitlist, with an arrival time or a menu change. Messages are queued and sent in batches. Registrants who opted out of event emails are skipped.
Charging for a tasting
Collecting money is a Pro feature in Eventonomy: paid tickets, Stripe and PayPal checkout, door check-in and organiser payouts. Whether a restaurant or you take the money, and any tax that follows, is something to settle with the venue and your accountant. For many guides the simplest arrangement is free RSVPs where each person pays the restaurant directly.
If you want a wider look at running events from your own site, our post on a Meetup alternative on WordPress goes deeper.
Bringing the guide and the community together
On their own, the three plugins work side by side. Link the directory, the events page and your neighbourhood spaces from the navigation and you have a working site.
BuddyNext Pro joins them up. With it:
- A newly published Listora listing posts to the feed and appears in community search.
- A member’s own listings show in a Listings panel on their profile.
- A space can run an approved Businesses tab, which suits a neighbourhood space that wants to showcase its own restaurants.
- Eventonomy events and “going” RSVPs appear in the feed, in search and on a space’s own Events tab, with a List or Calendar view.
That surfacing needs BuddyNext Pro; without it the plugins still run, they just do not show up inside the community. Create one BuddyNext space per neighbourhood or per cuisine and give each a category, so a newcomer can browse by what they care about. Members’ interests are drawn from those same space categories, so someone who ticks “Ramen” at sign-up sees the ramen space and its posts ranked higher.
What is free and what needs Pro
| You want to | Free | Pro |
|---|---|---|
| Publish restaurant listings with maps | Listora, Leaflet maps | Google Maps and clustering |
| Let diners review and owners reply | Yes | Multi-criteria and photo reviews |
| Let owners claim a listing | Yes, admin approves | Verification badge you assign |
| Feature your picks | Admin flag | Owners pay credits to feature |
| Run tasting meetups with RSVPs and a waitlist | Eventonomy | Paid tickets, check-in, advanced recurrence |
| Show listings and events inside the community | Plugins run alongside | BuddyNext Pro does the surfacing |
A launch order for a small team
- Define your boundary: one town, one neighbourhood cluster, or one cuisine.
- Set up the Restaurant type fields and your short features list.
- Switch submissions to manual review and write your review policy.
- Add 15 to 20 listings yourself.
- Invite a small first group of reviewers and ask each to write a handful of reviews.
- Run one meetup at a place already in the guide, and ask attendees to review it afterwards.
- Open submissions more widely once the first meetups have gone well.
You can browse the full range of companion plugins on our plugins overview, compare tiers on the free vs Pro page, and see how the theme ties them together on what Reign is. If your directory idea is closer to a business network than a food guide, see our related setup for a members-only business network.
Frequently asked questions
Can restaurants pay to be listed or ranked higher?
Listora supports paid placement through Pro pricing plans and credits. Nothing forces you to use them. If you do, label paid placements clearly and keep your review scores out of the pay-to-play system so readers know the ratings reflect diners.
Do I need Pro to show a map?
No. The free plugin includes Leaflet maps with a Near Me button. Pro adds Google Maps and marker clustering.
Can members review a restaurant more than once?
Each member can leave one review per listing. They can edit or delete it, which avoids duplicate reviews inflating a score.
How do I stop a restaurant owner writing fake reviews of their own place?
Listora cannot tell who is who behind an account. Require a minimum review length, hold reviews for approval while the site is young, use the report button, and watch for reviews that cluster around one listing. Our guide on local business directory SEO covers review hygiene too.
Can people book a table through the site?
Not through the guide itself. The Restaurant type has a Reservations field and a menu link, so a listing can tell diners how to book, but bookings happen with the restaurant. Eventonomy RSVPs are for your own meetups.
Can I let non-members RSVP to a tasting?
Yes. Eventonomy can accept guest RSVPs with a name and email and sends a magic link to view or cancel. Choose Must log in instead if you want every RSVP tied to a member.