← All posts

How to Let Business Owners Claim Listings in Your Directory

How claimable listings work in Listora: what an owner submits, what you review, what changes on approval, and how to undo a wrong call.

A directory built from imported or seeded data starts to go stale the day it launches. Phone numbers change, shops move, a cafe closes and its listing carries on. The people who know are the owners, and the easiest way to get them to fix things is to let them take the listing over.

That is what a claim does. This post walks through the whole flow in Listora, from the button a visitor clicks to what changes when you approve, so you can decide how strictly to run it.

What you switch on

Business Claims is one of the plugin’s feature toggles, and it is on by default. It is part of the free plugin. When it is off, the claim button disappears and the claim endpoint refuses requests, so there is no half-working state to worry about.

Claims apply to listings that already exist and have not been claimed. They are the second half of a directory strategy that starts with seeding: you import the first batch, and owners adopt their entries afterwards.

What a visitor sees

On a listing that has not been claimed, there is a Claim button next to Save and Share. A visitor who is not logged in gets the login prompt first, so every claim comes from a real account.

The claim form is short. It opens with “Claim This Business” and asks for two things:

  • Proof of Ownership, a required text box where the claimant explains how they are connected to the business, for example that they own it or manage the location.
  • An optional proof document, such as a business license or a utility bill. It can be a JPEG, PNG, GIF, WebP or PDF, up to 5 MB, and it is kept as a private attachment.

The button does not appear on a listing that is already claimed, and the owner of a listing cannot claim it again.

A few rules stop the obvious abuse. A member can have only one pending claim per listing. A listing that is already claimed cannot be claimed again. And claim submissions are rate limited per visitor, so a script cannot flood you.

What you review

When a claim arrives, an email goes to your site’s admin address, unless you have switched that notification off. The claims themselves are reviewed on a Claims screen under the Listora menu, available to administrators and to anyone you have given the claims capability.

Each claim has a status: pending, approved or rejected. You open it, read the explanation, look at the proof document if there is one, and decide.

One practical point: the form has no separate fields for a phone number or a business email. The claimant’s own account email is on file, but if you want a number to call, tell claimants to put it in the proof text. A line in your site’s claim instructions that says “include a phone number or company email we can check” does the job.

What approval does

Approving a claim does four things at once:

  • The listing’s author becomes the claimant, so they can edit it from their account.
  • The listing is marked as claimed, and the search index is updated to match.
  • The previous author is remembered, which matters for the undo below.
  • Any other pending claims on the same listing are rejected automatically, with a note saying another claim was approved.

The claimant gets an email telling them the claim was approved, with a link to edit the listing. A claim that gets rejected sends a “not approved” email, and whatever note you wrote is included, so the owner knows what to fix. If you leave the note empty, the email says no additional details were provided, so it is worth writing one.

The claimant also sees their claims under a My Claims tab on their dashboard, so they are not left wondering.

Undoing a mistake

Approving the wrong person is the mistake that matters, and it can be reversed. Change an approved claim to another status and the listing goes back: ownership returns to the previous author, and the claimed flag is cleared and the search index updated to match. The claimant then gets the not-approved email.

That safety net is a good reason to approve promptly and correct later, rather than leaving owners waiting.

Claimed is not the same as Verified

This is the distinction people trip over. A claim transfers ownership. It does not mark the listing Verified.

Verified is a separate flag, and managing it is a Pro feature. With Pro, the listing edit screen has a verification box where you set it yourself, and a badge then appears on cards and detail pages. Pro also adds a verified-only search filter and an is_verified value in the API. The same box shows whether a listing is claimed, so you can see both states together.

That separation is useful. You can approve a claim quickly to hand the listing to its owner, and award the Verified badge only once you have checked their proof properly.

When two people claim the same listing

It happens, especially with businesses that have more than one manager. Each person can submit their own claim, and the claims wait side by side. You review them one at a time. When you approve one, the plugin rejects the others on that listing automatically and notes why, so you never end up with two owners. Anyone whose claim is rejected gets the not-approved email, which is a good place to explain what to do if they believe the decision is wrong.

A sensible way to run it

Review claims by hand. There is no setting that approves claims automatically, which is the right default for a directory where a claim hands someone control of a business’s public page.

A few habits keep it easy:

  • Compare the proof to something public, such as the business website or a registry entry.
  • Check that the claimant’s email domain matches the business website where there is one.
  • Reject with a clear reason, because the note travels to the claimant. It is also stored with the claim, so it doubles as your record if the same person claims again.
  • Look at pending claims on a schedule, since they do not expire. Write the note as you would to a customer, because that is what it is.

After a claimant submits, they see a message saying the claim is under review, and then nothing until you decide. A line on your site saying how long you usually take to review saves you a stream of follow-up emails, and tells owners their claim was not lost.

Writing claim instructions

The form has one free-text box, so the quality of your claims depends on what you ask for. Put a short note near your claim policy, or on the page where you explain how your directory works, listing what a good claim contains: the claimant’s role, a business email or phone number you can check, a link to a public page that shows their connection to the business, and a document if they have one. Claimants who know what you want send claims you can approve in a minute.

A sample you can adapt: “To claim this business, tell us your role, include a business email or phone number we can check, and attach a document such as a business license or utility bill (JPEG, PNG or PDF, up to 5 MB). We review every claim by hand and reply within a few working days.” Change the last sentence to the promise you can actually keep, and then keep it.

Claims and privacy

Claims hold personal information, including the claimant’s account details and any document they upload. Listora registers claims with the WordPress privacy tools, alongside listings, reviews and favorites, so the standard personal data export and erase requests cover them. The proof documents are kept as private attachments, not in the public media library. Say in your privacy policy that you keep claim proof, and for how long.

For developers

Claims fire hooks you can use, so you can add your own checks and alerts without touching the plugin:

  • Before a claim is accepted: filter wb_listora_before_submit_claim and return an error to refuse it.
  • After submission: wb_listora_claim_submitted and wb_listora_after_submit_claim fire.
  • On approval: wb_listora_claim_approved and wb_listora_listing_claimed fire.
  • On rejection: wb_listora_claim_rejected fires.
  • The response sent to the claimant: filter wb_listora_rest_prepare_claim to change it.

That is enough for a Slack alert, a CRM record or an extra verification step.

Why it is worth the effort

Owners who claim a listing tend to keep it accurate, add photos and answer reviews, which is work you would otherwise do yourself or leave undone. A claim is also a clear signal that a person cares about their listing, which makes them the natural first audience for a paid plan once you add one.

If you are still seeding the directory, getting your first listings covers the import side. How directory websites make money covers what to do with owners once they have claimed, and Free vs Pro shows exactly what needs Pro. The features page lists the rest.