Collection pages: the most visited and the least written

They are the most visited pages after the home page and the only ones nobody has ever written. They answer the most common question of all, which is not “this product” but “which of these”. What to put on them, and where.

On almost every ecommerce site, collection pages are the most visited after the home page, they carry a significant share of search traffic, and they are also the only pages on the site nobody has ever written. They contain a heading generated from the category name and a grid of products.

That is odd, because they are also the pages answering the most common question of all: not "this product", but "which of these".

The question they answer

Somebody landing on a product page has already chosen. Somebody landing on a category is still choosing, and wants three things a grid does not give.

How to choose. Which two or three criteria actually matter in that category, and which look important but are not.

What changes between price brackets. Why one costs thirty and another a hundred and twenty. If you do not explain it, buyers use price as the only criterion, and often end up on the cheapest or the dearest by elimination.

What happens after the purchase. Maintenance, spare parts, future compatibility. These are the questions that block considered purchases and that no product page addresses, because they belong to the category rather than the item.

Where the text goes

There is an ugly tradition: the three-hundred-word paragraph shoved under the grid, written for engines and read by nobody. It serves no purpose, and it shows.

What works is a short guide above the grid, a few lines, saying how to orient yourself, plus optionally something longer at the bottom for anyone who wants depth. Help above, depth below. Not the other way round.

Filters are content, not interface

Here is the connection almost nobody makes: a collection page's filters only work if product attributes are populated. A material filter on a catalogue where the material field is empty on seventy per cent of products is not a broken filter, it is worse: it hides products that would have suited.

And the most-used filters tell you which categories deserve to exist on their own. If in "backpacks" the most-used filter is "for laptops", that is a page that should exist, with its own address and its own text, instead of being a filter combination nobody can link to or find on Google.

The technical problem not to ignore

Every combination of filters and sort orders typically generates a different address, and on a catalogue with a few attributes the combinations run into thousands. Left free, they produce an enormous number of near-identical pages, and engines treat them as what they are: noise.

The practical rule is to choose: a few combinations with genuine demand become indexable pages with their own text; all the others stay navigation tools and are declared as such. Letting them all be indexed is the fastest way to dilute a site.

What can be done in an afternoon

Take the five categories bringing the most traffic and add three lines above each grid saying how those products are chosen. Then look at which filters get used most and which attributes are empty.

It is modest work and it produces two results at once: pages that help whoever reads them, and the list of fields to fill in the catalogue.

How Uptonica handles this

Product fills attributes across the whole catalogue, which is the condition for a category's filters to work at all. Content writes the collection page text from that same data rather than from a generic prompt.

See what Product does

Frequently asked questions

How much text does a collection page need?

Little, and at the top. Three or four useful lines above the grid are worth more than three hundred words below it. If you have something long to say about that category, it is probably a guide in its own right, linked from the category.

Many narrow categories or a few broad ones?

Many narrow ones, but only where demand exists. A category created because it looks tidy in the menu, and that nobody searches for, is one more page to maintain with no return.

Do collection pages compete with product pages?

They answer different questions, so generally no. A category answers "which", a product page answers "this one". They compete only when the category is so narrow it holds a single product, and then it is worth choosing which of the two to keep.

Should out-of-stock products be removed from the category?

Not immediately and not silently. A product out of stock but on its way is worth more shown with the date than hidden, because it catches whoever was looking for it. What to avoid is an unexplained gap.

Should I rewrite categories that bring no traffic?

Not first. But mind the order of the reasoning: some bring no traffic because they do not deserve any, others because they have never had a line of text. The second kind is worth it, and you tell them apart by checking whether anybody searches for that subject.