Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Audit internal links for useful destinations

Internal links have piled up through app installs and rebuilds, and some now send shoppers to thin or retired pages instead of the ones the merchant promotes. In this case, the immediate task is to audit internal links for useful destinations. The workflow should produce an error inventory with repair and verification steps, ordered by page traffic.

Topic
Website Errors and Broken Links
Target keyword
shopify internal link audit
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 audit internal links for useful destinations.
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: [every internal link with its source page, anchor text, destination and destination status, the merchant's promoted pages, and per-source-page traffic for one reporting window]. Judge each link by where it lands, calling it sound when the destination is live, reachable by search engines and relevant to the anchor and the page linking out, poor when it stops at a retired or thin page with no equal successor, and replaceable when one of the merchant's promoted pages answers the same intent better.
Return an error inventory with repair and verification steps, prioritising links on pages with the most traffic 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.
Use in Spark
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.

01

Step 1

Collect every internal link with its source page, anchor text, destination and destination status, the pages the merchant wants promoted, and per-source-page traffic for one reporting window so each link can be ranked by how many shoppers meet it.

02

Step 2

Judge each link by where it lands, calling it sound when the destination is live, reachable by search engines and relevant to the anchor and the page linking out, poor when it stops at a retired or thin page with no equal successor, and replaceable when one of the merchant's promoted pages answers the same intent better.

03

Step 3

Deliver an error inventory with repair and verification steps ordered by the traffic of the page carrying each link so busy sources are fixed first, giving each entry its current destination, the replacement or removal proposed and a check that any promoted page still keeps at least one route from somewhere, then re-walk each changed page to confirm the edits resolve.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

What counts as a useful destination for an internal link?

One that is live, intended to be findable by search engines, and closely related to what the shopper was reading, so a buying-guide link to the matching product page is useful while the same link pointing at an empty tag page is not; relevance rather than existence is the test.

Are links in menus, footers and installed apps part of the audit?

Yes, because templates repeat across the storefront so one wrong entry reaches far more pages than a body link, and app-generated blocks are easy to miss in a page list; include them and note which blocks are actually editable, since some can only be changed inside the app.

Should a link whose target disappeared simply be removed?

Only when no equivalent destination exists and nothing depends on the route, because deleting can strand a page the merchant still wants discovered; otherwise point it at the closest live successor or at the promoted page, and record which choice was made and why.

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.