Google Merges AdSense for Search Policies Into One Set in 2027
Google will merge AdSense for Search and Search ads policies into one unified set effective January 17, 2027, tightening placement, traffic and demand rules for AFS publishers.

- Google merges AFS and Search ads policies into one unified set on January 17, 2027
- AFS ads banned on pages with more ads than organic search results and on no-results pages
- Ad requests must come from user-submitted queries; no pre-populated search boxes allowed
- Maximum two Google search boxes per page under the new rules
- AFS remains web-only; backfilling slots with AdSense for Content or Ad Manager is prohibited
Google will merge its AdSense for Search (AFS) policies and Search ads policies into a single unified policy set on January 17, 2027. The company published the full text of the new policy alongside the announcement. Google stated: "The update will simplify our policy structure, modernize requirements to reflect the current business landscape, and improve clarity and transparency."
This is a confirmed Google announcement, not tool-signal speculation. It targets publishers running AFS ads, including ads delivered through Google's Programmable Search Engine when an AdSense account is activated.
What changes on January 17, 2027?
The unified policy replaces two separate policy documents with one set of supplemental rules layered on top of the Google AdSense Program policies. Google confirmed AFS remains web-only: "AFS is only supported in web-based environments."
The policy defines three key terms:
- "AFS ads" — AdSense for Search ads, including ads via Programmable Search Engine and Search ads
- "Search ads" — AFS ads served through the Custom Search Ads (CSA) protocol
- "content" — everything shown to users, including organic results, ads and outbound links
Non-compliance carries defined consequences: Google may suspend services, require publishers to cease or modify implementation, or exercise rights under the AdSense Online Terms of Service.
Which content is restricted?
The new rules bar AFS ads on search results pages where results consist substantially of:
- Videos
- Images
- People
- Music
- Content originating from any Google service other than Programmable Search Engine — the policy names the YouTube API as an example
AFS ads must appear only on search results pages, defined as pages displaying results in response to a user-submitted search query. Google explicitly bans AFS ads on no-results pages, including zero-result responses, "Lorem ipsum" placeholder text, and gibberish or incoherent result strings.
The policy states that related suggestions such as "you may be interested in" do not count as search results.
How do the traffic quality rules work?
Every AFS ad request must originate from a user-submitted query with clear intent, from one of three permitted sources: a direct, unedited search box entry; an AdSense for Search Product-Integrated Feature; or an Alternative Search Query. Search boxes may not be pre-populated, and publishers may not create links containing pre-populated terms.
Additional implementation limits:
- One ad request per user action — a new search, a click, or a scroll loading more results
- Each AFS ad shown once only, unless Google approves in writing
- No interstitial content between ads and clicked pages, or before pages containing AFS ads
- No modification of AFS code, including framing, obscuring or reordering ad content
- AFS ads must display in a single continuous block, not interspersed with other ads or content
The traffic rules preserve one publisher freedom: nothing in the policy restricts sourcing, formatting or modifying ads not provided by Google.
What placement limits apply?
Three placement constraints cap monetization density:
- No more than two Google search boxes per page
- All paid material, Google or third-party, must be clearly identified and distinguishable from organic results
- Pages may not show more ads or paid promotional material than organic search results
What does the policy say about other Google demand?
The unified rules prohibit concurrent Google Ads text demand on the same page through other ad slots. They also ban backfilling: publishers may not fill AFS slots with results from AdSense for Content or Google Ad Manager, and may not alternate result types across views of the same slot.
Using AdSense for Content or Google Ad Manager in non-AFS slots remains permitted.
What should publishers watch next?
Publishers running Custom Search Ads or Programmable Search Engine monetization should audit implementation against the unified text before January 17, 2027 — particularly pre-populated search boxes, no-results pages and mixed-demand slots. Google's posted policy draft remains the reference point, and further technical protocol updates may follow before enforcement begins.
via support.google.com (Original)
More from Nathan Brooks
Show full bio
Senior reporter covering companies, deals and strategy in Search rankings and algorithm updates, generative engine optimization at SERP Journal.
226 articles