Search digestApril 2026
Google closed its March core rollout, made back-button hijacking an explicit spam-policy violation, and expanded preferred sources.
April closed one confirmed Google ranking rollout and added a concrete browser-navigation policy. The practical thread is simple: annotate the completed rollout, test real navigation behaviour, and keep generative-search features separate from ranking claims.
Calendar
Google completed the March core update
Google’s Search Status Dashboard marked the March 2026 core update complete on April 8. The update had been released on March 27, so April is the month in which the rollout closed, not a separate April ranking update. Treat the completion date as an analysis boundary: investigate material movement at query and landing-page level before changing content or templates.
Google listed the March 2026 core update as released.
rollout beganThe Search Status Dashboard marked the rollout complete.
analysis boundaryAction
Back button hijacking became an explicit spam-policy violation
On April 13 Google added back button hijacking to its malicious-practices spam policy. The practice interferes with browser history so a user cannot immediately return to the previous page, for example by inserting unsolicited pages or ads into the path. Google said the policy would be enforced from June 15, giving site owners time to remove or disable the responsible code, including code introduced by libraries or advertising platforms.
| Route to test | Expected result |
|---|---|
| Normal back navigation | Returns to the immediately previous page without a new unsolicited destination. |
| Third-party scripts | Do not add deceptive history entries or intercept the browser control. |
| After a fix | Retest on the affected browser and device, then record the deployed version. |
Product change
Preferred sources expanded to all Google Search languages
Google’s April documentation update said the preferred-sources feature became available in all languages where Google Search is available. This is a reader preference feature, not a publisher enrollment program or a visibility guarantee. It does not replace clear attribution, crawlability, or ordinary editorial links; a site owner’s practical task is to keep source pages identifiable and accessible rather than attempt to manufacture preference signals.
Action
What to check on your own site
- Annotate March 27–April 8 in ranking and Search Console reviews; separate query, landing-page, technical and demand changes before acting.
- Use the browser back control on key acquisition and conversion paths, including routes that load advertising or consent libraries.
- Inventory any script that calls history APIs or changes navigation after a back action; remove deceptive behaviour before the enforcement date.
- Keep source, author and page identity clear for readers; do not treat preferred sources as a new ranking signal.
Sources
- March 2026 core update — Google Search Status Dashboard (March 27, 2026)
- Introducing a new spam policy for back button hijacking — Google Search Central (April 13, 2026)
- Latest Google Search Documentation Updates — Google Search Central (April 30, 2026)