Ecommerce SEO Audit: A Shopify Checklist Built On Google’s And Shopify’s Own Documentation

Shopify builds several SEO basics into every store before anyone changes a setting. Its help center says every store automatically generates a sitemap (opens in new tab), ships a default robots.txt file (opens in new tab), gets auto-generated canonical tags (opens in new tab), and runs on themes that include structured data by default. So an ecommerce SEO audit on Shopify is a short list of checks. Each check looks for a place where a theme, an app or a merchant decision has broken or bypassed one of those defaults, or reads a Search Console report the way Google defines it.

BLKDG builds Shopify stores, so the checks below start from what the platform does by default and work outward to the theme and apps. If rankings have already fallen, diagnose the ranking drop first. A drop diagnosis looks for what changed, and an audit looks for what’s misconfigured, so the two start from different evidence.

Google’s Page indexing report documentation (opens in new tab) defines the target: “Your goal is to get the canonical version of every important page indexed. Duplicate or alternate pages shouldn’t be indexed.” A Shopify store fills the duplicate and alternate buckets as a matter of course, because the platform can serve one product at several URLs. Google says (opens in new tab) of those buckets that “Having a page marked duplicate or alternate is usually a good thing; it means that we’ve found the canonical page and indexed it.”

So read the report by status, not by its total. Here’s how we apply Google’s status definitions (opens in new tab) to a Shopify store. Collection-scoped and variant URLs that point their canonical at /products/ are expected to fill the duplicate and alternate buckets. “Duplicate without user-selected canonical” deserves a look on Shopify, though: Google defines it as a page that “doesn’t indicate a preferred canonical page,” and Shopify themes output a canonical tag by default.

The status to open on product URLs is “Duplicate, Google chose different canonical than user,” which Google defines this way: “This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical.”

For any product URL in that status, the URL Inspection tool (opens in new tab) shows the canonical you declared next to the one Google picked. For “Crawled – currently not indexed,” Google’s definition (opens in new tab) says “It may or may not be indexed in the future; no need to resubmit this URL for crawling.” For “Discovered – currently not indexed,” the same page says “Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.” A large share of URLs in that last status is one of the three site types Google’s crawl budget guide is written for, which gets its own section below.

How do you conduct an effective ecommerce SEO audit on a Shopify store? Start with the reports Google defines, then check each Shopify default in the order below: duplicate URLs and canonicals, filters and tags, robots.txt, crawl budget where it applies, sitemaps, redirects, pagination, structured data, on-page basics, Core Web Vitals and international setup. The first three apply to every store. The rest depend on what the store has installed and how it sells.

Shopify can put the same product at more than one path. The Liquid within filter (opens in new tab) “Generates a product URL within the context of the provided collection,” with a documented output of /collections/sale-potions/products/draught-of-immortality. Shopify’s own reference adds: “Because a standard product page and a product page in the context of a collection have the same content on separate URLs, you should consider the SEO implications of using the within filter.”

Whether a store has this problem depends on the theme. Shopify’s reference theme Dawn links product cards with {{ card_product.url }} and no within filter in its card-product.liquid snippet (opens in new tab), so on Dawn the collection grid links to the /products/ path. A theme or app that adds within puts the collection-scoped path into every internal link on the grid. Google’s canonical guidance (opens in new tab) says the opposite: “When linking within your site, link to the canonical URL rather than a duplicate URL.”

Duplicates aren’t a penalty. Google’s canonicalization overview (opens in new tab) says “Some duplicate content on a site is normal and it’s not a violation of Google’s spam policies,” and that “indicating a canonical preference is a hint, not a rule.” The same page says “The canonical page will be crawled most regularly; duplicates are crawled less frequently in order to reduce the crawling load on sites,” so whichever URL Google treats as canonical gets the most crawl attention.

Google ranks the signals it uses. Its canonical documentation (opens in new tab) calls redirects “A strong signal that the target of the redirect should become canonical,” a rel="canonical" annotation “A strong signal that the specified URL should become canonical,” and sitemap inclusion “A weak signal that helps the URLs that are included in a sitemap become canonical.” Internal links pointing at a duplicate path work against the canonical tag on that same page.

What the canonical tag did on one live store. On a live Shopify store we checked on September 23, 2026, the collection-scoped product URL returned a 200 and its canonical tag pointed at the /products/ URL. A ?variant= URL on the same product did the same, which matches Google’s ecommerce URL guidance (opens in new tab): “If you use optional query parameters to identify variants, use the URL with the query parameter omitted as the canonical URL.” That’s one store on a custom theme, on one day. Shopify’s canonical_url reference (opens in new tab) describes the object only as “The canonical URL for the current page,” and doesn’t document which URL it returns for collection-scoped, variant or filtered paths.

So the check is direct. View source on one product through /products/, through /collections//products/ and through a ?variant= URL, and confirm each page carries exactly one canonical pointing at /products/. Shopify’s metadata documentation (opens in new tab) shows the standard implementation as inside , and Dawn’s theme.liquid (opens in new tab) uses the same object. A theme that hardcodes or rewrites that tag, or an SEO app that injects a second one, is what breaks the default, and Google advises (opens in new tab) “Don’t specify different URLs as canonical for the same page using different canonicalization techniques”.

Google’s ecommerce URL guide (opens in new tab) tells platform users “you can most likely skip this section, as the platform has most likely already considered these issues for you.” On Shopify that holds for the URL design itself. The audit confirms that nothing installed since has undone it.

Don’t reach for noindex to force a canonical, either. Google says (opens in new tab) “We don’t recommend using noindex to prevent selection of a canonical page within a single site, because it will completely block the page from Search.”

Shopify’s storefront filtering documentation (opens in new tab) says “When filters are applied, they’re reflected in the collection or search URL through URL parameters,” in the form filter.p.product_type=Shoes for a product-level filter. Google’s faceted navigation guide (opens in new tab) says the parameter-based approach “can generate infinite URL spaces,” and names overcrawling and slower discovery crawls as the costs. The same guide splits the decision: “If you don’t need the faceted navigation URLs potentially indexed, prevent crawling of these URLs.”

Shopify’s default robots.txt covers part of this. The help center (opens in new tab) explains that “The Disallow: /collections/+ rule keeps filtered collection pages from being crawled, because they duplicate content that’s already on the collection page,” and that the sort_by rule blocks sorted views. The robots.txt served by Shopify’s own sample store (opens in new tab) on September 23, 2026 also disallowed /collections/filter&filter. Going by the rule syntax (our inference, not a Shopify statement), the defaults block collection URLs with multiple filters or multiple tags, while single-filter and single-tag URLs stay crawlable.

Google rates that fallback lower. Its faceted navigation guide (opens in new tab) says canonical and nofollow approaches “are generally less effective in the long term than the previously mentioned methods,” which include robots.txt, and that “Oftentimes there’s no good reason to allow crawling of filtered items, as it consumes server resources for no or negligible benefit”. On the live store we checked, a single-filter collection URL returned a 200 with a canonical pointing at the unfiltered collection, while a single-tag URL returned a 200 and was self-canonical.

That leaves the store with a choice, not a defect. If a single-filter view is something people search for, make it indexable and give it content that earns the index. If it isn’t, block the pattern in robots.txt.liquid. The check also includes loading a filter combination with no products, because Google says (opens in new tab) “Return an HTTP 404 status code when a filter combination doesn’t return results.”

Tag pages follow different rules. Shopify’s tag filtering documentation (opens in new tab) says “You should consider using storefront filtering instead of filtering by tag,” and “Tag filters are applied by appending /[tag-handle] to the collection URL”. It also says “If a tag in the URL isn’t used on any of the store’s products, then Shopify redirects to a collection URL with the tag removed,” and a dead tag URL on the live store we checked returned a 301 to the collection.

Merchants can’t redirect tag URLs themselves. Shopify’s redirect documentation (opens in new tab) says “You cannot create redirects for URLs that use collection tag filtering (such as yourstore.com/collections/collection-name/tag-name),” and “Even if no products exist with that tag, the URL path is still considered valid and cannot be redirected.” Read together, the two docs mean the platform handles dead tag URLs itself and the merchant can’t override it. The audit question is whether the theme still builds navigation on tags at all.

Shopify’s help center (opens in new tab) says “All Shopify stores have a default robots.txt file that’s optimal for Search Engine Optimization (SEO).” That’s Shopify’s claim about its own file. The mechanical point sits a few lines later on the same page: a theme with a robots.txt.liquid template that outputs the default rule groups “can include rules that the default file no longer has, such as Disallow: /search and Disallow: /policies/. To use the current default file, delete your robots.txt.liquid template.”

So a store with an old robots.txt.liquid can be serving a rule set Shopify has since changed. Shopify’s developer docs (opens in new tab) say “The default rules are updated regularly to ensure that SEO best practices are always applied.” The check is whether templates/robots.txt.liquid exists in the live theme and, if it does, whether each rule in it was added on purpose.

The same help page (opens in new tab) calls editing the template “an unsupported customization,” warns “Incorrect use of the feature can result in loss of all traffic,” and says of replacing it with plain text, “This method is strongly not recommended, as rules may become out of date.” It also says “Uploading a theme from within the Themes section of the Shopify admin won’t import robots.txt.liquid.” A store that uploaded a new theme through the admin may have lost its robots customizations without anyone deciding to remove them.

Shopify’s help center addresses the “Indexed, though blocked by robots.txt” status directly. Shopify calls it (opens in new tab) “normal behavior and usually not a cause for concern.” Google’s Page indexing documentation (opens in new tab) explains the mechanism: “Google always respects robots.txt, but this doesn’t necessarily prevent indexing if someone else links to your page.” Google’s robots.txt introduction (opens in new tab) says robots.txt “is not a mechanism for keeping a web page out of Google.”

That produces a conflict to check for. Google’s noindex documentation (opens in new tab) says “For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file, and it has to be otherwise accessible to the crawler.” A URL that’s both disallowed in robots.txt and tagged noindex never has its noindex read.

AI crawlers are a separate decision. Shopify’s help center (opens in new tab) says “Blocking AI crawlers at the /robots.txt or network layer affects only open-web discoverability. It doesn’t stop your product data from being sent by Shopify Catalog to the agentic storefronts that you’ve activated.”

The generated file on Shopify’s sample store now includes comments aimed at AI agents. How a store should handle AI search is its own topic, covered in our post on generative engine optimization for Shopify.

Google’s crawl budget guide (opens in new tab) is written for three kinds of site: “Large sites (1 million+ unique pages) with content that changes moderately often (once a week),” “Medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily),” and “Sites with a large portion of their total URLs classified by Search Console as Discovered – currently not indexed.” Google adds that “These are not exact thresholds.” Each page count comes paired with how often the content changes, so a 10,000-product store that updates weekly doesn’t fall into either numeric group.

The same guide (opens in new tab) says “If your site doesn’t have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don’t need to read this guide.” For those sites, Google says “keeping your sitemap up to date and checking the Page Indexing report regularly is adequate.” Shopify updates the sitemap automatically, which leaves the Page indexing report and the “Discovered – currently not indexed” share as the crawl budget check for most stores.

When crawl budget does apply, Google’s guide points at the same duplicates this audit already covers. It says Google “tries to crawl all or most of the URLs that it knows about on your site,” and when many of them are duplicates, “this wastes a lot of Google crawling time on your site. This is the factor that you can positively control the most.” Google’s list of fixes (opens in new tab) includes “Consolidate duplicate content,” “Eliminate soft 404 errors,” and “Avoid long redirect chains, which have a negative effect on crawling.”

Google also warns against one fix. The guide (opens in new tab) says “Don’t use robots.txt to temporarily reallocate crawl budget for other pages,” and that Google “won’t shift this newly available crawl budget to other pages unless Google is already hitting your site’s crawl capacity limit.” Server behavior is one of the factors that moves that limit: when a site “responds with server errors (5xx HTTP status codes) or rate-limiting signals (such as HTTP 429), the limit goes down and Google crawls less.” The Crawl Stats report (opens in new tab) in Search Console shows host status, average response time and requests broken down by response.

Two Google pages seem to disagree about noindex, and each is right about its own subject. The crawl budget guide (opens in new tab) says don’t use noindex to save crawling, “as Google will still request, but then drop the page”. The pagination guide (opens in new tab) lists the noindex robots meta tag as one way to keep filtered and sorted variants out of the index. Noindex controls indexing, not crawling.

Shopify’s sitemap documentation (opens in new tab) says “All Shopify stores automatically generate a sitemap.xml file that contains links to all your products, primary product image, pages, collections, and blog posts,” and that the files update automatically when you add content. Shopify generates that file, so the audit checks the product, page and collection settings that decide what goes into it.

Two settings take a URL out of it. Shopify’s documentation on hiding pages (opens in new tab) says the seo.hidden metafield set to 1 hides a page, blog post or product “from sitemaps, search engines, and your online store search,” and notes the metafield can be used by third-party apps. The same page says “When you set a product as Unlisted, the product is hidden from internet search, Shopify Catalog, and your store’s sitemap.” The check is a sweep for seo.hidden values and Unlisted status on products you want ranked, including values an app wrote before the store removed it, since Shopify notes the metafield “can be used by third-party apps.”

A few sitemap conditions apply before launch or on international setups. Shopify’s sitemap page (opens in new tab) says a sitemap reader “can’t access it if your website is set to private mode,” and “If you’re on the Basic plan or higher and use international domains, then you need to submit the sitemap file for each domain.” Shopify’s SEO FAQ (opens in new tab) adds that “Search engines don’t index trial stores.”

Shopify’s redirect documentation (opens in new tab) says “You can create a maximum of 100,000 URL redirects unless your store is on the Plus plan, which has a maximum of 20,000,000 URL redirects.” That limit counts URL redirects. The same page says a “Redirect Limit Exceeded” error from the Admin API isn’t related to it.

The rule that affects most audits is narrower. Shopify says (opens in new tab) “You can redirect only from broken URLs,” and “If the URL still loads a valid webpage, then the URL redirect won’t work.” If a product is republished or a handle is reused, the old redirect stops firing. For collections, Shopify says that if you change a hidden collection’s visibility back to Visible, “the URL redirect is automatically deleted because redirects only work for URLs that return 404 errors.”

A few more limits from the same page (opens in new tab) belong on the checklist. “You can’t redirect URLs that use fixed Shopify paths: /products, /collections, /collections/all.” Redirects apply across “all language or market subfolders set up using international sales tools,” and URLs with query strings “might not work as expected with URL redirects.”

The check is to export the redirect list from the admin and request every source URL. A source that loads a live page means that redirect no longer fires, and a target that redirects again is a chain. Chains hurt crawling, according to Google’s crawl budget guide (opens in new tab). For removed products with no replacement, Google’s guidance is to “Return a 404 or 410 status code for permanently removed pages.”

If the store recently changed platforms, our SEO migration checklist covers building the redirect map in the first place.

Google’s pagination guide (opens in new tab) says “Google’s crawlers don’t “click” buttons and generally don’t trigger JavaScript functions that require user actions to update the current page contents.” A theme or app that replaces collection page links with a Load more button or infinite scroll, and keeps no page links in the HTML, can leave deeper products reachable only through the sitemap. Google’s link guidance (opens in new tab) says “Generally, Google can only crawl your link if it’s an HTML element (also known as anchor element) with an href attribute.”

Dawn renders collection pages with Liquid’s paginate tag and real page links in main-collection-product-grid.liquid. The same Google guide (opens in new tab) says “Don’t use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL,” and that Google no longer uses rel next and prev. On the live store we checked, ?page=2 was self-canonical, which is what Google recommends.

Very large collections run into a Liquid limit. Shopify’s paginate reference (opens in new tab) says “The paginate tag allows the user to paginate to the 25,000th item in the array and no further.” Products past that point in a collection depend on the sitemap and other internal links.

How do you improve internal linking in an ecommerce store for SEO? Start with the rules Google documents. Google’s site structure guide (opens in new tab) says “If category pages don’t include direct links to all products in a category, Googlebot might not find all of your products by crawling alone,” and “Googlebot generally doesn’t try to submit searches into a search box as part of crawling a site.” It also says “As a general rule, the more links a page has to it within a site, the higher the relative importance of the page to other pages on your site,” so products and collections you want to rank need links from the navigation and from related pages, pointed at canonical URLs.

Shopify’s own guideline (opens in new tab) is that “Pages shouldn’t be more than 3 clicks away from the home page, wherever possible”. That’s Shopify’s number, and Google’s guide gives none.

Shopify says (opens in new tab) “Your Shopify store’s theme automatically includes microdata (also known as structured data) in its code,” and that current Shopify-supported and Theme Store themes include it by default. Dawn outputs {{ product | structured_data }} as JSON-LD in its main-product.liquid (opens in new tab) section. Shopify’s structured_data filter reference (opens in new tab) says “Product objects are output as a schema.org Product if they have no variants, and a ProductGroup if they have one or more variants.”

Google splits product markup by whether the page sells. Its product structured data overview (opens in new tab) describes product snippets as “For product pages where people can’t directly purchase the product” and merchant listings as “For pages where customers can purchase products from you.” Google’s merchant listing documentation (opens in new tab) requires name, image and offers on the Product, with price and priceCurrency on the Offer, and says “Unlike product snippets, merchant listing experiences require a price greater than zero.” Google’s merchant listing documentation recommends defining a standard return and shipping policy under Organization rather than on each Offer.

The merchant listing page also covers how markup is delivered. It warns that “dynamically-generated markup can make Shopping crawls less frequent and less reliable, which can be an issue for fast-changing content like product availability and price,” and recommends “putting Product structured data in the initial HTML for best results.” Here are the checks that follow from those docs. They’re things to look for, not problems Google or Shopify says Shopify stores have:

Those reports sit under Shopping, not Enhancements. Google’s rich result report documentation (opens in new tab) says “For product snippets and merchant listings, reports can be found under Shopping.” The product structured data overview (opens in new tab) also says “Providing both structured data on web pages and a Merchant Center feed maximizes your eligibility to experiences and helps Google correctly understand and verify your data.” Our post on structured data and product feeds for AI search covers the feed side.

Are Shopify themes SEO-friendly by default? For the basics, Shopify says so. Shopify’s SEO FAQ (opens in new tab) says “All Online Store 2.0 themes and themes that support theme blocks built by Shopify should have a valid title tag by default,” and its keywords guide (opens in new tab) says Shopify uses the title you enter to generate the H1 for product, collection, page and blog templates. The FAQ’s own diagnosis: “If you suspect that a page is missing a title tag, it’s likely the result of custom code or an app.”

Title length is Shopify’s field limit. Its keywords guide (opens in new tab) says “Page title: You can enter up to 70 characters in the title,” and Shopify recommends keeping titles to 60. The same page notes “Search engines, such as Google, can choose to rewrite page titles and meta descriptions based on the page content and other signals.”

For images, Google’s image guidance (opens in new tab) says “Avoid filling alt attributes with keywords (also known as keyword stuffing) as it results in a negative user experience and may cause your site to be seen as spam.” Shopify lets you set alt text on product images, collection featured images and blog featured images, per its keywords guide (opens in new tab). According to Shopify’s site structure guide (opens in new tab), you can’t rename an image in Shopify without uploading a new file, so alt text is the field to audit.

On product copy, Shopify advises that you “avoid directly copying text that’s provided to you by a manufacturer because that description might already be used by other websites,” in the same keywords guide (opens in new tab). Length isn’t a check. In its helpful content guidance (opens in new tab), Google asks whether you’re writing to a word count “because you’ve heard or read that Google has a preferred word count? (No, we don’t.)”

Google’s Core Web Vitals documentation (opens in new tab) sets the targets: LCP within the first 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Google says meeting them, “along with other page experience aspects, aligns with what our core ranking systems seek to reward.” That describes one input among many.

The Core Web Vitals report (opens in new tab) in Search Console uses “real world usage data (sometimes called field data),” and “the URL group’s status is its most poorly performing metric.” It also says “Only indexed URLs can appear in this report,” so a URL group rated Poor there is made up of pages that are already indexed. The fixes are theme and app work, covered in our plan for Core Web Vitals on Shopify.

Markets setups add one high-stakes check. Shopify’s automatic redirection documentation (opens in new tab) says “For markets that use dedicated domains, content is automatically indexed by search engines,” and “For markets that use shared domains, content isn’t indexed by search engines.” A market set up on a shared domain gets no separately indexable localized pages, per Shopify, so the check is whether each market the store wants to rank in has its own domain, subdomain or subfolder.

Shopify’s international domains guide (opens in new tab) recommends subfolders to merchants setting up for the first time, calling them “straightforward to set up and offer SEO benefits.” That’s Shopify’s advice. Its localization documentation (opens in new tab) says “Hreflang tags are added automatically, and all published languages are included in sitemaps, which help search engines detect the different languages on your store.”

Two Google rules apply on top. Google’s localized versions guide (opens in new tab) says “If page X links to page Y, page Y must link back to page X,” so hreflang annotations need return links, and that “Localized versions of a page are only considered duplicates if the main content of the page remains untranslated.” Google’s crawl budget guide (opens in new tab) says “Google’s crawling infrastructure defines a site as a unique hostname,” so each market subdomain gets its own crawl budget.

A crawler run against the store fills in what Search Console doesn’t show. Shopify’s crawler access documentation (opens in new tab) says “You can use Web Bot Auth to securely authorize your own crawlers, scripts, or tools to access your public Shopify online store,” including tools used “for accessibility and SEO audits”. The page names Screaming Frog, Jet Octopus, Sitebulb and OnCrawl as tools with custom-header documentation, and the setting lives under Online Store > Preferences > Crawler access.

Signatures are for your own tools, not for search engines. The same page (opens in new tab) says “Your store can be indexed by search engines and large language models (LLMs) without signatures.” It also says the signature’s “maximum period is 3 months,” and “If your crawler is receiving rate-limiting errors, then your signature isn’t valid.” If an audit crawl hits rate limits, set up a signature for the tool, or renew an expired one.

If you’d rather hand off the crawl, canonical and robots.txt layer, that’s the scope of our technical SEO audit.

Every check above in one table, each with where to look and what a bad answer looks like:

Is an ecommerce SEO audit worth doing if nothing looks broken? The mechanisms above point to specific moments to run one, more than to a calendar. Uploading a theme through the admin doesn’t carry over robots.txt.liquid. Apps can write seo.hidden values, add a second canonical tag or add duplicate Product markup. Republishing a product or showing a hidden collection again disables the redirect that pointed away from it, so a theme change, an app install or removal, a catalog cleanup and a new market are each a reason to rerun the checks.

The same approach works for paid search. Our PPC audit sets up an ad account review the same way, with one check per documented behavior. On the organic side, our SEO audit services cover content gaps and competitive positioning alongside the technical checks in this post.

If you’d like us to look at your store, start with a free ecommerce SEO audit. The request goes through our free Growth Audit: a no-obligation look at why your store isn’t getting found or converting, and where to start fixing it.