Key details

  1. Official Google AdSense policy change dated October 22, 2026.
  2. Accompanying Content no longer must load inside the page body.
  3. Sticky in-stream/accompanying video no longer must start in main content before scrolling.
  4. Accompanying video remains muted by default; sticky players require an unobstructed dismiss option.
  5. Autoplay still requires at least 50% ad-unit visibility and accurate placement signals.
  6. No published evidence establishes a general revenue or RPM increase from the change.

What builders should take away

  1. Review video ad layouts previously rejected for body-of-page or scroll-to-sticky placement restrictions.
  2. Check current Video inventory restrictions rather than relying on 2024 implementation guides that repeat superseded rules.
  3. Keep muted-by-default accompanying video, correct placement declarations, supported SDKs, autoplay visibility and dismissal controls.
  4. Test page performance, user annoyance and revenue; policy eligibility does not imply strong advertiser demand.
  5. Do not generalise the relaxation to CTV/digital-out-of-home sticky video or unrelated ad formats.

What changed

On October 22, 2026, Google revised its AdSense Video inventory restrictions. Its official policy change log explicitly removes two previous requirements: that Accompanying Content placements load within the body of the page, and that In-stream or Accompanying Content players must begin in the main content and only transition to a sticky placement when the user scrolls them off-screen. The live policy now gives a side-of-page or floating sticky video as an example of Accompanying Content. It continues to require accurate classification of placements, muted-by-default accompanying video, supported Google video SDKs, unobstructed controls, a visible dismiss option for sticky video and at least 50% visibility before autoplay. The change is a policy relaxation, not a guarantee that all inventory will be monetised.

Why it matters

Publishers and small editorial websites that use accompanying video ads can reconsider layouts previously blocked by Google's location and scroll-transition rules. The change potentially allows a video player to begin in a floating or sidebar position without first occupying an article slot, reducing layout constraints. It also creates room for experiments in reader experience and monetisation, but buyers may value such inventory differently and Google still restricts misleading or poorly implemented video. The material effect is an eligibility and implementation change, not evidence of increased RPM or advertiser demand.

Two specific placement restrictions have been removed

Google's policy log says accompanying-content video no longer must load inside the page body. It also removes the requirement that an in-stream or accompanying player start in the main content and become sticky only after a scroll transition. The revised live definition expressly allows accompanying video on the side of a primarily editorial page or as a floating sticky player. This is not a change to the definitions of in-stream, interstitial and standalone placements.

Other user-experience and technical rules remain

Accompanying Content must still be muted by default, and video inventory must declare the correct placement type and audibility. Supported Google Interactive Media Ads SDK or Programmatic Access Library implementations remain required for in-stream and accompanying content on supported platforms. Sticky players need an unobstructed dismiss option for the entire duration. Autoplay requires at least 50% ad-unit visibility; only one in-stream/accompanying player may autoplay in view at a time. Connected TV and digital-out-of-home inventory do not gain sticky-placement permission under this change.

Monetisation and user experience are separate questions

Google says restricted inventory may receive less advertising than non-restricted inventory, and its live guidance notes that implementation details influence individual advertisers' buying decisions. A technically allowed floating player may still perform poorly, annoy readers or fail other policy conditions. Publishers should test viewability, interaction, page performance, consent, bounce rate and revenue rather than treating a relaxed rule as an instruction to add intrusive autoplay.

What publishers should review now

Audit the ad unit's actual placement classification and SDK. For an existing player rejected only because it did not start in the article or was placed outside the body, compare the revised policy with the rejection reason before changing the implementation or requesting a review. Preserve muting, visible dismiss controls and accurate declarations. Document the October 22 policy change for ad-operations teams and avoid applying it to unrelated display formats.

What to watch next

  • Google's enforcement guidance or policy-review outcomes for newly permitted floating accompanying video.
  • Whether Ad Manager and AdMob implementation guidance clarifies edge cases under the shared video-inventory restrictions.
  • Publisher A/B tests on viewability, engagement, monetisation and user-experience trade-offs.
  • Any future restrictions on sticky video or autoplay placement.

Still unclear

  • Google has not provided an estimate of publisher revenue impact.
  • The change does not override other Google Publisher Policies or ad-network rules.
  • Implementation eligibility may depend on placement declarations, SDK, consent and account-specific restrictions.
  • Not every sticky or floating ad placement is automatically classified as Accompanying Content.

Sources

Direct reading behind this dossier.

3 sources
Video inventory restrictions
Google Publisher Policies Help primary current policy

Current definitions, placement and SDK requirements, autoplay visibility and sticky dismiss rule.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment