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

Identify useful internal linking opportunities

Key pages sit buried with almost no internal links leading to them, and past link lists were full of unjustifiable suggestions. In this case, the immediate task is to identify useful internal linking opportunities. The workflow should test each candidate link against the existing paths and keep only those that genuinely help a shopper or crawler arrive.

Topic
Technical SEO and Indexing
Target keyword
shopify internal linking tool
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 identify useful internal linking opportunities.
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 priority pages, the existing link inventory with the anchor text in use, the navigation and collection paths that already reach them, the click depth of each page from the home page, and the canonical each page declares]. Keep a candidate link only where the source page is topically related to the target, the link creates the first path or shortens the depth recorded for that target and the target is the canonical the merchant intends, dropping any link that leaves reachability unchanged or points at a duplicate URL.

Return a URL-level diagnosis with evidence and follow-up checks, with each suggested link tied to its source page 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

Take the priority pages, the existing link inventory with the anchor text in use, the navigation and collection paths that already reach them, the click depth of each page from the home page and the canonical each page declares.

02

Step 2

Keep a candidate link only where the source page is topically related to the target, the link creates the first path or shortens the depth recorded for that target and the target is the canonical the merchant intends, dropping any link that leaves reachability unchanged or points at a duplicate URL.

03

Step 3

Deliver a URL-level diagnosis with evidence and follow-up checks in which each suggested link names its source page, the depth before and after and the reason it qualifies, then confirm that every source page exists and is indexable and that the counted depth after the change matches the number of paths actually added.

FAQ

Common questions when running this scenario

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

When does a link actually help?

When it changes reachability: it either creates the first path to a page that had none or shortens the depth already recorded for it, and the source is topically related enough that a shopper would follow it. A link between two pages already one step apart adds nothing, so it is rejected with that reason.

Should the link go in a template or in page copy?

Record which one, because they behave differently: a template link appears across a whole section and scales at once, while a link in page copy carries context and reads as a next step. Both count toward depth, so each suggestion names its placement and template links are flagged where they would repeat on unintended pages.

Does a link from an excluded page help?

Barely. A source page the merchant does not intend to be public offers little to a crawler that may never return to it, so the suggestion is marked low value instead of counted as a new path. Where the same target can be reached from an indexable page, that link is preferred and the excluded source is listed as an alternative.

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.