# Planning a store restructure around customer language

URL: https://ekom.blog/planning-a-store-restructure-around-customer-language/
Published: 2026-11-14
Author: Ekom
Topics: Shopify & e-commerce

> A practical guide to planning a store restructure around customer language, with a clear process for making and checking the right decision.

Internal category names are rarely the words customers use. The team says "audio accessories", the shopper types something else, thinks about the product by task and ignores the department sign entirely.

Planning a restructure around customer language helps the new hierarchy feel natural. But a keyword list alone can't tell you where every product belongs. Combine search evidence with what you know about the catalogue and what shoppers actually ask.

## Collect language from several sources

Review on-site search, support questions, Search Console queries, product filters and interviews where you can get them. Each has limits. Internal search reflects current visitors, support reflects people who asked for help, and query data can hide low-volume terms. Group phrases by the task or distinction they express, not just by shared words.

## Build and test a taxonomy

Draft the parent categories, collections and filter attributes. Decide which distinctions are stable and which are temporary campaigns. Test the structure with real product examples, especially products that fit more than one group. Ask someone unfamiliar with the catalogue to find a sample item and explain their path. Fix confusing labels before you touch URLs or navigation.

## Preserve useful paths

Map current pages and links to the new structure. Keep URLs that remain useful, and plan relevant redirects for pages that move. After launch, validate internal links, breadcrumbs, sitemaps and collection assignments.

## Keep a language glossary

Write down the customer term, the internal term and the label you chose, with the reason. When someone later wants to rename a category, the glossary shows what evidence sits behind the current name. It also stops different teams drifting into their own vocabulary.

I'd rather keep a small, well-maintained glossary than a big one nobody updates. Review it whenever the range grows.

## Don't rename everything at once

A restructure can tempt you to change every label in one release. That makes it hard to tell which change helped or hurt, and it's a lot for returning customers to absorb. I'd start with the categories where the gap between internal and customer language is clearest, ship those, and learn from them.

Keep a note of what you changed and when. If search behaviour or support questions shift, you'll have a timeline to read them against, and you'll still need to allow for campaigns and stock changes happening at the same time.

## Apply the review to one real case

Define what a finished restructure changes for the shopper, not just what work the team did. Use the same scope and definitions across examples and note what you left out, so one product family doesn't stand in for the whole catalogue.

Follow one real URL from its source information to its published state, and check what a visitor can understand or do without an internal explanation. A copied export may describe an earlier template or configuration.

Treat pages that share a template differently from pages that share a user need.

Check the outcome where customers see it, since imports, apps, caching or theme behaviour can alter an approved change. If the evidence can't answer a question, say so and assign a follow-up. Where sources conflict, compare timestamps, definitions and ownership before choosing.

If the information is incomplete, a small reversible test beats a sitewide rule, especially when a wrong change could hit several journeys. Allow exceptions only for real user or operational problems and document their limits. Trigger the next review by a meaningful change to the range, market or platform, not an arbitrary reminder.

When you close the work, check nearby content that depends on the same facts. Make sure someone owns the guidance and knows how to restore the previous state. Before copying the approach to another market or product group, check that the audience and data are genuinely comparable.

## A worked example: one category, two vocabularies

Say a store has a category called "Audio accessories". On-site search and support messages show shoppers asking for "something to stop my earphones tangling" or "an adapter for my old headphones". Those are tasks, not departments. You might keep the parent and add child collections named for the tasks, such as cable organisers and headphone adapters, with a filter for connector type. Then test it: give a colleague one of those phrases and watch where they click. If they reach the right child through the parent, the structure works. If they go straight to search, the labels still don't match.

## Related reading

- SEO planning for a Shopify store with wholesale and retail buyers

- Planning organic search around a product range refresh

- Reviewing product pages using customer questions and store data

What product would expose the weakest spot in your proposed hierarchy?

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
