The compliance question every new affiliate operator hits is the same question generic legal templates don't answer: where exactly should the disclosure go on a real website so a reader sees it before clicking, without burying the message or weakening the operation? This article is the answer for solo operators. Site-wide disclosure page, inline near-link disclosure, clear-and-conspicuous placement. Three components, one architecture. The rest is implementation.

The Problem This Solves

The Compliance Question Every New Affiliate Operator Hits

Solo operators starting an affiliate-content site know they need a disclosure. The actual question is harder: where does it go on a real site with reviews, comparison articles, sticky CTAs, comparison tables, email sequences, and /go/ redirects? Most affiliate operators reach this question after their first or second monetised article and find that the legal-template content online describes requirements without translating them into website architecture.

This article is the implementation guide for the FTC affiliate disclosure question for solo operators. It covers what the FTC actually says, what that means at the page level, and what the disclosure architecture looks like across the common publishing stacks: WordPress, static sites, funnel platforms, and /go/ redirect patterns.

Why This Matters Beyond Cautious Housekeeping

The FTC doesn't merely publish guidance. It enforces against deceptive endorsement and advertising practices under Section 5 of the FTC Act, and the Endorsement Guides at 16 CFR Part 255 are the administrative interpretation applying Section 5 principles to endorsements and testimonials, including affiliate relationships.

The FTC has pursued enforcement actions involving inadequate disclosure of material connections — influencer cases, endorsement misrepresentation matters, and reviews where the commercial relationship was not made clear to the reader. Specific penalty figures change and are out of scope here. The operational point: the FTC actively enforces; the Guides aren't a polite suggestion. The architecture below reduces the surface area where a deceptive-failure-to-disclose problem can develop.

Why Generic Legal Templates Don't Solve Implementation

A standalone affiliate disclosure page is useful, but it doesn't solve the placement problem inside individual reviews, comparison articles, listicles, emails, social posts, or affiliate redirects. Legal-template content explains the rule. This article translates the rule into website architecture.

Generic legal-SaaS articles tend to stop at "have a disclosure page and make it clear." That doesn't help the operator who needs to decide whether the disclosure goes above the table, in the table caption, near each CTA button, in the email body, or all four. The reader of this article leaves with concrete patterns to apply across the four stacks affiliate operators actually run on.

Scope and Jurisdiction Guard

This article focuses on FTC disclosure principles for affiliate content and endorsements published from a solo-operator website. Non-US operators may still need to care if they target US consumers; jurisdictions outside the US may impose separate or additional requirements (EU consumer-law obligations, UK Advertising Standards Authority rules, and similar). Local rules are out of scope here.

No promise that this architecture makes a site "FTC compliant" follows. Compliance is context-specific. What follows is an implementation architecture designed around FTC public guidance and the operational lessons of running affiliate-content sites in 2026.

Site-wide disclosure page + inline near-link disclosure + clear-and-conspicuous placement. Three components, one architecture.

The Minimum Compliant Disclosure Architecture

The Three-Part Architecture

The architecture has three components:

  1. A site-wide affiliate disclosure page. Linked from the footer, accessible from every page. This is the reference document.
  2. Inline disclosure near affiliate recommendations. Visible before the reader encounters a monetised recommendation, on the same page where the recommendation lives.
  3. Clear-and-conspicuous placement before the decision point. Implementation-specific: the disclosure must be visible before the reader clicks, subscribes, or buys.

The disclosure page is the record. The inline disclosure is the reader-facing control. The placement rule is the operational test: would a normal reader see the disclosure before acting on the recommendation? If the answer requires interpretation, the placement isn't clear-and-conspicuous enough.

Why All Three Parts Are Needed

The FTC's material-connection principle treats endorsements differently when the endorser has a financial relationship that a reasonable reader wouldn't otherwise expect. Affiliate commissions create that material connection. If the relationship might affect how a reader weighs the recommendation, the FTC's Endorsement Guides say the connection should be disclosed in a way the reader will understand.

A homepage-only disclosure fails operationally because most search visitors arrive directly on a specific article — a comparison, a review, a tutorial — not the homepage. A footer-only disclosure fails because most readers don't scroll to the footer before clicking a recommendation. The FTC's affiliate-marketing FAQ explicitly addresses this: a single disclosure page on the homepage is not sufficient because users may land elsewhere and not see it.

The three-part architecture works because the components reinforce each other: the disclosure page is the reference; the inline disclosure is the visible operational signal; the placement rule keeps the disclosure where the reader actually makes the decision.

What "Clear and Conspicuous" Means in Implementation

The FTC's standard is that disclosures should be difficult to miss and easily understandable. In interactive media, the 2023 Endorsement Guides revision explicitly states that disclosures should be unavoidable.

Translated into website rules: visible before the first monetised recommendation; not hidden in footer-only text; not collapsed behind "more" buttons or accordions; not styled as grey-on-grey legal dust at the bottom of a page. On mobile, the disclosure should remain visible at the top of the relevant section, not pushed below the fold by a sticky header.

The reader-understanding test is the operational shortcut: would a normal reader, scrolling at normal speed on the device they're actually using, understand the financial relationship before they decide to click, subscribe, or buy? If the answer requires the reader to hunt for the disclosure, the placement isn't unavoidable enough to be clear-and-conspicuous in the FTC's framing.

Per-Page-Type Disclosure Recipes

This section carries the article. The architecture above is necessary but not sufficient. The implementation depends on the page type and the layout pattern.

Reviews and Product Walkthroughs

Recommended pattern: Place a disclosure block directly under the article intro or before the first product recommendation. If the first CTA appears much later in the article (after 1,000+ words), add a short reminder near that CTA.

Review pages are higher-risk because the entire article often functions as an endorsement, even when the writer treats it as a tutorial or walkthrough. The reader is being asked to consider a recommendation; the material connection should be disclosed before they form an opinion.

Comparison Articles and Comparison Tables

Recommended pattern: Top disclosure before the article's first product judgment, plus a caption or note above any comparison table that contains affiliate links.

For long comparison articles with multiple CTAs spread across sections, the top-of-article disclosure is the baseline. The FTC's "clear and conspicuous" standard is context-specific, and long pages with sticky CTAs, mobile cards, or table-based decisions create scroll-distance risk: the reader may act on a recommendation deep in the article without remembering the top disclosure. Reinforce the disclosure before major decision points where layout, scroll distance, or interactivity separates the CTA from the original disclosure.

Listicles and "Best Of" Roundups

Recommended pattern: Disclosure before the first ranked recommendation. Reinforce before any sticky CTA module, embedded offer box, or independent "best overall" card.

Ranking articles are trust-sensitive because commercial bias can hide behind editorial ordering. A reader who skims the article and lands on the "#1 pick" needs to see the disclosure before forming a buying intention.

Email Sequences

Recommended pattern: Disclose affiliate links inside the email body before the first monetised link. Don't rely on the destination page's disclosure.

Email is a separate decision environment. The reader may click directly from the inbox and never see the article's top-of-page disclosure. The disclosure has to ride with the email.

Social Posts

Recommended pattern: Use plain-language disclosure early in the post body. Don't rely solely on brand tags, vague hashtags, or platform-native tools.

The FTC's affiliate-marketing FAQ says tagging a brand is not sufficient to disclose a relationship, and the 2023 Endorsement Guides revision notes that platform built-in disclosure tools may not be adequate depending on how visibly they render. Vague, buried, unclear, or platform-only disclosures may fail the "clear and conspicuous" standard depending on context.

Clear disclosure is not a conversion leak. Hidden disclosure is a trust leak.

Stack-Specific Implementation

The same three-part architecture renders differently depending on the publishing stack. The mistake to avoid is assuming one platform's pattern transfers to another. A WordPress plugin doesn't solve disclosure for a static site; a Systeme.io built-in block doesn't solve disclosure for a Cloudflare Pages deploy.

One operator, multiple properties: if you run a main blog, a niche site, a separate funnel domain, and an email list under one operator, each property needs its own disclosure architecture. A disclosure on devonkorr.com shouldn't be treated as a substitute for a disclosure on a sister site, even if the same operator runs both. The architecture is the same; the implementation lives on each property.

WordPress

Recommended implementation:

  • A site-wide affiliate disclosure page linked in the footer.
  • A reusable block or pattern inserted under the intro of every monetised article.
  • A reusable comparison-table caption used as a shortcode or pattern.
  • Manual near-CTA reminders on long pages where the first CTA is far below the top disclosure.

SEO plugins like Yoast or RankMath manage page metadata and structured data, but they don't decide whether a disclosure is clear-and-conspicuous. Disclosure placement is editorial discipline, not plugin output. See the Systeme.io vs WordPress for Beginners comparison for the platform-choice context.

Static Sites: Astro, Next.js, Cloudflare Pages

Recommended implementation:

  • A reusable <AffiliateDisclosure /> component for reviews, comparisons, roundups, and tutorials.
  • Frontmatter flags such as hasAffiliateLinks: true or affiliateDisclosure: comparison that conditionally render the right disclosure block per article type.
  • Manual near-link disclosures where affiliate CTAs appear far below the intro disclosure or inside interactive cards.

Static sites give the operator the most precise control over disclosure placement because every page is a component composition. The trade-off is that nothing is automatic — you have to ship the disclosure component and use it deliberately on every monetised page.

Funnel Platforms: Systeme.io and Similar Tools

Recommended implementation:

  • Disclosure blocks above CTA sections, checkout-intent pages, bridge-page buttons, and email templates.
  • A site-wide affiliate disclosure page reachable from the footer of every funnel page.

Funnel templates often optimise for conversion and may place disclosures below the decision point by default. The operator has to override the template to put the disclosure where the reader actually decides. See the Systeme.io vs WordPress for Beginners comparison for the platform context.

/go/ Redirect Pattern and Affiliate Redirect URLs

Recommended pattern: Redirect URLs don't replace disclosure. The reader should understand the affiliate relationship before clicking the /go/ link, not on the destination page.

Disclose on the source page before the /go/ link or near the CTA that uses the redirect. The redirect handles outbound routing; the disclosure handles reader understanding. The FTC's affiliate-marketing FAQ guidance applies whenever an endorser is paid through affiliate links, regardless of whether the link goes through a redirect URL.

For the implementation pattern behind /go/ redirects on Cloudflare Pages, see How I Set Up Affiliate Tracking with Cloudflare Pages and /go/ Redirects (2026).

Disclosure Language That Meets the "Clear and Conspicuous" Test

Plain Language That Works

Complete sentences that name the relationship and the consequence work better than abbreviated labels. Three patterns that meet the test:

  • "I may earn a commission if you buy through links on this page."
  • "Some links in this article are affiliate links. I may earn a commission if you click and purchase."
  • "Affiliate disclosure: I may earn a commission from links in this comparison."

The FTC's affiliate-marketing FAQ indicates that wording such as "I get commissions for purchases made through links in this post" is clearer than vague labels like "affiliate link" alone. Plain language is also commercially better: it reduces reader suspicion without forcing the reader through legal phrasing.

Phrasings That Fail or Create Risk

Weak patterns to avoid:

  • Footer-only disclosure (the reader doesn't see it before the recommendation).
  • "Affiliate link" with no explanation (the FTC FAQ notes this label may not be understood by consumers).
  • "Commissionable link" (the FTC FAQ specifically calls this label probably unclear).
  • Grey-on-grey text or tiny font (fails the visibility part of clear-and-conspicuous).
  • Collapsed accordion or behind a "more" link (fails the unavoidable standard in interactive media).
  • Disclosure placed after the CTA (the reader has already made the decision).

The operator point: if a reader needs marketing knowledge to understand the disclosure label, the wording is too clever.

The Reader-Understanding Test

The functional question is whether a normal reader, scrolling at normal speed on the device they're actually using, understands before clicking that the operator may earn money from the recommendation. FTC guidance is context-specific; there is no universal magic sentence that creates a safe harbor.

Tied back to the Devon Korr operator philosophy: clear disclosure is not a conversion leak. Hidden disclosure is a trust leak. Operators who try to hide the commercial relationship from readers end up with a smaller audience that distrusts them. Operators who disclose plainly keep the trust, keep the audience, and keep the click conversion.

What to Do If You Have Published Without Disclosure

Audit First, Then Retrofit

Build the audit list across content types:

  • Reviews
  • Comparisons
  • Roundups and listicles
  • Tutorials with affiliate tool links
  • Email sequences with affiliate links
  • Social posts driving meaningful traffic
  • Landing pages and bridge pages

Sort by traffic, monetisation intent, and number of affiliate CTAs. Pages with comparison tables, "best" rankings, and high-converting CTAs get fixed first.

Keep a simple audit log: date, URL, issue found, disclosure before/after, verification status. This isn't framed as legally required. It's good operational hygiene and, if the question ever arises, evidence of a deliberate good-faith retrofit effort.

Update Current Live Content

If content is live and contains affiliate links, the disclosure architecture goes in. The priority order:

  1. Comparison tables and "best" rankings (high commercial intent per visit)
  2. Review pages (entire page functions as endorsement)
  3. Sticky CTA modules and floating banners
  4. Email templates with affiliate links
  5. Standalone bridge or sales pages

Retrofit reduces the ongoing gap on current live content. It does not erase past exposure. The operational framing: ship the architecture across all live content, then improve the wording iteratively.

Render-Verify the Fix

A disclosure that exists in HTML source but doesn't render visibly on the page is not a clear-and-conspicuous disclosure. After the retrofit, spot-check:

  • First-viewport rendering on desktop and mobile
  • Above the first CTA on long pages
  • Inside comparison tables and around table captions
  • Behavior of sticky or floating CTAs
  • Dark-mode or low-contrast theme rendering
  • Email client truncation (most email clients clip long emails after a length threshold)

The disclosure has to render visually where the reader actually sees it, not just live in the source code.

Speed-of-Fix Sequence

The suggested order for a retrofit, prioritising high-impact wins first:

  1. Add or update the site-wide affiliate disclosure page.
  2. Add a reusable top-disclosure block to all monetised article templates.
  3. Add comparison-table disclosure captions to existing comparison pages.
  4. Add near-CTA reminders on money pages with long scroll distances.
  5. Update email templates to include the disclosure before the first affiliate link.
  6. Recheck rendering on desktop, mobile, and email-client previews.

Ship the architecture first; improve copy second. A live disclosure that says "I may earn a commission" beats a perfectly worded disclosure that hasn't been deployed yet.

What to Do Next

The operational thesis: site-wide disclosure page + inline near-link disclosure + clear-and-conspicuous placement. Implement all three. Audit existing content against them. Render-verify on desktop, mobile, and email previews.

Build the Stack Around Disclosure, Not After It

Bottom Disclaimer

This article is operational guidance based on public FTC materials. It is not legal advice. For your specific jurisdiction and risk profile, consult qualified counsel.