Skip to main content

Why couldn't Atlas import my product URL?

Atlas needs a public product page it can read. Check the link opens without signing in, is a single product, and has real text and a price. Your Shopify catalog always works instead.

Written by Eddie Lavandera

Atlas needs a public product page it can read without signing in. If a product shows Couldn't import in the page builder, under the banner Couldn't import one of the URLs — check the link or remove it, or Couldn't create a product from that link. Go back and try another link or pick a product from your catalog. in the landing page wizard, the page was either not reachable, not a single product page, or had too little readable content. The fastest reliable fix is the same in both: add the product to your Shopify catalog and build from there.

In this article:


Step 1: Open the link yourself

Paste the URL into a new private or incognito browser window. That is the closest approximation to what Atlas sees.

What happens

What it means

The product page loads normally

The link is fine. Continue to step 2.

You are asked to sign in

Atlas cannot read pages behind a login. Use your catalog instead.

You see a region or age gate

Atlas cannot pass these. Use your catalog instead.

The page does not load

The link is wrong or the page is gone. Find the correct one.

You get a robot check

The site is blocking automated readers, and it will block Atlas too.

The private window matters. A page that works for you while signed in may be invisible to Atlas.


Step 2: Check it is a single product page

Atlas reads one product from one page. It cannot read:

  • a collection or category page

  • a search results page

  • a store home page

  • a blog post or article

  • a seller's shop front listing many items

  • a cart, checkout or account page

Navigate to the individual product and copy the URL from there.


Step 3: Clean up the URL

Long URLs from marketplaces often carry tracking parameters, session identifiers and referral codes that can confuse the fetch.

Cut everything from the question mark onwards and try the shortened link. Keep the part that ends in the product identifier and drop the rest.

💡 On marketplace sites, opening the product in a private window and copying the URL from the address bar usually gives you a much cleaner link than the share button does.


Step 4: Check there is text and a price to read

Some product pages are almost entirely images, with the description rendered inside a picture. Atlas reads text, so there is nothing for it to work with. It also needs a visible price.

Signs you have this problem: the page looks detailed to you, but selecting text with your mouse selects almost nothing, or there is no price on the page.

In this case, use your catalog and write a short description yourself, or add the detail to your project's customer research so Atlas has something to build from.


Step 5: Use your catalog instead

This always works, and it is usually the better route even when a link would have worked.

  1. Add the product to your Shopify catalog, with a title, description, images and price.

  2. In the Atlas wizard, find it under Browse your Shopify products with Search for your product, and tick it.

Why it produces a better page:

  • You control the input. The description you wrote is more accurate than one read from a supplier listing.

  • The price is right. A price read from a supplier page is unlikely to be your selling price, and a page quoting the wrong price is worse than no page.

  • Variants come through correctly, because Shopify already holds them properly.

  • The product exists to be bought. A landing page routes traffic to a product page, and that product has to be in your store.

⚠️ If Atlas does create a product from a link, check its price, inventory and shipping in Shopify before sending any paid traffic to it. Atlas creates the product so the page has something to sell. It does not set it up for selling.


The other messages you may see

While a product that failed to import is ticked, Continue setup stays disabled and hovering it shows Couldn't import one of the URLs — check the link or remove it. Untick the product to build without it, or remove it and paste the link again.

The same failure has other wordings depending on where you see it:

  • In the import window, the product's card says Couldn't import this product with Check the link, or remove it and try another. Select its delete icon to remove it.

  • On the Add products screen, the card says Couldn't load this product — remove it and paste the link again, and Confirm product(s) → stays disabled until you remove it.

Couldn't fetch the product from aliexpress.com. Try again, or go back and choose a different product. means a build stopped because Atlas could not read the product page while building. The message names the site your product link points to, aliexpress.com in this example. Select Retry once. If it fails again, go back and choose a different product or one from your catalog. See Why did my page generation fail?

The rest all have the same fix as above: pick the product from your catalog.

Message

What it means

Couldn't create a product from your ad. Go back and pick a product from your catalog.

The link came from an ad and could not be read

The ad's destination doesn't match a product in your store. Pick a product from your catalog instead.

The link resolved, but not to one of your products

The selected ad has no destination URL to build from. Pick a product from your catalog instead.

There was no link at all


If a supported site keeps failing

Amazon, Etsy, Shopify, AliExpress and Alibaba work reliably with Atlas. If one of those keeps failing across several different products, and the pages open in a private window, that is worth reporting rather than working around.

Start a chat from the bubble in the bottom right of Atlas, or email support@helloatlas.io. Either way, include:

  • two or three of the exact URLs that failed

  • confirmation that they open in a private browser window

  • your store URL

Send the URLs rather than a description of them. Support can test the exact links, which is the only way to tell a site-wide change from a single bad page.


Next steps

Did this answer your question?