01
Step 1
List the live handles with the product or collection name behind each, any redirects already configured, and the pattern the merchant wants comparable products to follow.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Review product URL handles for clarity and consistency
A merchant inherited handles from an earlier import, so some addresses still carry old naming and a word order that no longer matches the product. In this case, the immediate task is to review product URL handles for clarity and consistency. The workflow should produce a proposed handle per item plus a redirect note where an address would stop resolving.
Topic
SEO Metadata and Content Audits
Target keyword
shopify url handle optimization
Copyable AI prompt
A prompt you can drop directly into Spark
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.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me review product URL handles for clarity and consistency.
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: [live handles with their product or collection names, redirects already configured, and the handle pattern the merchant wants comparable products to follow].
Check each handle for readability, word order consistent with the current product name, and legacy artifacts from the earlier import such as discontinued ranges, and mark every proposed change whose old address has external links, indexing or saved references and would stop resolving.
Return a handle review with proposed slugs and redirect notes 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.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Check each handle for readability, word order consistent with the current product name, and legacy artifacts from the earlier import such as discontinued ranges, and mark every proposed change whose old address has external links, indexing or saved references and would stop resolving.
03
Step 3
Deliver the handle review with a proposed slug and redirect note per flagged item, then verify each proposed handle against the product name record and confirm every breaking change carries its redirect.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Which handle changes require a redirect?
Any change to a live handle whose old address has external links, search indexing or saved customer references requires a redirect from the old path to the proposed slug. The review flags each such change rather than leaving redirects to memory. Handles whose old address never resolved outside the store can change without one.
How are legacy artifacts spotted in a handle?
By comparing the handle's words and word order against the current product name record: old naming conventions from the earlier import, discontinued ranges, and word orders that no longer match how the product is named now. Each artifact is listed with the handle it sits in. Confirmed artifacts feed the proposed slug.
What pattern should new handles follow?
The pattern the merchant states for comparable products, applied so similar items read alike in their addresses. The pattern is recorded in the review, so future entries follow it without another audit. Entries that cannot be safely renamed keep their legacy handle and are listed as exceptions with the reason.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Next step
Want these AI scenarios embedded directly into daily operations?
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.