Getting and keeping a feed

A feed is harder to keep than to get. Approval is a one-off hurdle. Staying approved is a daily discipline, and the people who last in this business treat compliance as part of operations, not as a department that says no.

How approval works

Feed approval differs by route, but the questions are the same: who are you, where does your traffic come from, and what will the visitor see?

1. ApplicationCompany details, experience, expected volumes, and the topics and countries you plan to run.
2. Traffic source disclosureEach source is listed and reviewed. This is traffic source approval, and it is per source, not once for all.
3. Creative and page reviewSample ads, article pages and the layout of the search unit. On Google RSOC, a mock-up of the implementation must be approved, and each site needs approval.
4. Trial periodLow volume while the provider and the search engine watch quality signals.
5. ScalingLimits are raised as the record builds.

Expect a provider to ask for history: past feeds, past ad accounts, references. A new operator with no record usually starts small on a hosted setup.

Why feeds are capped

A feed cap is a limit on how much traffic or revenue an account may run in a day. Caps frustrate operators who have found a winning campaign, but they exist for sound reasons.

• Quality is judged with a lag. Advertiser conversion data takes days to arrive. A cap limits how much damage a bad campaign can do before anyone knows.
• The provider's own limits. The search engine may cap the provider, which then rations volume between its publishers.
• Advertiser demand is finite. Pushing volume into a term beyond what advertisers want simply lowers the price for everyone.
• Trust is earned. Caps on new accounts rise with a clean record.

What the search engine watches

1. A feed comes with a rulebook: A search feed is lent, not owned. The engine’s AFS and RSOC policies, plus the provider’s contract, say what the ads, pages and traffic must look like. Compliance is the price of keeping the tap open.
2. Something breaks a rule: Typical causes: a misleading ad that promises what the page does not deliver, search terms unrelated to the article, an unapproved traffic source, or wording that pushes people to click ads. Each is a policy violation.
3. It gets noticed: Automated checks, manual reviewers and advertiser complaints all feed a review. The provider is watching too, because the engine holds it responsible for its publishers.
4. First rung: a warning: For a first or minor problem the usual result is a notice naming the issue and a deadline. Fixing the ad or page, and showing it, normally ends the matter. This is the cheap exit.
5. Second rung: limits: If issues repeat or quality looks weak, the feed may be throttled: a feed cap on daily volume, fewer ads per page, or a ban on one traffic source. Revenue falls immediately while ad spend may still be running.
6. Third rung: revenue taken back: Earnings tied to the violating traffic can be withheld or deducted, sometimes for weeks already reported. If $28,000 was estimated and $8,000 of it is judged non-compliant, that Clawback (revenue deduction) alone wipes out the month’s profit in our example.
7. Last rung: termination: Serious or repeated breaches end in the feed being switched off, often without a second chance, and unpaid balances may be kept (feed suspension). Severe cases can skip every earlier rung. This is platform risk at its plainest.
8. The damage travels: A terminated publisher rarely gets another feed quickly: providers share the same few engines and ask about history. And a provider with too many bad publishers risks its own contract, which is why approval is slow and monitoring constant.

The ladder of consequences

Enforcement usually escalates. A policy violation produces a notice with a deadline to fix. Repeated violations lead to restrictions. On Google RSOC, under the Restricted Access Features system active since August 2025, Google's help page says ten in-scope violations (or one egregious one) make a strike, and accounts with strikes can lose features such as extra related search blocks and reporting channels. Beyond that come caps, then withheld revenue, then feed suspension.

Money follows the same ladder. Revenue shown in the dashboard is an estimate. After review it is finalised, and the difference is a clawback. In serious cases a provider may withhold an entire period's earnings.

1. Money goes out first: Through March the arbitrageur buys 100,000 visitors at $0.20 each. The ad platform bills its card every few days: $20,000 of ad spend is gone before any income arrives. (An illustrative month.)
2. The dashboard shows an estimate: Each day the feed reports estimated revenue. By month end it reads $28,000, a paper profit of $8,000. It is a running tally, like a restaurant bill before the manager checks it.
3. The engine reviews the clicks: After the month closes, the search engine’s systems finish checking for invalid clicks: bots, accidental taps, repeated clicks, traffic that broke policy. The publisher does not get an itemised list of what was removed.
4. Advertisers are credited: Clicks judged invalid are credited back to the advertisers who paid for them. Say that comes to 5% of this publisher’s clicks. Nobody in the chain earns anything on a refunded click.
5. The clawback: 5% of $28,000 is $1,400, deducted from the publisher: a Clawback (revenue deduction). The $20,000 spent buying those visitors is not refunded by anyone. A heavy clawback can turn a profitable month into a loss after the fact.
6. Revenue is finalised: $28,000 minus $1,400 gives finalised revenue of $26,600. Real profit is $6,600, not $8,000. Google’s own AdSense timeline posts finalised earnings around the 3rd of the following month; feed providers set their own dates.
7. Payment arrives on Net terms: The provider pays on Net terms, here Net 30: about 30 days after month end. Money spent on 1 March comes back around 30 April. Some contracts are Net 45 or Net 60.
8. Growth eats cash: By the time March is paid, April’s $20,000 has also been spent. This cash-flow float means a growing arbitrageur needs working capital of one to two months’ spend, and a late payout or large clawback can sink a business that looks profitable.

How feeds are lost

• Invalid traffic. Bought from a poor source, or sent by a sub-affiliate the operator did not vet.
• Misleading creatives. Often written by a junior buyer or copied from a competitor seen in a spy tool.
• Thin or duplicated content. Hundreds of near-identical articles produced to carry search units.
• Forced or irrelevant keywords. Chasing high prices with terms the user never chose.
• Undeclared sources. Testing a new traffic source without telling the provider.
• Nothing you did. The search engine ends a product or a contract. Google removed parked domains in February 2026, and System1's annual report says one of its Google agreements was ended by Google from the same date. No operator's conduct caused that.

Habits that keep a feed

1. Keep a written record of every approved source, creative style and vertical, and work only inside it.
2. Review every creative against the page before launch. Since November 2025 the ad text travels with the request, so mismatches are visible to Google.
3. Monitor traffic quality yourself. Do not wait for the provider's report. Independent IVT detection shows problems days before a deduction does.
4. Cut sources and placements that send poor visitors quickly, even when they look profitable on estimated revenue.
5. Answer violation notices promptly and fix the cause, not only the flagged example.
6. Scale gradually. A sudden jump in volume invites review and removes your margin for error.
7. Spread risk across feeds and providers where volume allows.