✨ 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 gemstones by color pages

Maintain a sheet of around 100 gem species crossed with their colour ranges. SleekRank publishes one page per combination at /gemstones-by-color/{slug}/ with hardness, refractive index, treatment notes, and OG card driven by the row.

€50 off for the first 100 lifetime licenses!

SleekRank for Gemstones by color pages

Gemstone search is colour first, species second

Most gemstone shoppers start with a colour. Blue, green, red, purple. The species follows the colour, not the other way around. A blue sapphire is sapphire, but so is yellow sapphire and pink sapphire; a green tourmaline shares a name with a black tourmaline but they are very different gems for a buyer. A library that indexes the corpus by gem-and-colour pairs ranks for the queries shoppers actually run, around 100 gems crossed with their colour ranges.

SleekRank reads the gem-colour sheet as the schema. Columns for slug, gem, color, variety_name, mohs_hardness, refractive_index, specific_gravity, treatments, price_band, and image_url feed the base page at /gemstones-by-color/{slug}/. Selector mappings fill the gemmological spec table, list mappings render the treatment notes, and a meta mapping wires the OG card.

Cluster blocks at the bottom of every page surface other gems in the same colour family (other blues, other reds) and other colours of the same gem (other sapphires). Both are list mappings against the same sheet, returning six related entries per page deterministically.

Workflow

From gem-colour row to buyer's page

1

Build the base buyer's page

Design one WordPress page with hero photo, gem and colour heading, gemmological spec table, treatment notes, care guide, price-band callout, and related-variety cluster. Every gem-and-colour combination inherits the layout.
2

Compile the gem-colour sheet

Pull species data from GIA reference and Mindat; cross with their occurring colour ranges. Normalize columns for slug, gem, colour, variety name, hardness, refractive index, treatments, price band, and image URL. 300 to 500 rows total.
3

Wire selector and list mappings

Tag mappings for title and H1, selector mappings for each spec table cell, list mappings for treatments and care, conditional mapping for organic gems and colour-change varieties. Schema mapping wraps gemmological fields into a JSON-LD block.
4

Cluster by colour family and species

Colour columns cluster all blues together, species columns cluster all sapphires together. Both list mappings against the same sheet, returning six related entries per page deterministically.

Data in, pages out

One row per gem-and-colour, one buyer's page

Columns for gem, colour, hardness, refractive index, and price band. Selector mappings fill the spec table; list mappings render treatment notes.
Data source: GIA reference / Mindat / curated CSV
slug gem color mohs_hardness price_band
blue-sapphire Sapphire Blue 9 $$$$
yellow-sapphire Sapphire Yellow 9 $$$
pink-tourmaline Tourmaline Pink 7-7.5 $$
green-emerald Emerald Green 7.5-8 $$$$
red-spinel Spinel Red 8 $$$
URL pattern: /gemstones-by-color/{slug}/
Generated pages
  • /gemstones-by-color/blue-sapphire/
  • /gemstones-by-color/yellow-sapphire/
  • /gemstones-by-color/pink-tourmaline/
  • /gemstones-by-color/green-emerald/
  • /gemstones-by-color/red-spinel/

Comparison

Hand-published gem guides vs SleekRank

Per-gem blog posts

  • One post per gem mashes all colours together, missing colour-specific queries
  • Hardness and refractive index typed by hand, drift between posts
  • Treatment notes phrased inconsistently across the corpus
  • Colour-family browsing built by hand and rarely complete
  • Schema and OG card configured per post, broken on most posts
  • Practical ceiling around 50 gem-and-colour pages

SleekRank

  • One row per gem-and-colour fills /gemstones-by-color/{slug}/ automatically
  • Selector mappings fill the gemmological spec table from columns
  • List mappings render treatment notes and care recommendations
  • Colour-family and species clusters at the bottom of every page
  • Meta mapping wires og:image from the same row
  • Around 100 gems crossed with colours yield 300-500 pages from one template

Features

What SleekRank gives you for Gemstones by color pages

Per-colour gemmological data

Hardness, refractive index, specific gravity, dispersion, and optic character land in their own cells of the spec table via selector mappings. Each colour variant carries the values specific to its variety, not a species-wide average that misses the trade names.

Treatment and disclosure notes

Treatments stored as a JSON array column with disclosure-level labels (none, heated, irradiated, oiled). The list mapping renders each as a separate disclosure under a heading buyers expect to see. The corpus stays consistent because the column vocabulary is controlled.

Price-band callouts

A price_band column with values like $, $$, $$$, $$$$ drives a visual callout on each page. Buyers see the rough market position before they read the spec table, and the price band column is one place to update across the corpus during market shifts.

Use cases

Who runs gemstone libraries on SleekRank

Independent jewellers and designers

Pair the buyer's library with the inventory. Each gem-and-colour page links to relevant pieces in the catalog, each piece links back to the variety page. Buyers explore by colour first, by species second, and find the inventory along the way.

Gemmology schools and societies

Run a teaching library off the same sheet that backs the loose-gem teaching collection. Every variety page reads the same data the students measured in lab, kept consistent without parallel editorial workflows.

Auction houses and appraisers

Publish a reference library of varieties with disclosure-level treatment notes. Appraisers cite the same page across reports; the page is data-driven, so the values stay current as treatment norms shift in the trade.

The bigger picture

Why colour-indexed gemstones beat species-indexed ones

Shoppers don't search for sapphire. They search for blue sapphire, or for a green gemstone, or for an alternative to emerald. The mental model is colour first, species second, and the sites that index their content the same way rank for the queries shoppers actually run.

A species-indexed library buries blue sapphire, yellow sapphire, and padparadscha on one big sapphire page, and the colour-specific queries land somewhere in the middle of a long scroll. A gem-and-colour indexed library has each variety on its own page, with the gemmological spec, the treatment disclosure, and the price band laid out cleanly. Building 300 to 500 such pages by hand is realistic but slow, and the values drift between pages as authors change.

Building them from a sheet keeps the corpus consistent because hardness, refractive index, and treatment vocabulary all flow from controlled columns. The other reason gem-and-colour pages benefit from data-driven generation is the cross-linking. A buyer reading the blue sapphire page wants links to other blue gems (tanzanite, blue spinel, paraiba tourmaline) and to other sapphire colours (yellow, pink, padparadscha).

Both lists are list mappings against the same sheet, generated automatically and kept current as new rows are added. The buyer browses sideways through the corpus, and every related-page block stays fresh.

Questions

Common questions about SleekRank for Gemstones by color pages

Not every species has every colour. Sheet rows exist only for combinations that occur (blue sapphire yes, blue emerald no). Around 100 species crossed with their occurring colours yields 300 to 500 pages. The sheet is the canonical list; the URL only resolves for rows that exist.

 

Trade names get their own rows alongside the colour rows. Padparadscha is a distinct row from pink sapphire and from orange sapphire, with its own variety_name column value. Selector mappings render the trade name in the heading; the species and colour columns still group it for navigation.

 

Yes. Add a synthetics and a simulants JSON array column with the relevant lab-grown or imitation materials. A list mapping renders both under disclosure headings. Buyers see what to expect in the market, and dealers can link to their own disclosure policy from the same block.

 

Add a grading_systems JSON array column with the relevant scale names and ranges. A selector mapping renders each grading system in its own callout. The page can show GIA blue-sapphire grading on the sapphire pages and a different scale on the emerald pages without splitting the template.

 

A colour_change boolean column drives a conditional mapping that swaps the single-colour heading for a colour-change callout showing both colours under different light sources. Alexandrite and rare colour-change sapphires share the same conditional block.

 

Add a price_per_carat JSON object column mapping carat bands to price ranges. A selector mapping renders the curve as a small table. The corpus stays current because dealers update the column, not the page layout.

 

An image_credit column per row carries the photographer and source. Pages with GIA reference photos credit GIA with attribution links; pages with dealer photos credit the dealer. The same selector mapping renders credit under the photo across the whole corpus.

 

Yes. A gem_class column with values like mineral, organic, glass, or synthetic drives conditional mappings. Organic gem pages hide the crystal-system row and show an organic-origin block instead. One template, several conditional blocks, the same sheet.

 

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