Managing SuiteCommerce Faceted Navigation for Search

Facets can create many URLs from one category. Some combinations may answer real searches; many differ only by sort order, display mode, or a low-value filter. The task is not to block every parameter. It is to choose which pages should exist in search and make the site consistent with that choice.

Google's faceted navigation guidance recommends preventing crawling when faceted URLs do not need to appear in search, or optimizing the URL order and behavior when they do.

Inventory before changing directives

Export facet URLs from a crawl, server logs, analytics, and Search Console. Group parameters by purpose:

• sort and view controls;
• pagination;
• product filters;
• tracking or session values;
• combinations with proven search demand.

Pick representative URLs and inspect the HTML returned to a fresh request. A tag added only after client-side JavaScript runs may not be the signal you think you shipped.

Define an index policy

For each URL class, choose one outcome:

1. Indexable landing page. It has stable demand, useful products, unique context, internal links, and a self-referencing canonical.
2. Crawlable but not indexable. Use a server-visible noindex while Google can still crawl the page and see that directive.
3. Not crawlable. Use robots.txt for patterns that do not need to be crawled, while understanding that blocked URLs can still be known from links.
4. Redirected or gone. Use this only when the URL should no longer resolve, not as a generic duplicate-content fix.

Do not combine a robots.txt block with a new noindex and expect Google to read both. If crawling is blocked, the crawler cannot see the page-level directive.

Use canonicals consistently

A canonical is a hint about the representative URL, not a way to erase every filtered page. Google's canonical guidance recommends consistent signals across redirects, HTML tags, sitemaps, and internal links.

Only canonicalize a facet to its parent when the pages are truly duplicates or near-duplicates. A red-size-10 category with a distinct product set may not be equivalent to the unfiltered category.

Generate canonicals from normalized server-side URL rules. Avoid mutating the tag after the page renders.

Clean internal links and sitemaps

Navigation should link to canonical forms. Remove session and tracking parameters from crawlable links. Keep noncanonical facet combinations out of XML sitemaps. If selected facets deserve indexing, link to them through ordinary anchors and give them stable URLs.

Test a small rule set

Before release, verify:

• one canonical tag in raw HTML;
• expected status code;
• expected robots directive;
• consistent parameter order;
• no accidental block of product or category pages;
• links and sitemap entries use the preferred URL.

Then watch crawl statistics, index reports, impressions, and server logs. Roll rules out by parameter class instead of deploying a broad regular expression across the catalog.

There is no safe universal rule such as “block three or more filters.” Base the policy on the site's URL behavior, product overlap, and search demand.