Technical SEO for Online Stores: The Checklist

In this article10 sections
Technical SEO for ecommerce makes sure search engines can find, crawl, understand and index the pages that matter in your store, without wasting effort on thousands of pages that do not. Online stores are especially prone to technical problems: filters create endless URL variations, products appear in several categories, items go out of stock and platforms add parameters to links. A store with sound technical foundations lets its products, categories and content compete on their merits. One with hidden technical faults can lose rankings no matter how good the content is.
Key takeaways
- Control which pages search engines crawl and index; most filter and sort combinations should stay out.
- Use canonical tags so every product and category has one main URL.
- Keep XML sitemaps clean: only live, indexable pages that return a normal response.
- Fix redirect chains, broken links and "soft" error pages that confuse crawlers.
- Add product, breadcrumb and organisation structured data, and test it regularly.
How search engines see your store
Search engines send crawlers that follow links from page to page, read what they find and decide which pages to add to their index. For a small website, crawlers usually manage everything. For an online store with thousands of products and filters, the number of possible URLs can run into millions. Crawlers then have to choose where to spend their time.
Google explains how it decides what to crawl on large sites in its guide to managing crawl budget. The practical lesson for store owners is simple: make it easy for crawlers to reach your important pages, and hard for them to wander into endless low-value ones.
Before changing anything, check Google Search Console. The Pages report shows which URLs are indexed, which are excluded and why. Large numbers of excluded or "crawled, currently not indexed" pages often point to technical problems worth investigating.
Crawling and indexing controls
robots.txt
The robots.txt file tells crawlers which parts of the site not to crawl. Use it to block areas with no search value, such as the cart, checkout, customer account pages and internal search results. Do not use it to hide pages you want removed from the index; a blocked page can still appear in results if other sites link to it.
Meta robots and noindex
A "noindex" tag tells search engines not to include a page in results, even if they crawl it. Use it for thin or duplicate pages you need to keep for shoppers, such as some filter combinations. Check that no important page carries a stray noindex tag, a common accident after launches.
Parameters and tracking codes
Marketing tags, sorting options and session codes can add parameters to your URLs, creating many versions of the same page. Keep parameters out of internal links where possible, and point every variation to the clean URL with a canonical tag. Check your platform settings too, as some add parameters by default.
Internal links
Crawlers find pages mainly through links. Every important product and category should be reachable through normal links from the menu, categories, breadcrumbs or related products, not only through search or scripts.
Duplicate content and canonical tags
Online stores create duplicate pages easily:
- The same product reachable through several category paths.
- URLs with tracking, sorting or session parameters.
- Product variants on separate URLs with nearly identical content.
- HTTP and HTTPS, or "www" and non-"www" versions of the same page.
A canonical tag tells search engines which URL is the main version. Every page should have one, pointing either to itself or to the preferred version. Link internally to the canonical URLs, not the duplicates, and make sure the canonical, the sitemap and the internal links all agree.
Our guide to category page SEO explains how to treat filter combinations that deserve their own indexable pages.
XML sitemaps
A sitemap lists the pages you want search engines to know about. For a store, it usually includes products, categories, content pages and blog posts, often split into several files.
- Include only pages that are live, indexable and return a normal response.
- Exclude redirected, noindexed, out-of-scope and error pages.
- Update it automatically when products are added, changed or removed.
- Submit it in Search Console and reference it in robots.txt.
- Use accurate "last modified" dates, which help crawlers find changes.
Compare the number of URLs in the sitemap with the number indexed. A large gap is worth investigating, because it often means search engines judge many of your pages as duplicates or too thin to include.
Redirects, errors and out-of-stock pages
Redirects
Use permanent (301) redirects when pages move. Avoid chains, where one redirect leads to another, and loops. Update internal links to point straight to the final URL.
Not-found pages
Pages that no longer exist should return a proper "not found" (404) or "gone" (410) response, not a normal page saying "product not found". Those "soft 404" pages confuse search engines.
Out-of-stock and discontinued products
Keep temporarily unavailable products live, marked as out of stock, so they keep their rankings. Redirect discontinued products with value to the closest replacement or category. Our guide to migrating without losing SEO covers redirect planning in depth.
Structured data
Structured data describes your pages in a format search engines understand directly. For stores, the most useful types are:
| Type | Where | What it can show |
|---|---|---|
| Product | Product pages | Price, availability, ratings in search results |
| BreadcrumbList | Products and categories | The page's place in your site structure |
| Organization | Site-wide | Your business name, logo and contact details |
| FAQPage | Pages with genuine questions and answers | Helps search engines understand the content |
| Article | Blog posts and guides | Author, dates and headline |
Keep structured data accurate and in line with what shoppers see on the page. Prices and stock in structured data must match the visible page. Test with Google's Rich Results Test and watch the enhancement reports in Search Console for errors.
International stores and hreflang
If you run versions of your store for different countries or languages, hreflang tags tell search engines which version to show to which audience. Each version should link to all the others, including itself, and use the correct language and country codes. Google's guide to localised versions of pages explains the setup. Mistakes are common, so check the tags with a crawler after every change. Our guide to selling online in Europe covers the business side of running several country versions.
JavaScript, speed and mobile
JavaScript
Search engines can render JavaScript, but it takes more effort and can delay indexing. Make sure product names, prices, descriptions and links are present in the page's HTML, not only added later by scripts. Test important templates with the URL Inspection tool to see what Google actually renders.
Speed
Slow pages frustrate shoppers and can hold back rankings. Our guide to Core Web Vitals for online stores explains what to measure and fix first.
Mobile
Google mainly uses the mobile version of your pages. Content, links and structured data must be the same on mobile as on desktop.
Your technical SEO for ecommerce checklist
Use this list as a regular review. Most items can be checked in Search Console and with a crawling tool; your developer can fix what you find.
| Area | Check |
|---|---|
| Indexing | No important page carries noindex; Pages report reviewed for unexpected exclusions |
| robots.txt | Cart, checkout, account and internal search blocked; nothing important blocked |
| Canonicals | Every page has one; it matches the sitemap and internal links |
| Filters | Valuable combinations indexable; the rest canonicalised or noindexed |
| Sitemaps | Only live, indexable URLs; submitted and updating automatically |
| Redirects | Single-step 301s; no chains or loops; internal links updated |
| Errors | Real 404 or 410 responses for removed pages; no soft 404s |
| Structured data | Product, breadcrumb and organisation markup valid and accurate |
| International | hreflang complete and reciprocal on every language version |
| Rendering | Key content and links present in HTML; URL Inspection matches |
| Speed | Core Web Vitals passing on mobile for main templates |
| HTTPS | One secure version of every URL; others redirect to it |
Monitoring between audits
Technical problems often appear quietly after a change: a theme update removes structured data, a new app adds parameters to every link, or a developer leaves a staging setting in place. Set up simple monitoring so you hear about issues quickly. Search Console can email you about new errors. A scheduled crawl of your main templates, run weekly, catches broken links, missing titles and unexpected noindex tags. Some teams also check server logs to see which pages crawlers actually visit; if crawlers spend most of their time on filter URLs and rarely reach new products, your crawling controls need work.
Working with your developer
When you report a technical SEO issue, give your developer the affected URLs, what you expected, what actually happens and where you saw it, such as a screenshot from Search Console. Ask for fixes at the template level, so every similar page benefits, and ask them to check the change on staging before it goes live. Keep a short log of technical changes and their dates. When traffic moves, that log is often the fastest way to find the cause.
Technical SEO is one part of a wider picture. Our e-commerce SEO guide shows how it fits with keyword research, content and links.
Frequently asked questions
How often should I run a technical SEO audit?
A full audit once or twice a year, plus monthly checks of Search Console and a crawl after every major change, such as a new theme, platform update or migration.
Should I block filter pages in robots.txt?
It depends. Blocking stops crawling but not indexing of linked pages. Many stores use canonical or noindex tags on most filter pages, and keep a few valuable combinations indexable.
Do I need a developer for technical SEO?
For many fixes, yes. You can spot problems in Search Console yourself, but changes to templates, canonical tags, redirects and structured data usually need a developer.
Will fixing technical issues increase traffic straight away?
Some fixes, such as removing an accidental noindex tag, can help quickly. Most improvements show gradually as search engines recrawl the site.
Want to know what is holding your store back technically? Ask us for a technical SEO audit, with clear priorities your team or ours can act on.
Want an expert to look at your store?
Tell us what you are working on. A senior e-commerce consultant will reply within one working day with honest, practical advice. No obligation and no sales script.
- Reply within one working day
- Advice even if we are not the right fit
- Your details are never shared