Set the cache duration to 24 hours and refresh the source sheet weekly. INELDA updates the certification database continuously as doulas certify and renew. The live directory lags the canonical source by at most one cache cycle and new INELDA-certified doulas appear within seven days of being added to the official roster.

Yes. Configure a filter on the data source that includes only rows where credential_tier equals INELDA-certified. Alternatively, run two page groups against the same sheet, one for certified at the main pattern and one for proficient at a dedicated pattern, each with its own canonical URL.

Add an immediate_vigil column with a boolean value indicating whether the doula can respond to active dying situations within 48 hours. A conditional selector mapping renders a labeled badge on these doulas, and a secondary page group filters to immediate availability for urgent referrals.

Funeralocity and similar platforms focus on funeral homes and cremation services, not end-of-life doulas. SleekRank uses the INELDA roster as the source, so the credential displayed is the credential INELDA recognizes. The URL stays on a domain controlled by INELDA or its delegated partner.

Yes. Add a hospice_affiliations column referencing hospice agencies the doula partners with. A list mapping renders the affiliations as a labeled block, and the Person JSON-LD includes an affiliation property. Hospice case managers can verify partnership before sharing the doula's page with a family.

No. End-of-life doula schema uses standard Person markup with knowsAbout fields like end-of-life care, vigil sitting, legacy work, and family meeting facilitation. Google indexes the content as professional services. Sensitive topic flags are not triggered because the content is informational, not promotional or distressing.

Yes. Add a price_range column for full-package pricing (typically $500 to $3,000 for a complete vigil arrangement, plus hourly rates for planning sessions). A meta mapping injects priceRange into the Person JSON-LD and a selector mapping shows it on the visible page when set.

Configure the data source as a partner-mirrored sheet that INELDA maintains itself or grants access to. The directory becomes an extension of INELDA's outreach rather than a third-party scrape. The credential stays verifiable through the canonical roster and INELDA retains editorial control over the data layer.