Most teams pull the directory directly from the FDA, which publishes the NDC Directory as a free download. SleekRank accepts CSV, JSON, REST endpoints, and WordPress custom post types as data sources, so the same template can swap from the FDA export in week one to a vendor-curated dataset in month six without rebuilding any URLs.

Production sites run the full 200,000-product NDC Directory 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 NDC with RxNorm add CDN edge caching layered on top of the same table.

The FDA publishes the NDC Directory as a public dataset under standard government open-data terms. SleekRank is the rendering layer, not the license. Teams pull the export from the FDA site, point SleekRank at the file, and include the standard FDA attribution on each generated drug product page.

Yes. SleekRank maps any data field to the document title, meta description, OG image suffix, and canonical URL. So the ndc 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 product.

The dose-form field on each row powers an automatic related cluster of up to six adjacent products. 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 strengths and labelers for the same active ingredient.

After the next cache clear, the discontinued row resolves to a historical view if you keep it in the dataset, or returns 404 if you remove it. Most teams keep discontinued rows with a status flag and a redirect to a current equivalent, so legacy backlinks always land on a sensible alternative in search results.

Yes. The base template includes a FAQ accordion that emits FAQPage JSON-LD, so each drug product 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 'Who makes NDC {ndc}?' so every page ships with answerable FAQs.

Yes. Each drug dataset becomes its own page group with its own URL pattern like /ndc/{slug}/, /rxnorm/{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.