A collection is a deliberate editorial grouping of items: "summer 2026 capsule", "under-$50 gift guide", "posts that shaped our pricing philosophy". Each one has a theme, a curator's intro, and a curated item list. WordPress categories and tags do not capture this pattern cleanly because a single item can belong to several collections without being its canonical home.

SleekRank reads a collections sheet keyed by slug with columns for label, theme, intro, cover image, and the included items (pipe-separated slugs, IDs, or a referenced sub-sheet). Each row drives /collection/{slug}/ on a shared template, with tag mappings handling label and item count, selector mapping injecting the intro and cover, and list mapping rendering the items.

Adding a collection is a single row append. Editing an item list is one cell. The base WordPress page is auto-noindexed; only the collection pages compete in search. Generated URLs land in SleekRank's sitemap on the next rewrite flush.

WordPress's category model treats grouping as canonical: an item gets one main category that becomes its archive home. Sites that want to publish multiple editorial groupings end up either creating dozens of overlapping categories (which fragments the canonical model) or stretching tags well beyond what they were designed for. Either way the resulting archive pages have no editorial framing, no curator credit, no seasonal identity.

SleekRank treats collections as editorial objects, not taxonomy. Each /collection/{slug}/ is one row in a curation sheet with its own theme, intro, cover, and curated item list. Items appear in collections by slug reference, never by canonical assignment, so a single product or post can show up in any number of collections without taxonomy conflicts.

Editors publish a new collection ("summer 2026 capsule", "gift guide under $50", "pricing essays") by appending one row. They retire it by deleting the row. Cover image, framing intro, curator credit all live in the same row, rendered via selector mapping into the same base template.

The collections sheet becomes the editorial index of curated surfaces on the site, totally decoupled from item-level taxonomies. That decoupling is what makes collection pages a different shape from category archives, and worth indexing on their own.