Clothing catalogues often change faster than most. At many retailers new lines arrive every few weeks, and a season’s stock sells through and is gone. Meanwhile one dress can appear in New In, Dresses, Occasionwear and Sale at the same moment. Every listing page offers filters for size, colour, fit, length, fabric and price. Search engines have to make sense of all of that, and they can end up crawling sale filters and expired styles while this week’s arrivals wait.

This guide applies Google’s documentation to the problems fashion retailers actually face. Each Google rule is linked to its source page where it first appears, and my own opinions are labelled as mine.

What happens to last season’s URLs

Two kinds of page go stale in fashion: products that sell out for good, and seasonal collection pages such as a summer edit or a festival shop.

Collection pages are categories, and Google’s ecommerce URL guidance covers them. An empty category can be marked noindex, or return a 404 once it has been removed for good. That fits a finished seasonal edit well.

Individual products are a different matter, and that guidance is not about them. My own approach for a style that will not return:

  • If it has links from press or social, or still gets search visits, redirect it to the closest live category or a successor style.
  • If it has neither, let it return a 404.
  • If it will be restocked, keep the page live and mark it out of stock.

I also advise keeping seasons out of category URLs. /dresses/midi/ can collect links for years, while /ss26-midi-dresses/ has a shelf life of months. Most of this pays off at replatforming time, when old URL patterns need mapping; my SEO migration service covers that work.

One dress, several category paths

A dress in the sale and in occasionwear should still have one product URL. Some platforms, Shopify among them, can link to a product through a collection path as well as through its own address. That can give Google several URLs for the same garment.

Google’s canonical documentation lists the ways to show which URL you prefer, from strongest to weakest: redirects, rel="canonical" and sitemap inclusion. It recommends a self-referencing canonical on the preferred page and internal links that point straight to it. It also lists things not to do:

  • Do not use robots.txt to choose a canonical. A blocked URL can still be indexed, just without its content.
  • Do not use noindex to pick a canonical within your own site.
  • Use absolute URLs in canonicals, not relative ones.

Campaign links cause the same problem from outside. Influencer, affiliate and email links often carry tracking parameters. Google’s canonical example takes a URL with ?gclid= and points it at the clean product URL. Its URL guidance adds that internal links should never use parameters that change per visit, such as session IDs or tracking codes.

Listing pages and their filters

A clothing category might filter by size, colour, fit range, length, neckline, sleeve, fabric, occasion and price, often with several values selected at once. Google’s faceted navigation guide warns that crawling these combinations costs server resources and slows discovery of new URLs. For a retailer adding new styles weekly, slow discovery is the real cost.

A few filter combinations match how people shop: black midi dresses, linen trousers, wide-leg jeans. Build those as category pages with their own copy, a clean URL and a place in the navigation. For the rest, Google’s options are to block filter parameters in robots.txt, keeping one unfiltered listing crawlable, or to hold filters in a URL fragment. Google’s robots.txt example blocks color= and size= parameters. A canonical to the unfiltered page, or nofollow on filter links, are weaker options in the long run, and nofollow only helps if every link to that URL carries it.

If filter URLs remain crawlable:

  • separate parameters with &;
  • for multi-select filters, combine values in one key instead of repeating it, as in Google’s example ?type=candy,sweet;
  • for filters written into the path, keep the order consistent and stop the same filter appearing twice;
  • return a 404 at the URL for combinations with no products.

Pagination and “load more”

Large categories run to many pages of products. Google’s URL guidance asks for a unique URL for each paginated page and a self-referencing canonical on each indexable page. Use one form of the first page everywhere: either always include ?page=1 or never include it.

Links need to be real <a href> links rather than script-driven navigation. A “load more” button that fetches the next batch only through JavaScript leaves those products with no crawlable path from the category. My preferred fix is to back the button with a normal link to ?page=2, so it works with or without scripts.

Size, fit and colour in product markup

Google’s product variant markup uses ProductGroup, hasVariant and variesBy. The allowed values cover colour, size, pattern, material, suggested gender and suggested age. Pattern suits named prints, and suggested age suits kidswear.

Fit ranges such as petite, tall, plus and maternity have no value of their own. A petite version is often cut from its own pattern and listed as its own product. I suggest treating each fit range as a separate product group when it has its own search demand, and folding it into the size value when it does not.

Colour choices depend on the range. A basic T-shirt in twelve colours suits Google’s single-page set-up, where each colour must be preselectable through its own URL and addable to the bag. Distinct named prints may each justify their own page under the multiple-page set-up.

Sale pricing needs care in merchant listing markup:

  • Use an Offer, not an AggregateOffer, with a price above zero.
  • If you set priceValidUntil, keep it current. Google says a listing may not show when that date is in the past.
  • Define shipping and returns once under Organization. Each offer can reference that policy, with an offer-level override only for lines with different terms.

On-model photography and video

Fashion photography is usually portrait. Google recommends merchant listing images in 16:9, 4:3 and 1:1 ratios, each at least 50,000 pixels in total. Plan those crops at the shoot rather than squeezing a portrait frame afterwards.

Google’s image SEO guidance calls alt text the most important image metadata. Describe the garment rather than the model: “Ivory linen wide-leg trousers, front view on model” helps a screen reader user and helps search. Some useful rules for clothing sites:

  • Second images that appear on hover are sometimes built as CSS backgrounds, and Google does not index CSS images.
  • Text-heavy campaign banners make poor preferred images. Point Google at the product photo using primaryImageOfPage or og:image.
  • If images are served from a CDN domain, an image sitemap can still list them. Verifying the CDN in Search Console shows its crawl errors.

For catwalk or on-model video on the product page, Google’s ecommerce structured data overview recommends VideoObject.

Fashion SEO checklist

  1. In Search Console, look for indexed sale filters, sold-out styles and collection-path product URLs.
  2. Open one product from three different categories and note the URL and canonical each time.
  3. Compare robots.txt with the filter parameters your listing pages use.
  4. Request a filter combination with no products, such as an unstocked size in a niche colour, and check for a 404.
  5. Turn JavaScript off and try to reach page two of a large category.
  6. Run a sale item through the Rich Results Test and check the price, offer type and priceValidUntil.
  7. Review last season’s collection pages and decide which to keep, noindex or remove.
  8. Search your templates for internal links that carry tracking parameters.

Lighthouse’s SEO checks were kinder to the five fashion pages I tested in October 2026 than its speed checks. Two scored 100. The other three scored 92, each losing points on one check: images without alt text, links Lighthouse could not crawl, or an invalid robots.txt file. The robots.txt result deserves attention on a clothing site, since step 3 depends on that file to keep filter parameters out of the crawl. A file with errors may not block what you expect. Lighthouse’s SEO audit is a short list of basics, so it says nothing about canonicals, variants or sale pricing.

For how clothing sells online more broadly, see selling fashion online. Listing pages with heavy grids and campaign images are covered in fashion website performance. For made-to-measure and personalised garments, see the clothing configurator. If you would like this done for your shop, see ecommerce SEO and my technical SEO audit.

Sources

Google documentation consulted for this fashion guide, checked October 2026:

My own tests: PageSpeed Insights, 5 UK product pages per industry, 23 October 2026 (the Lighthouse SEO results for fashion pages above).