Features
WP Medical Directory Plugin Features
Four building blocks, federal data, AI-search structured data, and accessibility — everything a provider directory needs, and nothing it doesn’t.
Start your 14-day free trialEvery feature, free for 14 days. No credit card.
The building blocks
Four healthcare-native entity types
Most directory tools give you one generic “listing.” WP Medical Directory gives you four content types designed for how healthcare organizations are actually shaped — and you use only the ones you need.
Brand
The parent organization or practice group. Enumerates its locations so the graph reads top-down and bottom-up.
Location
A physical site — around 40 fields across twelve sections: address, hours, accessibility, and the insurance plans accepted there.
Provider
A physician or clinician — around 37 fields across nine sections: credentials, NPI, specialty taxonomy, and languages spoken.
Insurance Plan
The plans a location accepts, modeled as its own entity so patients can filter by coverage and machines can resolve it.
A solo practice might use only Provider. A multi-location group uses Location and Brand. A full health system or association uses all four.
Accurate by construction
Federal NPI data, not manual entry
Provider records pull straight from the federal NPPES registry by NPI number — legal name, credentials, and specialty taxonomy — one at a time or in bulk. You stop retyping data the government already publishes.
- Pull any provider by NPI on the edit screen, or enrich in bulk during import.
- A CSV importer suggests column mappings with AI while you review and override, with a validation preview before anything commits.
- A routine check flags when a listing has drifted out of date.
- A weekly job compares each location’s name, address, and phone against your Google Business Profile and surfaces mismatches.
Found by patients and machines
Structured data built for AI search
This is the part a plain list can’t do. Every entity page emits Schema.org JSON-LD with verified NPI identifiers and bidirectional relationship declarations — a brand enumerates its locations and each location names its parent; a location lists its providers and each provider declares where they work; a location declares the insurance it accepts.
Google and AI tools like Perplexity, ChatGPT, and Google AI Overviews read those two-directional declarations as confirmed connections, not one-sided claims. Pages use stable @id references and emit FAQ schema where relevant. The deeper explanation lives in The Provider Graph Method™.
Compliant on every page
WCAG 2.1 AA accessibility, out of the box
Every patient-facing template the plugin ships is built to WCAG 2.1 Level AA — semantic HTML, full keyboard navigation, proper ARIA labeling, skip links, and no screen-reader dead ends. Accessibility is emitted with the page, not bolted on later. See Compliance & Security for how this maps to the HHS Section 504 standard.
More of what’s inside
Natural-language patient search
Patients search in plain language — “spanish speaking pediatrician near me that takes my plan” — plus filters for specialty, accepted insurance, telehealth, and distance/radius, and an A–Z browse.
Appointment request form
Per-location, collecting only routing details. It tells patients not to include health information, stores leads in its own table, and ships anti-spam with a hook for reCAPTCHA or hCaptcha.
Native WordPress AI
Draft and improve bios, generate specialty FAQs, classify entity relationships, and map import columns — provider-agnostic on WordPress 7.0+, with an Anthropic adapter on 6.9. No API key you manage.
Agent automation
Every meaningful operation is exposed through the WordPress Abilities API and MCP — 28 operations — so an AI agent like Claude Desktop or Claude in Chrome can build and maintain the directory.
Own your data
A plugin, not a theme. Your records live in your database, not a vendor’s SaaS. Uninstalling cleans up the plugin’s own tables but never deletes your directory content.
Graceful by design
If a license lapses, your published directory keeps rendering. Renaming or removing an entity registers the right redirect — 301 to the parent, or 410 for gone — so patients and search never hit dead links.
Runs on current WordPress
Requirements
WP Medical Directory requires WordPress 6.9.4 or newer and PHP 8.2 or newer. The AI features use the Abilities API introduced in WordPress 6.9: on 7.0 and up they run through the native WP AI Client via Connectors; on 6.9 they use a built-in Anthropic adapter. All AI features have manual fallbacks, so nothing is gated behind an AI account.
What are the four entity types in WP Medical Directory?
WP Medical Directory gives you four healthcare-native content types: Brand, Location, Provider, and Insurance Plan. You mix only the ones you need — a solo practice may use just Provider, a multi-location group uses Location and Brand, and a full network or association uses all four. Provider records carry around 37 fields across nine sections and Location records carry 40 fields across twelve, and the plugin links them into a connected graph so your directory reflects how your organization is actually structured.
Do I need an AI API key to use the AI features?
No. WP Medical Directory uses WordPress's native AI, so you don't manage a third-party API key and you're not locked to one vendor. On WordPress 7.0 and up the AI features run through the WP AI Client and your configured Connector; on WordPress 6.9 they use a built-in Anthropic adapter. Every AI feature — provider bios, specialty FAQs, import column mapping, natural-language search — is optional and has a manual fallback, so you can run the whole directory with no AI configured at all.
What WordPress and PHP versions are required?
WP Medical Directory requires WordPress 6.9.4 or newer and PHP 8.2 or newer. An older note citing WordPress 7.0 is out of date. The AI features use the Abilities API, which shipped in WordPress 6.9: on 7.0 and up they run through the native WP AI Client via Connectors, and on 6.9 they use a built-in Anthropic adapter. Either way the AI features are available, and all of them fall back to manual paths if you never configure an AI provider.
See it on your own site first
Run every feature free for 14 days — no credit card. Pull providers from the federal NPI registry, import a spreadsheet, and watch your directory emit structured data and meet WCAG 2.1 AA on your own theme.
Start your 14-day free trialAnnual licenses from $79/year · 14-day money-back guarantee.