It's a plugin, not a theme, and that's a deliberate choice. Most "medical directory" products are WordPress themes or theme add-ons that take over your whole site's design, so you're locked into their template. WP Medical Directory installs alongside your existing theme and adds the four directory content types, medical schema, and patient search without touching your site's look. You keep the theme you already have, and if you ever deactivate the plugin, your pages and design don't collapse into a broken template. For agencies, that means no client-facing lock-in.

WP Medical Directory is built by I Need Leads LLC. Our founder spent more than ten years in healthcare SEO and database management, the two disciplines a provider directory really comes down to: how patients find your providers, and how provider data stays accurate and clean. We built the plugin around both, specifically for the healthcare vertical, rather than bending a general business-directory tool into a medical shape. It's a maintained, funded product with ongoing updates, not a template that shipped once and went quiet.

The biggest difference is the model. Themes like Listeo, Doctreat, and MedicalProWP are built to help you launch a marketplace, with paid listing plans, appointment wallets, and payment gateways so the site owner earns commission. WP Medical Directory does none of that. It's a plugin for an organization or its agency to publish and maintain its own providers, with federal NPI data, WCAG 2.1 AA accessibility, and AI-search schema as the priorities. There's no theme dependency to buy on top, no owner-side monetization layer, and nothing patients log into. If you want a marketplace to monetize, another tool fits better; if you want an accurate, accessible directory you own, this is built for it.

WP Medical Directory gives you four healthcare-native content types you can mix to match your organization: Brand, Location, Provider, and Insurance Plan. Use only what you need. A solo practice might use just Provider; a multi-location practice uses Location and Brand; a full health system or association uses all four. Provider records carry around 37 fields across nine sections (credentials, NPI, specialty taxonomy, languages, and more), and Location records carry 40 fields across twelve sections (address, hours, accessibility, accepted insurance). The plugin links them into a connected graph, providers to the locations where they work and locations to their parent brand, so your directory reflects how your organization is actually structured.

Yes. Patients can search your directory in plain language, something like "spanish speaking pediatrician near corona", instead of guessing your categories, using natural-language search built on WordPress's native AI. They can also filter by specialty, accepted insurance plan, telehealth availability, and location with distance/radius search, plus an A to Z browse. Each provider and location profile is a structured, accessible page, so the same data that powers on-site search also feeds Google and AI assistants. The goal is simple: a patient, or a referring physician, finds the right provider quickly, whether they search on your site or ask an AI tool.

Yes. You can pull provider records straight from the federal NPPES registry by NPI number, legal name, credentials, and specialty taxonomy, right on the Provider edit screen or in bulk during a CSV import. That means you stop retyping data the government already publishes. The plugin can also run a routine check that flags when a listing has drifted out of date, and it can compare each Location's name, address, and phone against your Google Business Profile on a weekly schedule and surface any mismatches. Accurate provider data is half of what a good directory is for, so we pull it from the authoritative source.

Yes, there's a native appointment request form you can configure per location, and no, it deliberately doesn't collect health information. It captures only what's needed to route a request: name, phone, email, preferred contact method, preferred dates and time of day, insurance plan, and whether the patient is new or existing. Every form tells patients not to include any health details, and leads are stored in the plugin's own table. It ships with baseline anti-spam (a honeypot field, a timing check, and input sanitization) and a hook where your site can add reCAPTCHA or hCaptcha. Keeping health information off the form is one of the ways the directory stays out of HIPAA scope.

Yes, accuracy is built into the workflow, not left to manual upkeep. You can refresh any Provider record against the federal NPPES registry by NPI, so credentials and specialty taxonomy stay current, and a routine check flags listings that look out of date. For locations, a weekly background job compares each Location's name, address, and phone against your stored Google Business Profile and raises an admin notice when something doesn't match. When you rename or remove an entity, the plugin registers the right redirect (301 to the parent, or 410 for gone) through its own redirect table, so search engines and patients don't hit dead links. Your directory stays trustworthy as your organization changes.

You do. WP Medical Directory is a plugin on your own WordPress site, so your Brand, Location, Provider, and Insurance Plan records live in your database, not on someone else's SaaS platform. If you deactivate the plugin, your content isn't touched. If you fully uninstall it, the plugin cleans up its own options and tables but does not delete your directory posts; they stay in the database and come back if you reinstall. If you actually want them removed, you delete the posts first or use the plugin's delete tool. Owning your infrastructure is the point: no vendor holds your provider data hostage.

No. WP Medical Directory is public-facing by design, with no patient logins, no patient accounts, and no per-patient stored records. It's a directory that helps people find and contact your providers; it is not a patient portal, an EHR, or a booking system with patient sign-ins. That's a deliberate architectural choice: by never creating patient accounts or holding patient health information, the directory stays out of HIPAA scope, which keeps your compliance surface small. Patients search, view a provider or location profile, and submit a simple appointment request, nothing they need an account for.

WP Medical Directory requires WordPress 6.9.4 or newer and PHP 8.2 or newer. You may see an older note saying it needs WordPress 7.0, that's out of date. Here's the accurate picture: the plugin's AI features use the Abilities API, which shipped in WordPress 6.9. On WordPress 7.0 and up, those features run through the native WP AI Client via Connectors (fully provider-agnostic); on WordPress 6.9, they use a built-in Anthropic adapter instead. Either way you get the AI features, and all of them have manual fallbacks if you don't configure an AI provider at all. Check your versions under Tools then Site Health before installing.

Yes. WP Medical Directory ships a CSV importer for Brands, Locations, Providers, and Insurance Plans, and it comes with a ready-made import template so your columns line up. When you upload your file, the plugin's AI suggests how your columns map to directory fields; you review and override anything, then see a validation preview before a single record is committed. You can also enrich providers from the federal NPPES registry at import time, so records arrive with verified credentials and taxonomy. For a practice moving off a spreadsheet or another system, this turns hours of manual entry into a reviewed, one-pass import.

Yes. Because it's a plugin rather than a theme, WP Medical Directory works with the theme you already run; it adds the directory content types, patient search, and medical schema without replacing your site's design. You're not handing your organization, or your client, a locked-in template, and you're not maintaining a separate directory theme alongside your main site. That's a real difference from most "medical directory" products, which are themes you'd have to adopt wholesale. If your team builds with a page builder, your directory pages live on your own site and inherit your existing styling.

Setup takes minutes: the five-step wizard gets your directory's shape and connections in place. Populating it usually takes hours rather than weeks, because provider records pull from the federal NPI registry by number and existing lists import from a spreadsheet with AI-assisted column mapping and a validation preview. Structured data and WCAG 2.1 AA accessibility apply the moment a page publishes, so there's nothing extra to wire up. Being surfaced in Google and AI answers then follows the normal indexing timeline for your site. The plugin's job is to give you a complete, accurate, accessible directory fast; how quickly search picks it up depends on your site as a whole.

WP Medical Directory uses WordPress's native AI, so you don't manage any third-party API keys and you're not locked to one AI vendor. The built-in AI features help you draft and improve Brand, Location, and Provider bios, generate specialty FAQ content, classify how entities relate to each other, map spreadsheet columns during import, and power natural-language patient search. On WordPress 7.0 and up these run through the WP AI Client and your configured Connector; on WordPress 6.9 they use a built-in Anthropic adapter. All of it is optional: every AI feature has a manual path, so you can run the whole directory without AI if you prefer.

Completely. Every AI feature in WP Medical Directory is an enhancement with a manual fallback, and the plugin gracefully degrades when no AI provider is configured in WordPress's Connectors. You can write bios yourself, map your own import columns, and use standard filtered search instead of natural-language search. All the core directory functionality, the four content types, federal NPI enrichment, WCAG 2.1 AA pages, medical schema, and the appointment form, works with no AI at all. AI is there to save you time, not to gate the product behind an AI account.

Yes, this is one of the things that makes WP Medical Directory unusual. Every meaningful operation is exposed as a callable ability through the WordPress Abilities API, 28 of them, covering creating and updating all four content types, pulling NPI records, linking providers to locations, validating the entity graph, running a CSV import, and more. Because they're exposed over the Model Context Protocol, AI agents like Claude Desktop and Claude in Chrome can discover and run them directly. In practice, an agent can stand up and maintain a whole directory with no custom code and no admin screens to learn. It's built for people who work with agents, not just clicks.

Every entity page emits Schema.org JSON-LD tuned for how Google and AI tools like Perplexity, ChatGPT, and Google AI Overviews actually read healthcare information. Providers carry their NPI and a worksFor link to their locations; locations list their providers and their accepted insurance; brands enumerate their locations, and each relationship is declared in both directions. Google reads those bidirectional declarations as confirmed connections rather than one-sided claims, which is exactly what a plain list of names can't offer. Pages also use stable @id references and emit FAQ schema where relevant. The result is a directory machines can resolve into facts about your organization, not just text they have to guess at.

Yes. You can run the complete plugin, every feature and no limitations, free for 14 days, and you don't need to enter a credit card to start. That's enough time to run the setup wizard, pull a few providers from the federal NPI registry, import a spreadsheet, and see how your directory looks and performs on your own site with your own theme. If you decide to buy and then change your mind, there's also a 14-day money-back guarantee on top of the trial. We'd rather you confirm it fits your organization than commit blind.

Because a medical directory isn't a "ship once and forget" product. An annual license funds the work that keeps your directory trustworthy: accessibility updates as WCAG and the HHS Section 504 landscape evolve, refreshes to the federal NPPES data integration, security patches, and the AI features that ride on WordPress's own AI framework. One-time directory themes can't fund that ongoing maintenance, which is why so many of them go quiet after launch. The trade-off is deliberate: you're paying for a maintained, supported plugin that stays current with the standards a healthcare directory is actually held to, not a template frozen at its release date.

Your published directory keeps rendering. Because WP Medical Directory is a plugin on your own WordPress site, not a hosted service, the provider and location pages you've built stay live even if a license lapses, so you never end up with a broken site or a client left in the lurch. What an active license keeps flowing are the things that need ongoing support: plugin updates, security patches, and the premium data and AI features. You'd renew to keep receiving those. This is part of the own-it, don't-rent-it model: the directory is yours and stays on your infrastructure.

Licenses are sized for how you work. The single-site license ($79/year) covers one directory; the five-site license ($199/year) and the 25-site license ($499/year) are built for agencies and developers running WP Medical Directory across multiple client sites. Every tier includes the full feature set, the difference is only the number of sites, not what the plugin can do. For an agency, that means you can standardize on one purpose-built medical directory plugin across your healthcare clients instead of assembling a different stack for each build. If you're between tiers, pick the site count that matches your active projects.

Support and documentation come with your license. The plugin includes a first-run setup wizard and followable docs that walk through URL structure, connecting an AI provider, NPPES and Google Business Profile setup, importing your data, and configuring the appointment form. If you hit a wall, you can reach our team through the support channel tied to your account. Because WP Medical Directory is a maintained, funded plugin rather than a one-off theme, keeping documentation current and answering support questions is part of the product, not something that trails off after launch.