Most teams pull the monthly release directly from the National Library of Medicine, which publishes RxNorm freely with a UMLS license. SleekRank accepts CSV, JSON, REST endpoints, and WordPress custom post types as data sources, so the same template can swap from the release file in week one to a curated CPT in month six without rebuilding any URLs.

Production sites run the full 300,000-concept RxNorm release comfortably with object caching enabled. The items table caches each resolved row, so request-time work is a single indexed lookup plus the normal Timber render. Larger setups combining RxNorm with NDC and DailyMed add CDN edge caching layered on top of the same items table.

RxNorm is free under a UMLS Metathesaurus License, which requires registration with the NLM. SleekRank is the rendering layer, not the license. Teams pull the monthly release from the NLM site, point SleekRank at the file, and include the standard UMLS attribution block on each generated page.

Yes. SleekRank maps any data field to the document title, meta description, OG image suffix, and canonical URL. So the rxcui drives the H1, a seoTitle column drives the title tag, and a metaDescription column drives the snippet that appears in search results for that specific drug concept.

The term-type field on each row powers an automatic related cluster of up to six adjacent drug concepts. The order is deterministic per page (it uses an md5 of the slug pair) so search engines see a stable graph of internal links while readers see a natural variation between branded and clinical forms of the same ingredient.

After the next cache clear, the retired row resolves to a historical view if you keep the row in the dataset, or returns 404 if you remove it. Most teams keep retired rows with a status flag and a redirect to the replacing RxCUI, so legacy backlinks always land on a valid successor concept in search results.

Yes. The base template includes a FAQ accordion that emits FAQPage JSON-LD, so each drug page ships with structured data Google can use for rich results. The questions can either be authored per row or generated from a shared template like 'What does RxCUI {rxcui} represent?'

Yes. Each drug dataset becomes its own page group with its own URL pattern like /rxnorm/{slug}/, /ndc/{slug}/, and /dailymed/{slug}/. They share the base template and the items cache table, so one site can host the full medication crosswalk without splitting code across plugins or repos.