Google Search Console for Shopify: The 2026 SEO Playbook

Q: Why does Search Console show duplicate product URLs for my Shopify store?

Shopify can expose a product under both `/products/{handle}` and `/collections/{collection}/products/{handle}`. Shopify automatically adds a canonical tag pointing the collection-path version to the clean `/products/` URL, so Google consolidates the signals. You'll see "Alternate page with proper canonical tag" in the Pages report, which is normal and expected.

Most "Google Search Console for Shopify" guides stop at the verification step. They walk you through adding a meta tag, submitting a sitemap, and then leave you staring at a dashboard full of numbers you don't know what to do with. That's the easy 10%. The other 90% — actually using the data to grow a store — is where Shopify owners get stuck.

Shopify is its own beast. Its rigid /products/ and /collections/ URL structure, automatic sitemap generation, and the way it creates duplicate product URLs across collection paths all show up inside Search Console in ways that confuse first-time users. If you treat your store like a generic website, you'll misread your own reports.

This guide covers the full setup, then goes deep on the Shopify-specific realities — canonical duplication, faceted filter bloat, thin collection exclusions — and finishes with the part that pays the bills: turning striking-distance product and collection keywords into orders.

Setting Up Google Search Console for Shopify

You have two property types to choose from. Pick the right one or you'll fragment your data.

Domain property (recommended): Covers every subdomain and both HTTP and HTTPS. Requires adding a DNS TXT record at your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.), not in Shopify. This is the cleanest option because it captures www, non-www, and any subdomains in one place.
URL-prefix property: Verified with an HTML meta tag you paste into your Shopify theme. Only covers the exact prefix you enter (e.g. https://www.yourstore.com/).

For most stores, set up the Domain property. Here's the fast path:

Go to Search Console and click Add property > Domain.
Enter your root domain without https:// (e.g. yourstore.com).
Copy the TXT record Google gives you.
Log in to your domain registrar (the company you bought the domain from), open DNS settings, and add the TXT record.
Wait a few minutes, then click Verify.

If you only have access through Shopify and use a URL-prefix property instead, go to Online Store > Themes > Edit code > theme.liquid and paste the verification meta tag just below the opening <head> tag. Save, then verify.

Submitting Your Shopify Sitemap

Shopify auto-generates your sitemap at yourstore.com/sitemap.xml. You do not need an app or plugin — it's built in and updates automatically when you add or remove products and collections. The root sitemap is an index that points to child sitemaps for products, collections, blogs, and pages.

In Search Console, go to Indexing > Sitemaps, enter sitemap.xml, and click Submit. You only submit the root file; Google discovers the children on its own. If you want a deeper walkthrough of sitemap status codes and "Couldn't fetch" errors, see our Search Console sitemap guide.

One Shopify gotcha: you can't manually edit the sitemap. If you want a URL excluded from indexing, you control that with the noindex tag in theme.liquid or by setting product/collection visibility — not by editing the sitemap.

Understanding Shopify's URL Structure in GSC

This is the single biggest thing that trips up Shopify owners reading their Search Console data. Shopify forces a predictable URL pattern, and once you understand it, the Pages report suddenly makes sense.

| URL pattern | What it is | SEO priority | |---|---|---| | /products/{handle} | Individual product page | High — transactional intent | | /collections/{handle} | Category / collection page | High — broad commercial intent | | /collections/{handle}/products/{handle} | Product accessed through a collection | Duplicate — should canonical to /products/ | | /collections/{handle}?filter... | Faceted / filtered view | Usually should not be indexed | | /pages/{handle} | Static pages (About, FAQ) | Varies | | /blogs/{handle}/{article} | Blog content | High for top-of-funnel |

The line that causes the most confusion is the third one. By default, Shopify can surface a product under both /products/the-handle and /collections/some-collection/products/the-handle. These are the same product at two different URLs.

The Duplicate Product URL / Canonical Problem

Here's the good news: Shopify automatically sets the canonical tag on the collection-path version (/collections/.../products/...) to point back to the clean /products/... URL. So Google consolidates the ranking signals and indexes the canonical version. You can confirm this on any product page by viewing source and searching for rel="canonical".

The bad news: this only works if your theme and any custom links respect it. Problems creep in when:

A theme or app injects internal links to the long collection-path URLs, sending crawl budget to duplicates.
You've hard-coded links in navigation or blog posts to /collections/x/products/y instead of /products/y.
Apps generate their own URL parameters that Shopify doesn't canonicalize.

In Search Console, this shows up under Indexing > Pages as "Alternate page with proper canonical tag" or "Duplicate, Google chose different canonical than user." The first is fine and expected — it's Google correctly honoring your canonicals. The second is a warning that Google disagrees with your canonical choice and is worth investigating. For a full breakdown of every status in that report, read our guide to index coverage errors.

Action step: Always link to products using the clean /products/{handle} form in your menus, internal links, and blog content. It costs nothing and keeps crawl signals consolidated.

Faceted and Filter URL Bloat

When shoppers filter a collection by size, color, or price, Shopify generates URLs with query parameters or tag-based paths. At scale, a collection with five filter types can spawn hundreds of crawlable URL combinations. Google may crawl these, find them near-duplicate or thin, and waste crawl budget that should go to your real product and collection pages.

In the Pages report you'll often see these clustered under "Crawled - currently not indexed" or "Discovered - currently not indexed." That's usually Google's way of telling you it found low-value variations and chose not to index them — which is the correct outcome. You generally do not want filtered views in the index.

To keep this clean: ensure filtered URLs carry a canonical pointing to the base collection (most modern Shopify themes using the native filtering do this), and avoid linking to filtered URLs from indexable navigation.

If you're using a third-party filtering or "infinite collection" app, double-check its output. Some apps generate crawlable parameter URLs that don't inherit Shopify's native canonical behavior, quietly multiplying the number of thin pages Google has to wade through. The quickest audit is to apply a page regex filter of /collections/.*\? in the Performance report and see how many parameterized URLs are actually pulling impressions — if it's a long list of near-duplicates, your filtering setup needs attention.

Reading the Data: Products vs Collections Separately

Lumping all your pages together hides the story. A store's products and collections behave completely differently — products convert on long-tail, specific intent; collections capture broader category searches. You should analyze them as two separate funnels.

The fastest way to split them is the Performance report with a page filter using regex. Go to Performance > Search results, click + New > Page, switch the dropdown to Custom (regex), and paste one of these (Search Console uses RE2, so no lookbehinds or backreferences):

Products only:

/products/

Collections only:

/collections/

Product pages but NOT the collection-path duplicates:

^https://[^/]+/products/

Blog content only:

/blogs/

Compare the two segments side by side. A common, healthy pattern looks like this:

Collections: higher impressions, broader queries, lower CTR. They're your reach.
Products: fewer impressions, more specific queries, higher conversion. They're your revenue.

If your collection pages get impressions but almost no clicks, that's usually a low-CTR problem — weak title tags, missing meta descriptions, or being outranked by richer results. If they get neither, the page may be thin (more on that next). For a deeper dive on building these segments, our Search Console regex filters guide has copy-paste patterns for dozens of e-commerce scenarios.

Tired of building regex filters by hand and hitting the 1,000-row export cap? Search Console Tools connects to your store's GSC data through Google OAuth, automatically splits products from collections, and surfaces your best opportunities. It's free — try it free.

Why Thin Collection Pages Get Excluded

Shopify makes it trivially easy to create collections. Many stores end up with dozens of auto-generated or near-empty collections — a "collection" with two products and no description, or several collections that contain almost identical product sets. Google frequently flags these as "Crawled - currently not indexed" because there isn't enough unique value to justify indexing.

Fix thin collections by:

Adding genuine, unique intro copy (2-3 paragraphs) that targets the category keyword.
Merging near-duplicate collections so each one is substantial and distinct.
Removing or noindex-ing collections that exist purely for internal merchandising and have no search value.

A collection page with a real description, a healthy product count, and internal links pointing to it is far more likely to get indexed and rank.

Turning Striking-Distance Keywords Into Revenue

This is where Search Console becomes a revenue tool instead of a reporting tool. Striking-distance keywords are queries where you already rank on page two or the bottom of page one — typically positions 8 through 20. You're close enough that small, targeted improvements can move you into clickable territory, and the CTR difference between position 11 and position 5 is dramatic.

Here's the repeatable workflow:

Open Performance > Search results and set the date range to the last 3 months.
Add your /products/ regex page filter (or /collections/).
Click the Queries tab, then enable the Average position metric.
Sort by impressions, then scan for queries with high impressions and an average position between 8 and 20.

Those are your money keywords. For each one, decide which page should own it, then strengthen that page: work the exact query into the product/collection title tag and H1, expand the description to genuinely answer the query, and add internal links from related blog posts and collections using that query as anchor text.

The honest caveat: Search Console caps exports at roughly 1,000 rows per query, so a large catalog will hide a long tail of opportunities behind that ceiling. There are ways to work around it — date-range chunking and dimension filtering — covered in our guide to the 1,000-row limit. Pairing GSC with a structured process is also the foundation of keyword research using Search Console, and the broader strategy lives in our striking-distance keywords guide.

A Simple Prioritization Frame

Not every striking-distance keyword is worth your time. Prioritize by multiplying potential traffic against commercial intent:

First: Product-page queries at positions 6-15 with clear buying intent ("buy," "best," specific model names). These convert directly.
Second: Collection queries at positions 5-15 for your higher-margin categories. They drive qualified discovery.
Last: Informational blog queries — valuable for reach and links, but slower to monetize.

Work top to bottom, ship the on-page changes, and re-check positions in 4-6 weeks. Movement in GSC is your feedback loop.

If you want all of this done for you, Search Console Tools reads your verified property over Google OAuth, separates products from collections, finds your striking-distance keywords automatically, and turns them into prioritized content briefs — for free. If you're newer to the platform overall, start with our complete Google Search Console guide.

Frequently Asked Questions

Do I need a Shopify app to use Google Search Console?

No. Search Console is a free Google product that works with any website, and Shopify auto-generates the sitemap it needs. You verify ownership with a DNS record (domain property) or a meta tag in your theme, then submit sitemap.xml. No paid app is required for the core setup.

Why does Search Console show duplicate product URLs for my Shopify store?

Shopify can expose a product under both /products/{handle} and /collections/{collection}/products/{handle}. Shopify automatically adds a canonical tag pointing the collection-path version to the clean /products/ URL, so Google consolidates the signals. You'll see "Alternate page with proper canonical tag" in the Pages report, which is normal and expected.

Why are my Shopify collection pages not getting indexed?

The most common cause is thin content — a collection with few products and no unique description gets flagged as "Crawled - currently not indexed." Add genuine intro copy targeting the category keyword, merge near-duplicate collections, and link to important collections from your navigation and blog. Substantial, distinct collection pages get indexed far more reliably.

How do I separate product and collection performance in Search Console?

Use the Performance report's page filter set to Custom (regex). Enter /products/ to isolate product pages or /collections/ for collection pages, since Shopify's fixed URL structure makes this filtering reliable. Analyzing them separately reveals that collections drive impressions while products drive conversions.

Should I worry about filtered or faceted URLs in my Shopify store?

Usually not, as long as they aren't being indexed. Filtered collection URLs are near-duplicate and thin, so Google typically lists them under "Discovered - currently not indexed," which is the correct outcome. Just make sure filtered views carry a canonical to the base collection and that you don't link to them from indexable navigation.

What are striking-distance keywords and how do I find them on Shopify?

They're queries where you already rank in roughly positions 8-20 — close enough that targeted on-page improvements can push you onto page one. Find them in Performance > Search results: apply a /products/ or /collections/ regex filter, open the Queries tab, enable Average position, and look for high-impression queries in that range. Then optimize the matching page's title, description, and internal links.