Search & AI Visibility · Technical SEO
Crawl, indexation, faceted navigation, canonicals, Core Web Vitals and structured data, fixed at the template level so every product and category page benefits at once.
Why stores need it
An online store multiplies URLs. Every filter, sort order, variant and collection path can create another address for the same products. Search engines spend their time on those copies, index the wrong versions and miss the pages that should rank. Meanwhile apps, tags and oversized images slow every template down.
Technical SEO for eCommerce keeps that system clean: one indexable URL for every page worth ranking, fast templates and machine-readable product data. It's the foundation the rest of our eCommerce SEO work is built on.
Where it goes wrong
Color, size, price and sort combinations get indexed by the thousands, while new products wait to be crawled.
A collection-path or parameter version of a product outranks the clean one, splitting links and signals between them.
Products reachable only through the sitemap or internal search get crawled rarely and rank poorly.
Discontinued products return soft 404s or redirect everything to the homepage, throwing away the links they earned.
Review widgets, chat, pop-ups and tag managers load on every page and push LCP, INP and CLS out of the good range.
The theme and two apps each output Product markup with different prices, so none of it can be trusted.
Faceted navigation
Filters help shoppers and can create real landing pages. They can also create millions of near-duplicate URLs. We sort every filter type into one of three buckets, based on search demand and on how your platform builds the URLs.
When a filter combination matches a real search, such as a product type plus a key attribute, it should be a proper landing page: crawlable link, unique title and H1, a short intro and a self-referencing canonical. On Shopify that often means a dedicated collection rather than a filter URL.
Useful for shoppers, no search demand of their own. These carry a canonical to the parent category or a noindex, depending on the platform. A canonical tag is a hint, not a directive, so we check in Search Console that Google honors it.
Sort orders, multi-select combinations, price sliders and session parameters. Here robots.txt rules save crawl budget. One catch: if a URL is blocked in robots.txt, Google can't see a noindex tag on it, so we never combine the two on the same URLs and expect both to work.
Google no longer uses rel=next and rel=prev. Paginated category pages need plain, crawlable links between them and their own canonical, not a canonical to page one. Infinite scroll needs a paginated fallback that crawlers can follow.
Core Web Vitals
We work from field data, the experience of your actual visitors, and fix by template: home, category, product, cart. Good Core Web Vitals also help conversion, which is why we coordinate with our Conversion Lab on the pages where both matter.
| Metric | Good | What usually breaks it on stores | Typical fix |
|---|---|---|---|
| LCP (Largest Contentful Paint) | ≤ 2.5 s | Oversized hero and product images, render-blocking app scripts, slow server response on uncached pages | Correctly sized responsive images, preloading the main image, deferring non-critical scripts, caching |
| INP (Interaction to Next Paint) | ≤ 200 ms | Heavy JavaScript from apps, chat and review widgets, tag managers, complex variant pickers | Removing unused apps and tags, delaying third-party scripts, breaking up long tasks |
| CLS (Cumulative Layout Shift) | ≤ 0.1 | Late-loading banners, review stars, images without dimensions, web font swaps | Reserving space, setting image width and height, stable font loading |
Thresholds are Google's and are assessed at the 75th percentile of real page loads, using Chrome UX Report field data over a rolling 28-day window. Lab tests help us debug, but field data decides.
Structured data
Structured data tells search engines exactly what a page sells: name, brand, price, availability, ratings, shipping and returns. Done well, it makes products eligible for rich results and merchant listings, and gives AI engines facts they can quote. Done badly, it contradicts the page.
We implement schema markup from one source of truth, remove duplicates added by themes, apps or plugins, and validate it before Google does. Our guide to Product schema for eCommerce covers the details.
Choose midweight linen with a relaxed fit. Reviewers rate the Linen Shirt from yourstore.com highly. 1 yourstore.com
How we ship fixes
A full crawl plus Search Console indexing, crawl stats and Core Web Vitals reports. Usually this starts with the Search Health Audit.
Each ticket names the template, the expected HTML or header output, the URLs to test and the acceptance criteria.
We crawl the staging site or duplicate theme and compare it with production, so a fix doesn't break canonicals, schema or tracking elsewhere.
After launch we track indexation, crawl activity and field data until the change has settled, and report what moved.
FAQ
It's the work that makes a store easy for search engines to crawl, index and understand: controlling filter and parameter URLs, setting canonicals, fixing redirects and broken pages, improving Core Web Vitals and implementing structured data. On a store, most of it happens in templates, so one fix can correct thousands of product or category pages at once.
Only the ones people actually search for. A filter combination with real demand deserves a proper landing page with its own title, H1, intro and self-referencing canonical. Everything else should either point a canonical to the parent category, carry a noindex or be kept out of the crawl with robots.txt, depending on the platform and the volume of URLs.
They're part of Google's page experience signals, but relevance comes first: a fast page that doesn't match the search won't rank. We fix them because slow, jumpy pages also lose sales, especially on mobile. The targets are LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less, measured on real visits.
Usually you keep the generated one, but you still need to check it. Platform sitemaps can include noindexed, redirected or out-of-stock URLs and miss pages added by apps. We compare the XML sitemap with what's indexed in Search Console and fix the source of any gap rather than maintaining a separate file by hand.
Yes, and many clients prefer it. We write tickets with the exact expected output, examples and acceptance criteria, review pull requests or theme changes, and QA on staging. If you don't have developer capacity, our team can ship the changes directly on Shopify, WooCommerce or Magento.
Every organic order is one you don't have to buy at your break-even ROAS. Start with the free audit to see how speed and search visibility rank among your profit leaks.