EndcapThe External product URL field, and who can use it
Shopify's list of fields that AI platforms consider has one entry with a condition attached. External product URL applies to stores on the Shopify Agentic plan, and its presence in an otherwise universal list causes a fair amount of confusion.
In short
- External product URL is listed among the fields AI platforms consider, but only for stores on the Shopify Agentic plan.
- If you are not on that plan, this field is not why your products are being skipped.
- It is a different thing from the product URL handle requirement, which applies to every store.
The field, and the condition
Title, description, images, type, vendor, collections, tags, barcode and variant option names apply to every store. External product URL is listed alongside them but qualified: it is for stores on the Shopify Agentic plan.
If you are not on that plan, this field is not the reason your products are being skipped, and no amount of attention to it will change anything.
What to do if you are not on the plan
Nothing, other than making sure the universal fields are complete. Those nine cover the overwhelming majority of matching quality, and our own scan found the most common failures sitting squarely among them rather than at the edges.
Do not confuse it with the product URL requirement
Shopify Catalog separately requires every product to have an identifiable URL, which is your normal handle and applies to all stores. A product with an empty handle is excluded outright. That is a different thing from the External product URL field, and it is the one worth checking.
Why a field like this exists at all
An external product URL is only meaningful if the merchant sells somewhere the assistant should be sent instead of the Shopify storefront: a marketplace listing, a regional site, a distributor. That is a real situation for larger operations and a rare one for everyone else, which is presumably why it is scoped to a plan built for that scale rather than exposed to every store.
It is worth understanding the shape of it even if you cannot use it, because it tells you something about how the feed is meant to work. The destination is part of the record. An assistant is not only deciding what to recommend, it is deciding where to send someone, and a broken or absent destination is as disqualifying as a missing price.
How Endcap handles this
Endcap does not check the External product URL field, because it applies to a plan most stores are not on and reporting a finding nobody can act on is noise dressed as diligence. What it does check is the requirement underneath it: every product needs an identifiable URL handle, and a product without one is excluded outright.
That check runs on every product, links to the Shopify requirement it comes from, and is one of the fastest things to verify in a catalog. If you are on the Agentic plan and using external URLs, treat that as a layer above a clean handle rather than a replacement for one.
Common questions
Do I need the Agentic plan to appear in AI assistants?
No. The universal requirements and the nine fields that apply to every store are what decide inclusion and matching. The External product URL field is an addition for stores on that plan, not a prerequisite.
What is the difference between this and my product handle?
The handle is your normal storefront URL and is a hard requirement for every store; a product without one is excluded. The External product URL points somewhere else entirely and is scoped to one plan.
Does Endcap check this field?
No, deliberately. Reporting a finding most merchants cannot act on is noise. It does check that every product has a URL handle, which is the requirement underneath it.
Source: Shopify documentation
Check your own catalog
Endcap runs every check in this guide and shows you which products fail, and why.
Add to Shopify, free