The new collections model, in detail
Until now, a Shopify collection fell into one of two categories: a manual (custom) collection, where you pick products one by one, or an automatic (smart) collection, driven by rules that decide what qualifies. It was one or the other — combining both inside a single collection wasn't straightforward.
The new model, published in the 2026-07 GraphQL Admin API (changelog dated June 17, 2026), replaces that split with "sources": a collection can now combine several sources at once — automatic conditions, manual selections, exclusions, or even another collection entirely as a source. Three structural changes, as described in Shopify's announcement to partners:
- Multiple sources. A single collection can now mix automatic rules (say, products tagged "summer") with a hand-picked manual selection of featured products, plus the ability to explicitly exclude specific products — something the old model couldn't do within one collection.
- Variant-level targeting. A collection can now target specific product variants instead of entire products — for example, showing only the red variants of an item that comes in multiple colors, or only certain sizes.
- Sub-collections. A collection can use one or more other collections as a source, staying automatically in sync as those source collections change.
Existing collections keep working without modification, and migration to the new model is incremental — nothing forces a merchant to rebuild anything right away.
Why Shopify is making this change
According to Shopify, the old model forced a binary choice that few merchants found satisfying: either automation or manual control, rarely both at once within the same collection. A sale collection, for instance, often needs automatic rules (discounted products) while also excluding certain categories and featuring a handful of hand-picked items — a need the old model never covered cleanly, forcing workarounds.
The change also opens the door to what Shopify calls "shareable sources": third-party apps can now publish their own product sources — a reviews app that surfaces the best-rated products, or a subscription app that identifies top recurring sellers — that merchants can add directly to their native collections, instead of duplicating that logic in a separate system outside Shopify's own collections.
What this means for your SEO
Shopify doesn't present this change as an SEO update — it's primarily a data-model change aimed at developers and apps. But several of its implications touch the structure of your collection pages directly, and deserve the same caution as everything else on this blog: what follows is our own reading of the change, not a claim made by Shopify.
Sub-collections open up a new way to build "hub" pages — a broad collection that aggregates several more specific ones, staying up to date automatically, without manually re-copying the product list every time the catalog changes. That's a useful tool for building a page that covers a broad category while letting the more specific collections exist on their own — a principle already central to thinking in terms of programmatic SEO. It's also, if used carelessly, a new way to create a page whose scope nearly duplicates another one: a sub-collection that's too close to one of its source collections reproduces exactly the problem we cover in our guide on Shopify keyword cannibalization. The risk isn't in the feature itself — it's the same discipline that's often already missing today: checking that a new page doesn't overlap an existing one before publishing it.
Variant-level targeting improves how precisely a collection's contents match the keyword it's built around. A "[color] [product]" collection can now contain only the genuinely relevant variants instead of the entire product with every variation, reducing the risk of showing off-topic items in the grid. One important detail: this doesn't create a new URL per variant — the collection remains a single page, only its contents become more precise.
Shareable sources for apps mean the content of a native collection could, going forward, be shaped by several different apps at once — reviews, subscriptions, recommendations — without any of them duplicating the page in a parallel system. That's potentially good for site coherence, provided the merchant keeps a clear view of what's contributing to each collection.
What hasn't changed (yet)
For now, this is an API-level change. Existing collections aren't automatically converted, and nothing in the sources Shopify has published indicates that the standard admin's collection editor already exposes all of these new capabilities in a few clicks for every merchant, as of this writing. How quickly it shows up in the interface depends on how fast Shopify rolls it out natively and how fast App Store apps adopt the new API — two timelines we can't predict on Shopify's behalf.
One technical detail worth knowing if you or your agency build on the Shopify API: a collection using the new capabilities (multiple sources, exclusions, variant targeting) simply isn't visible to an integration still querying an API version older than 2026-07 — it gets filtered out of the results rather than returning an error. Worth watching if several apps act on the same collections.
What to do now
For most merchants managing collections from the standard admin, no immediate action is needed: your existing collections keep working normally, and nothing forces a migration. The thing to watch is mainly for stores that rely on one or more third-party apps to create or manage collections — including programmatic SEO apps: checking, as updates roll out, that those apps stay compatible with the 2026-07 API version avoids unpleasant surprises the day you start using shareable sources or sub-collections.
Summary
Shopify's new collections model replaces the manual-or-automatic split with a multi-source system, adding variant-level targeting and synced sub-collections. It's an API-level change available since June-July 2026, rolling out incrementally, that opens up new structuring options — and a new cannibalization risk if sub-collections are used without checking their scope against existing collections. Shopify hasn't attached any ranking or traffic promise to this change, and neither do we.