How to investigate a search drop after a Google update

What does a Google core update mean for your website?

Core updates are broad changes to Google's search systems. They do not target a particular business, and a page that moves down is not necessarily a bad page. Other results, customer expectations and the information available on the web can change.

Use Google's core-update guidance to assess a suspected connection. Check the Search Status Dashboard for the actual update dates rather than treating every change in traffic as an algorithm problem. This guide does not assume that a particular update is currently running.

What should you compare before making changes?

For a suspected core-update effect, Google recommends waiting at least a full week after the rollout completes before analysing Search Console performance. Compare that period with a suitable period before the update, and keep the scope consistent.

• Pages and queries: identify which landing pages and relevant searches changed, rather than relying on the sitewide average alone.
• Search type: review Web, Images, Video or News separately where relevant to the business.
• Country and device: compare the same audience and device conditions.
• Business context: note seasonality, changed services, site releases or reporting changes that could affect the comparison.

A small position movement is different from a sustained large drop. Google's guidance discourages drastic changes to content that is already performing well. Record what changed and what remains stable before deciding how much work is justified.

Is the page missing from the index or receiving fewer clicks?

Inspect the intended URL in Search Console. An indexed page with fewer impressions or clicks needs a different investigation from a page Google cannot index. The indexed record and a live test answer different questions; a successful live test does not establish that the page is indexed.

Our website indexing and ranking guide explains that diagnosis. If Google has selected another canonical, check whether that choice is appropriate before removing redirects or rewriting the page. Expected duplicate and redirected URLs are not automatically defects.

Which website problems should you verify?

Access and page delivery

Check what the intended public URL returns: the correct content, an error, a login screen or a redirect. Review crawl restrictions, noindex instructions, canonical URLs and internal discovery where they are relevant. A technical change should resolve an observed barrier, not simply make an exclusion count smaller.

Use the URL Inspection documentation to understand what the indexed and live results establish. Keep the URL, inspection date, finding and proposed correction in the review record.

The answer the customer needs

Read the affected page as the prospective customer. Does it explain the actual service, coverage, important constraints, relevant evidence and the next step? A broad company introduction may not answer a service-specific question. Another page may provide more useful information without your page being technically broken.

Use Google's people-first content questions to evaluate originality, accuracy and usefulness. Strengthen the missing substance using information your business can verify. Repeating a phrase, changing a date or adding generic paragraphs is not a substitute for a better answer.

Internal links and page roles

Help visitors reach a relevant service, comparison or project example from the page they are reading. Links should explain why the destination is useful. Review pages with similar purposes so each makes a distinct contribution rather than producing a new page for every wording of a search.

Preserve established URLs and useful content unless the evidence supports a change. If addresses must change, plan the equivalent destinations and links rather than redirecting everything to the homepage.

Loading and mobile usability

Fix problems that prevent people from reading or completing the intended action. Review image sizes, unnecessary scripts, stability and readable controls using the devices your customers use. These checks also matter when search performance is unchanged.

Google's page-experience guidance says Core Web Vitals are used by ranking systems, but good scores do not guarantee top rankings. Do not treat a performance score as proof of the cause of a search drop, or promise a ranking recovery from speed work alone.

Links from other websites

Review evidence of a link-policy problem rather than assuming every unfamiliar link is harmful. A manual-action notice or records of a link scheme requires a different response from an ordinary backlink report. Google's disavow guidance says most sites do not need that tool and identifies specific conditions for its use.

Do not make broad link-removal or disavow changes just because an SEO tool assigns a low score. Record the actual concern and follow the applicable guidance before selecting a remedy.

How should search intent shape the review?

The page should help with the decision expressed by the query. A customer comparing providers may need scope, relevant work and an enquiry path. Someone learning about a problem may need an explanation and a clear route to the service when appropriate.

Compare the query with the intended page and the information it provides. Check whether several pages repeat the same answer or whether an important question is missing. Use a specific example from your service and approved evidence instead of expanding copy solely to reach a word count.

What can structured data and AI-search work do?

Appropriate structured data can describe content for supported search features. It should match what people can see on the page, and a feature's requirements still apply. Markup does not guarantee crawling, indexing, rankings or a rich result.

Google's AI-feature guidance says there are no additional technical requirements or special schema needed for AI Overviews or AI Mode. Pages must be indexed and eligible for a search snippet to appear as supporting links; eligibility does not guarantee selection.

Keep those limits clear when comparing an SEO proposal. Business information, useful content and discoverable pages matter, but an agency cannot control a Google or AI recommendation.

What should the review leave you with?

A useful review connects a finding with a specific decision. Record the affected page and query, comparison dates, indexed status, verified problem, proposed change, owner and recheck point. Also identify what should remain intact.

AMÁRQUEZ's SEO service describes technical, content and local search work that can be agreed. If suitable visitors arrive but requests do not progress, investigate the website enquiry journey as a separate business problem. A traffic increase alone does not establish more received or qualified enquiries.

Bring that record when you contact our team. The scope should follow the problem found, with realistic responsibilities and reporting rather than a promise to protect every ranking.

Frequently asked questions

Can we recover rankings after an update?

Meaningful improvements may help, but a recovery or return to a previous position is not guaranteed. Google continually reassesses results. Focus on changes that improve the page for its intended audience and review the evidence over time.

Is E-E-A-T a score we should optimise?

Google describes experience, expertise, authoritativeness and trustworthiness as aspects of helpful content. Its guidance says E-E-A-T itself is not a specific ranking factor. Publish accurate authorship, relevant experience and dependable information instead of claiming a numerical E-E-A-T score.

Should we fix technical SEO or rewrite the content first?

Prioritise a verified access or indexing barrier when the intended page cannot be found or processed. For an accessible, indexed page, examine the customer question, evidence and performance context. Neither a universal technical checklist nor a blanket rewrite identifies the right fix for every page.

How long will a change take to affect search?

There is no fixed recovery timetable. Google's core-update guidance says effects can take days or several months, with some broader changes requiring more time to be recognised. Repeated edits and indexing requests do not create a guaranteed result date. Keep the change record and compare suitable periods.