✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekRank for fossil species pages

Maintain a sheet of around 10k fossil species pulled from the Paleobiology Database. SleekRank publishes one page per species at /fossil/{slug}/ with geological age, formation, locality, taxonomy, and OG card driven by the row.

€50 off for the first 100 lifetime licenses!

SleekRank for Fossil species pages

Fossil ID belongs in a structured, generated library

A fossil collector finds a trilobite in shale and wants the species name. A graduate student traces a single brachiopod genus across formations. A museum publishes a regional fossil guide tied to its collection. Three audiences, one shape of page: a per-species entry with taxonomy, geological age, depositional environment, and known localities. Around 10,000 well-documented species cover the audience.

SleekRank reads the species sheet as the schema. Columns for slug, name, scientific_name, order, family, age_period, age_ma_low, age_ma_high, type_locality, formations, diagnostic_features, and image_url feed the base page at /fossil/{slug}/. List mappings render formations and diagnostic features; selector mappings fill the geological time and locality cells; a meta mapping wires the OG card.

Cluster blocks at the bottom of every page surface other species in the same family (other trilobites of the order Phacopida) and other species from the same formation (other fossils from the Wheeler Shale). Both are list mappings against the same sheet, returning six related species per page deterministically.

Workflow

From fossil species row to ID page

1

Build the base fossil page

Design one WordPress page with hero photo, scientific name and order heading, age and locality block, diagnostic features list, formations list, related species cluster, and a small inline stratigraphic column. Every species inherits this layout.
2

Compile the species sheet

Pull species from the Paleobiology Database. Normalize columns for slug, scientific name, order, family, age period, age in Ma, type locality, formations, diagnostic features, and image URL. Around 10,000 well-documented rows.
3

Wire mappings to the template

Tag mappings for title and H1, selector mappings for age and locality cells, list mappings for formations and diagnostic features, conditional mapping for fossil_class blocks. Schema mapping wraps biology fields into a JSON-LD block.
4

Cluster by taxonomy and formation

Order and family columns drive taxonomic clusters; formations column drives depositional clusters. Both list mappings against the same sheet, six related species per page deterministically ordered by md5 hash so internal links stay stable.

Data in, pages out

One row per fossil species, one ID page

Columns for age, formation, type locality, and diagnostic features. List mappings render formations and features; selectors fill the time and locality cells.
Data source: Paleobiology Database / JSON
slug scientific_name order age_period type_locality
elrathia-kingii Elrathia kingii Ptychopariida Cambrian Wheeler Shale, Utah
tyrannosaurus-rex Tyrannosaurus rex Saurischia Late Cretaceous Hell Creek Formation
megalodon Otodus megalodon Lamniformes Miocene-Pliocene Calvert Cliffs, Maryland
archaeopteryx Archaeopteryx lithographica Saurischia Late Jurassic Solnhofen Limestone
ammonite-perisphinctes Perisphinctes sp. Ammonitida Jurassic Madagascar
URL pattern: /fossil/{slug}/
Generated pages
  • /fossil/elrathia-kingii/
  • /fossil/tyrannosaurus-rex/
  • /fossil/megalodon/
  • /fossil/archaeopteryx/
  • /fossil/ammonite-perisphinctes/

Comparison

Hand-written fossil guides vs SleekRank

Per-species WordPress posts

  • Each species written manually, with age and formation typed by hand
  • Taxonomy drifts between entries as authors disagree
  • Locality data and formation references inconsistent across posts
  • Order and family cross-links built by hand and almost always incomplete
  • OG card and schema set per post, broken on most posts
  • Practical ceiling around 100-200 species in any one library

SleekRank

  • One row per species fills /fossil/{slug}/ automatically
  • Selector mappings render geological age, period, and type locality
  • List mappings render formations and diagnostic features
  • Order, family, and formation columns drive related-species clusters
  • Meta mapping wires og:image from the same row
  • Around 10k species become 10k indexable URLs from one template

Features

What SleekRank gives you for Fossil species pages

Geological time and stratigraphy

Age period (Cambrian, Jurassic, Miocene) and absolute age in Ma both render on every page via selector mappings. A small stratigraphic chart in the template uses the age columns as data attributes so the species' position on the geologic time scale is always visible.

Type locality and formations

Type locality as a string column, formations as a JSON array. Selector and list mappings render both onto the page, and a list mapping clusters fossils that share a formation (Burgess Shale fauna, Solnhofen Limestone fauna).

Order and family clusters

Order and family columns drive taxonomic clusters; formation columns drive depositional clusters. Both list mappings against the same sheet, returning six related species per page deterministically so internal linking stays stable.

Use cases

Who runs fossil ID libraries on SleekRank

Museum collections

Run a public-facing fossil library off the same sheet that backs the specimen catalogue. Curators maintain one data source; the public page reads the same age, locality, and taxonomy values as the internal record.

Paleontology departments

Build a teaching fossil library tied to lab teaching collections. Diagnostic features per species stay consistent because they flow from one column, and exam-prep students always read the same fields across the corpus.

Fossil dealers and shows

Pair the species library with the dealer inventory. Each species page links to specimens for sale (when available); each product page links to the species page for taxonomic reference. One sheet, two intersecting catalogs.

The bigger picture

Why fossil libraries belong in structured generation

Paleontology is a field with extraordinary depth and a comparatively small number of writers. Building a fossil ID library by hand at 10,000 species is the work of a research team over years, and the field's taxonomy is too active to stay current without continual editor effort. A data-driven library inverts the workflow.

The Paleobiology Database publishes a curated species list under a permissive license; the editor curates which subset enters the local library, normalizes columns for age, formation, and diagnostic features, and the corpus emerges from the template. When a phylogenetic revision changes an order assignment, the column updates and every related page reflects the change on the next cache refresh. The other reason fossil ID benefits from data-driven generation is the depth of cross-linking.

Fossils belong to formations, formations belong to ages, ages belong to periods. A user landing on a Wheeler Shale trilobite can follow links to other Wheeler Shale fossils, to other Cambrian trilobites, and to other Ptychopariida species. Each cluster is a list mapping against the same sheet, generated automatically, and stays current as new species are added.

The user explores the deep time of the corpus without the editor ever maintaining a link graph by hand.

Questions

Common questions about SleekRank for Fossil species pages

The Paleobiology Database publishes a comprehensive species list under a permissive license. iDigBio carries specimen-level records. Combine them in a sheet with one row per species, normalize columns for taxonomy, age, and locality, and feed the sheet to SleekRank. Attribution lives in a static block in the template.

 

Add a nomenclature_qualifier column with values like sp., aff., cf., or formal. Selector mappings render the qualifier in the heading. Pages for open-nomenclature names exist and are crawlable but display a note explaining the provisional taxonomy. The corpus reflects the field's actual practice.

 

A fossil_class column with values like body, trace, or microfossil drives conditional mappings. Trace fossil pages show a tracemaker block and hide the body-fossil-specific anatomy. One template, several conditional blocks, the same sheet.

 

When a species gets revised or synonymised, the row's scientific_name changes. A redirects column carries old names that now redirect to the current entry. The slug stays the same so internal links don't break; visible name and JSON-LD update on the next cache refresh.

 

Yes. A static SVG stratigraphic column lives in the template, and the species' age_ma_low and age_ma_high columns are passed in as data attributes. A small inline script positions a marker on the column to show the species' range. One template script, per-species positioning.

 

An image_credit column per row carries the institution or photographer. Pages with museum-held specimens credit the museum with attribution links; pages with field-collected specimens credit the collector. The same selector mapping renders credit consistently across the corpus.

 

Yes. Add a collecting_locality JSON array column for fossils commonly found in publicly accessible exposures, with notes on access and ethics. A selector mapping shows the locality block only when collecting_locality is populated. Hunters get practical pointers; cautioned species hide the field.

 

The default page uses Article schema with paleontological fields in the body. For richer markup, add a custom JSON-LD block that maps scientific name, family, age, and type locality into a custom type. Search engines don't all consume it, but the markup doesn't harm the page.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€99

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€179

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Launch Offer

€299

€249

EUR

once

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView