If search enquiries fell around the March update, you need to know what deserves attention before commissioning a rewrite. Google's March 2026 core update began on March 27 and completed on April 8, according to the official status record. ROI.LIVE uses those dates to anchor a review of affected pages, queries and business outcomes. Timing starts the investigation; it does not identify the cause.
The public record does not establish that the update assigned three new weights to information gain, topical authority and author expertise. A handful of client observations cannot reveal those internal settings. March is also a historical event; check the current update history before describing it as Google's latest update.
Establish what changed
Compare the same metric across periods. A fall in impressions and a rise in clicks can both occur if the query mix changes. Put impressions, clicks, click-through rate and average position in separate columns. Keep country, device, search type and date windows consistent.
Put your own release history beside the search data: migrations, redirects, template edits, removed content, tracking changes and outages. Otherwise the team may blame the update for a problem it can repair. Check indexing and manual-action information as separate questions. A decline during a core update does not prove a spam action.
A review sequence
Review the rollout against your own release history
Dates
Mark the March 27–April 8, 2026 rollout and site releases.
Segments
Compare matching pages, queries, devices and markets.
Causes
Check access, demand, competition and content quality.
Repairs
Make supported changes and retain a baseline.
Read the full explanation
Mark the rollout and your own release history.
Compare matching pages, queries, devices and markets.
Check access, demand, competition and content quality.
Make evidence-based improvements and retain a baseline.
Google's core-update guidance recommends assessing performance after a rollout has finished and avoiding impulsive changes based on a small movement. Use its current advice alongside the exact incident dates.
Separate demand loss from visibility loss
Different declines call for different checks
Less demand or different mix
Inspect queries and absolute changes, even if average positions move.
Whole section disappears
Investigate technical access before rewriting everything.
A narrow question changes
Compare the current results and available answers.
Cross-check
Inspect gains as well as losses, and branded versus non-branded queries.
Read the full explanation
A seasonal business may receive fewer searches even when its pages retain similar positions. A change in which queries show the site can also move average position without a like-for-like ranking decline. Review the queries responsible for the largest absolute changes, not only the percentage headline.
Compare branded and non-branded searches. Inspect pages that gained as well as those that lost. If a whole section disappeared, investigate technical access before rewriting every article. If a narrow question changed, compare the current results and what users can now find there.
Review quality without reverse-engineering a patent
Read the affected pages as someone deciding whether to buy from you. Check whether the answers are correct, current and supported, and try the tools and links. Note where you would still have to explain scope or answer a missing question on a call. The content audit worksheet turns those gaps, along with repeated content and factual errors, into specific repairs.
A Google patent can inform technical discussion, but it does not prove deployment or weighting in this update. The information gain definition explains that distinction. Avoid replacing one unverified algorithm theory with another.
Plan the repair and the measurement together
Save the old page and record each change so the next review has something to compare. Where practical, sequence independent repairs to make their effects easier to inspect. A broken canonical or false price deserves correction even if it never explains the decline. You can fix a known problem without claiming to have solved the entire traffic loss.
Keep a baseline from before the intervention. Compare equivalent later periods, noting demand, seasonality and other releases. A recovery may take time and may not occur. Do not promise the next update will restore a particular position.
What to report to the owner
You should be able to leave the review knowing which pages and queries changed, the size of the change and what the team has repaired. Ask for confirmed technical problems to be separated from hypotheses. Connect the search change to qualified enquiries or sales where tracking supports it, and keep incomplete attribution visible. That makes the next spending decision easier to discuss, even while questions about the cause remain.
The next useful action is to export a matched set of page and query data and pair it with the site's release log. That record is more valuable than a confident claim about an algorithm weight nobody outside Google can inspect.
Questions owners ask
When did the March 2026 core update run?
The official Google status record lists March 27, 2026 as the start and April 8, 2026 as the completion date.
Did Google confirm three new ranking weights?
The cited public incident record does not establish those weights. Client observations and patents do not reveal the deployed algorithm’s exact configuration.
Does a decline during the rollout prove a penalty?
No. Check technical access, demand, query mix, competing results and other changes. A core-update movement and a manual action are different questions.
Should every declining page be rewritten?
Inspect the cause and the reader need first. Fix confirmed errors, but do not delete useful content or make broad changes solely because a short-term metric moved.
Sources and method
External claims use the sources below. Worked examples and tools are labeled in the article; they are not customer results.
- Google: March 2026 rollout record: Confirmed rollout dates.
- Google: core-update review guidance: Post-rollout review and change assessment.
Substantively revised September 8, 2026. Definitions, calculations, sources and internal destinations were reviewed for this edition.
