From empty directory to live: using demo data, listing types, and paid plans

A new directory install has the same problem as a new forum: it looks empty. Visitors land, see no listings, and leave. The conversion problem is not price or features - it is the blank-slate first impression that signals “this site is not live yet.”

Listora ships a demo seed command that loads 128+ realistic listings instantly, giving you a fully-populated directory to configure against before you invite real submitters. This post covers the full path from that seed command to a live directory accepting paid submissions.

Why start with demo data

The demo data serves two purposes:

Configuration. It is much easier to configure search facets, listing cards, and category pages when there is real data to render against. A filter that shows 0 results because there is no data looks broken even when the filter is configured correctly. The demo data lets you verify that every piece of the configuration works as intended.

Stakeholder review. If the directory is for a client or requires internal sign-off, a populated site is dramatically easier to review than a blank one. Demo data lets you show the real product before real submissions exist.

The demo data is not published to visitors - you remove it before the public launch.

Step 1 - Run the demo seed command

After installing and activating Listora, run the seed command from WP-CLI:

wp listora demo seed --pack=places

This loads 128+ city-guide-style listings with realistic names, addresses, categories, images, hours, and ratings. The command takes 30-60 seconds.

If you are building a different vertical, alternative seed packs are available:

wp listora demo seed --pack=restaurants
wp listora demo seed --pack=jobs
wp listora demo seed --pack=services

Pick the pack closest to your vertical. The seed data is tagged internally so you can remove all demo listings with a single command before launch:

wp listora demo clean

Run the seed command, then open your directory frontend. You should see a populated listing archive with working search and filters.

Step 2 - Configure your listing types

Listing types define the field schema for each category of listing. From Listora - Listing Types, review the types that the seed pack created and adjust them to match your directory’s actual needs.

For a city guide:

For each type:

1. Open the listing type configuration.
2. Review which fields are marked Required vs. Optional.
3. Add any vertical-specific fields your directory needs that are not in the defaults.
4. Verify that the fields you want to use as search facets are marked as Filterable.

The seed data populated these fields - you can see immediately whether a field renders correctly on the listing card and detail page before you ask real submitters to fill it in.

Step 3 - Verify your search facets

From the frontend archive page, test each active search filter:

• Does the category filter reduce results correctly?
• Does the geo radius filter return listings within the radius?
• Do the price band, rating, and amenity filters stack correctly?
• Does the URL state preserve when you apply a filter (so a visitor can share a filtered search)?

If a filter returns 0 results when it should return some, check that the field it filters on is marked as Filterable in the listing type configuration and that the index was rebuilt after you saved the change (admin - Listora - Tools - Rebuild Search Index).

Step 4 - Configure paid listing plans (Pro)

If you are monetizing the directory, this is where you define what submitters pay for. From Listora - Pricing Plans:

1. Click Add Plan.
2. Define the plan:
   • Name (Basic / Featured / Sponsored)
   • Duration (30 days / 60 days / 90 days)
   • Credits required (how many credits from the submitter’s balance this plan costs)
   • Visibility tier (standard placement / featured rotation / prime top slot)
   • Included features (verified badge, analytics access, lead capture - Pro features)
3. Repeat for each tier.

A common three-tier structure for a city guide:

Then configure credit packs (what submitters pay to buy credits):

1. Go to Listora - Credit Packs - Add Pack.
2. Example: 100 credits for $39, 250 credits for $79, 500 credits for $149.
3. Connect your payment adapter: Stripe direct, PayPal, WooCommerce, or MemberPress.

The Hold-and-Commit mechanism holds credits when a submitter starts the process and commits them only when the listing goes live. If the listing is rejected, the credits return to the submitter’s balance.

Step 5 - Test the submission-to-live flow end to end

Before removing the demo data and announcing the site:

1. Submit a test listing as a guest. Verify the email verification flow, draft auto-save, and the form UI on mobile (390px viewport - check this explicitly; the wizard should be fully functional on a phone).
2. Submit a test listing that triggers a paid plan. Verify the credit purchase flow, the credit hold during submission, and the credit commit when you approve the listing.
3. Approve the listing from the moderation queue. Verify it appears in the archive and in the correct category.
4. Reject a listing and verify the rejection email sends and credits return.
5. Submit a spam listing to verify the anti-spam layers catch it before it reaches your queue.

Run these tests on a staging copy if you have one. If not, run them on production before you send traffic.

Step 6 - Clean the demo data and launch

When your configuration is verified:

wp listora demo clean

This removes all demo-tagged listings but leaves your configuration, listing types, paid plans, and real listings intact.

After cleaning:

• Verify the archive page shows 0 listings (or any real listings you added during testing).
• Add 5-10 real listings manually to seed the directory before you invite public submissions. Even a few real listings are better than zero.
• Publish the submission form page.
• Announce.

Day-one launch checklist

• Demo data cleaned
• At least 5 real listings published
• Submission form tested end to end (guest + paid flow)
• Email verification confirmed working
• Mobile layout verified at 390px on the archive, listing detail, and submission form
• Paid plan checkout tested with a real payment
• Admin notification email confirmed for new submissions
• Search index rebuilt after any listing type changes
• Category pages verified (popular categories should show listings in the right facet groups)

What comes after launch

The first 30 days after launch are about submission volume. Two things drive it:

Manual outreach. Contact businesses or people who belong in the directory and invite them to submit. Personal invitations convert much better than a general announcement. For a city guide, call the 20 most obvious restaurants and offer to list them.

Search indexing. Each listing is a unique, indexable page. Within 2-4 weeks of launch, your directory pages start appearing in search results for “[category] in [city]” queries. This is the long-term acquisition channel - the directory’s value compounds as the listing count grows and more category pages earn rankings.

The demo-data-to-live workflow compresses what would otherwise be weeks of configuration guesswork into a few focused hours. The directory looks real from day one, the configuration is verified against real-looking data, and the launch is a clean cutover from demo to live rather than a gradual, uncertain ramp.