# Topical maps for ecommerce stores

A store's map is not a blog plan with a shop attached. It is built around the pages that sell, and every other page exists to send a reader to one of them. Here is how I plan one, with the rules for filters, variants and stock, the limits Shopify and WooCommerce set, and a real store branch read row by row.

By Kevin Jeppesen, AI growth engineer. Founder, FrameworkSEO & Ascendily. Updated 2026-11-13. Source: https://frameworkseo.com/learn/topical-maps/topical-map-for-ecommerce

**Ecommerce topical map:** An ecommerce topical map is the plan of every page an online store needs, built around its collection and product pages, with each informational page placed to send readers to the page that sells what it talks about.

## Key takeaways

- In the 22 store maps we delivered in October and November 2026, a median 37% of pages sell, yet the informational pages hold a median 68% of the recorded searches, and 93% of them link to a collection or product page.
- A filter value earns its own collection page only when shoppers type the combination as one phrase, the store can fill it, and the page can say something its parent cannot; every other combination stays a filter.
- Sizes and colors are variants on one product page, not rows on the map; Google asks that each variant be reachable at its own URL, and Shopify allows up to 2,048 variants and three options per product.
- Keep an out-of-stock product page live and marked out of stock, as Google advises; redirect a product that is gone for good to its closest replacement, and keep one seasonal collection address every year.
- On Shopify, a filter combination is a parameter on a collection, not a page, and the default robots.txt keeps filtered collection URLs with a plus sign out of the crawl, so a facet you want found must become its own collection.

## How a store's topical map differs from any other map

A store's [topical map](https://frameworkseo.com/learn/topical-maps/what-is-a-topical-map) is built around the pages that sell: collection pages (also called category pages) and product pages. Every guide, comparison and blog post on the map exists to send a reader to one of them. On a publisher's map the articles are the product. On a store's map they are the road to the product.

Koray Tuğberk Gübür, the person most often credited with making the topical map a standard SEO deliverable, put the reason in one line in his 2022 Oncrawl case study: for an ecommerce site, "the source context is purchasing a specific product or a specific type of product". The [source context](https://frameworkseo.com/learn/semantic-seo/source-context-central-entity) is why the site exists. For a store, that is a purchase, so every page has to lead to one.

### What our store maps show

I counted the 22 store maps we delivered in October and November 2026 (maps with five or more collection pages). The middle map is 187 pages. A median 37% of its pages sell, and the middle half of the maps sits between 26% and 44%. The rest is the informational layer.

That layer is where the searches are. Informational pages hold a median 68% of each map's recorded monthly searches. And 2,407 of the 2,586 informational pages in those maps, 93%, link to a collection or a product page, directly or through the page they sit under.

![A store map in two layers: collection and product pages, which sell, about 37% of the map, and the informational pages that feed them, comparisons and brand pages included, holding 68% of the searches.](https://frameworkseo.com/learn/topical-map-for-ecommerce/store-map-two-layers.webp)

*Most of the searches land on the feeding layer; 93% of those pages link to a page that sells.*

So the map is a bridge. The searches sit mostly on one side and the money sits on the other. A store that publishes only collections gives up most of the searches. A store that publishes only blog posts collects the searches and sells nothing from them. The map decides which page carries a reader across.

The order follows the same logic. In those 22 maps, a median 12.5 of the first 20 pages to publish are pages that sell. Guides go live after the collection they link to, so their links work on day one.

## What sits in a store's core section and what sits in its outer section

A store's core section holds the pages that settle a purchase: collection pages, the product pages that earn their own row, and the comparisons and brand pages a buyer reads in the last step. The outer section holds guides built from the attributes of what the store sells: care, fit, use, style, materials and gifting.

The general theory of the two halves is in [core section and outer section](https://frameworkseo.com/learn/semantic-seo/core-and-outer-sections). For a store, one rule does most of the work: the outer section is built from product attributes, not from blog ideas. A guide earns a row when it is about an attribute of something the store sells. "How to shrink a shirt" is about cotton, weight and fit, so it has a place on a T-shirt store's map. "Summer festival checklist" may be popular, but if the store sells no festival gear, it has no collection to send a reader to.

| Section | Page types | Built from | Its job |
| --- | --- | --- | --- |
| Core | Collection pages, chosen product pages, brand pages, buying comparisons | Product types and the filter values people search for | Take the order |
| Outer | Guides, how-tos, definitions, gift and occasion guides | Attributes of the products: care, fit, material, use, era | Answer the question, then send the reader to the collection |

### Where Koray saw a store map fail

Koray described an old store map that broke this rule. In his 2023 write-up of Snuffstore.de, a German tobacco and e-cigarette store, he wrote that its map had almost no informational content "and there are no reciprocal links between information and commercial links". His fix in one sentence: "The product review, and product selling content have to be paired with each other." He reports more than 1,200% growth in organic clicks over three months, year on year, after the rebuild. That is his number from his own screenshots, not an audited result. The structural point stands on its own: an informational page with no link to a page that sells is a dead end on a store. More of his model is in [Koray Tuğberk Gübür's topical map framework](https://frameworkseo.com/learn/semantic-seo/koray-topical-map-framework).

## Collection, product page or guide: which page owns a search

Every search on a store's map gets one owner page. A product type or a filter phrase belongs to a collection page. A named item belongs to a product page. A question, a how-to or a choice between two things belongs to a guide or a comparison. A search for something the store does not sell gets no page that sells.

That last rule matters more than it looks. A keyword tool will happily show a T-shirt store that "band merch" has volume. If the store does not sell band merch, a collection page for it is a promise the store cannot keep. Never add a money page for something the store does not sell. A guide can still touch the subject, but only when it leads to a collection the store fills.

![A four-question path that sends a store search to a product page, a collection page, a guide, or no money page at all.](https://frameworkseo.com/learn/topical-map-for-ecommerce/who-owns-the-search.webp)

*Ask in order; the first answer that settles it picks the owner, and every other page that mentions the search links to it.*

| Search pattern | Example from a T-shirt store | Owner page | What decides it |
| --- | --- | --- | --- |
| Product type | graphic tees | Collection page | Check Google: store category pages and product grids rank for it |
| Type plus one filter value | oversized graphic tee | Collection page | The filter test in the next section |
| A named item | a design name the store sells | Product page | The search names one thing you can add to a cart |
| "Best X for Y" | best t shirts for working out | Collection page or guide | What Google ranks today: product grids mean a collection, articles mean a guide that links to one |
| How-to or care | how to shrink a shirt | Guide | A task, not a purchase |
| What is, X vs Y | what is a boxy tee | Comparison or definition page | A choice the buyer has to settle before buying |

Two pages for one search is the classic store mistake: a collection called "heavyweight T-shirts" and a blog post called "best heavyweight T-shirts", both chasing the same words. Pick one owner and let the other link to it. The test for when a search needs a page at all is in [when a search deserves its own page](https://frameworkseo.com/learn/topical-maps/page-or-section), and the repair for two pages competing is in [keyword cannibalization](https://frameworkseo.com/learn/topical-maps/keyword-cannibalization).

## Filters and facets: which filter values become pages

A filter value becomes its own collection page only when three things are true. Shoppers search the combination as one phrase. The store has enough products to make it a real page. And the page can say something its parent cannot. Every other combination stays a filter.

### Store filters are facets, and libraries solved this first

Store filters are what library science calls facets. A facet is one independent way to divide a subject: by type, by material, by who it is for, by where or when. Library scholar S. R. Ranganathan reduced the facets of any subject to five in his Colon Classification: personality, matter, energy, space and time (PMEST), as M. P. Satija describes it in the ISKO Encyclopedia of Knowledge Organization (2017). Put in a store's words, those are what it is, what it is made of, what it does, where and when.

Library science also draws the line a store needs. Birger Hjørland's ISKO entry on facet analysis (2018) separates two uses. A post-coordinate system lets the searcher combine facets at search time. A pre-coordinate system, like a catalog, combines them in advance, and there "more thought must be given to the sequence of facets". The facet-analysis steps his entry quotes give the rule for that sequence: "The chosen order should be that of greatest utility to the person using the system."

That is the filter question in other words. A filter is post-coordinate: the shopper combines facets. A collection page is pre-coordinate: you combine them once, in advance. So you build in advance only the combinations of greatest use to the people searching, and the best evidence of use is that they type the combination as one phrase. "Oversized graphic tee" gets 22,200 US searches a month in the map below, so it is a page. "Oversized black graphic tee in medium" is a filter.

![A filter lets the shopper combine facets; a collection page combines them in advance. Three yes answers turn a filter value into a page.](https://frameworkseo.com/learn/topical-map-for-ecommerce/filter-or-collection.webp)

*Library science calls the two post-coordinate and pre-coordinate; only the second is a page Google can rank.*

### The three questions, with a real branch

1. **Do shoppers search the combination as one phrase?** Look up the phrase. A filter value with no searches as a phrase can still help shoppers on the page, but it does not need its own address.
2. **Does the store have enough products to fill it?** A collection of three products is a thinner copy of its parent. There should be enough that the page looks different from the page above it.
3. **Can the page say something its parent cannot?** A heavyweight collection can explain fabric weight and fit. A "medium" collection has nothing to say that the size filter does not.

In the real store branch below, every collection under the pillar is one facet that passed the test: fit (oversized), material (heavyweight), audience (women), era (vintage), and a second product type (hoodies).

![The collections of a real graphic tee store map sorted into five facets: type, material, fit, audience and era, with monthly searches.](https://frameworkseo.com/learn/topical-map-for-ecommerce/facets-of-a-graphic-tee.webp)

*Each collection answers one question about the product, which is why none of them compete with each other.*

### What happens to the filters that stay filters

Google's page on faceted navigation (last updated 18 December 2025) gives two routes. "If you don't need the faceted navigation URLs potentially indexed, prevent crawling of these URLs", with robots.txt or with URL fragments. If you do need them indexed, Google asks for the standard "&" separator, filters that always appear in the same order, and a 404 when a filter combination returns no results. Shopify already takes the first route for tag combinations by default: its robots.txt carries "Disallow: /collections/*+*", which, in Shopify's words, keeps filtered collection pages from being crawled "because they duplicate content that's already on the collection page".

> **Test the tree on customers before you build it:** Before you settle which facets become collections, run a card sort: give a few customers the product names on cards and ask them to group and name the piles. The Nielsen Norman Group describes the method (2024). If customers group by fit and you planned collections by color, the menu and the map are both wrong.

The sheet below holds the test as columns, with the real branch filled in as the worked example. Add a row per filter value in your store and the decision column fills itself in.

[Download the facet decision sheet](https://frameworkseo.com/learn/topical-map-for-ecommerce/store-facet-decision-sheet.csv) (CSV, one row per filter value: phrase, searches, products, decision and the page it becomes)

## How to map product variants without making a page per size

Sizes and colors of one product are variants on one product page, not rows on the map. A variant earns a row only when people shop it as a range across many products, and then it becomes a collection: "black graphic tees" is a collection, the black option of one tee is not.

Google still wants each variant reachable. Its ecommerce URL guide (updated 10 December 2025) says "make sure that each variant can be identified by a separate URL", with a path segment such as /t-shirt/green or a query parameter such as /t-shirt?color=green. When you use a parameter, the URL without it is the canonical one. On the page, Google's product variant documentation (updated 8 September 2026) groups variants with ProductGroup and the properties variesBy, hasVariant and productGroupID.

| Case | On the map | On the site |
| --- | --- | --- |
| One tee in six sizes and four colors | One product row, or no row at all | One product page, a variant URL per option, ProductGroup markup |
| Black tees across the whole range | A collection row, if it passes the filter test | A collection page with its own title and words |
| A design people search by name | A product row | The product page owns that search |

Most product pages never need their own row. The product exists in the catalog whether or not the map names it. Three of our 22 store maps had no product rows at all, including the 391-page map in this lesson: its 137 collections carry the buying searches, and the products sit inside them.

Shopify sets the ceiling here. Its help center says you can create up to 2,048 variants for a product and each product can have up to three options. A product that needs a fourth option is usually two products, and two products often means a collection.

## What to do with out-of-stock, discontinued and seasonal pages

Keep an out-of-stock page live and marked out of stock. Redirect a product that is gone for good to its closest replacement, or let it return a 404 when nothing comes close. Keep one seasonal collection address every year. The map row stays in every case. What changes is what the page does.

Google answered the out-of-stock question directly in its 2020 Search Central post on pausing an online business: "Should I use the Removals Tool to remove out-of-stock products? No." and "It's better to still allow that page, and mark it out of stock." The same post asks you to update structured data to show the current availability.

![Five states of a store page: in stock, out of stock, gone for good, empty collection and seasonal, and what its address does in each.](https://frameworkseo.com/learn/topical-map-for-ecommerce/product-page-life-cycle.webp)

*The map row stays through every state; only the page's status and links change.*

- **Gone for good.** Shopify's help center gives the case itself: "if you delete a product, then you can set up a URL redirect so that when customers enter the URL for that product, they're redirected to a similar product on your store." A redirect to a page that is not similar helps no one; a 404 is the honest answer then.
- **An empty collection.** Google's URL guide says that when a category has become empty and your site removes it from search and browse, "consider returning a 404 (not found) HTTP status code for the page." If the range comes back each year, keep the page instead.
- **Seasonal collections.** A Halloween or Christmas collection keeps one address with no year in it, and the page is refreshed before each season. A new URL every year usually starts from zero every year. On the map, the row carries the season and the date to refresh it.
- **Hidden stock on WooCommerce.** WooCommerce has an "Out Of Stock Visibility" setting that hides out-of-stock items from the catalog. Hiding the item from collection pages also removes the internal links to it, so check what the setting does to pages you want to keep found.

> **Deleting sold-out pages is the expensive mistake:** A store that deletes every sold-out product throws away the links and the history those pages built, and then rebuilds them when the stock returns. The page costs nothing to keep. Mark it, keep its links, and decide its fate only when the product is gone for good.

## Run the store blog as series that feed collections

A store blog works as a set of series, not a stream of posts. Each series sits under one hub page, covers one attribute of the catalog, and each post in it names the one collection it sends readers to.

In the real branch below, the style series is a hub called "How to wear it: style, fit and care guides". Under it sit the guides on styling an oversized T-shirt and on shrinking a shirt, and the two comparisons on heavyweight and boxy tees. Each one names a collection: oversized, heavyweight, cropped. The series is how the hub becomes a [pillar page](https://frameworkseo.com/learn/topical-maps/pillar-pages) for its corner of the catalog.

### How to plan a series

1. Pick one attribute that many products share: fit, fabric, care, occasion, era.
2. List the questions buyers ask about it, from searches, reviews and support emails.
3. Give each question a guide and a collection to send readers to. A question with no collection to send them to is cut.
4. Put a hub page above the series that links to every guide in it, and link the hub to the collection it supports.

Koray's bookstore case shows the same pattern at scale. In his 2023 write-up of BKMKitap.com, a Turkish bookstore, the authors and genres were used as entities to organize the content, with contextual bridges between the informational pages and the pages that sell the books. He reports more than 350% growth in organic clicks. Again, that is his reported number. The pattern is the useful part: the informational pages are organized around something the store sells.

## What every informational page on a store links to

Every informational page on a store links to one primary collection that sells what the page discusses, to the hub of its series, and to one or two sibling guides. The words of the link to the collection are the collection's own name, the same every time.

| Link | Where on the page | Words of the link | Example |
| --- | --- | --- | --- |
| The primary collection | In the paragraph that talks about the product | The collection's name | The shrink guide links to "heavyweight graphic T-shirts" |
| The hub of the series | Near the top or in the closing lines | The hub's name | "style, fit and care guides" |
| One or two sibling guides | Where the reader's next question comes up | The sibling's own name | The boxy tee comparison links to the oversized styling guide |

Google says the same about importance. Its page on ecommerce site structure (updated 10 December 2025) says that if you have a best selling product, "consider linking to it from the home page or in other content, such as blog posts or newsletters on your site." Google's 2024 leaked API documentation also lists a field called onsiteProminence, described as measuring a document's importance within its site by propagating simulated traffic from the homepage and from pages people click. The field exists; its weight is unknown. Both point the same way: the pages you link to from your content look more important.

Do not link every post to the homepage or to an "all products" page. A link that could sit on any post tells nobody where this reader should go next. The full rules for links inside a map are in [internal links inside a topical map](https://frameworkseo.com/learn/topical-maps/internal-links-in-a-topical-map).

## What Shopify and WooCommerce let a store map do

Both platforms fix part of every address and decide which views can be pages at all. A store map has to fit those rules, because a map that plans URLs the platform cannot make is a map nobody can publish. These are the rules from their own documentation, checked on 13 November 2026.

| Topic | Shopify | WooCommerce |
| --- | --- | --- |
| Addresses | /products and /collections are "fixed Shopify paths", and URL redirects cannot be set on them | Defaults /product/, /product-category/ and /product-tag/, all changeable under Settings, Permalinks |
| Groups of products | Collections, manual or by conditions; up to 5,000 collections with conditions, 60 condition values per source | Categories (with parent and child levels) and tags (flat, no "subtags") |
| Filters | Up to 25 filters per store; applied filters are URL parameters such as filter.v.option.color=red | Attributes filter products; an attribute gets its own address only when "Enable archives" is turned on |
| Tags in addresses | Tag filters append /[tag-handle] to the collection URL | Product tag archives at /product-tag/ |
| Crawl rules | Default robots.txt disallows /collections/*+* (filtered) and /collections/*sort_by* (sorted) | The WooCommerce pages checked here set no crawl rule for filters |
| Variants | Up to 2,048 variants and three options per product | Variable products with variations built from attributes |
| Stock | Delete a product and redirect its URL to a similar one | "Out Of Stock Visibility" hides out-of-stock items from the catalog |

### What that means for the map

- **On Shopify, a facet you want found must be a collection.** A filter is a parameter on a collection, and a tag combination with "+" is blocked from the crawl by default. Automated collections built on a tag or a product type turn a facet into a real page with its own handle, title and text.
- **On WooCommerce, decide which taxonomy carries the facet.** Categories carry the facets you want as pages. Tags and attribute archives make pages too, so turn on archives only for the attributes that passed the filter test, and leave the rest as filters.
- **On both, plan blog paths you can keep.** Shopify blog posts live under /blogs/, with the blog's handle in the path (Shopify's developer docs show /blogs/potion-notions/ followed by the post), so a series can be its own blog. Changing paths later means redirects for every post.

## How big a store's topical map gets

Our median growth plan is 159 pages (as of 5 November 2026). A map can be anywhere from about 50 pages to over 20,000, depending on the size of the company, what central entity they have that needs that sort of coverage, how many services they have, and so on. For stores, that means the size of the catalog's structure, not the number of products.

The 22 store maps we delivered in October and November 2026 run from 81 to 400 pages, with a median of 187. None of those numbers is a target. What sets a store map's size:

- **Product types.** Each type the store sells is a collection, and often a hub with collections under it.
- **Facet values that pass the filter test.** A store with five fits, four materials and three audiences that people search for has more collections than one with a single cut.
- **Attributes worth a guide.** Care, fit, use and occasion each carry questions. A product with no questions around it needs few guides.
- **Not the SKU count.** Ten thousand products in three types can need a smaller map than four hundred products in forty types.

The full method for building one, from research to publish order, is in [how to build a topical map](https://frameworkseo.com/learn/topical-maps/how-to-build-a-topical-map). We built our own system for this, which is how a map of about 159 pages takes us about 2 to 2.5 hours.

## One real store branch, read row by row

These 12 rows come from a 391-page US store map we delivered to a paying buyer whose subject is graphic tees. No word in them was changed. The same rows appear in [topical map examples](https://frameworkseo.com/learn/topical-maps/topical-map-examples) as an example of a map. Here I read each one as the store decision it makes.

| P | Page | Type | Main search | Searches a month | The decision this row makes |
| --- | --- | --- | --- | --- | --- |
| 1 | Graphic tees: funny, weird and vintage statement T-shirts | collection | graphic tees | 201,000 | The product type itself. An existing collection, rebuilt as the pillar of the branch. |
| 2 | Oversized graphic tees | collection | oversized graphic tee | 22,200 | The fit facet. A filter value people type as one phrase, so it became a page. |
| 3 | Vintage and retro graphic tees | collection | vintage graphic tees | 14,800 | The era facet. Same test, same answer. |
| 4 | Graphic hoodies | collection | graphic hoodies | 40,500 | A second product type. A hub with collections of its own under it. |
| 83 | Graphic tees for women | collection | graphic tees for women | 18,100 | The audience facet. An existing women's collection, folded into the tee branch. |
| 86 | Heavyweight graphic T-shirts | collection | heavyweight t shirt | 9,900 | The material facet. A new collection the store could fill from stock. |
| 145 | 90s outfits: how to dress the decade today | guide | 90s outfits | 110,000 | An outer page on the era attribute. Links to the vintage collection. |
| 202 | How to wear it: style, fit and care guides | hub | how to style graphic tees | 720 | The hub of one blog series. An existing post, rebuilt to gather the series. |
| 203 | How to style an oversized T-shirt | guide | how to style an oversized t shirt | 720 | Fit attribute, question form. Links to the oversized collection. |
| 204 | How to shrink a shirt (and how to unshrink one) | guide | how to shrink a shirt | 18,100 | Care attribute. Links to the heavyweight collection. |
| 329 | Heavyweight vs regular T-shirts: GSM, fit and feel | comparison | what is a heavyweight t shirt | 390 | Defines a filter value in plain words. Links to the heavyweight collection. |
| 341 | What is a boxy tee? Boxy vs oversized T-shirts | comparison | what is a boxy tee | 320 | Settles a fit choice. Links to the oversized and cropped collections. |

### What the rows teach

- **The pillar is a collection, not a guide.** P1 answers the product type, 201,000 searches, with a page that sells. On a store, the top of the map is where the products are.
- **Existing pages are rebuilt, not doubled.** P1, P4, P83, P202 and P203 already existed on the store. The map rebuilds each one for its search instead of adding a second page beside it.
- **Every guide names a collection.** The shrink guide and the heavyweight comparison both send readers to heavyweight T-shirts. A shirt that shrinks less is the honest answer to the question, and the collection sells it.
- **The biggest search is not the first page.** "90s outfits" has 110,000 searches a month and goes live 145th, after the vintage collection it links to. A guide published before its collection has nowhere to send its readers. The full logic is in [publishing order](https://frameworkseo.com/learn/topical-maps/publishing-order).
- **Small comparisons stay.** The heavyweight and boxy comparisons answer 390 and 320 searches a month. They stay because each one defines a filter value a buyer has to understand before choosing, and each links straight to the collection that sells it.

> **The same branch on a smaller store:** A made-up example: a store selling only heavyweight tees in two fits. Its pillar would be "heavyweight T-shirts", its collections the two fits, and its outer section the care and fabric questions. The facets the graphic tee store turned into pages (era, audience, hoodies) would not exist, because the store does not sell them.

## The mistakes we check for in store maps

Three mistakes show up in the maps buyers build themselves. The pages do not build on each other. There are off-topic pages that do not deserve to be there when they could have been part of another post. And a query does not deserve its own page: many searches are a section of a page, not a page. On a store, each of those has a shop-specific form, and these are what we check for:

1. **Posts with no collection to send readers to.** A guide that names no collection is a dead end. Either give it one or merge it into a guide that has one.
2. **Filter pages indexed by the thousand.** Every color, size and price combination opened to Google is a page with nothing of its own. Only the combinations that pass the filter test become pages.
3. **A collection and a post for one search.** One owner per search, the other page links to it.
4. **A row per SKU.** Products live in the catalog. The map names only the product pages that own a search of their own.
5. **A money page for something the store does not sell.** Search volume is not a reason to promise a product.
6. **Deleting out-of-stock pages.** Keep them live and marked until the product is gone for good.
7. **A new URL every season.** One seasonal address, refreshed each year.
8. **Blog topics with no link to the catalog.** Any website that has worked with a bad agency before has a large share of off-topic posts, published because the retainer counted posts. Every page needs a purpose. Before deleting one, check whether it can be merged into a page that is more relevant; the method is in [pruning, merging and updating](https://frameworkseo.com/learn/topical-maps/pruning-and-merging).

If you sell services rather than products, the same logic runs with service pages in place of collections: see [topical maps for local and service businesses](https://frameworkseo.com/learn/topical-maps/topical-map-for-local-and-service-businesses). And if you would rather have your store's map built and checked for all of the above, that is [the growth plan](https://frameworkseo.com/).

## Sources

- [Importance of Semantic Network for SEO: Creating Semantic Content Networks with Query and Document Templates (Case Study)](https://www.oncrawl.com/technical-seo/creating-semantic-content-networks-with-query-document-templates-case-study/), Koray Tuğberk Gübür, Oncrawl, 2022
- [How to Expand a Topical Map for Higher Topical Authority?](https://www.holisticseo.digital/seo-research-study/topical-map), Koray Tuğberk Gübür, Holistic SEO & Digital, 2023
- [Facet analysis](https://www.isko.org/cyclo/facet_analysis), Birger Hjørland, ISKO Encyclopedia of Knowledge Organization, 2018
- [Colon Classification](https://www.isko.org/cyclo/colon_classification), M. P. Satija, ISKO Encyclopedia of Knowledge Organization, 2017
- [Card Sorting: Uncover Users' Mental Models](https://www.nngroup.com/articles/card-sorting-definition/), Nielsen Norman Group, 2024
- [Managing crawling of faceted navigation URLs](https://developers.google.com/search/docs/crawling-indexing/crawling-managing-faceted-navigation), Google Search Central, 2025
- [Ecommerce URL structure best practices](https://developers.google.com/search/docs/specialty/ecommerce/designing-a-url-structure-for-ecommerce-sites), Google Search Central, 2025
- [Help Google understand your ecommerce website structure](https://developers.google.com/search/docs/specialty/ecommerce/help-google-understand-your-ecommerce-site-structure), Google Search Central, 2025
- [Product variant structured data (ProductGroup, Product)](https://developers.google.com/search/docs/appearance/structured-data/product-variants), Google Search Central, 2026
- [How to pause your business online in Google Search](https://developers.google.com/search/blog/2020/03/how-to-pause-your-business-online-in), Google Search Central Blog, 2020
- [PerDocData (onsiteProminence), Content Warehouse API documentation](https://hexdocs.pm/google_api_content_warehouse/0.4.0/GoogleApi.ContentWarehouse.V1.Model.PerDocData.html), hexdocs.pm copy of the leaked Google API documentation, 2024
- [Adding variants](https://help.shopify.com/en/manual/products/variants/add-variants), Shopify Help Center, 2026
- [Filters (Search & Discovery)](https://help.shopify.com/en/manual/online-store/search-and-discovery/filters), Shopify Help Center, 2026
- [Editing robots.txt.liquid](https://help.shopify.com/en/manual/promoting-marketing/seo/editing-robots-txt), Shopify Help Center, 2026
- [Creating and managing URL redirects](https://help.shopify.com/en/manual/online-store/menus-and-links/url-redirect), Shopify Help Center, 2026
- [Creating collections](https://help.shopify.com/en/manual/products/collections/automated-collections/auto-create), Shopify Help Center, 2026
- [Storefront filtering](https://shopify.dev/docs/storefronts/themes/navigation-search/filtering/storefront-filtering), Shopify Developers, 2026
- [Filter collections by tag](https://shopify.dev/docs/storefronts/themes/navigation-search/filtering/tag-filtering), Shopify Developers, 2026
- [article (Liquid object)](https://shopify.dev/docs/api/liquid/objects/article), Shopify Developers, 2026
- [Permalinks](https://woocommerce.com/document/permalinks/), WooCommerce, 2026
- [Managing product categories, tags and attributes](https://woocommerce.com/document/managing-product-taxonomies/), WooCommerce, 2026
- [WooCommerce settings: Products](https://woocommerce.com/document/configuring-woocommerce-settings/products/), WooCommerce, 2026