← Affiliate Disclosure Checker
Affiliate Disclosure Checker vs. checking a post by eye
Re-reading a post you already published catches an obviously missing disclosure. It reliably misses an affiliate link hidden behind ordinary anchor text, a rel="sponsored" attribute with no visible marker at all, and whether the disclosure actually sits before the first affiliate link once a post has more than one — which is what this free, no-upload checker computes exactly, in one pass.
Where re-reading it yourself stops being enough
Every blogger who has ever added an affiliate link already does this: publish the post, then read it back and check whether the disclosure is there. For the obvious case — no disclosure sentence anywhere on the page — that read-back is enough on its own. The problem is the other three things a real disclosure check needs are not visible from reading the rendered words at all.
| What you're trying to confirm | Reading the post yourself | This checker |
|---|---|---|
| No disclosure sentence anywhere on the page. | Works. This is the one case a plain read-back reliably catches. | Also catches it, in the same pass as everything below. |
An affiliate link disguised behind ordinary anchor text ("click here", "this gadget") — the tracking signal is in the href, not the words you read. | Invisible while skimming rendered text. Confirming it means opening view-source and checking every link's underlying URL by hand, one at a time. | Classified automatically from the href against known Amazon, ShareASale, CJ, Impact, Skimlinks, AWIN, and similar tracking patterns. |
A rel="sponsored" attribute with no visible marker on the page at all. | Cannot be seen by reading the page; it exists only in markup a reader never renders. | Read directly from the anchor's rel attribute. |
| Whether the disclosure genuinely appears before the first affiliate link, once a post has several links spread across multiple paragraphs. | Requires holding your reading position and every link's position in mind at once and comparing them — easy to misjudge in a longer post. | Computed as an exact character-offset comparison between the disclosure and every recognised link. |
| Whether an Amazon link specifically carries Amazon's own required exact statement, as distinct from a generic "affiliate links" note. | Easy to assume a generic disclosure covers it — both read as disclosure-shaped sentences. | Checked as a separate condition from the generic disclosure match. |
| Re-checking an entire blog's back catalogue after adding a new affiliate link somewhere. | One post at a time, remembered by hand, every time something changes. | One CLI command against a whole build-output directory. |
A quick read-back is still the fastest way to catch a post with no disclosure at all, and this checker is not doing anything a careful line-by-line audit couldn't — it is reading the same markup a careful audit would, just checking every link's href and every character position automatically instead of leaving the comparison to be remembered by hand.
This tool needs no account and no sign-in: the browser page parses HTML you paste entirely in your own browser, and the CLI reads only local files. Neither ever sends your content anywhere.
Common questions
Can't I just re-read my post and check for the disclosure myself?
For a post with one affiliate link and a disclosure sentence right above it, yes -- that case is obvious on a single read. What re-reading does not reliably catch is a disclosure that is present but appears after the first affiliate link rather than before it, an affiliate link whose href carries a tracking domain or parameter you did not recognise while skimming the rendered text, or a rel="sponsored" attribute that has no visible marker at all. Those need the actual markup checked in the order a reader encounters it, not remembered while reading the words.
Why is spotting an affiliate link harder than it looks?
Because the signal that makes a link an affiliate link lives in the href, not in the anchor text you actually read. "Buy it here" gives no clue whether the underlying URL carries an Amazon tag= parameter, routes through a shortener like amzn.to, or goes through a tracking domain such as shareasale.com, cj.com, impact.com, or skimlinks.com -- and rel="sponsored" is an attribute on the tag, never rendered as visible text at all. Confirming any of that means opening view-source and checking every link's markup by hand, one link at a time, which is exactly the comparison a skim of the rendered page does not do.
Doesn't having a disclosure somewhere on the page cover it?
No -- the FTC's guidance is specifically about a disclosure appearing before the first affiliate link a reader would encounter, not merely existing on the page. In a short post with one link near the top, eyeballing that order is easy. In a longer post with several affiliate links scattered across multiple paragraphs, correctly judging whether your disclosure sentence's position precedes every one of them means holding both positions in mind at once and comparing them -- which is a character-by-character ordering question, not a skim.
Is a generic "affiliate links" note enough for an Amazon link?
Not for Amazon specifically, and this is the mistake reading a post yourself is most likely to miss: a generic disclosure phrase reads as sufficient at a glance, so nothing about re-reading a post prompts you to check for Amazon's separate, exact required wording ("As an Amazon Associate I earn from qualifying purchases"). The two are easy to conflate on sight because both are disclosure-shaped sentences; only checking for the exact phrase, not just the presence of some phrase, tells them apart.
Is this page making a live comparison against a tool or company?
No. This page describes a manual habit every blogger already has -- re-reading a published post and checking it by eye for a disclosure. It names no competing product or company. The checker itself makes no network request of any kind: the browser page parses pasted HTML in your own browser, and the CLI reads only local files.
Never written a disclosure yet? See this checker vs. Post Affiliate Pro's Disclosure Generator, or read what disclosure Amazon Associates and the FTC actually require.