Deduplicating Joins Across Citation, Referral, and CRM Data
Website owners comparing citation reports with referrals and customer relationship management (CRM) outcomes need to keep the three record types separate. A…
In an online store, navigation is the set of links shoppers use to move from the homepage to product groups and individual products. Organize those links around product types and groups shoppers recognize, then test whether people can find representative products. This gives shoppers clearer choices and gives search engines links to follow.
The way you arrange these routes and pages is your ecommerce site architecture. A category groups related products, a product listing presents items to browse, and a filter narrows a listing by an attribute such as size or color. These roles can overlap, but shoppers should be able to tell what each page helps them do.
Start with the products you sell and the words customers use for them. A company’s internal department names or inventory codes may make sense to employees but leave shoppers unsure where to click. Look for customer language in support questions, on-site search terms, product descriptions, and other customer-facing content. Each source offers clues, but none gives a final answer. Search terms show what shoppers already know, while support questions can reveal where they get stuck.
Next, decide which product differences deserve a category of their own. Give a product type its own navigation category when shoppers look for it as a distinct group. Use filters for attributes that help shoppers narrow down a group, including color and size; price is another option. For example, a store could place “Running Shoes” under “Shoes” and let shoppers filter the resulting listing by size or color. The right choice depends on the catalog and how shoppers look for its products.
Avoid adding layers just to mirror internal ownership or product data. A smaller catalog may need only a few levels, while a larger one may need subcategories to make browsing manageable. There is no evidence that one category count or hierarchy depth suits every store.
Use card sorting to explore how shoppers group products. In this method, participants sort product names or descriptions into groups and suggest labels. Keep the item descriptions neutral: labels that repeat the same terms as the proposed categories can steer participants toward matching words instead of grouping products by meaning. NN/G’s card-sorting guidance explains this risk.
Then test the proposed hierarchy with a tree test. Participants see the category structure without the store’s visual design and try tasks such as finding a particular product type. Record whether participants reach the intended destination. Also note any alternate route they choose and where they hesitate. NN/G’s tree-testing guidance distinguishes this evaluation step from card sorting, which helps generate possible structures.
Treat the results as evidence about the tested tasks and participants. A small test that asks participants to explain their choices can reveal confusing labels, but it cannot establish a precise success rate for all shoppers. A tree test also isolates the hierarchy, so it does not show whether the live page design, product content, or filters cause other problems.
A category page should help shoppers choose a narrower group or begin browsing relevant products. A product-listing page should make it easy to scan a set of products and narrow it with filters. Some stores combine those functions on one page. If yours does, make the next action clear through the page title, visible subcategory links, product grid, and filters.
For example, a broad “Outdoor Gear” page might link to “Backpacks” and “Tents.” A “Backpacks” listing could then show products with filters for capacity or intended use. That structure gives shoppers a route through the catalog without requiring them to know a precise product name. Baymard’s category-page research discusses the role category pages play in helping shoppers browse product groups.
Keep on-site search available alongside navigation. Shoppers who know what they want may search directly; shoppers who are exploring need clear browsing routes. Research on apparel shopping, for example, reports that the balance between search and category browsing varies by context. Do not assume one route should replace the other for every store.
Internal links connect pages on your store. Google says it uses links between pages to understand ecommerce site structure, including the relationships between category, subcategory, and product pages. Link important categories from visible navigation, link subcategories from their parent pages, and link products from relevant listings. Google also says its web crawler, an automated program that visits pages, generally does not use a store’s search box to find products. Give products you want Google to discover a direct link. See Google’s ecommerce navigation guidance.
Readable, consistent URLs help people and search systems identify pages, but URL nesting alone does not communicate the full hierarchy to Google. A path such as /shoes/running/ does not replace links from the store’s navigation and category pages. Use descriptive URLs where practical. Keep internal links and sitemap entries consistent with the signals that identify the preferred page version. Follow Google’s URL guidance for ecommerce.
Check the live routes directly. Confirm that important category and product pages have working internal links. Check that shoppers can reach products without submitting a search. Check that links point to the preferred versions of the pages. A crawler’s ability to reach a page does not mean Google has added it to its search index. A sitemap entry alone does not prove that Google has indexed the page.
Filters help shoppers narrow a product set, but combinations of filters can generate many URLs. If each combination creates a crawlable page, search engines may spend time fetching low-value variations instead of discovering useful pages. Google’s faceted-navigation guidance describes this crawl-management problem.
Decide which filtered pages deserve to be search landing pages. A combination should earn that role because it serves a distinct shopper need and has a useful product set, not simply because the store can create a URL for it. Manage routine combinations deliberately, and check that empty or nonsensical combinations do not produce unwanted pages. Google notes that canonical tags, which identify a preferred page URL, and the nofollow link attribute, which asks search engines not to follow a link, can be less effective over time than primary approaches to controlling faceted URLs. Follow its current guidance rather than relying on one signal alone.
Usability tests show whether people understand the categories and reach the products they expect. Search Console can help you check whether important category pages appear in Google Search and identify technical issues. Neither measurement substitutes for the other: search visibility does not prove that shoppers understand the menu, and a successful tree test does not prove a ranking or sales increase.
Baymard’s homepage and category-navigation benchmark reports that 76% of the studied ecommerce sites performed at “mediocre” or worse for this user-experience area. Its benchmark covered 344 top-grossing US and European ecommerce sites. The finding indicates that navigation problems are common in the sites it assessed; it does not estimate the rate across all stores or show that a particular navigation change improves rankings or revenue. Its separate 2024 product-finding update describes more than 5,550 research hours and 219 qualitative user/site sessions across 12 named sites. That work covered product finding broadly, including search, product lists, and filtering, so it should not be treated as a taxonomy-only test. See Baymard’s benchmark and 2024 research update.
Google says its AI Search features require no special SEO optimization or separate schema beyond its existing guidance. Crawlable pages, useful content, and clear internal links remain relevant fundamentals. A clear category structure can help Google discover pages and understand their relationships, but the available guidance does not establish that reorganizing navigation earns AI citations or guarantees visibility in an AI answer. Google’s guidance on AI features also makes clear that meeting its requirements does not guarantee indexing or appearance.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com