✨ 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 archive index pages

Maintain one row per archive scope with label, item count, and a list of included entries. SleekRank renders /archive/{slug}/ for each, with list mapping over the archive entries and tag mappings handling label and totals.

€50 off for the first 100 lifetime licenses!

SleekRank for archive index pages

Archive index pages need editorial scope

WordPress ships date and category archives, but they aren't editorial. They list everything under a date or term with no introduction, no curated subset, no per-archive title. Real archive index pages have a defined scope ("interviews 2020 to 2022", "deep dives, payments stack", "every guide on schema markup") with a written framing and a curated list, not an auto-generated dump.

SleekRank reads an archives sheet keyed by scope slug with columns for label, framing note, total count, and the list of included entries (pipe-separated slugs or a referenced sub-sheet). Each row drives /archive/{slug}/ on a shared template, with tag mappings handling label and count, list mapping rendering the entries, and selector mapping injecting the framing intro.

The default WordPress date and category archives stay disabled or noindexed; the SleekRank archive pages take over as the canonical surface. The base WordPress page is auto-noindexed; only the scoped archive pages compete in search.

Workflow

From scope rows to archive URLs

1

Sheet your archive scopes

Build an archives sheet keyed by slug with columns for label, scope_type (date-range, topic, curated), framing note, entry_count, and the list of included entry slugs (pipe-separated or referenced sub-sheet). One row per archive surface.
2

Configure the page group

Point a SleekRank page group at the archives sheet, set urlPattern to /archive/{slug}/, pick a base page laid out as the archive index template, and choose a cacheDuration. Daily or longer works since archive scopes change slowly.
3

Map per-archive fields

Tag mappings handle label and entry count. Selector mapping injects the framing intro. List mapping iterates over the entry list, rendering each as a card with title, excerpt, and link. Meta mapping sets per-page og:title and description.
4

Flush cache and rewrites

Clear the SleekRank items table after each new scope or entry-list edit, then flush WordPress rewrites so /archive/{slug}/ resolves. Submit the sitemap once; ongoing edits only need a cache flush after the row is updated.

Data in, pages out

From scope rows to archive URLs

One row per archive scope with label, framing, and included entries drives one indexable URL.

Data source: Google Sheets / CSV / JSON
slug label scope_type entry_count framing
interviews-2020-2022 Interviews 2020 to 2022 date-range 47 Operator interviews from the early scaling era
deep-dives-payments Deep dives, payments topic 23 Long-form essays on payments infrastructure
schema-guides Schema markup guides topic 18 Every guide on JSON-LD and structured data
foundational-essays Foundational essays curated 12 Posts that shaped the site's thesis
reader-favorites Reader favorites curated 30 Most-cited posts by readers and other writers
URL pattern: /archive/{slug}/
Generated pages
  • /archive/interviews-2020-2022/
  • /archive/deep-dives-payments/
  • /archive/schema-guides/
  • /archive/foundational-essays/
  • /archive/reader-favorites/

Comparison

WordPress default archives vs SleekRank

Built-in date and category archives

  • Default archives auto-list everything with no editorial framing
  • Year and month archives mix posts of wildly different quality
  • Category archives ignore curated cross-topic groupings
  • There is no place for a framing intro on a default archive
  • Custom scopes (interviews 2020 to 2022) cannot live on one URL
  • Default archives often get noindexed because they offer no editorial value

SleekRank

  • One scope row drives one indexable /archive/ URL
  • List mapping renders only the curated entries for that scope
  • Selector mapping injects framing intros per archive
  • Tag mapping handles label and entry count
  • Sitemap exposes every scoped archive page
  • Default WordPress archives can stay noindexed

Features

What SleekRank gives you for archive index pages

Scope rows

Each row in the archives sheet defines a single archive scope by slug. A scope_type column lets selector mapping branch between date-range, topic, and curated framing. Adding a new archive scope is a single row append.

Curated entry lists

Each scope row carries either pipe-separated entry slugs or references a sub-sheet of included posts. List mapping over that set renders only the curated entries, not every post that happens to share a tag or date.

Framing intros

Selector mapping injects a per-archive framing intro into a designated container. Editors write a sentence or two explaining why this archive exists, which turns a list page into something worth indexing on its own.

Use cases

Where archive index pages fit on SleekRank

Long-running publications

Sites with years of archives publish curated scopes: "interviews 2020 to 2022", "essays on growth". Readers and search engines see editorial surfaces instead of auto-listed date archives no one bookmarks.

Content site backcatalogs

Content sites surface their backcatalog through scoped archives instead of relying on tag pages. Each scope earns its own intro, link list, and indexable URL targeted to a specific reader research path.

Editorial reading lists

Teams publish curated reading lists as archive scopes: "the canon", "start here". Each list lives at /archive/{slug}/ with a framing intro and a curated entry list, easy to bookmark and share.

The bigger picture

Why curated archives beat default WordPress archives

WordPress's built-in archive pages exist for completeness, not for editorial quality. They render a tag or date list with the theme's default loop and nothing else: no intro, no framing, no curation. Most serious sites end up noindexing them because they offer search engines no editorial value and they often compete with better URLs the editor actually cared about.

SleekRank inverts the pattern. An archive becomes an explicit editorial object with one row in an archives sheet. The scope is named, the framing intro is written, the included entries are chosen by hand or by query result.

"Interviews 2020 to 2022" is a deliberate editorial archive that does not exist by default in WordPress because no native taxonomy matches that scope. SleekRank turns it into /archive/interviews-2020-2022/ with a framing paragraph, a curated list, and structured data tagging it as a CollectionPage. Multiple archives can include the same entry, which is impossible cleanly with WordPress's single-canonical taxonomy model.

The archives sheet becomes the editorial index of the site, with one row per surface the editor wants to highlight. That structural difference (explicit curation versus default auto-listing) is what makes scoped archive pages worth indexing instead of hiding from search.

Questions

Common questions about SleekRank for archive index pages

Default category archives include every post under a term with no editorial intro and no curation. SleekRank archive scopes are explicitly listed: one row, one framing intro, one curated entry list. Two archives can include the same post if its slug appears in both rows.

 

Often yes. If your scoped /archive/{slug}/ pages are the canonical surface for grouped content, default date and category archives compete with them. Use a SEO plugin to noindex defaults and let SleekRank-rendered archives take over for indexed grouping pages.

 

Yes. The list mapping reads each scope row's entry list independently. A post can appear in /archive/schema-guides/ and /archive/reader-favorites/ without duplication issues since each archive URL is a curated index, not a canonical home for the post.

 

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; every new scope row joins the index after the next rewrite flush.

 

Edit the entry list cell on the scope row to add or remove slugs. Flush the SleekRank items cache and the archive page reflects the change. The URL stays the same; only the curated list updates.

 

Yes. Add a CollectionPage JSON-LD block to the base template and inject row-specific values like name, description, and an itemListElement built from the entries. Each /archive/{slug}/ renders its own structured data sourced from its row.

 

Yes. Use meta mapping at og:image pointing to a per-row image URL, or pair with SleekPixel and a templated suffix so each /archive/{slug}/ renders its own preview showing the archive label and count without manual asset work per scope.

 

Delete the row from the archives sheet. Flush the cache and the URL stops resolving. If the page had inbound links, add a 301 in your redirect plugin to a parent hub or related archive to preserve link equity for the retired scope.

 

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