Step 1
Collect the candidate URLs with their rendered body copy, titles, headings and the parameters, filters or tags that generated each version.
Filtered and tagged variants have multiplied page URLs until the merchant cannot tell which versions shoppers would notice as different. In this case, the immediate task is to identify duplicate page content that needs review. The workflow should compare each candidate URL pair for substantive differences and group the duplicates by their generating cause.
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 identify duplicate page content that needs review.
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 candidate URLs with rendered body copy, titles and headings, the parameters, filters or tags generating each version and the merchant's intended representative URL for each group]. Judge each pair on whether a shopper would see a substantive difference in the products listed, the copy and the intent served, treating differences only in URL, filter state or sort order as duplicates, and group the duplicates by the generating cause rather than by address.
Return a URL-level diagnosis with evidence and follow-up checks, grouping duplicates by cause rather than by URL alone 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 candidate URLs with their rendered body copy, titles, headings and the parameters, filters or tags that generated each version.
Judge each pair on whether a shopper would see a substantive difference in the products listed, the copy and the intent served, treating differences only in URL, filter state or sort order as duplicates, and group the duplicates by the generating cause rather than by address.
Deliver the diagnosis with each duplicate group, its cause, the URL the merchant wants to represent the content and the links or sitemap entries still disagreeing, then recheck the group after correction and confirm the count falls as intended.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
No. Shared policy text and common boilerplate are expected. The review should focus on pages that chase the same intent with no meaningful difference for the shopper.
One tag or filter pattern explains dozens of addresses, and the fix sits at the pattern. Grouping by URL turns a single template change into a long list of individual edits.
Which URL should represent the content, chosen from the merchant's intent, followed by a check that internal links and the sitemap agree with that choice. Consolidating first leaves those signals pointing elsewhere.
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.