Discussion
  • eCommerce SEO
  • Indexing
  • WordPress SEO

WooCommerce tag and attribute archives: index, noindex or delete? Has anyone seen them drive meaningful revenue?

Published 1 reply

Discussion starter: an ecommerce SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    Decide archive by archive, starting from a different default for each of three URL types: tag archives, attribute archives and the filtered listings that get lumped in with them. Index a tag or attribute archive only when it matches something people search for, lists a product set no single category already covers, holds enough in-stock products to be worth landing on, and has been curated like a landing page. Archives that fail those tests but that shoppers use in navigation can stay live with noindex. Tags nobody uses should be deleted, with a 301 only where the archive has organic traffic or links. The filtered URLs your layered navigation generates are a separate problem, handled with robots.txt rather than noindex.

    On revenue: public evidence specific to WooCommerce tag archives is thin and anecdotal, and no controlled public test exists that I can point to. When an archive does earn money, the reason is structural: it works as a category in disguise, covering a material, brand or use case that cuts across the category tree and has real demand. You can pull the numbers for your own store in an afternoon, but read landing-page revenue carefully. If an archive duplicates a category, much of its revenue may be sessions the category would otherwise have received.

    Three URL types that get lumped together

    Type How it is created Example Default stance
    Product tag archive Every tag gets one. Tags are flat (WooCommerce notes “there is no hierarchy in tags”), and staff who edit products can create them on the fly /product-tag/linen/ with the default tag base Noindex or delete unless it passes the tests below
    Attribute archive Only when “Enable archives” is ticked for a global attribute. WooCommerce says you can then “view a page with all products having any term of this attribute” /material/linen/ Switch off unless a specific term earns its place
    Filtered listing Layered navigation widgets and filter blocks add parameters such as filter_colour= and min_price= to shop and category URLs; filter plugins add their own patterns /dresses/?filter_colour=black Keep out of the crawl with robots.txt; build any filter worth ranking as a real landing page

    The first two are taxonomy archives, which WooCommerce’s product taxonomy documentation describes. The third is a parameter version of a category, and it is where crawl volume multiplies.

    Why tag archives start at a disadvantage

    Tags accumulate unless someone governs them. Because staff add them while editing products, a store with a few years of history can end up with near-duplicates (“linen”, “Linen shirts”, “linen-shirt”), single-product tags, and internal labels never meant for customers, such as promotion names or supplier codes. Each one is a public archive. When a tag’s products are mostly the same as a category’s, the tag page is a thinner copy of that category grid, and Google’s ranking systems guide describes deduplication systems that “show only the most relevant results to avoid unhelpful duplication”. In the Page indexing report, tag archives listed under “Duplicate, Google chose different canonical than user” or “Crawled - currently not indexed” are consistent with that problem.

    They get crawled at scale for a simple reason. WooCommerce’s default single-product template prints each product’s tags as links, so unless your theme removes that line, every product page links to its tag archives, thin ones included.

    Tags also do jobs that have nothing to do with search. WooCommerce’s related products documentation says “Related products are automatically generated by WooCommerce based on shared tags or categories with the currently viewed product.” Blocks and shortcodes can also pull products by tag for promotions. Deleting tags can therefore change what appears on product pages and campaign pages, so check before you clean up.

    When a tag or attribute archive earns its place

    An archive worth indexing passes five tests:

    • Demand: it already gets impressions for a query class, or keyword research shows one, and no category serves that query.
    • A distinct product set: the list is not a near-copy of one category, and the cross-category mix matches the intent. Someone searching “linen” may want shirts or sheets; the results page shows which.
    • Depth: enough in-stock products to be worth landing on. Set your own minimum; two products is not a landing page.
    • Curation: its own title and heading, a short intro that helps people choose, a sensible default sort, and links from the relevant categories.
    • Conversion: sessions that land on it buy, and the revenue is not simply displaced from a category.

    An archive that passes all five is a category in everything but name, so consider making it one. Categories carry hierarchy, breadcrumbs, thumbnails and a place in category navigation, which tags lack. Create the category, assign the products, and 301 the old archive to it.

    Index, noindex or delete

    Situation Action Watch for
    Passes all five tests Index, curate and link it from navigation, or convert it into a category Keep it in the XML sitemap and watch it in the Page indexing report
    Shoppers use it (navigation, promotions), but it has no search demand of its own or duplicates a category Keep it live with noindex and out of the XML sitemap. SEO plugins such as Yoast SEO and Rank Math set this per taxonomy, with per-term exceptions Google has to crawl the page to see the noindex, so do not also block it in robots.txt
    Duplicates a category and has organic traffic or external links Delete the tag and 301 the archive to that category Update internal links and check the effect on related products
    Unused, thin or internal-only, with no traffic and no links Delete the tag; its archive then returns a 404 Check blocks, shortcodes and related products that use it first
    Attribute archives where no term earns its place Untick “Enable archives” for that attribute Confirm the old URLs now return a 404 (or redirect any with traffic), and check that your filters still work

    Two alternatives get suggested, and both are weaker. A canonical from a tag archive to a category makes sense only when the product lists are near-identical: a canonical is a signal for duplicates, and pointing a different product list at a category is a mixed signal that Google may not follow. And noindex does not stop crawling. Every noindexed archive is still requested so the directive can be seen. For a few hundred tag pages that cost is modest. For filter URLs, where combinations multiply, it is the wrong tool.

    Filter URLs are the bigger crawl risk

    Layered navigation multiplies URLs: every attribute, term, price range and sort order can combine with every category. Google’s faceted navigation guidance describes the cost. Crawlers “will typically access a very large number of faceted navigation URLs before the crawlers’ processes determine the URLs are in fact useless”, and “If crawling is spent on useless URLs, the crawlers have less time to spend on new, useful URLs.” For filter URLs you do not need indexed, it recommends robots.txt disallow rules, notes that filters built on URL fragments have no impact on crawling, and calls rel="canonical" and rel="nofollow" “generally less effective in the long term” than those methods. If some filtered URLs should be indexed, it asks for the standard & separator, a consistent filter order, and a 404 when a filter combination returns no results.

    For WooCommerce’s own parameters, that means rules along the lines of Disallow: /*?*filter_, Disallow: /*?*min_price= and Disallow: /*?*orderby=, adjusted to the parameters your theme and filter plugin actually produce. Test the patterns against a sample of real URLs with a robots.txt parser before publishing, because an over-broad wildcard can block category pages. If many filter URLs are already indexed, a blocked URL can no longer show Google its noindex, so decide whether to let a noindex be seen first. Any filter that deserves to rank, such as “black linen dresses”, is better built as a real category or curated landing page than left as a parameter URL.

    Finding out whether yours drive revenue

    1. Inventory. Export tags with their product counts (the Tags screen under Products shows a count per tag), list the attributes with archives enabled, and note which archives are linked from product pages or navigation.
    2. Search Console. In Performance, filter pages to URLs containing your tag base (/product-tag/ by default) and your attribute paths, across the full 16 months. For each archive with clicks, check whether a category page also gets impressions for the same queries. In Page indexing, count how many archives are indexed and why the rest are not.
    3. GA4. In the landing page report, filter to organic search sessions landing on those paths and read sessions, key events and revenue. That is revenue from sessions that started on the archive, not revenue the archive created.
    4. Test incrementality where it matters. For a batch of tags that duplicate categories, 301 them to their categories in stages and compare combined organic clicks and revenue for each tag-and-category pair against pairs not yet redirected. If the pairs hold, the tags were displacing revenue, not adding it. Read the result once Google has recrawled most of the redirected URLs (URL Inspection shows the last crawl) and the categories have had a few weeks to absorb them.
    5. Set “meaningful” in advance. For example, the share of organic revenue the archives would still hold after the duplicates are redirected. Choosing the threshold after seeing the data invites motivated reasoning.

    Hypothetical example:

    A homewares store has 1,400 products, 900 tags, and archives enabled for four attributes: colour, size, material and brand. Search Console shows 14 tag archives with meaningful clicks. GA4 shows purchases from sessions landing on five of them, and three of those five duplicate categories that rank for the same queries. The colour and size archives get almost no impressions. The material archive gets impressions for “linen bedding” and “linen tablecloths” and converts, and the brand archive gets brand searches and revenue.

    The decision: turn the earning material and brand terms into proper landing pages (categories, or a brand taxonomy if the store has one) and redirect them; switch off archives for colour and size; curate and keep indexed the two tags that are genuinely distinct; redirect the three duplicates as a staged test; noindex the promotional tags marketing uses; and delete the rest after checking related products. The store ends with fewer, stronger landing pages, and a test that shows whether the duplicates were adding revenue at all.

    The order I would work in

    Start with the filter parameters. Once you have checked how many filter URLs are already indexed, their robots.txt rules do not depend on any archive’s data, and that is where the crawl volume is. Then sort the tag and attribute archives into three piles from the 16-month Search Console export. No clicks and no external links: delete the tag or switch off the attribute’s archives after the related-products check, or noindex it if shoppers use the page. Clicks, but the same products as a category: the staged redirect test. Clicks and a distinct product set: curate it, and consider promoting it to a category. That redirect test, not landing-page revenue, is what answers the revenue question for your own store.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.