Your learning path: 93 lessons.
Module 13 / Lesson 71 · Read, apply, check
Classify variant and filter URLs before deciding which pages should be discoverable and indexed.
List product variants, sort orders, filters, pagination and tracking parameters separately. Similar-looking query strings can serve different purposes. Identify what the customer sees at each URL and whether the state can be opened directly, rather than deciding solely from the parameter name.
A useful filtered collection may deserve a stable page when it serves distinct demand and contains worthwhile inventory. Every possible combination does not. Decide which combinations should be maintained as search destinations before allowing navigation to generate an unlimited crawl space.
A canonical suggests a representative for duplicate or similar content. A noindex directive concerns indexing and needs to be seen by the crawler. Robots restrictions concern crawling. Combining these controls without understanding their interaction can prevent the intended instruction from being processed.
Open a product variant directly and verify the selected item, image, price and availability. Test filters with useful inventory, empty combinations and different sort orders. Work with the platform owner on a scoped rule rather than applying a broad robots change from one example.
Same inventory in a different order; usually not a new shopping purpose.
Distinct maintained range with real customer value.
Must open the intended size or color with matching facts.
No useful inventory; inspect platform behavior rather than indexing blindly.
Hypothetical example: a clothing store has size and color variants, a price sort parameter and thousands of filter combinations. The merchandiser wants a stable collection for waterproof jackets because it represents a useful range, but not a search destination for every size-color-price permutation. The technical lead inventories the patterns, checks direct variant URLs and documents how each changes the page. A sort-only URL does not create a new product range, while the intentional waterproof collection has a maintained purpose. The team tests representative pages before changing navigation or directives. Its deliverable is a URL policy supported by examples, not a blanket instruction to block every URL containing a question mark.
A developer blocks all parameter URLs in robots.txt and then adds noindex directives to the same pages, expecting Google to read them immediately. The crawling restriction can prevent those page-level instructions from being seen. Another developer canonicalizes every variant to an unrelated category. Both shortcuts confuse different controls. The remedy is to classify the actual page states and choose a consistent treatment with the platform maintainer.
Misconception: every filter creates a valuable landing page. Combinations can multiply faster than useful customer demand or editorial maintenance. Deliberate collections and accurate variant behavior matter more than making every generated URL indexable.
Large catalogs and platform constraints require technical review. This lesson produces a proposed policy and sample checks; it does not authorize deploying site-wide crawl restrictions without a tested implementation and monitoring plan.
Do this today · 40 minutes
Classify variant and filter URLs before deciding which pages should be discoverable and indexed.
A sample URL inventory or read access to a test catalog; technical changes require the platform owner.
Examples: /jackets; /jackets?sort=price; /jackets?waterproof=yes; /coat?color=blue; /jackets?size=xxs&color=orange with no inventory.
Before: “Block every parameter URL.”
After: A reviewed policy distinguishing sort orders, useful collections, variants and empty combinations.
Notes stay in this browser. Download a copy to keep them.
After an approved change, check representative responses and search indexing evidence; investigate unexpected product-discovery losses before expanding the rule.
Before you move on
A store has sort-only URLs, useful curated collections and product variants. A developer proposes blocking every parameter URL while also relying on page-level noindex instructions there. What should the SEO lead do before approving the change across the catalog?
Next lesson →Google: Ecommerce URL structure
Lesson edition 1 · References reviewed 15 October 2026 · Practical exercise reviewed 15 October 2026. Examples are illustrative teaching scenarios.
Free learning. Informed choices.
Built for aspiring SEO directors, existing practitioners and business owners who want to turn sound judgment into practical results.
Course hub · Free skills assessment · Privacy
No Sitetrail account is required. Course progress and assessment results are saved in this browser when storage is available; they do not sync to the app. Download your worksheets and certificate to keep your own copies.
Your free trial starts automatically. No license key is needed yet.
