✨ 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 essential oil pages

Every essential oil has the same fields: botanical source, extraction method, scent profile, primary uses, blends-well-with, safety cautions. SleekRank reads one row per oil and renders one indexable URL per essential oil.

€50 off for the first 100 lifetime licenses!

SleekRank for essential oil pages

Aromatherapy reference needs structure

An essential oil reference covers dozens of oils (lavender, peppermint, tea tree, eucalyptus, lemon, frankincense). Every oil has the same fields: botanical source (Lavandula angustifolia), extraction method (steam distillation, cold press, CO2 extraction), scent profile (floral, herbaceous, citrus, woody, spicy), primary uses, blends-well-with chips, safety cautions (photosensitivity, dilution requirements, pet toxicity, pregnancy contraindications). Hand-building these pages drifts on extraction-method format, scent-profile vocabulary, and safety-caution completeness, and missing a safety note on a citrus oil's photosensitivity is a real harm.

SleekRank reads oils from a Google Sheet or CSV and renders one page per row against a base WordPress page with safety blocks in fixed selector slots. Tag mappings handle the oil name, botanical source, and extraction method. List mappings render scent-profile, blends-with, and safety-caution arrays with controlled vocabulary. Selector mappings drop in the properties paragraph and dilution-rate guidance. SleekRank does not generate aromatherapy advice; it only renders what the dataset contains.

Lavender pulls Lavandula angustifolia, steam distillation, floral-herbaceous scent, calm and sleep uses, blends with bergamot and chamomile. Peppermint pulls Mentha piperita, steam distillation, fresh-minty, energy and headache uses, with a pet-toxicity warning for cats. Same template, dozens of rows, dozens of URLs.

Workflow

From oil dataset to per-oil reference pages

1

Build the oil sheet

One row per oil with slug, name, botanical source, extraction method, scent family, scent profile, uses array, blends-with array, safety-caution array, dilution-rate array, and pet-toxicity notes.
2

Configure the page group

Set urlPattern to /essential-oils/{slug}/, point at the source file, and pick the base WordPress page with the botanical badge, scent chips, uses list, blends-with chips, and fixed safety block.
3

Wire the mappings

Tag mappings for name, botanical, extraction, scent family; list mappings for uses, blends, and safety cautions; selector mappings for the properties paragraph and safety block; meta mapping for description.
4

Cache and crawl

Clear the SleekRank items cache so the dataset re-imports, flush rewrites, and verify all /essential-oils/{slug}/ URLs appear in the sitemap with correct titles and per-oil safety summaries.

Data in, pages out

From oil rows to per-oil reference pages

One row per oil with botanical source, extraction method, scent profile, and arrays for primary uses, blend partners, and safety cautions.

Data source: Google Sheets / CSV
slug oil botanical extraction scent_family
lavender Lavender Lavandula angustifolia Steam distillation Floral
peppermint Peppermint Mentha piperita Steam distillation Minty
tea-tree Tea Tree Melaleuca alternifolia Steam distillation Medicinal
eucalyptus Eucalyptus Eucalyptus globulus Steam distillation Camphoraceous
lemon Lemon Citrus limon Cold press Citrus
URL pattern: /essential-oils/{slug}/
Generated pages
  • /essential-oils/lavender/
  • /essential-oils/peppermint/
  • /essential-oils/tea-tree/
  • /essential-oils/eucalyptus/
  • /essential-oils/lemon/

Comparison

Manual oil pages vs a sheet-driven set

Manual oil pages

  • Each oil page is hand-built from a layout copy
  • Extraction-method format drifts page to page
  • Scent-profile vocabulary is inconsistent
  • Safety cautions are sometimes missing entirely
  • Pet-toxicity warnings appear on some pages and not others
  • Adding a 'dilution rate' field touches every page

SleekRank

  • One row per oil, one URL per row, uniform layout
  • Botanical source, extraction, scent family via tag mappings
  • Uses, blends, and safety cautions via list mappings
  • Safety block sits in a fixed selector slot
  • Cache flush re-pulls when safety guidance updates
  • Sitemap registers every oil URL automatically

Features

What SleekRank gives you for essential oil pages

Per-oil URL

Every row becomes a /essential-oils/{slug}/ page with name, botanical source, extraction method, scent profile, uses, blend partners, and safety cautions rendered consistently from the data.

Safety cautions as lists

List mappings render safety-caution arrays as repeated list items with controlled vocabulary (photosensitivity, dilution required, avoid in pregnancy, pet toxicity). The structured approach keeps required notices from quietly going missing.

Fixed safety slot

Reserve a selector for the safety block and dilution-rate guidance so the layout never drifts page to page. Every generated oil page enforces the same safety posture by construction.

Use cases

Where essential oil pages get used on SleekRank

Aromatherapy retailer sites

Aromatherapy retailer content sites that document oils to support product pages, with one URL per oil and consistent safety notices across the catalog.

Aromatherapy reference hubs

Standalone reference sites documenting essential oils with consistent fields (botanical, extraction, scent, uses, safety) on a uniform per-oil template.

Holistic practitioner sites

Practitioner sites documenting oils used in their offerings, with structured safety cautions and dilution guidance that match the practitioner's protocols.

The bigger picture

Why aromatherapy reference rewards structured publishing

Essential oil content carries real safety obligations: photosensitivity from citrus oils, pet toxicity (peppermint and tea tree for cats), pregnancy contraindications, dilution requirements for skin application, hot-oil reactions on sensitive tissue. Hand-edited oil sites fail every safety obligation at scale. Citrus oil pages forget the photosensitivity warning.

Pet-toxicity warnings appear on some pages and not others. Dilution rates render as a paragraph on one page and a list on another, with rates that drift between editors. A sheet-driven approach fixes all of this.

Safety cautions sit in a controlled-vocabulary array that renders identically on every oil page. Pet-toxicity warnings are a structured column that the base template surfaces conditionally without exception. Dilution rates are an array of use-case-and-rate pairs rendered through a list mapping with consistent formatting.

The clinical or editorial team owns the dataset; SleekRank just renders it. For aromatherapy retailers, reference hubs, and practitioner sites, that auditable structure is non-negotiable for keeping safety signals intact at scale.

Questions

Common questions about SleekRank for essential oil pages

Use a controlled-vocabulary safety_cautions array column (photosensitivity, dilution required, avoid in pregnancy, pet toxicity, skin irritant, hot oil) and a list mapping to render them as warning chips. Because every oil page renders the array from the row, a citrus oil's photosensitivity warning cannot be accidentally dropped, it is part of the row, and the base template's safety block always renders it.

 

Yes. Add a dilution_rates array column with use-case and rate pairs (topical: 2%, bath: 1%, diffusion: 5 drops) and use a list mapping to render them as a structured list. Some oils have different recommended dilution rates per use case; the array shape handles that without forcing a single-rate convention.

 

Add a pet_toxicity column with affected species (cats, dogs, birds) and a severity level. Use a selector mapping to render a dedicated warning block when the column is non-empty, with conditional rendering so safe oils don't carry an empty warning. Tea tree and peppermint warrant cat-specific cautions; the structured column makes those warnings impossible to forget.

 

Add an extraction_method column with controlled values (steam distillation, cold press, CO2 extraction, solvent extraction, enfleurage). Different methods yield slightly different chemical profiles and therapeutic claims; the controlled vocabulary lets editors and readers compare oils on extraction without dealing with format drift.

 

Yes. Add a blends_with array column with slugs of compatible oils and use a list mapping to render them as linked chips. Slug-based linking keeps the relationships intact across renames, and the chips link readers to other per-oil pages on the same site.

 

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template. Aromatherapy queries are long-tail and oil-specific ('lavender essential oil uses and safety'), so per-oil URLs matter more than category aggregations for organic traffic.

 

No. SleekRank is a rendering layer. Editorial responsibility for therapeutic claims, safety guidance, and dilution recommendations stays with the publisher and any consulting clinical aromatherapist. The advantage is consistency: once a safety caution is approved in the source, it propagates to every relevant oil page on a cache clear.

 

Add a product_url column to link from the reference page to the commerce product page. Use a selector mapping to render a 'shop this oil' CTA conditionally when the URL is present. Keep the educational content and the commerce data separate so editorial doesn't get crowded out by inventory state, and so reference pages remain useful for non-purchase intent.

 

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