Google Sheets is easiest for dietitian teams to maintain directly. JSON works well when the data flows from Notion or another structured system. Both formats let SleekRank read columns and arrays the same way. Switching between formats later requires only a config change, not a content rebuild.

Store RDA as a JSON column with brackets (rda: {male_adult: 8, female_adult: 18, pregnant: 27}) or split into rda_male, rda_female, rda_pregnant columns. The template renders the bracketed table from the structured value. JSON is cleaner with many brackets; split columns are easier for a sheet.

Yes. Store interactions and cofactors as arrays of slugs (vitamin-c, vitamin-d, levothyroxine) and list-map them as linked items. If you also run vitamin or drug-interaction page groups, each link points to the relevant page. All three libraries can share coordinated sources so adding a mineral makes it available everywhere it interacts.

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 minerals get crawled within hours of cache flush. Mineral-name queries are very competitive, but the structured per-page content signals authority that listicles cannot match.

Cache duration is configurable per source. For active editorial work, set fifteen to thirty minutes. For a stable library, a day or longer is fine. A manual cache flush via wp-cli pushes urgent updates (a corrected RDA, for example) live on the next request.

No. The base template is a normal WordPress page. Any theme with clear typography and well-styled lists works. Symbol and classification badges render through the theme's existing styles plus the few classes you assign. SleekRank only injects values; the visual identity stays in the theme.

Yes. Add a citations array per row with reference IDs or URLs and list-map them into a references block at the bottom of each page. For more visible citations inline, use selector mapping with a placeholder element next to a claim and inject the citation marker there. Editorial teams maintain the list once in the source.

Store forms as a JSON or array column (forms: [ferrous sulfate, ferrous gluconate, heme iron]) with notes per form. List mapping renders the forms with their bioavailability notes. A second URL pattern under /minerals/form/{slug}/ can give each form its own page when you want to target form-specific queries directly.