← Back to all articles

How to Fix Shopify Sitemap HTTP General Error: sitemap_collections_1.xml (2026)

⚡ Executive Takeaway for Store Owners
Troubleshoot and fix Google Search Console 'Sitemap could not be read: HTTP error' on sitemap_collections_1.xml in Shopify. Step-by-step diagnostic and 301 redirect guide.

How to Fix Shopify Sitemap HTTP General Error: sitemapcollections1.xml

One of the most frustrating errors Shopify merchants encounter in Google Search Console (GSC) is under the Sitemaps report:

> "Sitemap could not be read: HTTP error" or "HTTP general error on sitemapcollections1.xml"

When this happens, Googlebot temporarily stops indexing your newly launched product categories, inventory changes, and collection updates. If left unresolved, this can cause category ranking drops and a loss of valuable organic search traffic.

In this technical breakdown, you will learn why Shopify triggers sitemap<em>collections</em>1.xml errors, how to diagnose the root cause, and how to permanently resolve it using automated 301 URL redirects.


What Is sitemap<em>collections</em>1.xml in Shopify?

Shopify automatically generates and hosts your store's XML sitemap index file at:

text
https://yourstore.com/sitemap.xml

This main file functions as a parent index linking to individual sub-sitemaps:

  • sitemap<em>products</em>1.xml (All active products)
  • sitemap<em>pages</em>1.xml (Standard content pages)
  • sitemap<em>collections</em>1.xml (All public product collections)
  • sitemap<em>blogs</em>1.xml (Articles and blog posts)

Because Shopify generates these files dynamically, you cannot edit sitemap<em>collections</em>1.xml manually in the theme code. When Google Search Console flags an HTTP general error on this file, it is almost always caused by one of three underlying issues.


3 Core Reasons for the sitemap<em>collections</em>1.xml HTTP Error

1. Deleted or Renamed Collections Returning 404

When you delete an old collection (for example, /collections/black-friday-2023) or change its URL handle to /collections/black-friday-deals, Shopify's sitemap cache can take several days to purge the old URL. If Googlebot attempts to crawl the collection URL listed in the sitemap and receives a 404 Not Found, GSC can mark the entire sub-sitemap as having an HTTP crawl issue.

2. URL Redirect Chains or Loops on Collections

If you set up manual 301 redirects for collection URLs (e.g. /collections/shoes redirects to /collections/footwear, which accidentally redirects back to /collections/shoes), Google's crawler hits a redirect loop. When a loop occurs within a sub-sitemap target, GSC reports an HTTP General Error.

3. Password Protection or Staging Mode Active

If your Shopify store is locked behind a storefront password (under Online Store > Preferences > Password protection), Googlebot receives a 403 Forbidden or 302 Found redirect to /password. This immediately causes GSC to reject all sitemaps with an HTTP error status.

Step-by-Step Fix: How to Clear the Error

Step 1: Verify the Live XML File in Your Browser

Open an incognito browser window and navigate directly to:
text
https://yourstore.com/sitemapcollections1.xml
  • If it renders valid XML with a list of <loc> tags: The file itself is functioning properly, and Googlebot likely hit a temporary server timeout or transient DNS latency.
  • If it returns 404 or a blank page: Ensure your store has at least one active, published collection available on the Online Store sales channel.

Step 2: Test Collection URLs for 404s and Redirect Loops

Use our free 301 Redirect & HTTP Status Checker to test key collection URLs: 1. Copy the top 5–10 collection URLs from your store. 2. Run them through the redirect checker. 3. Verify that each returns a clean 200 OK or a direct 301 Moved Permanently with zero circular chains.

Step 3: Implement 301 Redirects for Deleted Collection Handles

If you recently deleted, merged, or renamed product collections, you must redirect the old URLs to relevant active categories: 1. Navigate to Online Store > Navigation > View URL Redirects in Shopify. 2. Click Create URL redirect. 3. Set Redirect from to your old collection path (e.g., /collections/summer-2023). 4. Set Redirect to to your new category (e.g., /collections/summer-clearance). 5. For bulk updates, use our free Shopify Bulk Redirect CSV Generator to upload hundreds of rules at once.

Step 4: Resubmit the Sitemaps in Google Search Console

Once your collection URLs return clean 200/301 headers: 1. Open Google Search Console. 2. Select your verified Shopify domain property. 3. Click on Sitemaps in the left sidebar under Indexing. 4. In the "Add a new sitemap" input box, submit: * First: sitemap.xml * Second: sitemap<em>collections</em>1.xml 5. Refresh the status. In most cases, the error will update to "Success" within 24 to 48 hours.

Automate Collection 404 Detection with GP Easy Redirects

Manual sitemap troubleshooting takes hours of searching through server logs and Search Console reports.

With GP Easy Redirects:

  • Real-time 404 Monitoring: Catches every deleted collection or dead URL the instant a customer or Googlebot encounters it.
  • Automated Smart Suggestions: Recommends the most relevant active collection so you can fix broken paths in one click.
  • Global Edge CDN Redirects: Redirects traffic in under 5ms, ensuring Googlebot never encounters an HTTP timeout or dropped connection.

Install GP Easy Redirects today to protect your store's search rankings and prevent sitemap indexing drop-offs.

SHOPIFY APP STORE • 100% FREE FOREVER

Eliminate 404 Broken Links & Retain Search Revenue

Deploy autonomous 301 redirection and AI catalog auto-healing across your entire Shopify store in 60 seconds.

Install Free on Shopify App Store →
✓ Unlimited Redirects✓ Edge CDN (<5ms)✓ No Credit Card Required