Yes. Use the REST API source to consume their public JSON endpoint and filter by sponsor, condition, or NCT ID. Map fields like NCT ID, condition, phase, recruitment status, and locations to the base page. Many sponsors mirror their own registry data through ClinicalTrials.gov rather than maintain a parallel feed.

Each source has a configurable cache duration. Set it to match how often your registry export runs, typically daily or twice daily. Flush manually when a recruitment status changes mid-cycle. For high-volume sponsor sites, a 6 to 12 hour cache balances freshness against load on the source.

Approved language lives in your data source, where the trial team controls it. SleekRank just renders it, so the page reflects whatever your clinical operations team has signed off on. This is the safest model from a compliance perspective: there is no separate marketing copy that can drift from the protocol or registry submission.

Yes, two ways. Filter by status in the source feed so only active trials reach SleekRank. Or use a status column with selector mappings to swap recruiting copy out and remove pages from the sitemap when trials close. The page can either disappear or stay as a historical record without calling for new participants.

Yes. Use list mappings to render inclusion and exclusion criteria as repeated list items from arrays in your data. Most CTMS systems already store eligibility as structured criteria, so the data is ready. The same pattern works for primary and secondary endpoints, which also tend to be array-shaped.

Expose CTMS data as JSON via your existing integration layer or middleware, then point a SleekRank source at that endpoint. Salesforce, Veeva CTMS, and Medidata all support REST exports through their standard APIs. The middleware step is usually where you handle authentication and field mapping, leaving SleekRank to consume a clean feed.

Update the source data when the amendment lands. If eligibility tightens or sites change, those changes flow to the page on the next cache cycle. For amendments that change the trial substantively, force a cache flush so the public page reflects the new protocol within minutes rather than waiting for the standard refresh.

Yes. Add MedicalStudy or MedicalTrial JSON-LD to the base template with mappings for studyDesign, healthCondition, sponsor, and status. Each trial page validates with its own schema. Search engines treat trial pages as a specialized result type, so accurate schema can earn richer SERP treatment.