Affiliate Link Cloaking Guide 2026: /go/ Redirects Done Right
Affiliate link cloaking replaces ugly tracking URLs with clean branded redirects — `yoursite.com/go/tool` instead of `afflat3e1.com/trk/lnk/0080372A-...` — and gives you click analytics, centralized link management, and protection against commission stripping.
Done right, cloaking is 100% white-hat and actually improves transparency when paired with proper disclosure. Done wrong, it can violate affiliate terms or hide links from readers. This is the right way — the same /go/ system this site runs on.
- Cloak via your own /go/ redirect — clean URL, click counting, one place to update dead links
- Affiliate outbound links get rel="sponsored nofollow" — Google requires it
- noindex your /go/ routes so redirect URLs never enter the index
- FTC: disclose affiliate relationships regardless of cloaking — cloaking changes the URL, not the disclosure duty
Why cloak at all
Raw affiliate links fail on four fronts: they look untrustworthy (a 100-character tracking string kills click-through), they expose your affiliate IDs to anyone who views source, they give you zero click data, and a broken merchant link means editing every article that links to it.
A /go/ redirect fixes all four: readers see a clean branded URL, you see clicks per link per page, and a dead program means editing one redirect — not forty articles.
The /go/ architecture
The pattern is simple: a registry file maps slugs to destination URLs, a route handler issues a 307 redirect, and every article links to `/go/[slug]`. This site runs exactly that — registry in `affiliate-links.ts`, handler at `app/go/[slug]/route.ts`.
- Create the registry slug → exact affiliate URL, plus a verified flag so you know which links track commissions
- Build the /go/ route look up the slug, 307-redirect to the destination
- Link everywhere via /go/slug — never paste raw affiliate URLs in content — Link everywhere via /go/slug — never paste raw affiliate URLs in content
- Optional log the click before redirecting (timestamp, slug, referrer) — that log is your conversion funnel data
Use 307 or 302, not 301 — temporary redirects preserve no-SEO-equity semantics and let you change destinations without fighting browser caches.
The SEO rules that are not optional
Google requires affiliate links to carry `rel="sponsored"` (or nofollow). Your /go/ links are outbound affiliate links — mark them. This is not optional decoration; undisclosed dofollow affiliate links are a manual-action risk.
Second rule: noindex the /go/ paths themselves. Add `X-Robots-Tag: noindex` on the redirect route or disallow in robots.txt — redirect URLs should never surface in search results.
Some affiliate programs (notably Amazon Associates) prohibit link cloaking in their ToS — check each program before cloaking its links. Most networks allow branded redirects.
Click tracking: the hidden ROI
The redirect is also your measurement layer: log slug, timestamp, and referrer page on every click. That log answers the questions affiliate dashboards cannot — which articles drive clicks, which anchors convert, which programs get clicked but never bought.
Clicks ÷ conversions (from your affiliate dashboard) = per-page conversion rate. Your best-converting page is the one worth updating monthly; see affiliate conversion optimization for the full CRO playbook.
Disclosure: cloaking does not exempt you
FTC (and equivalents elsewhere) requires clear affiliate disclosure regardless of URL shape. A visible disclosure near the top of money pages — "we may earn a commission" — covers you and, honestly, builds trust: readers who know you earn still click when the recommendation is honest.
The honest framing is a conversion asset, not a tax. Sites that disclose and recommend genuinely-good tools outconvert sites hiding both.
Common mistakes to avoid
- Missing rel="sponsored" — the most common compliance gap on affiliate sites
- 301 redirects on /go/ — browsers cache the old destination forever
- Indexed /go/ URLs — junk results in Google and potential cloaking-flag scrutiny
- No click logging — flying blind on which content actually earns
- Cloaking for deception — hiding that a link is affiliate at all. The redirect masks the URL, never the relationship
Affiliate link cloaking done right is infrastructure: branded /go/ redirects, sponsored attributes, noindexed redirect paths, click logging, and honest disclosure.
Set the registry up once, route every money link through it, and your click data will tell you exactly which content earns its traffic.
FAQ
Is affiliate link cloaking legal?
Yes — branded redirects through your own domain are legal and standard practice. You must still disclose affiliate relationships (FTC) and mark links rel="sponsored" (Google). Some programs like Amazon prohibit cloaking in their ToS.
Does cloaking affiliate links hurt SEO?
No — when done correctly: /go/ links carry rel="sponsored nofollow", the redirect routes are noindexed, and 307 redirects pass no false signals. Problems only appear when links pretend to be editorial.
What redirect type should cloaked links use?
307 (temporary) or 302 — never 301. Temporary redirects preserve the ability to change destinations and avoid passing link equity signals meant for editorial links.
Can I cloak Amazon affiliate links?
Amazon Associates' operating agreement restricts link cloaking — their links should be used as provided. Most other networks and direct programs allow branded /go/ redirects.
How do I track affiliate link clicks?
Log every hit on your /go/ route (slug, timestamp, referrer page) before redirecting. That log divided by dashboard conversions gives per-page conversion rates — the metric affiliate dashboards cannot show you.
Alex Mercer
AI Marketing Strategist · 8+ years
Alex has tested 200+ AI marketing tools on real campaigns with $50,000+ in ad spend. He writes hands-on reviews based on actual usage data, not press kits. His work has helped 10,000+ marketers build AI automation stacks that generate real ROI.