GitHubDownload ZIP

Search digestMarch 2026

Google ran a global spam update, began a core rollout and clarified how crawl bytes constrain rendering.

Issue 43 min read3 primary sources

March contained two distinct ranking rollouts and a crawl-implementation explanation. Keep their dates and scopes separate: a completed global spam update is not the same event as a core rollout that continued into April.

Do not combine all March movement into one diagnosis. Review pages and queries against the specific rollout window, then eliminate indexing, technical and demand changes.

Product change

A global spam update completed

Google released the March 2026 spam update on March 24 at 12:18 Pacific. It applied globally and to all languages, and the status dashboard marked it complete on March 25. A spam rollout is a policy-enforcement event: the corrective action is to remove violating behaviour, not to chase a generic content tweak. Primary source.

Product change

The March core update began

Google released the March 2026 core update on March 27 and said rollout could take up to two weeks. It was still underway at the end of March and finished on April 8. See Google’s rollout record.

24–25 MarSpam update

Released globally and completed the next day.

all languages
27 MarCore update

Released; completion belongs to the April record.

up to 2 weeks

Action

Googlebot explained the byte budget

Google’s March 31 crawler explanation says Googlebot fetches up to 2 MB per individual URL, excluding PDFs; it advises keeping critical metadata, links, canonicals and structured data early in the HTML. Rendering cannot execute bytes the crawler did not fetch. See the primary source.

CheckWhy
HTML response size and orderingCritical discovery and canonical signals should not sit beyond the fetched portion.
External JavaScript and CSSEach resource is fetched separately and has its own constraints.
Server logs and response healthCrawlers can back off when a server struggles to serve bytes.
Conceptual diagram of the implementation choices described in this issue.

Action

What to check on your own site

  • Map observed changes to the correct update and completion window.
  • Audit policy-sensitive templates, redirects and programmatic pages for spam risks.
  • Inspect raw HTML size and put essential metadata, canonical links and structured data early.

Sources