No. SleekRank does not generate species content. You provide the sheet, and SleekRank renders one page per row. Editorial responsibility for taxonomy and edibility classification stays with you. Given the stakes around toxic and deadly species, the editorial standard should be high; SleekRank's role is the rendering and routing layer.

Yes. Add image_url and spore_print_url columns to the sheet and map them via tag or selector mappings that inject tags. For Open Graph cards, pair SleekRank with SleekPixel for dynamic OG images that include the binomial and edibility badge.

Use a dedicated lookalikes_deadly array column rendered with prominent styling on the page (red badge, warning text). The selector mapping injects the list with a danger class. Foragers see the warning in the same place on every page, not buried in prose.

Some species are edible in one region and toxic in another due to chemistry or preparation differences. Use a notes_per_region array column with structured entries, or split into regional slugs (chanterelle-northeast, chanterelle-pacific-northwest) if the differences are large enough to warrant separate pages.

SleekRank caches the source per cacheDuration set in seconds. Edit the sheet, clear the SleekRank cache via WP-CLI or admin, and the next request rebuilds the page with new data. For mushroom taxonomy set cacheDuration high since reclassifications are slow.

Yes. Each generated URL is a real WordPress page included in the sitemap. The base template is excluded automatically so the scaffolding does not compete with real species pages. Run a rewrite flush after adding new slugs so the routes resolve immediately on production.

Yes, but that's a hub page rather than the per-species URL. Build /mushrooms/ as a filter page that pulls from the same dataset and filters by edibility, season, or habitat. SleekRank handles the per-species detail pages; the hub uses the same source.

Pick a canonical slug (usually the long-standing common name) and store former binomials as an array column rendered as 'formerly known as' on the page. Add redirects from old-name URLs so prior links land on the canonical page. The dataset stays the source of truth.