SleekRank for pottery listings
Per-maker and per-form landing pages built from one spreadsheet. Map maker marks to headlines, glaze and clay body to spec tables, kiln and firing details to schema, and ship indexable WordPress pages from a single base template.
€50 off for the first 100 lifetime licenses!
Form-level pages are how studio pottery gets found
Studio-pottery search is unusually specific. A collector hunting "Lucie Rie footed bowl manganese glaze 1970s" wants the maker mark, the form, the glaze recipe, the period, and a clear note on whether the piece is signed and documented. The rankable surface is maker x form x glaze x period - thousands of permutations once you cover both production studio ware and one-off art pottery. Hand-building those pages is impossible. SleekRank reads a single Google Sheet, CSV, JSON file, or REST endpoint and emits one WordPress page per row, all sharing the base template you already designed in the editor.
The data layer is the studio inventory. Add a row for a Lucie Rie footed bowl in manganese glaze at $4,200 with photographed maker mark and the page goes live on the next cache refresh. Update the firing notes after a fresh examination, every relevant page picks it up. No static rebuilds, no per-piece edits, no engineer.
Mappings do the wiring. Tag mappings push the maker and form into the H1 and document title; selector mappings put the glaze and clay body into the spec block; list mappings render firing notes from a JSON column. The XML sitemap auto-includes every generated URL. Sold rows return 404 cleanly on the next refresh.
Workflow
From inventory row to ranked pottery page
Design the base page
Connect the sheet
Wire the mappings
Publish and flush
Data in, pages out
From inventory row to live listing URL
Each row becomes one page. The slug column maps to the URL, the rest of the columns flow into headlines, spec tables, firing notes, and OG tags through simple selector or list mappings.
| slug | maker | form | glaze | period | price |
|---|---|---|---|---|---|
| lucie-rie-footed-bowl-manganese-1970s | Lucie Rie | Footed bowl | Manganese, sgraffito | ca. 1970s | $4,200 |
| hans-coper-spade-form-1965-stoneware | Hans Coper | Spade form | White slip, manganese rim | ca. 1965 | $28,000 |
| bernard-leach-st-ives-tenmoku-jar | Bernard Leach | Lidded jar | Tenmoku | ca. 1955, St Ives | $3,800 |
| shoji-hamada-mashiko-platter-1960 | Shoji Hamada | Square platter | Kaki and nuka | ca. 1960, Mashiko | $6,400 |
| edmund-de-waal-vitrine-vessel-2018 | Edmund de Waal | Cylindrical vessel | Celadon, lead | 2018, ed. 1/1 | $8,900 |
/pottery/{slug}/
- /pottery/lucie-rie-footed-bowl-manganese-1970s/
- /pottery/hans-coper-spade-form-1965-stoneware/
- /pottery/bernard-leach-st-ives-tenmoku-jar/
- /pottery/shoji-hamada-mashiko-platter-1960/
- /pottery/edmund-de-waal-vitrine-vessel-2018/
Comparison
Hand-crafting pottery listings vs SleekRank
Building each listing manually
- Each piece is a duplicated WordPress page with hand-typed spec table
- Adding 50 new acquisitions means 50 pages built one at a time
- Glaze attribution updates require touching every page individually
- No structured data layer - VisualArtwork schema hand-written per piece
- Sitemap, indexing, OG tags - all maintained per page
- Catalogue lags reality, sold pieces linger online
SleekRank
- One base page in WordPress, thousands of pottery pages generated from data
- CSV, Google Sheets, JSON, REST API, or Notion as the source of truth
- Edit a row → page updates automatically on the next cache refresh
- Mappings handle title, H1, spec tables, firing notes, meta tags, and OG images
- XML sitemap auto-generated for every produced URL
- WordPress-native - works with your theme, your blocks, your editor
Features
What SleekRank gives you for pottery listings
Seven data source types
Google Sheets, CSV files, JSON URLs, JSON files, Notion databases, REST APIs, and CSV URLs. Mix multiple sources in one page group when studio inventory and reference-mark data live separately.
Four mapping types
Replace by tag (h1, title), by CSS selector (#glaze, #clay-body), by list iteration for firing notes, or by meta tag for description and og:image. Each mapping targets one cell.
Cache and rebuild
Set cache duration per source - 1 hour around a kiln opening, 24 hours when stable. Invalidate on schedule or on demand. Pages render from cache, not from a static build step.
Use cases
Where pottery listings shine with SleekRank
Studio-pottery dealers
Per-form pages with maker mark, glaze, and period beat a generic studio archive. Collectors search for specific glaze families directly - serve them a URL with the maker mark photographed and the firing detail laid out.
Working studios
Each fresh kiln opening lands as a new batch of rows, generating pages overnight that catch the long-tail glaze-plus-form queries collectors actually type. The studio sheet stays the system of record.
Pottery reference projects
Maker biographies and mark catalogues can publish a page per documented form, drawn from a community-edited spreadsheet, ranking on niche queries no general archive page would surface.
The bigger picture
Why per-form pottery pages outrank studio archives
A single studio archive filtered by query string cannot win "Lucie Rie footed bowl manganese 1970s" against a competitor who built a dedicated, schema-marked URL for it. Google ranks pages, not parameters. Studio-pottery intent is also bottom-of-funnel - the collector quotes the glaze name, knows the period, has a price band in mind, and is comparing two dealers in the same week.
Duplicated boilerplate gets bounced and unique data wins. The pieces that rank carry specifics: photographed maker marks, glaze recipes, clay body notes, kiln details, scale shots beside common references. Maintaining that uniqueness across 1,300 pieces by hand is impossible; maintaining it across 1,300 rows in a sheet is an afternoon.
SleekRank turns the studio spreadsheet into the SEO surface, which collapses the gap between the potter or registrar and the team that owns the URLs. The base page still belongs to WordPress, so design, tracking, and CRO experiments stay where they always lived. Adding a fresh kiln load becomes a batch of rows plus a cache flush rather than a sprint.
Questions
Common questions about SleekRank for pottery listings
Page groups with 5,000+ generated URLs run on a single base template without issue. The data layer is cached and rendering re-uses your existing WordPress page, so the practical ceiling is your hosting plan and your sitemap budget. Most pottery catalogues top out well below the technical limit because Google's crawl budget for new pages slows past a few thousand.
Yes. Edit your Google Sheet, push to your studio REST endpoint, or update the CSV in the theme. SleekRank refreshes on the next cache cycle, and you can clear the cache manually from the admin or via WP-CLI. No theme deploy, no static site build, no engineering ticket.
Yes. SleekRank uses your existing base WordPress page as the template. Whatever theme, blocks, page builder, or custom CSS rendered that page renders every generated URL identically. Bricks, Elementor, Gutenberg, Oxygen, and classic themes all work because SleekRank operates on the rendered HTML.
Yes. They are real WordPress URLs with full HTML, sitemap inclusion, and per-page meta tag mappings for title, description, canonical, and og:image. The base template page is excluded from the sitemap and marked noindex automatically so it never competes with the generated listings.
Yes. You can branch a mapping based on a maker column, or run multiple page groups against subsets of the data. A common pattern: /pottery/{slug}/ for general stock with a richer template, /pottery/leach-circle/{slug}/ for a focused canon with a leaner one.
On the next cache refresh the URL stops resolving and returns 404. The sitemap is regenerated automatically so search engines drop the URL cleanly. If you would rather redirect a sold piece to a similar form by the same maker, point the slug at a wildcard rule in your normal WordPress redirects plugin before deleting the row.
Make the data carry the difference. Maker marks, glaze recipes, kiln notes, firing temperatures, and photographs of the actual piece all vary per row. Avoid copy-paste paragraphs that swap only the form. The richer the per-piece data, the lower the duplicate-content risk.
Yes. A URL pattern like /{maker}/{form}/ produces /lucie-rie/footed-bowl/, /lucie-rie/vase/, /hans-coper/spade-form/ from a combined data set or two joined sheets. Use a maker sheet and a form sheet, then run mappings against the cross-product.
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
EUR
per year
further 30% launch-discount applied during checkout for existing customers.
- 3 websites
- 1 year of updates
- 1 year of support
Pro
EUR
per year
further 30% launch-discount applied during checkout for existing customers.
- Unlimited websites
- 1 year of updates
- 1 year of support
Lifetime ♾️
Launch Offer
€299
EUR
once
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
€749
Continue to checkout