How to decide which Shopify URLs should be in an XML sitemap
An XML sitemap can hold thousands of URLs and still be useful, or hold very few and still be wrong. For a Shopify store, the question isn’t how to make the sitemap bigger. It’s whether the file helps search engines find canonical, indexable pages the business wants considered for search.
Sitemaps are a discovery aid, not an indexation guarantee. Google can find pages through links, and inclusion doesn’t force it to index anything. Treat the sitemap as a clean statement of the preferred URL set.
Begin with URL purpose
List the types of URL the store creates: products, collections, pages, articles, variants, filtered views and search results. Decide which have a clear purpose as standalone search pages. A useful product or collection may belong in the sitemap. A temporary sort order or an internal search query usually doesn’t need its own search result URL.
Don’t decide by URL type alone. A collection with no distinct assortment or customer value may be weak even though it’s technically a collection. A policy page may help customers without being a priority for organic discovery. Let the page’s role and quality drive the decision.
Check canonical and indexability
For each intended URL type, check pages return a successful response, can be crawled, are indexable and canonicalise to themselves or the preferred URL. Sitemap entries that redirect, error, carry noindex or canonicalise elsewhere send mixed signals. Find out whether Shopify, the theme or an app controls the output before attempting a fix.
A canonical is a hint, and search engines may choose differently. If many pages canonicalise away from themselves, ask whether they’re genuinely duplicates, whether the target is right and whether internal links back up the same choice. Don’t add every page to the sitemap hoping it will override other signals.
Understand platform-generated sections
Shopify generates its sitemap structure, and it can change with store configuration. In my own work on a Shopify store, I open the live sitemap and its child sitemaps instead of relying on an old guide. Some stores use apps or custom implementations that modify the output, so confirm what is actually published and crawlable.
Variants deserve a careful look. Some variant URLs are useful because they represent meaningfully different choices, and others are alternate views of one product. Decide how the store handles them and check canonical and internal-link behaviour. Don’t create indexable pages for every parameter combination without a reason.
Keep filters and search separate
Filters improve browsing, but combinations multiply URLs fast. A filtered collection being reachable doesn’t mean it should be indexed or in the sitemap. Before treating a combination as a search page, look for stable demand, distinct inventory and a useful landing experience.
Internal search results mostly serve a shopper’s immediate query, not a lasting public destination. Review how the theme handles their crawlability, links and directives. Sitemap exclusion alone won’t manage crawl behaviour, so look at links and technical rules together.
Think about quality as well as eligibility
A technically indexable URL may still be a poor candidate if it has no unique purpose. Review thin collections, empty search pages and near-duplicate variants. If a page helps shoppers but isn’t meant for organic discovery, keep the user experience and the indexation decision separate. The sitemap should show the intended search set, not every route the platform can generate.
When a product is temporarily out of stock, consider whether its page should stay available. It depends on replenishment plans, alternatives and what customers still need. If the page stays, check its content and status. If it’s retired, apply a deliberate replacement or removal policy instead of leaving a stale entry.
Audit the sitemap in batches
Download the sitemap and its child files, then compare entries with a crawl or a catalogue export. Look for non-canonical URLs, redirects, duplicates, empty pages and unexpected parameter variants. Sample across templates and markets. If the sitemap is large, automate the comparison, but keep an explanation for each exclusion rule.
After a change, validate the response, XML format and representative destinations. Submit or inspect it in Search Console where appropriate, then watch processing and indexing reports over time. An accepted sitemap doesn’t mean every URL will be indexed, so track the outcome, not just the submission.
Write down the rule
Document what qualifies a URL for inclusion, who owns the rule and how new page types get reviewed. That stops a future app or theme change silently altering the URL set. Save a short list of URLs expected in each section and URLs expected to be absent, and run it after theme, app or catalogue changes. It catches regressions faster than a coverage report weeks later.
When the live sitemap differs from what you expected, find the system that creates it before changing page metadata. A platform update, an app or an edge rule may be responsible. I’d always ask the technical owner whether a custom fix will survive the next deployment, because a fix that disappears on the next release isn’t a strategy.
Related reading
- Choosing which product attributes belong in visible copy
- How to decide which search synonyms belong in your store
- How to decide when an unavailable product page should stay indexed
Choose one sitemap entry you’d be surprised to see indexed and trace why it’s there. What rule should decide whether it belongs?