✨ 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 pottery glaze recipe pages

Maintain pottery glaze recipes in a sheet or JSON. SleekRank generates an indexable page per recipe with cone, surface, color, ingredient batch, application notes, and firing schedule.

€50 off for the first 100 lifetime licenses!

SleekRank for pottery glaze recipe pages

Glaze recipes share a tight schema

Every pottery glaze recipe has the same fields: name, cone (06, 6, 10, etc.), atmosphere (oxidation, reduction, salt, wood), surface (matte, satin, gloss, crystalline), base color, ingredient list with percentages, application notes, firing schedule, and safety cautions. The shape repeats across hundreds of celadons, shinos, tenmokus, ash glazes, and contemporary studio recipes. Writing each page in the editor leaves percentage rounding inconsistent and safety notes missing from half the library.

SleekRank reads the recipe source from Google Sheets or JSON and renders one page per glaze at /glaze/{slug}/. List mapping handles ingredients, application notes, and substitution arrays. Selector mapping fills the cone, atmosphere, and surface badges. Meta mapping writes per-recipe descriptions and og:image references.

Because every page pulls from one source, a refined percentage, ingredient substitution, or new safety note flows through the library on the next cache cycle. Studio managers own the source, the design team owns the template, and the WordPress side stays a pure layout concern.

Workflow

From recipe sheet to per-glaze URLs

1

Maintain the recipe source

Keep rows with slug, name, cone, atmosphere, surface, color, ingredients array (with material and percentage), substitutions, application notes, firing_schedule, cautions array, and image URL.
2

Design the recipe template

Create one WordPress page with a hero (name, cone, atmosphere badge), color callout, ingredients table, application notes, firing schedule, cautions block, and a gallery of test tiles.
3

Map recipes to template

Tag-map title to name, selector-map cone, atmosphere, surface, and color, list-map ingredients, substitutions, application notes, and cautions arrays, meta-map description and og:image per recipe.
4

Flush cache, sitemap, indexes

After the first import, clear the SleekRank items cache and flush WordPress rewrites. New recipe URLs appear in the sitemap, cone and atmosphere indexes populate automatically, and Search Console picks up the URLs on the next crawl.

Data in, pages out

Recipe rows to glaze URLs

One row per glaze with slug, name, cone, atmosphere, and surface.

Data source: Google Sheets / JSON
slug name cone atmosphere surface
leach-celadon Leach Celadon Cone 10 Reduction Satin gloss
oribe-green Oribe Green Cone 10 Oxidation Gloss
carbon-trap-shino Carbon Trap Shino Cone 10 Reduction Matte
tenmoku Tenmoku Cone 10 Reduction Gloss
ash-glaze Pine Ash Glaze Cone 10 Reduction Satin
URL pattern: /glaze/{slug}/
Generated pages
  • /glaze/leach-celadon/
  • /glaze/oribe-green/
  • /glaze/carbon-trap-shino/
  • /glaze/tenmoku/
  • /glaze/ash-glaze/

Comparison

Hand-built glaze pages vs SleekRank

Manual page per recipe

  • Ingredient percentages get edited in one place and forgotten elsewhere
  • Atmosphere labels drift across recipes as different writers use different conventions
  • Safety cautions appear on some pages and not on similar recipes
  • Substitution notes vary depending on who last edited the recipe
  • OG cards per glaze rarely receive attention beyond a generic studio image
  • Adding a new recipe means duplicating a page and editing many ingredient fields

SleekRank

  • One indexable URL per recipe under /glaze/{slug}/
  • Selector mapping fills cone, atmosphere, and surface badges
  • List mapping renders ingredients with percentages, substitutions, and cautions
  • Updated percentages flow across every reference of the glaze
  • Sitemap entries per recipe, base template noindexed
  • Pair with SleekPixel for per-glaze OG cards labeled with name and cone

Features

What SleekRank gives you for pottery glaze recipe pages

Cone and atmosphere badges

Selector mapping renders cone and atmosphere badges (Cone 6 Ox, Cone 10 Red, Salt, Wood) so potters see firing context immediately and avoid wasting a load on a mismatched glaze.

Ingredient lists

List mapping renders the ingredients array with percentages and substitution notes. The same materials vocabulary feeds every recipe, so the silica in one recipe matches the silica in another.

Safety cautions

List mapping renders the cautions array (barium, lithium, lead substitutes, manganese) on every relevant recipe. Studio managers update the safety vocabulary once and the new language propagates everywhere.

Use cases

Who builds glaze pages with SleekRank

Studio potters

Working studios publish their full glaze library with stable URLs apprentices and visiting artists reference, sourced from the spreadsheet the studio already maintains.

Ceramics programs

College and high school programs maintain a structured glaze reference students bookmark for studio sessions, with cones and atmospheres labeled consistently.

Ceramics publishers

Publishers cover the full glaze landscape with focused per-recipe URLs sourced from one dataset, ranking for specific glaze queries instead of fighting a single mega-list page.

The bigger picture

Why glaze libraries reward depth

Pottery glaze search is specific by recipe name and by attribute. Potters look up "Leach celadon recipe," "carbon trap shino cone 10," "oribe green oxidation," and a focused per-recipe page outranks a generic listicle every time. The underlying data is structured by definition: name, cone, atmosphere, surface, ingredient list, and firing notes.

That information already lives in studio notebooks and ceramics teachers' files, often more accurately than what a marketing team has time to compile fresh. Hand-building a page per recipe is a multi-month project that decays the moment a studio swaps a feldspar or updates a safety note. The pages drift, the percentages drift, and the authority that should belong to working potters leaks to forum threads with worse data.

SleekRank lets studios, programs, and publishers author once in a sheet and renders the result through a template the design team built once. Adding a new glaze becomes a row insertion. Substitutions and cautions propagate on the next cache cycle.

Pair with SleekPixel for OG cards labeled with the glaze name and cone so social previews look intentional rather than generic.

Questions

Common questions about SleekRank for pottery glaze recipe pages

Yes. Store one image_url column for the hero photo and an additional gallery_urls array for test tile variations across clay bodies and firing positions. List mapping renders the gallery, and the SleekPixel pairing can generate per-recipe social cards labeled with the cone.

 

Store a substitutions array per ingredient (substitutions: [{material: Custer Feldspar, swap_for: G200, ratio: 1:1}]). List mapping renders the substitutions as inline notes so potters running a different material library see the equivalent without leaving the page.

 

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new recipes get crawled within hours of cache flush. Glaze-name queries rank well because the structured per-page content signals authority.

 

Yes. Use a template-level conditional that reads the atmosphere value and renders an extra reduction-schedule block for reduction glazes, or a salt-loading note for salt-fire recipes. The data stays in one source, the template branches on the value.

 

Delete or unpublish the row in the source. The URL begins serving a 404 on the next cache cycle and drops from the sitemap. If the recipe was renamed or merged with a sibling, add a redirects column referencing the new slug so the old URL passes link equity forward.

 

Cache duration is configurable per source. For active development, set fifteen to thirty minutes. For a stable library, a day or longer is fine. A manual flush via wp-cli makes urgent updates appear immediately on the next request.

 

No. Each recipe has a distinct slug, name, cone, atmosphere, ingredient list with percentages, surface, and application notes. Google reads the structured fields as differentiated content. Generic boilerplate is the duplication risk, which the template avoids by keeping the dynamic fields prominent.

 

Yes. Build separate page groups for clay bodies and slips (one row per recipe) and link from each glaze page to the recommended clay bodies via a related_clays array. List mapping renders the linked items so potters can plan a full surface from one 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