Yes. The base page renders a screening-application form via your existing tool, and SleekRank passes the retreat slug through hidden fields so applications land tagged to the right cohort. SleekRank does not process screening or store medical history, so use a tool appropriate to your jurisdiction's privacy rules for the actual intake step.

Lineage detail lives on the source row and is rendered through tag and selector mappings in the base page. When a center updates its lineage description or adds a new lead facilitator from a specific tradition, the source edit propagates to every relevant URL on the next cache cycle, keeping copy consistent across the catalog.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel for dynamic retreat cards combining lineage, ceremony count, and venue photo. The Open Graph card matters when retreat URLs get shared in integration communities, podcast notes, and journalist features where the preview drives the click.

No. SleekRank renders pages and does not process payments. Use your existing booking platform or Stripe checkout embedded after the screening step in the base page, and pass the retreat slug through hidden form fields so deposits land tagged to the right cohort without manual matching from the center team.

Yes. Add ceremony-schedule and integration-support array columns with day, activity, and notes, then surface them through list mappings in the base page. Visitors see exactly how many ceremonies, when they happen, and what integration support looks like before they apply, which improves the fit of the cohort that does end up being accepted.

Add a jurisdiction column with values like Peru, Brazil, Netherlands, or other, and a legality-note column. Surface them through tag and selector mappings in the base page so buyers see the legal context before they commit. For legal jurisdictions like the Netherlands, surface the legal-framework note prominently; for traditional jurisdictions like Peru, surface the cultural-respect framing instead.

Yes. Add a lineage column with values like shipibo, santo-daime, or independent, and reference it in the urlPattern as /retreats/ayahuasca/{lineage}/{slug}/. Or run a parallel page group per lineage if the layouts need to differ between, say, traditional Amazonian programs and Western-led integration-heavy retreats.

Add columns for prep-window length, diet restrictions, and pre-retreat coaching availability. Surface them through selector and list mappings in the base page so buyers see exactly what prep looks like before they commit, which differentiates rigorous programs from short brochure-style offerings and reduces the gap between expectation and actual cohort experience.