How to Migrate from AFD to RSOC

AFD ends effective February 10, 2026. That date comes from the November 2025 industry briefing on NamePros: "AFD, the foundation of domain monetization for the past decade, is ending effective February 10, 2026" (NamePros, November 2025). If you still have AFD inventory paying out, this guide is your migration playbook.

The short version: audit your AFD inventory, pick an RSOC feed provider that accepts your actual traffic source, rebuild your landing pages to RSOC's content-first standards, and migrate traffic in stages rather than all at once. The long version — with the specific provider-side requirements that trip up most operators — runs through the rest of this article.

When exactly is AFD shutting down?

The hard deadline is February 10, 2026. The decline that led to it played out over more than a year, and understanding the timeline helps with what to migrate first.

Three dated anchors are public:

1. April 14, 2025 — Novabeyond's market summary documents the start of advertiser opt-outs against AFD inventory: "another 6-8 month cycle, that is, by the autumn there may be a definite ending" (Novabeyond). The opt-out wave triggered the steeper revenue drop.
2. Through 2025 — Above.com tracked the decline in two phases: a ~60% drop from Google policy changes, followed by approximately a 95% drop on the remaining base after advertiser opt-outs (Above.com, February 2026).
3. February 10, 2026 — The end-of-AFD date confirmed by the Giant Panda briefing on NamePros. Above.com's February 2026 post described AFD as "shutting down this month" on the same timeline.

The financial impact on public companies in the space confirms how real the transition is. Edison Group described Team Internet's situation as "rebasing for Google AdSense transition" with "a significant reduction in revenues and gross margin as the company navigates the switch from AFD to RSOC" (Edison Group, March 2025). Investing.com reported Team Internet expected "a temporary financial trough in 2025 due to the anticipated faster decline in AFD" (Investing.com, March 2025).

If you are still receiving AFD payouts in May 2026, you are on borrowed time and your provider is likely batching final reconciliations. Migrate now.

What do you need before you start migrating?

Migration is not a one-click switch. Five things should exist on paper before you contact any provider:

1. An inventory list. Every domain or page you currently monetize through AFD, with traffic volume and revenue.
2. Domain categorization. Group each domain as typo, generic-dictionary, brand-adjacent, expired-with-backlinks, or content-capable. Each category demands a different migration path.
3. A traffic-source list. Where does the traffic actually come from? Direct navigation, typo, paid social, native, or a mix? Provider acceptance is driven by source.
4. A content plan. Which domains can support real editorial content (you write articles for them) versus redirect to existing content versus retire? Most operators retire 30 to 60% of their AFD portfolio.
5. A budget for the gap. Revenue dips during migration. The shorter your runway, the more important it is to pick a provider with fast onboarding and short payout cycles.

This audit step is the single biggest predictor of a successful migration. Operators who skip it end up paying for traffic to landers that get rejected by RSOC compliance, or they pick a provider that does not accept their traffic source and have to start over.

For deeper context on the underlying format differences, our AFD vs RSOC comparison walks through the structural changes in traffic, keyword control, and compliance.

Step 1 — Pick your RSOC feed provider

Provider choice is driven by traffic source compatibility first, payout terms second, RPM claims last. The "best" provider depends entirely on whether they accept your actual upstream.

Three traffic profiles cover most former AFD operators:

• Organic domain traffic (type-in, expired-domain catchers). Best fit: providers that accept and specialize in domain-portfolio inventory. Above.com runs RSOC for organic domain traffic and explicitly bans paid: "we are strictly against any type of paid or incentive-based traffic being sent to our RSOC pages" (Above.com, February 2026). Sedo and Giant Panda also fit here.
• Paid social and native traffic at scale. Best fit: buyer-focused providers with API integration and structured onboarding. Iron Click's Google RSOC program accepts Facebook, Taboola, Outbrain, TikTok, and Snapchat for buyers spending $10,000+/month. System1 and Coinis also accept paid traffic with public payout schedules.
• Mixed or large-portfolio. Best fit: providers with broader account types, like System1, who positioned themselves on their Q3 2025 call as "the market leader in RSOC" representing "a much larger" opportunity than the AFD they replaced (Seeking Alpha, November 2025).

Rather than committing to one provider upfront, most operators apply to two in parallel and let approval timing decide. Compare current options in our best RSOC feed providers guide.

Step 2 — Build RSOC-compliant landing pages

This is where AFD veterans get rejected. The Giant Panda briefing on NamePros stated the requirement directly: "RSOC ad units can only be invoked on fully-developed, pre-approved websites" (NamePros, November 2025). A parked domain does not qualify, no matter how good the traffic.

The page-level requirements come from three independent sources:

1. Real editorial content above the fold. AdsPower's RSOC compliance summary specifies content must be "visible without scrolling too much" with clear separation between content and search units, and no misleading labels or fake buttons (AdsPower, December 2025).
2. A 60/40 content-to-keyword ratio. firstbridgedigital documents the rule: at least 60% of the page area should be genuine editorial material; keyword blocks take up no more than 40% (firstbridgedigital, March 2025).
3. No deceptive UI elements. Fake video play buttons, fake "Next" buttons that route to search results, unrelated clickbait images, and sticky monetization frames are explicitly prohibited.

In practice, RSOC landers look like topic pages or news articles. Headings, paragraphs, internal navigation, real images, and a single related-search unit embedded in the body. Most former AFD operators copy a content site they already know — an "answer-this-question" article with the search unit positioned mid-page.

For pages built on previously parked domains, the realistic options are: rebuild as a content site (best long-term outcome), redirect 301 to existing content elsewhere (preserves any backlink equity), or retire the domain (skip the content build entirely if traffic is not worth it).

Step 3 — Connect via API or portal

Once the lander is approved, integration usually takes a day or two. Two integration models dominate:

• API integration. The feed unit is requested server-side or via JavaScript, the provider returns rendered search terms, and tracking is wired in via standard pixels or postbacks. Iron Click's Google RSOC product uses API integration with instant statistics and keyword recommendations surfaced in the partner dashboard.
• Portal or widget. Some providers offer a simpler embed snippet that drops in via copy-paste. Easier to start, less flexible at scale.

Whichever model you use, tracker setup matters. Most paid-traffic operators run ClickFlare or RedTrack to attribute revenue back to creatives and audiences. The 2026 default workflow is: ad platform → tracker → lander → RSOC unit, with conversions firing back to the ad platform via the tracker's postback URL.

Test in low-volume mode before scaling. Send 5–10% of normal traffic, confirm the unit renders correctly, payouts register in the dashboard, and tracker attribution matches provider stats within an expected tolerance. If something is misaligned, fix it before increasing spend.

Step 4 — Migrate traffic gradually

Do not dump 100% of your AFD traffic onto a new RSOC unit on day one. Three things go wrong when operators try:

1. Compliance reviews trigger automatically. A sudden traffic spike on a new account is one of the strongest signals provider compliance teams watch for. Even legitimate traffic at full volume from a new account gets a manual review.
2. Keyword themes have not stabilized. Google's keyword override on RSOC means the first week or two often shows lower RPMs than the steady-state. Optimizing creatives against an unstable RPM curve burns budget.
3. Lander issues do not surface at low volume. A broken tracker, a slow page, a layout that fails compliance — all easier to spot and fix at 10% traffic than at 100%.

The standard migration ramp is 10% → 25% → 50% → 100% over two to four weeks, with at least three to five days at each step to gather stable data. Iron Click partners get keyword recommendations during this phase based on what is actually monetizing rather than what was targeted — a useful steer for creative and lander iterations.

Track three numbers daily: RPM (revenue per thousand visitors), payout-to-spend ratio (your ROAS proxy), and compliance flags from the provider dashboard. Any sudden change in any of the three is worth pausing to investigate.

What are the most common AFD-to-RSOC migration mistakes?

The mistakes that close accounts are predictable. Avoiding all five gets most operators to a stable steady-state inside the 30-to-90-day window.

1. Sending parked-domain typo or direct-nav traffic straight to RSOC. Will fail compliance and may close the account.
2. Skipping the content build step. "Will write content later" landers get rejected on first review.
3. No tracker between the ad platform and the lander. You cannot optimize what you cannot attribute. Use ClickFlare, RedTrack, or equivalent.
4. Choosing a provider on RPM claims alone. A high claimed RPM means nothing if your traffic source is not on the provider's approved list.
5. Not pre-clearing creatives and landers during onboarding. Most providers will pre-review on request. Use it.

For media buyers running paid social at $10K+/month, Iron Click handles the pre-clearance during onboarding — creatives, landers, and tracker integration are reviewed before the feed activates. The full product page is at /rsoc-feeds-by-iron-click, and the partner application is at /search-provider.

Frequently asked questions