Active ingredient (INN) is the universal join key. Most regulator feeds expose it as a standard field; for those that do not, your ingest job needs a normalization step (Wegovy and Ozempic both map to semaglutide). Maintain a normalization table that gets updated when new INNs publish, typically a few entries per quarter.

Combinations like nirmatrelvir/ritonavir need their own canonical slug because the combination is the regulated product. Maintain both the combination page and the individual-component pages, with cross-links between them. Most users searching for the combination land on the combination page; users searching for the component land on the component.

Yes. Orphan designations are flagged in openFDA, EMA, and Health Canada feeds. Drive an orphan-status badge on the page from those flags and run a separate /drugs/orphan/ index for users searching specifically for orphan-designated treatments. The data is in the feeds; the surface is up to you.

Do not. The page should reflect only approved indications per regulator. Off-label use is a clinical-judgment topic that belongs on editorial pages, not on a regulatory-record page. Tag mapping from the indications field keeps the page strictly within the regulator's approved language.

Yes, schema.org Drug with proprietaryName, nonProprietaryName, activeIngredient, manufacturer, and (optionally) administrationRoute and dosageForm. Render JSON-LD via a tag mapping on the base page; the same template handles every drug.

DEA scheduling for US-controlled substances comes from a separate dataset. Join it against the drug feed by active ingredient and render the schedule as a chip on the page. EMA and other regulators publish their own scheduling equivalents that can render in a per-regulator section.

Source dosing only from current labeling files (FDA SPL, EMA SmPC, Health Canada Product Monograph). Pull the labeling URL into a selector mapping and render the labeling reference prominently on the page. Editorial copy summarizing dosing should be reviewed every label update or removed entirely in favor of a direct labeling link.

Once the regulator publishes the approval and your ingest job picks it up (typically within a day for openFDA, slightly longer for EMA EPAR releases), SleekRank generates the URL on the next cache refresh. Most teams run a daily delta pull and flush the cache manually on big approval days to push major drug pages live within hours.