New pages went live days ago, yet the sitemap still lists old URLs and omits the fresh ones. In this case, the immediate task is to investigate missing or stale sitemap entries. The workflow should match the merchant's current entries against publication timestamps and rule settings, assigning each gap a cause and a recheck date.
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 investigate missing or stale sitemap entries.
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 current entry list and the previous snapshot of it, publication and unpublication timestamps for every affected page, the last generation timestamp, and the exclusion rules in force for templates, robots directives and market visibility]. For each gap, compare the page's publication timestamp with the last generation timestamp so a page published afterwards is attributed to generation timing, attribute a page published earlier to an exclusion rule only when the rule named actually covers it, mark a gap as expected where the page is unpublished or hidden, and leave anything still unexplained as unattributed.
Return a URL-level diagnosis with evidence and follow-up checks, assigning each gap a cause and a recheck date 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 current entry list together with the previous snapshot of it, the publication and unpublication timestamps for every affected page, the timestamp of the last sitemap generation and the exclusion rules in force for templates, robots directives and market visibility.
For each gap, compare the page's publication timestamp with the last generation timestamp so a page published afterwards is attributed to generation timing, attribute a page published earlier to an exclusion rule only when the rule named actually covers it, mark a gap as expected where the page is unpublished or hidden, and leave anything still unexplained as unattributed.
Deliver a URL-level diagnosis with evidence and follow-up checks that assigns each gap a cause and a recheck date set after the next generation, then verify that the difference between the current and previous entry lists accounts for every URL that appeared or disappeared and that newly published pages are present in the next snapshot.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Compare the page's publication timestamp with the last generation timestamp: a page published afterwards has simply not been through a generation yet, while a page published earlier and still absent must be explained by a named rule. Where no rule covers it, the gap stays unattributed rather than being given a convenient cause.
Set the recheck date after the next scheduled generation, since only a new file can close a timing gap. Gaps attributed to an exclusion rule are rechecked once that rule changes, and gaps left unexplained are carried forward with the checks already attempted recorded against them.
No. Removal only stops the file from recommending the address, and the page can stay reachable and indexed for as long as it resolves. Follow-up checks therefore confirm whether the merchant also wants the page blocked or redirected, instead of treating absence from the sitemap as removal from search.
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.