The sitemap has never been reconciled with what the merchant actually wants public, and error URLs may sit beside missing pages. In this case, the immediate task is to check sitemap coverage against intended public pages. The workflow should compare the sitemap entries and intended page list one by one, surfacing missing entries and entries to remove.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me check sitemap coverage against intended public pages.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [the sitemap index and its child files, the merchant's intended public page list, each candidate URL's returned status, its declared canonical target, and the URLs already recorded as returning errors]. Mark a URL as required when it appears on the intended public list, returns a non-error status and declares itself canonical, mark it as an entry to remove when it is absent from that list, redirects to another address or no longer resolves, and record as unconfirmed any case where one of those three checks could not be completed.
Return a URL-level diagnosis with evidence and follow-up checks, listing missing entries and entries to remove for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect the sitemap index and every child file it references, the merchant's list of pages intended to be public, the status each candidate URL returns, the canonical target each one declares and the URLs already recorded as returning errors.
Mark a URL as required when it appears on the intended public list, returns a non-error status and declares itself canonical, mark it as an entry to remove when it is absent from that list, redirects to another address or no longer resolves, and record as unconfirmed any case where one of those three checks could not be completed.
Deliver a URL-level diagnosis with evidence and follow-up checks that lists missing entries and entries to remove with the reason and the record behind each one, then confirm that the entries counted across all child files equal the URLs examined and that every required URL still returns its recorded status.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
List the final destination rather than the old address, and only after the merchant confirms the redirect is intentional. A redirect left behind by a retired page belongs in the removal list, while a deliberate vanity or shortened path keeps its target in the file and is recorded with that decision.
Three conditions together: it appears on the intended public list, it returns a non-error status, and it declares itself as canonical. Missing any one of them makes the entry questionable, so it is reported with the condition that failed rather than quietly added or quietly dropped.
Follow the intended public list rather than the URL shape. Where filter and page states are not meant to rank, they stay out and the choice is written into the caveats, so the exclusion is a reviewable decision instead of an accident of how the file was generated.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.