Anywhere structured. Google Sheets and Notion work well for collaborative editorial teams, a flat JSON file or CSV works for solo curators who prefer git, and a custom WordPress post type works for teams that already live inside WP. SleekRank reads any of them via the matching data source.

Store synonyms as an array per row. A list mapping renders them as a 'Also known as' block on the species page when the array has entries and skips the block when empty, so the layout stays clean for monotypic genera and richly synonymized species alike.

Yes. The genus column drives the URL pattern and the related cluster. One sheet can carry every genus, with the template rendering each species page consistently regardless of how many genera are in scope.

Add a photo_credit and photo_license column. The template renders the credit line under the lead image automatically, so attribution stays attached to the image without manual work per page.

Plant pages do not have a dedicated Schema.org type with rich-result rendering today, but the generic Thing or Article schema with name, image, description, and identifier still helps disambiguation. SleekRank emits it from the same fields the page renders.

A status column with values like accepted, synonym, or unresolved drives a badge at the top of each page. Synonym rows can redirect to the accepted-name page via a redirect rule, so the canonical URL is always the accepted name.

Add columns for Kew Plants of the World, World Checklist, or IPNI identifiers. A small Twig macro renders the external link block on every page that has an identifier, so the corpus links to authoritative references consistently.

Edit the row. The cache expires on the configured cycle and the page reflects the new data on the next request, so a taxonomic revision or a new synonym propagates across the corpus without per-page edits.