§ 01 The decay
The decay problem in apparel collections
Apparel brands launching seasonal drops accumulate /collections/ URLs at a rate no other vertical matches. A brand with two seasonal lines per year, monthly capsule drops, and rolling collaborations adds 12-20 collection URLs per year — most of which become 'dead' inventory within 90 days as the products sell through or get moved to the main catalog. Five years in, a mid-sized apparel brand has 80-120 dead collection URLs, each emitting weak signals to Google and the AI engines.
The decay is structural. A 'Spring/Summer 2025' collection makes sense at launch, sells through over 2-4 months, and then exists as an empty or near-empty URL with most of the original products either out-of-stock or repurposed into the main catalog. The AI engines reading Shopify Catalog see the collection title, the products it currently contains, and the products it once contained as conflicting signals. Shopify's automatic-sitemap-update behavior3 means the dead URLs stay in the sitemap until manually addressed.
§ 02 The decision tree
Redirect vs noindex vs archive — the decision tree
Three options per dead collection. Redirect to the evergreen canonical when the collection's products have a clear long-term home ('Spring/Summer 2025 Dresses' redirects to '/collections/dresses' once SS25-specific URLs are no longer driving traffic). Noindex while keeping accessible when the collection still receives email or paid traffic but should not compete in organic search (use the seo.hidden metafield or theme.liquid handle condition). Archive cleanly with a /collections/archive/ pattern when the collection has historical or editorial value and should be preserved as a brand asset.
The redirect path is the highest-leverage option for most dead collections. Shopify's SEO FAQ4 documents the indexing-update timing (48-72 hours typically), and a 301 redirect from a dead seasonal URL to an evergreen canonical preserves whatever link equity the dead URL accumulated. The noindex path is the right choice when the URL has active retargeting pixels or active paid traffic — the seo.hidden metafield2 or a theme.liquid handle condition removes the URL from organic search without breaking the existing traffic flows. The archive path is the right choice for collaborations or capsule drops that carry editorial value — moving the URL under a /collections/archive/ structure preserves the brand history while signaling clearly to crawlers that the content is historical.
§ 03 Evergreen structure
Evergreen collection structure vs drop structure
Two collection structures coexist on most apparel sites. Evergreen collections ('Dresses', 'T-Shirts', 'Outerwear') are the long-term canonicals — they accumulate link equity, AI-citation signal, and product organization weight over years. Drop collections ('SS25', 'Fall Capsule', 'Holiday 2025') are short-term marketing constructs — they drive seasonal traffic but lose value within 3-6 months. The install treats the two differently: evergreens get long-form content, schema, and consistent product membership; drops get clean launches and clean retirements.
The Shopify Catalog optimization doc5 lists Product organization (including Collections) as one of the AI-readable fields, and the evergreen collections are the ones the AI engines weight most for category-level queries ('show me wide-leg trousers'). Drops compete for branded and seasonal queries ('Pangaia SS25 collection') but rarely rank for category-level queries. The install structure: evergreen collections carry rich descriptions, FAQs, and schema; drop collections carry concise launch copy, a clear seasonal date in the title, and a predefined retirement strategy.
§ 04 Schema
Collection schema and breadcrumb hygiene
Shopify themes auto-emit BreadcrumbList JSON-LD for collection pages, which is the schema surface AI engines and Google parse for navigation context. The install verifies the breadcrumbs reflect the actual taxonomy (Shop > Dresses, not Shop > Spring 2025 > Dresses unless the seasonal structure is intentional), adds CollectionPage schema where appropriate, and ensures the collection URL canonicalizes correctly per Shopify's auto-canonical behavior.
Breadcrumb hygiene is the under-discussed half of collection SEO. A collection URL nested under a seasonal parent breadcrumb sends a different signal than the same URL nested under a category parent — and most theme defaults pick one without merchant input. The install checks the breadcrumb path on every collection, ensures the path matches the intended taxonomy, and corrects via theme code or metafield where the default is wrong. CollectionPage schema is optional but useful for evergreen collections that warrant their own editorial content (long-form description, curated lookbook, styling guide).
§ 05 The archive
The rolling archive — what to keep for AI citation
The rolling archive is the strategic asset most apparel brands underuse. Dead collections that carry editorial weight (notable collaborations, signature capsules, runway-shown drops) compound brand-citation signal in AI engines if archived cleanly rather than 301'd away. The install creates a /collections/archive/ pattern with metadata-rich pages for each archived drop, linked from the founder or about page, indexed but not crawled aggressively.
The choice between 301 and archive is editorial more than technical. A generic SS25 drop with no signature pieces redirects to the evergreen — there is no compounding value in keeping it. A signature collaboration with a notable artist, a runway-shown capsule, or a sold-out limited-edition release archives — the URL stays accessible, carries the drop's editorial content, and accumulates citation signal as the brand history matures. The install audits the existing collection set, categorizes each as redirect / noindex / archive, and applies the chosen treatment in a single migration sweep.
