If you manage category pages, tag archives, or blog topic pages for a client, you have probably had this conversation: someone flags a category page as thin content, and the fix everyone reaches for is "add more words above the grid." That is the wrong move more often than not. A category page does not need a word count. It needs a short, page-specific job done well: tell the visitor what the collection is, help them choose within it, and answer the one or two questions that are actually particular to this collection. Below is a copyable template you can run across every client's category page content and tag page SEO work, plus the reasoning behind each field so your team fills it in instead of padding it. It works the same way whether you are writing ecommerce category page optimization copy for a product grid or orienting a reader on a blog topic archive.
The template
Copy this. Fill in the bracketed fields for a single category, blog category, or tag or topic archive. Skip a block entirely when it would only repeat another block on the page.
PAGE TYPE: [product collection / blog category / topic or tag archive]
PAGE TOPIC AND VISITOR TASK: [what visitors expect to find or decide here]
PAGE-SPECIFIC ANGLE: [what distinguishes this collection from its neighbors]
H1: [plain-language name for this collection]
SHORT INTRO ABOVE THE LIST:
[What is collected here? Who is it for? What can visitors do or find here?
Mention a meaningful distinction or selection criterion particular to this page.]
PRIMARY LIST:
[Visible, clearly labeled products or articles. Make each entry understandable
without requiring the visitor to open it merely to discover what it covers.]
CHOOSING OR BROWSING GUIDANCE, IF NEEDED:
[Choice 1: which need, reader, use case, or question does it serve?]
[Choice 2: how does it differ from Choice 1?]
[Important limitation, compatibility question, or exception to check.]
[Point to the appropriate product, subtopic, or article where the answer lives.]
PAGE-SPECIFIC FAQ, IF NEEDED:
Q: [A real question visitors have about choosing within this collection.]
A: [A direct answer, with qualifications and a next move where useful.]
Q: [A second distinct question, if one exists.]
A: [A direct answer.]
EDITORIAL CHECK:
[Can someone tell what belongs here, distinguish the relevant options,
and take a useful next step without reading another generic introduction?]
This is an editorial template, built from how category page SEO and tag page content actually need to work, not a list of Google requirements. Nothing in it is a ranking formula. It is a way to make sure a page-specific job actually gets done, client after client, without you or a writer reinventing the checklist each time.
What goes in each field, and why
H1 and intro: name the collection, not the taxonomy label
The H1 should be the name a visitor would recognize, not the internal label your client's catalog uses. The intro above the list has one job: orient someone who just landed on this particular collection, not the category next to it. A fast way to test a draft intro is to swap in a neighboring category's name. If the sentence still reads fine, it was never specific to this page and needs to name something real about this one, an intended use, a compatibility note, the kind of questions the posts here actually answer.
Google's own guidance backs this up directly: it recommends category descriptions for less specific shopping queries, because a description helps match a browsing query to the right collection. It also states plainly that there is no minimum, maximum, or preferred word count for ranking. Those two facts sit together on purpose. Useful, page-specific orientation earns its place. A paragraph written to hit a length target does not.
The list: this is a collection page, not a disguised essay
Keep the products or posts visible and prominent. Good ecommerce category page optimization never buries the grid: on a product collection, clear names, a meaningful distinguishing detail, images and prices let a shopper compare options without opening each one. Some category pages exist mainly to route a visitor to the right subcategory rather than to sell directly from the grid; treat those as navigation pages and keep the copy light, since an invented buying essay about products the page does not even display helps no one.
On a blog tag archive, the list only works if the tag actually gathers related posts. No introduction, however well written, rescues an archive of loosely connected articles. If a tag consistently holds only one or two posts, that is usually a sign the tag exists for the writer's convenience rather than the reader's, and it is worth merging or removing rather than dressing it up with intro copy.
Guidance: answer the choice the grid cannot explain
This is where a lot of category pages actually go thin, not in the intro, but in the missing help with the decision itself. For an ecommerce category, name the distinctions that matter within this specific category: intended use, sizing, materials, a feature trade-off, a compatibility check, something a shopper should verify before buying. Never assert a spec or a stock claim the client's catalog does not actually support. This block should stay collection-level guidance, not a rewritten buying guide and not a copy-paste of individual product descriptions.
For a blog category or tag page, the equivalent is browsing guidance: point a newcomer to the right starting article, separate two subtopics that look similar, or say plainly which piece answers which question. Do not just paste post summaries into a second block of prose under a different heading; that is padding with extra steps.
FAQ: only when a real question is left over
Add a page-specific FAQ when, after the intro and the guidance, visitors still face a recurring question that belongs to this collection specifically, how to choose between two product types, what spec to check before ordering, where a beginner should start in a topic archive. If the guidance section already answers it, do not repeat the answer in FAQ format just to have an FAQ. And do not add one as a copy-paste shipping and returns block across every category, since an identical FAQ on every page is exactly the kind of boilerplate that makes a whole set of pages look thin.
One more thing worth knowing if your team has been pitching FAQ blocks as a rich-result play: Google's documentation confirms FAQ rich results stopped appearing in Google Search as of May 7, 2026. Write the FAQ because it genuinely helps the visitor, not because it used to buy extra search-result real estate.
Worked example: a product collection
This is illustrative copy to show the structure. Check every claim and distinction against the actual client catalog before anything like it goes live.
H1: Travel Backpacks
Intro above the products:
Browse travel backpacks by how you pack and carry them. If you need room
for a laptop, start with bags that list a dedicated device compartment;
if you expect to carry the bag for long stretches, compare the straps and
fit details shown on each product page.
[Product cards appear here.]
How to choose:
- For work trips, check device fit and access to items you'll need en route.
- For longer walks, compare carrying features and the manufacturer's fit guidance.
- Before choosing a bag for a flight, check the bag's published dimensions
against the baggage rules for your particular airline and fare.
FAQ:
Q: Will every travel backpack here qualify as cabin baggage?
A: Do not assume so. Check the published dimensions of the specific bag
against your airline's current allowance before buying.
Q: How do I choose between two similarly sized bags?
A: Compare the features that matter to your trip, such as device storage,
access and carrying comfort, using the individual product specifications.
Notice what this example does not do. It does not claim every bag in the grid shares a feature. It does not invent an airline rule. It resolves two real decisions a shopper on this exact page would have, and nothing more. That is the bar for the guidance and FAQ blocks on a real client page too: specific, checkable, and genuinely tied to this collection.
Adapting the template for a blog category or tag archive
A category usually groups a broad area of a site; a tag connects posts on a narrower recurring topic, and the exact split is different on every client's site. A tag page earns its own landing-page treatment when the posts it gathers form a real, usable set and its intro can say something a neighboring category page does not already say.
H1: Editorial Calendar Planning
Intro above the articles:
These articles cover how to choose topics, schedule publication and keep
an editorial calendar usable as plans change. Start with the overview if
you're setting up a calendar; use the workflow articles if you already
have one and need to coordinate reviews.
[Relevant article cards appear here.]
Where to start:
- New to the topic? Read the overview of calendar decisions first.
- Managing reviews? Open the article on approvals and ownership.
- Revising an existing calendar? Start with the article on rescheduling.
Optional FAQ:
Q: Is this archive about choosing topics or assigning publication dates?
A: It covers both; begin with the topic-selection articles if you're
building a backlog, or the scheduling articles if topics are chosen.
Treat the article descriptions in "where to start" as placeholders for posts that need to actually exist and actually match. Do not publish routing copy like this ahead of the archive having the posts to back it up. And if the archive is small, a clear heading and one short paragraph will usually serve the reader better than invented guidance stretched to fill a template it does not need.
How much unique copy is actually enough
There is no defensible universal word count here, and it is worth saying that plainly to a client who is asking for one. Google rejects a magical target outright, and nothing in the wider guidance backs a specific number that separates thin from acceptable. As loose, non-binding reference points: a short collection description of a sentence or two is often enough context on its own, and a single well-written paragraph above a product list can do the whole job on a straightforward category. Neither is a formula. Both are examples of restraint working.
Use a task-based stopping rule instead of a length target. Does the page say what the collection contains? Does it explain a distinction the visitor could not have guessed from the cards alone? Can the visitor pick a next step? Is everything on the page actually true of what is currently in the collection? If the answer to all four is yes, stop writing. If any answer is no, add the specific missing piece, not a filler paragraph sized to make the page look substantial.
Acceptance checklist for agency delivery
Reuse this checklist as your standing category page SEO and tag page SEO service, even though the actual questions, distinctions and facts change per client and per page:
- Collection promise: the heading, intro and the actual products or posts on the page describe the same thing.
- Unique angle: at least one distinction is genuinely specific to this category or tag, not a category name swapped into a shared paragraph.
- Visible task: the visitor can see the collection right away and understand what to pick; the copy does not push the grid below the fold.
- Decision help: guidance answers a real category-level question, or it is left out entirely.
- Evidence: every claim about attributes, compatibility, availability, or article coverage matches the client's current catalog or published posts.
- FAQ discipline: each FAQ question has an answer that is not already stated above, and no FAQ exists purely for search appearance.
- Adjacent-page separation: the copy is not substantially repeated on a neighboring category or a near-duplicate tag archive.
- Search presentation: the page has its own accurate title and, where used, its own meta description, understood as a search-result tool rather than a substitute for on-page content.
- Maintenance: claims get revisited when the assortment or the set of posts changes, not left to age against a catalog that has since moved on.
The repeatable part of this service is the checklist and the template itself. What changes every time is the actual content you put into each field. That is what keeps the pages from reading like they were all written by the same script, even when the process behind them is identical.
