SleekView for GeoDirectory: listings as tables
GeoDirectory stores listings in dedicated database tables with rich location and category fields. SleekView reads those rows and renders a real admin grid for directory operators managing thousands of entries.
♾️ Lifetime License available
Every listing in one filterable grid
GeoDirectory does not lean on standard postmeta for performance reasons. Each registered listing CPT gets its own detail table, like wp_geodir_gd_place_detail, with columns for city, region, country, latitude, longitude, rating, claim status, and any custom field you defined. That schema is what makes GeoDirectory fast on a fifty-thousand-listing directory, but the default admin still mixes generic post fields with directory data.
SleekView queries those detail tables directly. City, category, rating, featured flag, claim status, and any custom listing field become columns or filters. Operators get one cross-listing grid with the inline edits they actually need, and the queries hit the same indexed columns GeoDirectory uses on the front end, so even a large directory stays responsive.
Inline edits write back through GeoDirectory's normal save paths. Front-end map markers, category archives, and search results refresh exactly as they do when you edit through the plugin's own screens. SleekView is admin-only and never touches the front end.
Workflow
From per-CPT detail tables to one operator grid
Pick the listing CPT
Add the columns operators need
Build saved views
Bulk approve and feature
Sample columns
A typical GeoDirectory listings view
wp_geodir_gd_place_detail (and per-CPT detail tables)
| Listing | Category | City | Rating | Featured | Status |
|---|---|---|---|---|---|
| Mama's Kitchen | Restaurant | Brooklyn | 4.6 | Yes | Published |
| Northside Plumbing | Services | Chicago | 4.1 | No | Pending |
| Hilltop Hostel | Lodging | Lisbon | 4.8 | Yes | Published |
| Closed Diner | Restaurant | Austin | 3.2 | No | Trash |
Comparison
Default GeoDirectory admin vs SleekView
Default GeoDirectory admin
- Default list mixes generic post fields with directory data
- Cannot edit city, category, or rating from the list
- No saved views per directory or city
- Filtering by custom listing fields needs URL hacks
- Featured and claimed status hidden behind tabs
SleekView
- Configurable columns reading from per-CPT detail tables
- Inline edits for city, category, and featured flag
- Save views per directory, city, or category
- Filter by rating, claim status, or expiry
- Bulk approve or feature listings during launches
Features
What SleekView gives you for GeoDirectory
Listings by city
Group and filter listings by city, region, or country to keep local directories tidy. Save city-specific views per operator and surface counts at a glance.
Filter by category
Surface only restaurants, services, or lodging when working on one segment. Combine category with claim status or rating to find exactly what needs attention.
Edit details inline
Fix typos, swap categories, or feature a listing without opening each record. Inline edits write back through GeoDirectory's save paths so the front end refreshes.
Audience
Who uses SleekView for GeoDirectory
Directory operators
Manage thousands of listings across cities and categories from a single grid. Filter by city, sort by rating, and edit featured flags without ever opening a record.
Sales teams
See which listings are featured, expired, or due for renewal in one view. Sort by expiry to drive renewal calls and bulk feature listings during paid campaigns.
Moderators
Approve, edit, or trash listings with bulk actions during launches. Filter pending submissions, audit claim requests, and clean the directory in one sitting.
The bigger picture
Why directory operators outgrow the default admin
GeoDirectory was built to scale, but the WordPress admin was not. A small directory survives the default list view fine. The moment you cross a few hundred listings spread across cities and categories, the experience falls apart.
Operators end up writing URL hacks to filter by city, opening every record to fix a typo, and missing expired listings because there is no global view of what is live versus stale. Sales teams cannot see at a glance which listings are featured this month and which are due for renewal, even though that data sits right there in the gd_place_detail table. Moderators cannot bulk approve a batch of submissions during a launch event because the default screens only let them do it one record at a time.
SleekView gives operators a working surface over data that already exists. It does not change how GeoDirectory stores listings, how the front-end map renders, or how location search resolves a query. It just makes the admin match the scale GeoDirectory was designed for.
Questions
Common questions about SleekView for GeoDirectory
Yes. The per-CPT detail tables, like wp_geodir_gd_place_detail, are queried directly. That means the grid is fast on large directories and operators can sort or filter on any indexed column without going through postmeta workarounds. Custom CPTs registered through GeoDirectory get the same treatment.
Yes. Any custom field defined in GeoDirectory, whether a text input, dropdown, multi-checkbox, or file upload, becomes a column or filter. Cuisine types, service areas, payment options, and bookable hours all become first-class operator data instead of hidden record details.
Yes. SleekView is admin-only and does not touch the front end at all. The leaflet map, the radius search, the category archives, and the listing detail pages all keep working exactly as configured. Inline edits write back through GeoDirectory's normal save paths so the front end stays in sync.
Yes. Select rows and apply a featured flag or claim status to all selected listings at once. Useful during paid campaigns when you need to feature thirty restaurants for a city food week, or during cleanup when you need to unfeature dozens of expired listings.
Yes. Each registered listing CPT, like Places, Events, or a custom Service Providers directory, gets its own dedicated view with the columns and filters that match its schema. Operators running a multi-CPT directory site can switch between views without remapping anything.
Yes. Filtered views export to CSV with all selected columns. Useful for delivering a list of expiring renewals to the sales team, sharing approved listings with a partner network, or backing up a category before a bulk update.
Claim status is stored on the detail table and SleekView exposes it as a column and filter. Build a view of pending claim requests, see who claimed what and when, and bulk approve or reject claims after verification. Front-end claim notifications still fire through GeoDirectory's hooks.
Yes. Expiry is a column and filter on every listing view. Save a view for Expiring next 14 days, sort by expiry date, and hand the list to your sales team for renewal outreach. You can also bulk extend expiry on a batch of listings during a paid promotion.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout