I'm building an ecommerce site with filter pages and parameter URLs what technical SEO setup do I need?

For an ecommerce site with filter pages / parameter URLs, the main technical SEO goal is to make sure search engines can crawl the important pages, index the right URLs, and avoid duplicate/thin content issues caused by faceted navigation.

Here’s the setup I’d recommend.

---

1) Decide which filter pages deserve to rank

Not every filter combination should be indexable.

Usually index:

• Core category pages
• Valuable subcategory pages
• A small set of high-demand filter landing pages, e.g.:
  • /shoes/running/
  • /dresses/black/
  • /laptops/gaming/

Usually noindex / canonicalize:

• Endless parameter combinations
• Sort orders
• Temporary filters
• Empty or near-empty combinations
• Facets that don’t create unique search demand

A good rule: only index filter URLs that have unique search intent and enough product inventory.

---

2) Create a URL strategy before launch

You need a clear pattern for how filters appear in URLs.

Best practice

Use clean, crawlable path-based URLs for valuable landing pages:

• /category/filter-value/
• /women/shoes/black/

Use parameters mainly for sorting, pagination, or non-indexable filters:

• ?sort=price_asc
• ?page=2
• ?color=black&size=9

Avoid:

• Multiple parameter variations for the same page if possible
• Session IDs
• Random tracking params being indexable
• URLs that generate infinite combinations

---

3) Control indexation with canonical tags

For duplicate or near-duplicate parameter URLs, use canonical tags.

Example

If this is a filtered result page:

• /shoes?color=black&brand=nike

Canonical might point to:

• /shoes/black/nike/
  or
• /shoes/

depending on whether that filtered page is meant to be indexed.

Important

• Canonical should usually point to the preferred version of the same content
• Don’t canonical every filtered page to the homepage unless that’s truly the intended equivalent
• Canonicals are a strong hint, not a guarantee

---

4) Use robots.txt carefully

Robots.txt can reduce crawl waste, but it does not remove already indexed URLs by itself.

Good use cases

Block useless crawl paths like:

• internal search results
• login/account URLs
• infinite calendar or sort combinations
• some parameter patterns that generate massive crawl traps

Be careful

Do not block URLs you want Google to see canonical tags on if those URLs are needed for discovery. If blocked, Google may not process the canonical or content.

Common approach

• Allow crawling of important category/filter landing pages
• Block truly useless parameter patterns if they cause crawl traps

---

5) Use meta robots for index control

For pages you don’t want indexed but do want crawled:

• Use meta robots="noindex,follow"

This is useful for:

• low-value filtered pages
• sort pages
• duplicate parameter URLs

Why follow?

It lets search engines continue crawling links from those pages.

---

6) Manage pagination properly

Pagination is important for ecommerce category pages.

Recommendations

• Make paginated URLs crawlable
• Each page should have a unique URL
• Canonical should generally self-reference on paginated pages
• Don’t canonical all paginated pages to page 1 if products are different
• Ensure products are reachable through category navigation and internal links

Examples:

• /shoes/?page=1
• /shoes/?page=2

Or cleaner:

• /shoes/page/2/

---

7) Build internal linking around indexable pages

Search engines discover important pages through links.

Make sure your site links to:

• main categories
• high-value filter landing pages
• top-selling subcategories
• pagination paths

Avoid overlinking to every possible filter combination

That creates crawl bloat and weakens site architecture.

Best practice

Create curated landing pages for important combinations and link to them from:

• category headers
• facet modules
• editorial content
• navigational menus where appropriate

---

8) Handle faceted navigation intelligently

Facet systems can create an explosion of URLs.

Common facets

• color
• size
• brand
• price
• rating
• material
• availability
• sort

Indexable candidates

Usually:

• category + brand
• category + major attribute
• category + high-intent product type

Usually not indexable:

• multiple attribute combinations
• size filters
• price sliders
• rating filters
• availability-only filters
• sort combinations

---

9) Avoid thin-content indexable pages

If a filtered URL has:

• very few products
• no meaningful text
• little differentiation from another page

…it probably should not be indexed.

For pages you do want indexed

Add:

• unique title tag
• unique H1
• short intro text
• helpful copy about the filter/topic
• structured data where relevant

---

10) Use XML sitemaps strategically

Only include URLs you want indexed.

Include:

• main category pages
• valuable SEO landing pages
• products
• important subcategories

Exclude:

• parameterized filter URLs
• sort pages
• noindex pages
• low-value duplicates

This helps search engines focus on the right URLs.

---

11) Consider parameter handling rules in Google Search Console

Google used to have a URL Parameters tool, but it’s no longer broadly used as a main solution. Don’t rely on it as your primary strategy.

Instead, use:

• proper URL design
• canonicals
• robots rules
• noindex
• internal linking
• sitemaps

---

12) Ensure consistent URL normalization

Make sure only one version of each page is accessible.

Normalize:

• HTTP → HTTPS
• www → non-www or vice versa
• trailing slash consistency
• lowercase URLs
• one version of query parameter order if possible
• remove tracking params from indexable links

Example

These should not all be treated as separate pages:

• /shoes/
• /shoes
• http://example.com/shoes/
• https://www.example.com/shoes/?utm_source=email

---

13) Use structured data where relevant

For ecommerce product and category pages, add:

• Product schema
• Breadcrumb schema
• Organization schema
• Offer schema where appropriate

For filter landing pages, structured data should reflect the page’s actual content, not generic markup.

---

14) Make crawl behavior observable

You’ll want to monitor:

• indexed pages
• crawl stats
• duplicate titles/descriptions
• parameter URL indexation
• pages discovered but not indexed
• soft 404s
• crawl traps

Tools

• Google Search Console
• server log analysis
• SEO crawlers like Screaming Frog, Sitebulb, etc.

---

15) A practical SEO policy for parameter URLs

Here’s a simple policy you can implement:

Index

• Category pages
• Curated SEO landing pages
• A limited set of high-value filter pages

Noindex

• sort URLs
• most parameter combinations
• low-value filtered results
• internal search results

Canonical

• self-canonical for important indexable pages
• canonical to preferred category or landing page for duplicates

Robots.txt

• block crawl traps and useless paths
• don’t block pages you need crawled for canonical/noindex logic

Sitemap

• include only canonical, indexable URLs

---

Example setup

Indexable

• /mens-shoes/
• /mens-shoes/running/
• /mens-shoes/nike/
• /mens-shoes/black/

Not indexable

• /mens-shoes?sort=price_asc
• /mens-shoes?color=black&size=11
• /mens-shoes?brand=nike&sort=best_selling
• /search?q=shoes

---

Recommended default architecture

If you want a safe default:

1. Make core categories indexable
2. Create only a limited number of static, SEO-focused filter landing pages
3. Keep most faceted combinations as non-indexable
4. Canonicalize duplicates
5. Noindex sort and low-value parameter pages
6. Block crawl traps in robots.txt
7. Include only approved URLs in sitemaps

---

Quick checklist

• Clear indexable vs non-indexable filter policy
• Clean URL structure
• Canonical tags implemented
• noindex,follow on low-value parameter pages
• Robots.txt blocking crawl traps
• Pagination handled correctly
• Only canonical URLs in XML sitemap
• Normalized URL variants
• Internal links to important pages only
• Monitoring in GSC and logs

---

If you want, I can also give you:

1. a sample robots.txt + canonical strategy,
2. a decision tree for which filter pages should be indexable, or
3. a technical SEO implementation spec for developers.