If you are using Shopify for your ecommerce store, check your Google Search Console and make sure the Sitemaps section reflects the new collections sitemap structure. That is the entire instruction, and the rest of this article is the why and the how, written from what we found while managing our own client accounts when the change landed.
The discovery sequence on our side was simple. Shopify updated the structure for collections and pages sitemaps. Google Search Console began showing a Failed status for the previously submitted XML sitemaps. And the old URLs themselves, sitemap_collections_1.xml and sitemap_pages_1.xml, either displayed an XML parsing error or returned a 404. Three symptoms, one cause, every Shopify store exposed at once. I wrote about how the change looked from the discovery side separately; this is the fix-it companion.
MageCloud Fix Note
The Issue and Both Solutions
THE SYMPTOM
Failed status in GSC Sitemaps
Old collections and pages sitemap URLs error out. GSC flags the submitted sitemaps as Failed and may notify you it cannot read them.
OPTION A
Do nothing
Google will eventually discover and adopt the new sitemap structure on its own. Acceptable for small, slow-moving catalogues.
OPTION B
Submit the new URLs manually
Two minutes in GSC closes the discovery gap immediately. The right call for any store where catalogue freshness earns money.
Paul Ryazanov · MageCloud · two-minute fixes are still fixes
How to Check Your Store Right Now
Open Google Search Console, choose your store’s property, and go to Sitemaps in the left navigation under Indexing. Look at the list of submitted sitemaps and their status column. Healthy entries say Success with a recent read date. What you are looking for is any entry marked Failed, specifically the collections and pages sitemaps, and the giveaway timing is a failure that began around when Shopify shipped the change rather than after anything you did.
If you only ever submitted the master sitemap.xml, check its status too: the master file references the child sitemaps, and Google’s view of the children is what matters. Click into the entries and GSC will show you exactly which child URLs it could not fetch and why, parsing error or not found. That detail view is your confirmation that you are looking at the platform change and not some unrelated breakage.
Choosing Between Doing Nothing and Two Minutes of Work
Option A is legitimate, and I want to say that clearly because technical SEO writing loves manufacturing emergencies. Google re-crawls sitemap locations and follows the master sitemap’s references; it will reconcile the new structure on its own schedule. A 40-product store that changes twice a quarter can ignore this entire episode and suffer nothing measurable.
Option B exists because eventually is doing heavy lifting in that paragraph. While Google reconciles, your store’s freshest URLs, new collections, new pages, are discovered by crawling rather than declared by sitemap, which is slower and less complete. For stores with large catalogues, frequent collection changes, or seasonal velocity, that lag has a cost, and the insurance against it is two minutes: in the same Sitemaps panel, enter the new sitemap URLs from your live sitemap.xml and submit. The status flips, the discovery pipe reopens, done. We did Option B across every managed account the week the change landed, recorded a short video of the exact clicks for clients, and moved on. It is the same calculus as every silent breakage I write about: detection is the expensive part, the fix is nothing.
The Habit That Makes This a Non-Event
Notice what this incident required to be painless: somebody glancing at the Sitemaps panel within a week or two of a platform change nobody announced to merchants. That is the entire moat. The weekly Search Console read turns platform surprises into routine maintenance, and skipping it turns routine maintenance into archaeology, where you discover a Failed status of unknown age and have to reconstruct what it cost you.
If you check your GSC today and find the Failed entries, you now know exactly what to do, and it will take you longer to log in than to fix. If you would rather a team simply handled this category of thing across your store permanently, get in touch. Platform changes are not going to stop. Somebody just has to be watching.