Bags and luggage are bought on measurements as much as on looks. A buyer wants a cabin case that fits an airline’s allowance, a backpack that takes a 16-inch laptop, or a holdall with enough litres for a long weekend. Those numbers are often the words they type into search. A product page that keeps them in a spec image or a PDF risks missing that search.

Luggage adds sets, materials and colourways on top. Bags also sit in overlapping categories by use: travel, work, school and gym. This guide works through each problem using Google’s documentation. Where something is my recommendation rather than a Google rule, it is labelled as mine.

Size and capacity are the search terms

Luggage searches often include a number or a size name: cabin, underseat, medium, large, or a set of dimensions in centimetres. Laptop bags are often searched by screen size. Rucksacks and holdalls are often compared by capacity in litres.

My advice is to show every one of those figures as text near the top of the product page, then repeat them in a full specification table:

  • external dimensions in one consistent order, usually height, width and depth, with wheels and handles included;
  • empty weight, which matters to anyone flying with a weight limit;
  • capacity in litres, and the expanded figure if the case expands;
  • the largest laptop the sleeve takes.

Size groups with real demand, such as underseat bags or 15-inch laptop backpacks, are best built as category pages with their own copy and a clean URL. A filter URL is a poor substitute.

Range sliders for height or capacity are a particular risk. Each position can produce a different URL, so the number of crawlable combinations can run very high. Google’s faceted navigation guide gives two ways to keep filters out of the crawl: block the filter parameters in robots.txt, keeping one unfiltered listing open, or hold the filter state in a URL fragment. Either suits a slider.

Sets, single pieces and the offer markup

A luggage range often comes as cabin, medium and large, plus a set of two or three. These need different treatment.

In my view, the individual sizes are variants of one product. Google’s product variant documentation handles them with a ProductGroup, a hasVariant list and variesBy set to https://schema.org/size. In the single-page set-up, each size must be preselectable through its own URL, show the right image, price and availability, and be addable to the basket.

A set is better treated as a separate product, with its own page, SKU and price, linking to the pieces it contains. The markup supports that view. Google’s merchant listing documentation allows only one value for inProductGroupWithID, so in the markup a cabin case cannot sit in its range’s group and a set’s group at once.

Price markup needs checking on luggage ranges. A theme that shows “from” a starting price may mark the range up as an AggregateOffer with a low and high price. Merchant listings need an Offer, because the merchant must be the seller, and the price must be above zero. Give each size its own Offer at its own price.

Leather, canvas and colour

Many bag designs come in more than one material, such as full-grain leather, waxed canvas or recycled nylon. The material changes the price, the weight and the care instructions. Colour then varies within each material.

Google’s allowed variesBy values include material, colour and pattern, so these fit the markup directly. The page structure is a judgement call:

  • Where a leather version has its own search demand, give each material its own page under the multiple-page set-up. A leather weekender sold beside a canvas one is a typical case.
  • Colours within one material usually belong on one page.

Leather colour names cause their own small problem. A page might say cognac, chestnut or tan, while the filter groups them all as brown. I suggest using the shopper-facing name on the page and in the markup’s color, and mapping it to a simple colour family for filters.

Every variant needs a unique sku or gtin, and the group needs its own ID. For WooCommerce, my WooCommerce structured data guide covers how plugins handle this.

Use-based categories and feature filters

One backpack may sit in travel bags, work bags, laptop bags and school bags. Google’s canonical documentation recommends a self-referencing canonical on the preferred URL and internal links that point to it. Google’s URL guidance adds that internal links, sitemaps and canonicals should all use the same form of URL. A product should therefore keep one address, whichever category it is reached from.

Feature filters multiply quickly in this trade: spinner wheels, hard shell, built-in lock, expandable, USB port, RFID pocket and water resistance. A few combinations are likely to match real searches, such as hard-shell cabin cases. Build those as proper category pages. For the rest:

  • block the parameters in robots.txt, or keep filters in a fragment;
  • if filter URLs stay crawlable, return a 404 at the URL for combinations with no products;
  • for filters in the URL path, keep their order consistent and stop the same filter repeating.

Interior shots, scale and video

Bag buyers want to see inside: the compartments, the laptop sleeve, how much fits. They also want a sense of size on the body or in the overhead locker. Google’s image SEO guidance has several points that apply:

  • Use <img> elements. Google does not index images set as CSS backgrounds, which some zoom galleries use.
  • Write alt text that says what the photo shows: “Interior of a 40-litre holdall, showing the separate shoe compartment” rather than “inside view”.
  • Place images near the text they relate to, so the dimensions diagram sits beside the specification table.
  • Feature graphics covered in text callouts make poor preferred images. Point Google at a clean product shot through primaryImageOfPage or og:image.

Merchant listing images must be crawlable and indexable. Google then recommends several high-resolution shots of at least 50,000 pixels, ideally in 16:9, 4:3 and 1:1 versions. A packing or walkthrough video on the product page can carry VideoObject markup, which Google recommends in its ecommerce structured data overview.

Monogramming and personalised builds

Initials, luggage tags and strap choices turn one bag into thousands of possible builds. None of them should be an indexable URL. Keep the personaliser on the canonical product page and store a build in a fragment or a saved-build link, as covered in save and share product configurations. The product page still needs crawlable text, images and markup that do not depend on the personaliser’s script.

Returns terms for personalised items may differ from the rest of the range. Google’s merchant listing documentation allows a returns policy at organisation level, which offers can reference, and a policy on the individual offer where the terms are different.

Bag and luggage SEO checks

  1. Open a cabin case page and check that its dimensions, weight and capacity appear as text, not only in an image.
  2. List every URL a luggage range produces: sizes, sets and colours. Check each canonical.
  3. Run a range page through the Rich Results Test. Look for an Offer per size, each above zero, and no AggregateOffer.
  4. Reach one backpack through three different categories and confirm it keeps one URL.
  5. Move a capacity or height slider and see what URL it creates, and whether robots.txt blocks it.
  6. Check that interior and scale photos are real images with alt text that describes them.
  7. Build a monogrammed bag and confirm the result is not an indexable page.

The bag and luggage pages I tested in October 2026 did well on Lighthouse’s SEO checks: three of the four that loaded scored 100. The fourth scored 61. It was blocked from indexing and had links Lighthouse could not crawl. A product page kept out of the index can be deliberate, but confirm that yours are not. The fifth product URL returned a 404, a broken link of the kind discontinued colours and ranges can leave behind. Lighthouse checks only a few basics, so dimensions, offers and filters all fall outside it.

For the wider picture of selling bags online, see bag and luggage ecommerce. Galleries, videos and personalisers also affect speed, covered in bag and luggage website performance. The bag configurator page covers personalisation tools. If you want an audit of your own site, see ecommerce SEO.

Sources

Google documentation behind this bags and luggage guide, checked October 2026:

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