WordPress Medical Directory Plugin
A provider directory patients and AI search actually find — NPI-accurate, WCAG 2.1 AA, and yours to run without a developer.
It’s built on a different idea — The Provider Graph Method™ for healthcare organizations: your brands, locations, and providers linked as verified facts, pulled from the federal registry, that Google and the AI assistants patients ask first read as confirmed.
Find a provider
Product preview · sample data
You’ve priced every way to build this — and each one costs something you can’t afford.
You need a “find a provider” page patients can actually use. So you looked. A general listings plugin files your physicians next to restaurants and gyms — no specialty taxonomy, no credentials, no insurance — so patients can’t search the way they think, and Google can’t tell a doctor from a plumber.
A directory theme hits a wall on a setting you couldn’t change without code, and then the support goes quiet after a week. A custom build arrives as a quote that made you wince, plus a developer on call for every edit. And every route ends the same way: retyping data the government already has into an empty directory that’s out of date the day you finish.
Here’s the part most teams miss: a directory doesn’t fail on how the page looks. It fails on the architecture underneath it — whether provider identity is verified, whether the relationships between entities are machine-confirmed, and whether the pages meet the accessibility standard the regulators and the machines now expect.
We get it. Every option either made you wince or made you dependent on someone else.
You want to be the organization patients — and their AI assistant — reach for first. Not just a directory that exists, but the one Google and the answer engines resolve to for your specialty. Here’s the specific thing that gets you there, and no listing plugin or directory theme is built to do it:
Provider identity from the federal registry
Records pull from the federal NPPES registry by NPI — legal name, credentials, specialty taxonomy — on the edit screen or in bulk. Identity is confirmed, not typed, and a routine check flags when a listing drifts out of date.
Relationships declared both ways
The parent enumerates its children — brand → locations → providers → accepted insurance — and each child declares its parent. Google and AI search read a two-way declaration as a confirmed JOIN, not a one-sided assertion.
An AI agent can build and run it
Every operation is exposed through the WordPress Abilities API and MCP, so an AI assistant like Claude Desktop or Claude in Chrome — or your own team, no developer — can create providers, pull NPI records, and maintain the directory.
And two things that come standard, because healthcare requires them: every patient-facing page ships to WCAG 2.1 Level AA — the standard the HHS Section 504 rule sets for organizations that receive federal financial assistance through Medicare, Medicaid, or CHIP — and the whole directory stays out of HIPAA scope by design: no PHI, no patient accounts, public-facing only. See compliance & security. (Not legal advice.)
From an empty page to a directory patients and AI search find — in three steps
Start your free trial and shape the directory
Spin it up in 14 days free, no credit card. The first-run wizard commits your URL shape and switches on only the entity types you need — Brand, Location, Provider, Insurance Plan. A solo practice uses just Provider; a network uses all four.
Pull the data, link the graph, emit the schema
Auto-fill providers from the federal NPI registry, import a CSV with AI-assisted column mapping, and let the plugin link brands, locations, and providers and emit the bidirectional structured data — or hand the whole job to an AI agent over MCP.
Your providers get found — accurate and accessible
Patients search in plain language, and the AI assistants they ask first return your providers as confirmed facts. Records stay current, every page meets WCAG 2.1 AA, and your team runs it — no developer, no PHI, no HIPAA scope you didn’t ask for.
Explore
Not testimonials we wrote. Things you can verify.
This is a day-one product, so we’re not going to show you invented reviews. We’ll show you what you can check yourself before you trust a word of it.
The data source is real and federal
NPPES/NPI is the U.S. federal provider registry. The plugin pulls from it directly — you can confirm the source yourself before you type a single record.
The schema is testable
Paste any provider or location page into Google’s Rich Results Test and confirm the bidirectional JSON-LD and NPI identifiers emit. The structured data isn’t a claim — it’s inspectable.
The accessibility is auditable
Run any patient-facing template the plugin ships against WCAG 2.1 AA. The accessibility is something your auditor can test — not something we ask you to take on faith.
Built by people who’ve done this for a decade. WP Medical Directory is made by I Need Leads LLC; its founder spent 10+ years in the two disciplines a provider directory lives or dies on — healthcare SEO and provider-data management. And it stays out of HIPAA scope by design: no PHI, no patient accounts, and forms that tell patients not to share health details. (Not legal advice — your counsel knows your obligations.)
Client results will appear here once real customers consent — we don’t invent them:
Built for healthcare, and honest about what that requires
- WCAG 2.1 Level AA on every patient-facing template the plugin ships — the standard the HHS Section 504 rule sets for organizations that receive federal financial assistance through Medicare, Medicaid, or CHIP. (Not legal advice.)
- Out of HIPAA scope by design — no PHI, no patient accounts, public-facing only. Patient-facing forms tell people not to share health details.
- Four composable entity types — Brand, Location, Provider, Insurance Plan. Use any subset: a solo practice uses only Provider; a network uses all four.
- Federal NPI data (NPPES) — provider records auto-fill from the federal registry, and a weekly check flags when a listing drifts.
- 28 operations over MCP — the WordPress Abilities API exposes create, import, link, and validate to agents like Claude Desktop and Claude in Chrome.
- Requires WordPress 6.9.4+ and PHP 8.2+ — native, provider-agnostic AI via the WP AI Client on 7.0+; a built-in Anthropic adapter on 6.9.
- License lapses? The public directory keeps rendering. Admin features lock; patients still find your providers — you never leave a site broken.
Built on standards you can check
The plugin’s data and claims trace to public authorities — not to our own say-so:
Frequently asked questions about a WordPress medical directory
Is WP Medical Directory HIPAA compliant?
WP Medical Directory is deliberately scoped to operate outside the HIPAA covered-entity model. It does not collect, store, or transmit protected health information (PHI), it has no patient accounts, and its patient-facing forms explicitly tell people not to include health details. That is scope avoidance, not a HIPAA-compliance guarantee. This is not legal advice — your own counsel knows your specific obligations.
Is there a free version or a free trial?
WP Medical Directory is premium-only and is not listed on WordPress.org. There is no permanently free tier. Instead, every feature is free for a 14-day trial with no credit card required, and if you buy and it is not right, there is a 14-day money-back guarantee. Annual plans cover 1, 5, or 25 sites; see the pricing page for current details.
Does the directory meet accessibility requirements (WCAG 2.1 AA)?
Yes. Every patient-facing template WP Medical Directory ships is built to WCAG 2.1 Level AA — semantic HTML, keyboard navigation, proper ARIA, no screen-reader dead ends. That is the accessibility standard the HHS Section 504 rule sets for healthcare organizations that receive federal financial assistance through Medicare, Medicaid, or CHIP. This is not legal advice; confirm your current obligations with qualified counsel.
Where does the provider data come from?
Provider records in WP Medical Directory auto-fill from the federal NPPES registry by NPI — legal name, credentials, and specialty taxonomy — on the provider edit screen or in bulk during CSV import. A routine check flags when a listing drifts out of date. You confirm data your government already maintains instead of retyping it, so records stay accurate over time.
Do I need a developer to run it?
No. WP Medical Directory ships four structured entity types, a first-run setup wizard, and a CSV importer with AI-assisted column mapping, so marketing or web staff can run it. Every meaningful operation is also exposed through the WordPress Abilities API and MCP, so an AI agent such as Claude Desktop or Claude in Chrome can build and maintain the directory without custom code.
What WordPress version does it require?
WP Medical Directory requires WordPress 6.9.4 or higher and PHP 8.2 or higher. On WordPress 7.0 and up its AI features use the native, provider-agnostic WP AI Client through Connectors, with no third-party key management. On WordPress 6.9 it uses a built-in Anthropic adapter configured in the plugin settings. Every AI feature also has a manual fallback.
What happens to my directory if my license expires?
Your public directory keeps rendering. If a WP Medical Directory license lapses, the admin-side premium features lock, but the patient-facing directory pages continue to display, so patients still find your providers and you are never left with a broken site. That matters especially for agencies handing a finished directory to a healthcare client.
Ready to build a provider directory patients and AI search find?
Start free for 14 days — no credit card. Pull your providers from the federal registry, link the graph, and ship pages that meet WCAG 2.1 AA. If you buy and it’s not right, there’s a 14-day money-back guarantee.