Amazon OneLink Not Working: How to Find the Cause

If Amazon OneLink is not redirecting your international visitors, the cause is almost always one of five things: the OneLink script is not loading on the page, your links are cloaked or shortened so the script does not recognise them as Amazon links, a consent banner or ad blocker is stopping the script from running, a cache is serving a version of the page without it, or the visitor’s country is not one you have linked and been approved for. All five look identical from the outside, which is why OneLink feels random when it breaks.

The reason there are so many failure points is that OneLink works in the visitor’s browser. Amazon gives you a small script, and that script rewrites Amazon links after the page loads. Anything sitting between your HTML and a fully running page can interrupt it. Here is how to check each cause in a sensible order, and what to do if you would rather not depend on a browser script at all.

First, Know What OneLink Should Do

OneLink is Amazon’s own free tool for international affiliates. You link the marketplaces you have been approved for in Associates Central, add your tag for each, and add Amazon’s script to your site. When a visitor from a supported country loads your page, the script rewrites your Amazon links so the click lands on their local store with your tag for that store. Amazon’s international linking documentation is the authority on what is supported.

Two things follow from that design. It only affects countries you have actually linked, and it only affects links the script can recognise as Amazon URLs. A lot of reported OneLink failures are OneLink behaving exactly as documented in a situation the owner assumed was covered.

Check the Script Is Loading at All

Start here, because it is the most common cause and the easiest to confirm. Open a page with an Amazon link, press F12 to open your browser’s developer tools, and look at the Network tab, which lists every file the page downloaded. If Amazon’s OneLink script is missing from that list, nothing else you configure matters.

If it is missing, suspect your optimisation setup. Performance plugins combine, defer and delay scripts, and a script delayed until the visitor interacts, or bundled with a file that throws an error, effectively never runs. An error earlier on the page can also stop later scripts, so check the Console tab for red errors. Excluding Amazon’s script from combining, deferring and delay-until-interaction usually settles it, and MDN’s reference on the script element explains why loading order matters.

Cloaked and Shortened Links Are Invisible to It

This one surprises people. The script scans your page for links pointing at Amazon domains. A cloaked link on your own domain, say yoursite.com/go/kettle, is not an Amazon URL when the script looks at it, so the script leaves it alone. The visitor then follows your redirect to whatever single storefront it was configured for, in every country.

The same applies to third-party short links. If you cloak your affiliate links, either exclude Amazon links from cloaking or handle the routing in the redirect itself, which is what a server-side plugin does. This is the single most common reason OneLink looks broken on otherwise well-built sites: the tool never saw the links.

Consent Banners and Ad Blockers Stop It Cold

If you run a cookie consent tool, it very likely holds non-essential scripts until a visitor accepts, which is what the ICO’s guidance on cookies and similar technologies expects for anything that is not strictly necessary. Every visitor who ignores or declines the banner keeps your original links. That is not a bug in your setup, it is the consent tool doing its job.

Ad blockers and privacy-focused browsers add a second layer, because Amazon’s ad-system domains are on common blocklists. A meaningful slice of your audience runs one, and for them the script simply never arrives. We covered the wider version of this problem in how ad blockers break browser-based tracking. Both cases share a lesson: anything essential to your earnings is fragile when it depends on the visitor’s browser cooperating.

Caching and Content Added After Load

Full-page caching serves saved HTML. If you added the OneLink script after a page was cached, visitors keep the old copy until the cache clears, so your change appears to have done nothing. Purge your cache and any CDN after touching the script, then test in a private window.

Then there is content that appears after the script has run: links inside popups, tabs, lazy-loaded blocks, infinite-scroll listings or anything loaded by JavaScript after the initial page. The script processed the page as it existed at the time. Links that arrive later can be missed entirely, which is why one page works and another with the same links does not.

The Country or the Tag Is Not Set Up

Once the mechanics check out, go back to the setup. OneLink can only send a visitor to a store you have linked in Associates Central, with a valid tag for that store, and each Amazon marketplace approves affiliates separately. A visitor from a country you have not covered gets your original link, and their purchase on their local store earns you nothing. That is the default state we explain in why international Amazon clicks earn nothing.

Test properly before you conclude it is working. Use a VPN in a clean browser profile with no ad blocker, load a page, and hover an Amazon link to see the real destination. Check two or three of your biggest overseas countries rather than one, because coverage is per marketplace.

The Server-Side Alternative

If you would rather not depend on a script surviving optimisation, consent tools and blockers, move the decision to the server. Instead of rewriting links in the browser, the destination is chosen at the moment of the click, before the browser has any say. DevDome Affiliate Manager works this way: it resolves the visitor’s country server side and sends them to their local Amazon with your tag for that store, across 22 storefronts, and stores you have no tag for are never targeted.

With no browser script in the path, blockers and consent banners cannot remove it, caching cannot serve a version without it, and links added by JavaScript later behave like any other. It also tags links at display time without editing your posts, and monitors products for out-of-stock and 404. Measuring on the server changes what the click column means, too: over the last 30 days on one of our affiliate sites, people made about 9,450 tracked clicks and bots fired another 4,070, so roughly 3 in 10 raw click events were not human and only a server-side check separated them. We compared both approaches in Amazon OneLink versus a geo plugin, and plans start free, with paid tiers on our pricing page.