The pages publish reference content sourced from a reviewed dataset. The dataset reflects the publisher's clinical review, not personalized advice. The template should include the publisher's standard disclaimer block, which is part of the WordPress page and renders on every generated URL. SleekRank only injects values from the source into matched elements; medical responsibility stays with the publisher.

Google Sheets, CSV, JSON, REST API, or a custom WordPress table. Most clinical teams keep the master record in a vetted system and export to a sheet or REST feed that SleekRank reads. The source format is independent of the rendering, so a migration from sheet to API later does not require rebuilding the pages.

Selector mapping reads the severity column and assigns a CSS class to the badge element. Style each class (Contraindicated, Major, Moderate, Minor) to match the visual signal you want. The badge stays consistent across the library because it is driven by one column, not by per-page editor choices.

Yes. Every generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new pairs get crawled within hours of cache flush. Pair queries are competitive but structured per-page content (severity, mechanism, management) signals authority that generic lookup pages cannot match.

Cache duration is configurable per source. For active dataset maintenance, set fifteen to thirty minutes; for stable references, a day or longer is fine. A manual cache flush via wp-cli makes urgent updates (a newly recognized contraindication, say) appear immediately on the next request.

Yes. Keep language-specific columns (mechanism_en, mechanism_es) or separate sources per language, and route via different URL patterns like /es/interacciones/{slug}/. Separate sources scale better for multilingual sites because translators edit each in isolation without seeing the others. WPML or similar handles routing alongside SleekRank.

Add a class_pair column for situations where the interaction applies to a whole class (all SSRIs with tramadol, for example). The template can selector-map the class label and list-map the specific drugs covered. A second URL pattern under /interactions/class/{slug}/ generates class-level pages from the same source, with the specific pair pages linking back to them.

No. The base template is a normal WordPress page. Any theme with clean typography and clear callouts works. Severity badges and management checklists render through the theme's existing styles plus the few classes you assign. SleekRank only injects values into matched elements; the visual identity stays in the theme.