Author: shivamcrushpressai

Your traffic graph dropped during the May core update, and now you need to know whether to rewrite pages, change your SEO strategy, or simply wait. Start by resisting the urge to make sitewide edits. A core update can expose weak content, but it can also coincide with changes in demand, search-result layouts, competitors, or tracking.

The useful response is a page-level diagnosis. You want to identify where visibility changed, determine what those pages now fail to deliver, and improve them without destroying content that still works.

Anchor your diagnosis to the actual rollout

The official rollout ran from May 21 through June 2. Noticeable ranking movement appeared by May 23 and continued into the following week. This was the second core update of 2026, so earlier changes in your reporting may belong to a different event.

Build clean comparison periods

In Google Search Console, compare May 7-20 with June 3-16. These are equal 14-day periods immediately before and after the rollout, without mixing rollout days into either side. If your business has strong weekly or seasonal patterns, compare each period with the equivalent days from a normal prior period as a second check.

Export clicks, impressions, click-through rate, and average position by query and page. A chart of total clicks is not enough. It can tell you that performance changed, but not why.

Separate ranking losses from other traffic losses

If positions declined across several important queries for the same pages, investigate relevance, usefulness, and competition. If impressions declined while positions remained broadly stable, check whether search demand or the set of queries triggering those pages changed. If positions and impressions held steady but click-through rate fell, inspect the live results for new answer features, stronger titles, or a changed search intent.

Also rule out unrelated technical problems. Check whether affected URLs are indexed, canonicalized as intended, crawlable, and returning the correct status code. Review analytics changes, security incidents, migrations, and major template releases. A core-update diagnosis cannot fix a broken canonical or missing tracking tag.

Find the losses that actually need intervention

Sitewide averages hide the decisions you need to make. Group affected URLs by topic, search intent, template, author, and content type. Then calculate the change for each group. A fall concentrated in old comparison pages calls for a different response than a decline across every page using the same template.

Start with URLs that combine three traits: a material visibility loss, meaningful business value, and a problem you can clearly describe. Do not prioritize a page merely because its percentage decline looks dramatic. A page that fell from ten impressions to two is usually less urgent than one that lost a large share of qualified visits.

Inspect the queries that disappeared

For each priority URL, compare its pre-update and later query sets. Ask whether it lost its main query, a cluster of secondary questions, or visibility for terms that never matched its real purpose. Losing poorly matched impressions may not require a repair. Losing the queries that express the page’s central promise does.

Search those important queries manually and examine the pages now appearing above yours. Look for differences in intent, scope, specificity, first-hand evidence, freshness, and format. The goal is not to copy competitors. It is to understand what searchers can accomplish with the current results that they cannot accomplish with yours.

Look for patterns across winners and losers

Your unaffected and improving pages are useful controls. Compare them with declining pages from the same site. If both groups share the same design, author box, and schema, those elements are less likely to explain the difference. If losses cluster around thin location pages, outdated tutorials, or articles built from the same generic outline, you have a stronger hypothesis to test.

Audit for satisfaction, not an imaginary update factor

The update was intended to favor relevant and satisfying content. That direction is more useful than hunting for a new word-count target, schema type, or keyword-density rule. Google has not provided a single prescribed fix for pages that lost visibility.

Test whether the page fulfills its promise

Read the title, opening, and major headings without relying on your memory of the page. They should define one clear task or question. Then check whether a reader can complete that task without returning to search for missing steps, definitions, evidence, or limitations.

Remove introductions that delay the answer. Put the central answer or decision criteria near the relevant heading, then support it with explanation. If the query requires a procedure, make the sequence explicit. If it requires a choice, explain who each option suits and what changes the decision.

Add value that another generic page cannot reproduce

A rewrite that merely changes wording preserves the original weakness. Add the missing substance: a worked example, a transparent method, a limitation, an expert interpretation, a screenshot that proves a step, or an explanation of what happens when the standard advice fails. Keep only material that helps the reader act or decide.

For factual or high-consequence claims, make the basis visible. Identify the responsible organization or expert where that identity matters. Link to supporting material you actually used. Show when the page was reviewed, and update that date only after a meaningful review. An unexplained assertion does not become trustworthy because it sounds confident.

Check ownership, duplication, and internal competition

Decide which URL should own each core intent. Several pages targeting the same question can divide internal links and leave each version incomplete. Consolidate genuine duplicates when one stronger destination can serve the reader. Keep separate pages when the intents, audiences, or required answers are materially different.

Update internal links so descriptive anchor text points to the intended owner. Make sure related pages support one another instead of repeating the same opening-level information. Do not delete a large group of URLs solely because traffic fell during the rollout; first determine whether each page has a distinct, supportable purpose.

Improve search and AI visibility without conflating them

A Google core update and visibility inside frontier language models are not the same measurement system. A decline in Google rankings does not prove that ChatGPT, Claude, or another answer engine stopped citing you for the same reason. Track conventional search performance and AI citations separately, even when the same content improvements may benefit both.

For answer-oriented visibility, make important facts easy to locate and interpret. Use descriptive headings, answer the stated question directly, name entities consistently, and keep qualifications beside the claim they modify. Tables should represent real comparisons, while lists should represent genuine steps or criteria. Formatting cannot compensate for an unsupported answer, but it can make a strong answer easier to extract correctly.

Apply JSON-LD only when it accurately describes visible content and the page’s real entity relationships. Schema is packaging, not evidence. Adding more markup will not repair stale facts, unclear authorship, duplicated intent, or an answer that misses the query.

Measure AI visibility with a stable set of prompts tied to your customers’ questions. Record whether your brand is mentioned, cited, represented accurately, or omitted. Keep that record beside, but not merged into, your Search Console analysis. This prevents a gain in one channel from concealing a loss in another.

Make controlled changes and preserve what you learn

Create a change log for every priority URL. Record the date, the affected query or intent, your diagnosis, and the substantive edits. That turns recovery work into a testable process. Without a log, several teams can modify the same page and leave you unable to connect later movement with a plausible cause.

Work in related batches rather than changing the entire site at once. Start with a small group that shares a documented weakness. Recheck query-level performance after those pages have accumulated enough impressions for a meaningful comparison. Keep the changes if the intended queries recover without harming conversions or accuracy; revise the hypothesis if they do not.

Do not judge success only by restored clicks. A revised page may attract fewer but better-matched visits. Review conversions, qualified leads, engaged visits, and the queries now associated with the page. The objective is durable visibility for the right need, not the recreation of every impression that existed before May 21.

Key takeaways

• Use May 21 through June 2 as the rollout window, and keep those dates out of your before-and-after comparison periods.
• Diagnose changes by page and query; total traffic alone cannot distinguish ranking, demand, click-through, and technical problems.
• Prioritize valuable pages with a clear loss and a specific weakness instead of rewriting the whole site.
• Improve intent match, distinct value, evidence, ownership, and internal linking before reaching for more schema.
• Measure Google rankings and AI-answer visibility separately, with a written change log for both.

Your next move is simple: export the two 14-day comparison periods, select the five affected URLs with the greatest business value, and write one testable diagnosis for each. Make only the changes that diagnosis supports. That gives you a recovery plan you can measure instead of a collection of update myths.

References

• CrushPress.AI – Google’s May 2026 Core Update Completes with Major Impact