Google Sheets is easiest for an herbalist team to maintain directly. JSON works well when the data flows from a structured reference system like Notion. Both formats let SleekRank read the same fields. The format choice can change later without rebuilding the pages.

Keep them as separate columns (traditional_uses, evidence_summary) and render them in distinct sections of the template. That way the page is explicit about which is which, which matters both for credibility and for compliance with claims regulations in the publisher's market. The herbalist controls both fields in one source.

Yes. Store drug_interactions as an array of drug slugs and list-map them as linked items. If you also run a drug-interaction page group, each link goes to the relevant per-drug page. The two libraries can share coordinated sources so adding a herb makes its interactions available on the drug side too.

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 herbs get crawled within hours of cache flush. Common-name and Latin-name queries both rank well because 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 newly recognized interaction, for example) live on the next request.

No. The base template is a normal WordPress page. Any theme with clear typography works. Latin-name and family 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.

Store preparations as a JSON or array column (preparations: [tincture, decoction, infusion, capsule]) with dosage notes per form. List mapping renders them in a dedicated section. A second URL pattern under /herbs/preparation/{slug}/ can give each preparation its own page when those queries matter.

Yes. Add a citations array per row with reference IDs or DOIs and list-map them into a references block at the bottom of each page. For inline citations, use selector mapping with a placeholder element next to a claim and inject the marker there. The herbalist maintains the citation list once in the source, keeping references consistent across the library.