✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekRank for hospice nurse directories

Pull the HPNA CHPN roster of around 3,000 certified hospice and palliative care nurses into a Google Sheet, wire SleekRank to it, and emit a URL like /hospice-nurse/{slug}/ per row with credential, region, and care setting baked in.

€50 off for the first 100 lifetime licenses!

SleekRank for Hospice nurses

Why a CHPN nurse roster needs one URL per clinician

The Hospice and Palliative Nurses Association, HPNA, certifies around 3,000 CHPN, CHPPN, and ACHPN nurses through its credentialing arm. The HPCC find-a-nurse tool sits behind a single filterable widget, which Google indexes once as a wrapper. Searches like "CHPN nurse Portland" or "palliative care RN Chicago" land on that wrapper and the family bounces back to Vitas, Care.com, or LinkedIn instead of an HPNA-owned page.

SleekRank turns the same roster into around 3,000 indexable WordPress pages. Export the HPCC directory to a Google Sheet with columns for slug, name, credential, city, state, care_setting, and year_certified.

Mappings carry the data into the layout. A tag mapping pushes name into the H1 and title, a selector mapping drops the credential into a labeled badge, a list mapping renders care setting chips like home hospice, inpatient unit, pediatric, and a meta mapping builds the OG image from slug. The sitemap auto-includes every URL so search engines see 3,000 distinct nurse records inside one crawl budget.

Workflow

From HPCC roster CSV to live hospice directory

1

Export the HPCC CHPN roster

Download the HPCC find-a-nurse export or pull from a private API mirror that the HPNA maintains. Confirm the columns include name, credential, city, state, care setting, year certified.
2

Design the nurse base page

Build one WordPress page in your existing theme with hero, bio, credential badge, care setting chips, contact card, and a hidden JSON-LD Person block. Mark the selectors you want SleekRank to target with stable IDs.
3

Wire mappings to columns

Map name to H1 and title via tag mappings, credential to #credential-badge via a selector mapping, care_setting to #setting-list via a list mapping. The base template stays the existing design.
4

Publish and flush rewrites

Save the page group, flush rewrites once, and watch the sitemap fill with around 3,000 URLs. Submit the new sitemap to Search Console. Future updates to the CSV propagate on the next cache cycle.

Data in, pages out

From HPNA roster sheet to one URL per nurse

Each row in the HPCC CHPN export becomes one WordPress page at /hospice-nurse/{slug}/. Columns flow into headline, credential badge, setting chips, and OG image.
Data source: HPCC CHPN nurse roster
slug name credential city care_setting
karen-bell-portland Karen Bell, RN CHPN Portland, OR Home hospice
diane-kim-chicago Diane Kim, RN ACHPN Chicago, IL Inpatient unit
marcus-young-tampa Marcus Young, RN CHPN Tampa, FL Long-term care
leah-okafor-houston Leah Okafor, RN CHPPN Houston, TX Pediatric
joel-tanaka-phoenix Joel Tanaka, RN CHPN Phoenix, AZ Hospital consult
URL pattern: /hospice-nurse/{slug}/
Generated pages
  • /hospice-nurse/karen-bell-portland/
  • /hospice-nurse/diane-kim-chicago/
  • /hospice-nurse/marcus-young-tampa/
  • /hospice-nurse/leah-okafor-houston/
  • /hospice-nurse/joel-tanaka-phoenix/

Comparison

HPCC find a nurse widget vs SleekRank

JS-rendered finder widget

  • Single JavaScript filter that Google indexes once, with no per-nurse URL anywhere
  • No structured Person schema, no city pages, no care setting pages for pediatric
  • Family referrals leak to Vitas and Care.com because those platforms own nurse URLs
  • Updates push to a JSON endpoint but never produce indexable HTML pages on HPCC
  • Nurses cannot link to a canonical CHPN-credentialed profile that they actually control
  • No sitemap inclusion, no canonical tags, no per-row OG image for any nurse profile

SleekRank

  • 3,000 CHPN, CHPPN, and ACHPN pages from one HPCC roster CSV export per refresh
  • URL pattern /hospice-nurse/{slug}/ with WordPress canonicals per row
  • Tag mappings for H1 and title, selector mappings for credential and city
  • List mappings render home hospice, inpatient, pediatric, and consult chips
  • Per-row OG image built from slug via meta mapping for social shares
  • Sitemap auto-includes every URL, schema.org Person markup per nurse page render

Features

What SleekRank gives you for Hospice nurses

Credential-aware badges

Selector mappings branch on the credential column to swap the badge label and color. CHPN gets teal, ACHPN gets navy for advanced practice, CHPPN gets soft purple for pediatric. One template, three visual states, driven by the data row.

Google Sheet or REST source

Export the HPCC roster to a Google Sheet weekly, or pull from a private REST endpoint that mirrors the official find-a-nurse data. Both work as live data sources. Cache for 24 hours and the entire site refreshes overnight.

Schema.org Person per row

A meta mapping injects JSON-LD Person markup for every nurse with name, credential, address, and contact point. Google's rich-result tester sees a structured hospice and palliative care provider record instead of a generic page.

Use cases

Where a CHPN nurse roster surface earns its keep

Long-tail city care searches

Queries like "CHPN nurse Portland" or "pediatric palliative nurse Houston" land on a nurse page with intake link and phone number, instead of a wrapper widget. Family conversion rises.

Credential verification pages

Each generated URL serves as canonical proof that a nurse holds CHPN, ACHPN, or CHPPN certification. Nurses can link to it from their employer site.

City and care setting hubs

A second page group keyed to the city column emits /hospice-nurse/city/{slug}/ for every metro with at least three CHPN nurses. A third keyed to setting emits /hospice-nurse/setting/{slug}/ for home hospice, inpatient.

The bigger picture

Why CHPN nurse pages deserve indexable URLs

End-of-life referrals almost always travel by name. A hospitalist mentions a nurse, a hospice social worker recommends a clinician, a discharge planner cites a team. The family then types the name into Google.

If the only HPCC result is a JavaScript filter that needs a state dropdown, the family bounces to Vitas, Care.com, or LinkedIn. The CHPN credential that makes the nurse distinctive vanishes in transit. Every CHPN, ACHPN, and CHPPN certified nurse deserves a canonical URL on the body that certified them, with the credential badge front and center and the care setting spelled out.

SleekRank makes that surface cheap to maintain because the HPCC roster already lives in a spreadsheet. One export, one cache cycle, around 3,000 indexable pages. Adding a new certification cohort each year becomes 300 new rows in the sheet rather than 300 manually built pages.

The credentialing body becomes the source of the lead and the citation.

Questions

Common questions about SleekRank for Hospice nurses

Set the cache duration on the data source to 24 hours and refresh the source CSV weekly from the HPCC roster export. SleekRank reads the current sheet on the next cache cycle and dropped rows return 404 cleanly. The XML sitemap regenerates so Google drops removed nurses within one crawl pass.

 

Yes. Add a conditional selector mapping that targets the credential badge and a separate list mapping that renders prescriptive authority blocks only when the credential column is ACHPN. The same base page renders three credential variants without three hand-built templates or duplicated copy.

 

Remove the row from the source sheet. On the next cache cycle the URL returns 404 and the sitemap regenerates. If the nurse wants a redirect to an employer page instead, point the slug at a redirect rule in your normal WordPress redirects plugin before deleting the row from the sheet.

 

Yes, given the pages carry per-row specifics. Each nurse has a unique name, city, credential, and care setting combination, which signals to Google that the page is not boilerplate. Submitting the sitemap in Search Console accelerates the first crawl pass and full coverage lands within three weeks.

 

Vitas and Care.com own the URL, layout, sidebar ads, and lead form. A SleekRank page sits on the HPNA domain or your own site, uses your branding, captures the inquiry directly, and links out only to verified CHPN-credentialed peers. The nurse controls the canonical record openly.

 

Yes. Add an employer_url and a contact_phone column to the sheet, plus a calendar_embed for nurses in private practice. A selector mapping injects the contact card on each nurse page. Rows with empty values fall back to a generic HPCC contact card with no scheduling embed at all.

 

Most HPCC certifications are US-based, but Canada has crossover. Add country and locale columns to the sheet. A second page group with pattern /hospice-nurse/country/{slug}/ emits one URL per country. The base template references locale for date and phone formatting so non-US pages render properly.

 

Yes, as long as the source data carries those fields. HPCC tracks the year of certification and many nurses list their preceptor through the HPNA mentorship registry. A list mapping renders a small training history block on each nurse page, which helps families recognize an institution they know.

 

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.

Starter

€99

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€179

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Launch Offer

€299

€249

EUR

once

Get started

further 30% launch-discount applied during checkout for existing customers.

  • 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