No. SleekRank does not generate fossil content. You provide the sheet, catalog number, taxon, formation, age, locality, and so on, and SleekRank renders one page per row. Editorial responsibility for paleontological accuracy stays with you. SleekRank's role is the rendering and routing layer between the dataset and the live site.

Yes. Add an image_url column to the sheet and map it via a tag or selector mapping that injects an . For Open Graph cards, pair SleekRank with SleekPixel for dynamic OG images that take the slug as a parameter and render a branded card with the taxon and age.

Add an elements array column with each preserved element (skull, femur, ribs) and render it via a list mapping. For specimens with multiple catalog numbers across the same individual, use a related_catalog column rendered as cross-links on the page.

Store period, epoch, and stage as separate columns and render each one with a selector mapping that wraps it in an anchor to a hub page like /periods/jurassic/. The dataset carries the values, the template carries the links.

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 fossil catalogs (a slow-changing domain) set cacheDuration high so the sheet is not constantly refetched.

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 specimen 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-specimen URL. Build /fossils/ as a filter page that pulls from the same dataset and filters by period, formation, or country. SleekRank handles the per-specimen detail pages; the hub uses the same source as the single point of truth.

Pick a canonical slug (usually the original or most-cited name) and store synonyms as an array column rendered as 'also referred to as' on the page. Add redirects from old-name URLs so external citations resolve to the current page. The dataset stays the source of truth.