Shopify already handles most of the technical SEO a store needs: sitemaps, canonical tags, robots.txt, HTTPS, and mobile templates. The technical work left for merchants is protecting that foundation from app bloat, indexable filter URLs, broken redirects after handle changes or deletions, and badly planned migrations.
Most Shopify stores do not lose organic traffic because the platform is bad at SEO. They lose it because someone installed, renamed, deleted, or migrated something without thinking about what Google had already indexed.
Picture a merchant who sends over an SEO audit PDF. Forty pages, a red score on the cover, and 1,800 “duplicate content” errors on page three. The agency that ran it is quoting a monthly retainer to clean it up. The store runs a standard Shopify theme with about 400 products, and almost every one of those errors is a product URL that Shopify has already told Google how to handle.
It is a familiar pattern. Technical SEO is the part of search most merchants feel least equipped to judge, so it is the easiest part to sell them work they do not need. Meanwhile the problems that do cost traffic on Shopify rarely show up on page one of an automated report, because they come from decisions the merchant made, not from the platform.
This guide splits the two. If you are just getting started, the first half will save you money. If you are scaling, the second half is where your traffic is most likely leaking.
Shopify handles the technical SEO foundation for every store on a standard Online Store theme: it generates an XML sitemap, serves a default robots.txt file, adds canonical tags to product and collection templates, issues an SSL certificate, and delivers pages through a global CDN on mobile ready themes. None of that needs an app or a developer to switch on.
That matters because the classic technical SEO checklist was written for self hosted platforms, where each of those items could be missing or misconfigured. Jeff Oxford, founder of the ecommerce SEO agency 180 Marketing, made the point directly when he joined me on episode 409 of the podcast on Shopify SEO after AI:
“Shopify pretty much covers a lot of the technical SEO issues we see. Now. If we were having this podcast 10 or 15 years ago, when most people are on Magento or Volusion or Yahoo Stores, all these old platforms, it’d be an entirely different conversation.”
He went further: “But if you’re on Shopify, honestly in most cases technical SEO is most likely an afterthought and you don’t need to go too much into it.” That matches what I saw during my years working with Shopify merchants. The stores that struggled in search were rarely held back by the platform’s technical setup. They were held back by thin collection pages, weak titles, or a change that broke something Google had already learned to trust.
There are limits. Shopify’s defaults assume you use the platform the way it was designed: products, collections, pages, and a blog, served by a theme. The moment you add a filtering app that creates new URLs, a page builder that renders content in JavaScript, or a headless frontend, you start taking back responsibilities Shopify was carrying for you. Oxford’s point holds as long as you know where that line is.
So the first technical SEO decision on Shopify is a subtraction: stop treating the platform’s foundation as a project. Verify your domain in Google Search Console, submit the sitemap at yourstore.com/sitemap.xml, and then spend your attention on the things only you can break.
Most automated audits flag Shopify’s collection aware product URLs as duplicate content, but on a standard theme each of those URLs carries a canonical tag pointing to the single /products/ address, which is exactly how Google recommends handling duplicates. The warning is accurate about the URLs existing and wrong about it being a problem.
Here is the mechanic. When a shopper reaches a product from a collection, many themes link to an address like /collections/summer/products/linen-shirt. The same product also lives at /products/linen-shirt. A crawler that ignores canonical tags sees two pages with identical content and logs an error. Google does not ignore them. Its guidance on consolidating duplicate URLs with canonical tags describes precisely this setup as the way to tell it which version to show.
The same pattern shows up with robots.txt. Audit tools often complain that Shopify blocks /cart, /checkout, /account, and order pages from crawling. Those blocks are deliberate: none of those pages should rank. Shopify does let you edit the file through a robots.txt.liquid template, and its own guidance on editing robots.txt warns that mistakes can cost you all of your traffic. I would treat that template as a tool for one specific problem, usually filter URLs (covered below), and never as a place to “clean up” warnings.
The risk with these false positives is not only wasted money. It is the fix. A store that removes canonical tags, rewrites theme links, or blocks whole URL patterns to clear an audit score can create a real indexing problem where there was none. A red score on a report is not evidence of lost traffic. Search Console’s Page indexing report, showing which URLs Google actually indexed and why others were excluded, is the evidence that counts.
Two scope notes. Shopify themes also output basic Product structured data, so the common structured data problem is not missing schema but a reviews or SEO app adding a second, conflicting Product block; Google’s Rich Results Test will show you if a page carries two. And stores selling into several countries through Shopify Markets have an extra layer (language and country URLs with hreflang) that deserves its own review; the defaults described here assume a single market.
If your organic revenue is falling and you need a triage order rather than a primer, the technical SEO priority list for stores losing organic sales walks through how to tie a decline to specific pages and dates before changing anything.
Shopify stores break technical SEO in four places the merchant controls: filter and tag URLs that multiply into thousands of indexable pages, apps that inject content through JavaScript or slow every template, product handles that get renamed or deleted without redirects, and platform migrations run without a redirect map.
Filter and tag URLs. Collection filters create parameter URLs for every combination of size, color, price, and availability. A collection with five filters can generate more URLs than the store has products. Google’s own documentation on managing crawling of faceted navigation says these URLs can waste crawl capacity and slow discovery of the pages you care about. Filtered views are rarely pages you want ranking anyway. Jeff Oxford’s advice on episode 409 was the practical alternative: when people search for a specific variant, such as blue running shoes, give it a real collection page with its own copy instead of relying on a sidebar filter. Filter apps vary in whether they create crawlable links, so check what yours does in Search Console before you assume.
JavaScript rendered content. Reviews widgets, page builder sections, and some product description apps load their content after the page renders. Google can process JavaScript, but its JavaScript SEO basics explain that rendering is a separate step, which is why the safe default is to keep anything you want ranked in the HTML the server sends. Run Search Console’s URL Inspection tool on a key page and look at the rendered HTML. If your collection copy or FAQ is missing, Google may not be counting it.
Renamed and deleted products. When you change a product’s URL handle, Shopify offers to create a redirect from the old address, and its URL redirect documentation shows where to manage them. Unticking that box, or deleting a discontinued product outright, turns an indexed page with links into a 404. For a product that earned backlinks or ranked well, redirect it to the closest replacement or its collection.
Migrations. This is the expensive one. A move to Shopify from another platform changes nearly every URL on the site, and every old address needs a one to one redirect to its new home. In the migrations I worked on during my agency years, a temporary dip while Google recrawled the new structure was normal. A permanent loss usually traced back to a redirect map built in a hurry at the end of the project.
Measure Shopify speed with real visitor data from the Web performance report in your admin, and when a template is slow, remove or replace the heaviest app before paying for code optimization. Most Shopify speed problems are added by apps and theme customizations rather than by the platform.
Shopify’s web performance reports show Core Web Vitals from real visitor sessions, which is closer to what Google uses than a one off lab test. Lab tools like PageSpeed Insights are useful for diagnosis, but a single mobile lab score swings from run to run and is a poor basis for a buying decision. The metric most merchants have not caught up with is Interaction to Next Paint, which replaced First Input Delay as a Core Web Vital in March 2024. INP measures how quickly the page responds when a shopper taps a variant, opens a menu, or adds to cart, and it is the metric script heavy apps hurt most.
The fix order I recommend is subtraction first. List every app that loads on the storefront, note which templates it touches, and ask whether it earned its place in the last 90 days. Apps you uninstalled can leave code in the theme, so check the theme files or ask the app developer what to remove. Only after the app list is honest is it worth paying a developer to defer scripts or compress images.
Keep speed in proportion. It is a ranking factor, but a modest one compared with whether the page answers the search. A collection page that loads quickly and says nothing will lose to a slightly slower page with useful copy. Speed earns more of its value in conversion than in rankings, which is a good reason to fix it, as long as nobody sells it to you as the reason you are not on page one.
On a mid size Shopify store with a long app list and a past migration, I would start with the redirect history and indexed filter URLs, then the app list, and leave the audit tool’s duplicate content warnings alone. This is a composite, built from patterns I have seen across merchant conversations, not one real store, and the details below are illustrative.
Picture an apparel brand doing around $1.5M a year. It moved to Shopify two years ago from an older platform, runs a third party filter app on its collections, has a reviews widget and a page builder installed, and has been told by an agency that its technical SEO is “critical.” Organic revenue has been flat while paid spend keeps rising.
What I would look at, in order. First, Search Console’s Pages report: how many URLs are indexed compared with how many products and collections the store has. If indexed pages run far ahead of the catalog, filter URLs are the likely cause. Second, the redirect list against the old site’s top pages, using whatever backlink data is available. Migrated stores often redirect products but forget old category pages and blog posts, which are frequently the ones with links. Third, URL Inspection on two collection pages to see whether the page builder’s copy appears in the rendered HTML.
What I would conclude. If filter URLs are being indexed at scale, the fix is to stop the app generating crawlable links or to block those parameters, and that one change does more than every item on the audit’s first page. Missing redirects for old category URLs get mapped to their closest collections. If the page builder hides collection copy from Google, that copy moves into the theme’s native description field.
What I would remove or not buy. The monthly retainer to fix duplicate product URLs, because the canonicals already do that work. And probably the page builder on collection templates, because a native section does the same job without the script weight or the rendering risk.
You could disagree with the order. A store with a serious INP problem on mobile might reasonably fix speed first. But on most mid size stores, the indexing and redirect problems are bigger and cheaper to fix, and Oxford’s view on episode 409 is a useful reminder of what comes after them: when a collection page sits at position ten behind a competitor, the gap is usually links and content, not another technical fix.
Technical SEO priorities on Shopify scale with the number of URLs and the number of people touching the store: under $500K a year the job is mostly protecting defaults, between $500K and $5M it is policing apps, filters, and redirects, and above that it becomes a governance process with someone accountable for every URL change.
If you are just starting, the whole technical list is short. Verify Search Console, submit the sitemap, keep the redirect box ticked when you rename a product, and resist installing apps you are not sure you need. Put your effort into page titles and collection copy instead. Getting those right is covered in this guide to writing titles and meta descriptions Google actually shows, and it will move your traffic more than any technical change at this stage.
If you are scaling through $500K to $5M, the catalog and the app list are both growing, and so are the ways to break things. This is the stage where a quarterly check earns its time: indexed page count against catalog size, a review of new apps for storefront scripts, and a redirect check after every product cull. Merchants at this stage fail far more often from accumulated complexity than from anything the platform did.
Above $5M, the risk shifts to coordination. Several people and agencies edit the theme, launch landing pages, and change navigation. Technical SEO becomes a process: a named owner for redirects, a staging review before theme changes go live, and an SEO voice in any replatforming or headless discussion months before launch rather than weeks. If you are weighing a bigger platform change, the signs in this piece on knowing when you have outgrown your ecommerce platform are worth reading before you commit to a migration and its redirect workload.
At every stage, the same foundation now feeds AI search as well as Google’s blue links. Indexable pages with accurate product data are what AI Overviews and assistants draw from, as this look at Google AI Overviews coverage for Shopify shopping searches explains. Protecting the technical basics protects both.
Shopify is good for technical SEO on a standard Online Store theme, because it generates the sitemap, robots.txt file, canonical tags, and SSL certificate automatically and serves pages through a fast CDN. Most of the technical checklist written for self hosted platforms is already handled. The weaknesses people mention, such as fixed URL prefixes like /products/ and /collections/, rarely affect rankings in practice. Where Shopify stores do run into trouble is with what merchants add: filter apps that create thousands of crawlable URLs, apps that load content through JavaScript, and redirects missed during migrations or product deletions. If you avoid those, the platform will not be what holds your rankings back.
On a standard Shopify theme you usually do not need to fix duplicate product URLs, because each collection based product URL already carries a canonical tag pointing to the main /products/ address. That is the method Google recommends for consolidating duplicates. Audit tools that ignore canonical tags will still report these as errors. Check the real picture in Google Search Console’s Pages report, which shows whether Google chose your canonical. Genuine duplicate content problems on Shopify usually come from elsewhere: filter or tag parameter URLs being indexed, the same description copied across many products, or a page builder creating near identical landing pages. Fix those instead of editing theme links or canonicals.
Most Shopify stores should not edit robots.txt, because the default file already blocks the cart, checkout, account, and order pages that should never rank. Shopify allows edits through a robots.txt.liquid template, and its help documentation warns that incorrect edits can cost you all of your traffic. The main legitimate reason to edit it is to stop search engines crawling large numbers of filter or parameter URLs created by a collection filtering app. Even then, make one narrow change, test the affected URLs in Search Console, and keep a copy of the original. Never edit the file just to clear warnings in an audit tool.
Deleting a product on Shopify makes its URL return a 404 error, and any rankings or backlinks that page earned stop helping your store. Shopify does not redirect deleted products automatically. Before deleting a product that had organic traffic or links, create a URL redirect in your admin from the old address to the closest replacement product or its parent collection. For seasonal items that will return, consider keeping the page live and marked out of stock instead. Check Search Console’s Pages report after a large product cull to catch any important URLs that slipped through without a redirect.
Shopify apps can slow down your store when they load scripts on every storefront page, and the effect shows up most in Interaction to Next Paint, the Core Web Vital that measures how quickly the page responds to taps and clicks. Speed is a modest ranking factor, but slow templates also cut conversion. Check Shopify’s web performance reports for real visitor data, then review which apps load on the storefront and which templates they touch. Remove apps that have not earned their place, and ask developers what code their apps leave in the theme after uninstalling, since leftover snippets can keep loading.
