Why has my Google traffic dropped or a page disappeared?

First check what actually declined

Fewer quote requests in one week do not necessarily mean Google has lowered your website's ranking. Demand may have fallen, analytics may have changed, or there may be a technical obstacle. You may also have just as many search impressions but fewer clicks or enquiries. Break your investigation into three questions: what fell, where did it fall and when did it begin?

Treat Google Ads clicks and calls from Google Business Profile separately too. They matter commercially, but are not the same measurement as Search Console's web search report. If Search Console is stable while GA4 drops, also check analytics tags, cookie consent, channel settings and website changes.

Use our Search Console beginners' guide if you are unfamiliar with its reports. Never share Google account passwords: ownership and access can be managed separately.

The three-filter investigation: what, where and when?

1. What fell? Enable clicks and impressions in the Performance report; look at CTR and average position as well. If only clicks fell while impressions remained stable, you have not established that the page was deindexed.
2. Where did it fall? Check the Pages and Queries tabs, then filter by country, device and search type. A drop on one service page calls for a different response from almost every page losing impressions at once.
3. When did it start? Compare two complete periods of equal length, and for seasonal businesses check the corresponding weeks in the previous year. Record website updates, URL changes, hosting errors, analytics changes and campaign adjustments.

Don't compare the latest partially processed day with a complete day. A weekend service may naturally have a different traffic pattern from weekdays. Search Console's longer date range (up to 16 months) can help reveal seasonality.

Ten common symptoms: what do they prove and what should you do next?

The following table is not an automatic diagnosis. It starts with observations, identifies missing evidence and suggests who should investigate.

The table scrolls horizontally on mobile. One observation can have several possible causes.

What if an important old service page disappeared?

A page Google can no longer access is different from an indexed page people search for less often or that ranks lower. First paste the full old URL into Search Console's URL Inspection tool. Then open it separately in your browser and inspect its live HTTP response. Search Console's previously processed data may differ from its current status.

Fictional example: the electrical-services page of a fictional company in Szolnok, “Mintavill Kft.”, was at /villanyszereles/. Following a redesign, the content lives at /szolgaltatasaink/villanyszereles/ but the old URL returns a 404. If the new page really is the old one's replacement, a server-side 301/308 redirect, updated direct internal links, a new canonical and sitemap update may be appropriate. If the old URL covered a discontinued service, the right decision is different.

If the page returns a 404, read our guide to handling 404 errors. If the URL is still indexed, investigate relevant searches, competing results and the page content instead.

Is it a website update, server issue or algorithm change?

Website and hosting changes

A new design is not necessarily the problem. Trouble can arise when important URLs change without redirects, an accidental noindex remains on pages, Googlebot is blocked, the main content fails to render or the server repeatedly returns 5xx errors. A change log helps: exact dates, who deployed what and which pages were affected.

Algorithm updates and seasonality

Google's search systems evolve; its official Search Status Dashboard can help identify when events occurred. But an update coinciding with a drop in a graph does not prove causation. If search interest changed, you can examine relative trends with Google Trends, although it doesn't show a business's complete search volume.

A genuine manual action

Search Console's Manual actions and Security issues reports can show genuine warnings. A traffic drop does not itself equal a manual Google penalty. The solution is to address the specific notice and underlying cause, not buy an automatic “penalty removal” service.

What should you avoid doing in a panic?

• Don't rewrite every title and page at once. You lose the ability to compare changes when the problem may be a server setting.
• Don't buy links promising “instant ranking recovery”. Neither restored positions nor search traffic can be guaranteed.
• Don't request indexing for every URL every day. Repeated requests won't fix missing content or a faulty redirect.
• Don't measure only by searching for your own business on Google. Results depend on location and device; compare consistent reports instead.
• Don't replace the whole website because of one graph. First establish a supported hypothesis and assign responsibility for fixing the problem.

A nine-field issue report for your developer or SEO specialist

You can copy this checklist into your own document. Share the facts and appropriate access needed for diagnosis, not your passwords.

1. Website: the exact domain and Search Console property examined.
2. Date: when you noticed the issue and which two complete periods you compared.
3. Search type: web search, images or another available type.
4. Metrics: clicks, impressions, CTR and average position in both periods.
5. Affected URLs and queries: preferably exported directly from the report.
6. Filters: country, mobile/desktop and other relevant breakdowns.
7. Technical checks: HTTP response, URL inspection, canonical and noindex, if known.
8. Change log: dates of development, CMS, hosting, domain, campaign or analytics-tag changes.
9. Business impact: reliably measured leads, quote requests and calls, if available.

For widespread issues, agree who owns measurement, who investigates server faults and who reviews search relevance. This leads to better decisions than a simple ranking list.

A practical order for your issue report: first copy the facts from your reports, then write your own theory separately. For example, “Impressions on /szolgaltatas/ fell over the last two complete weeks” is an observation; “last week's template change caused it” remains a hypothesis. When your developer makes a fix, record its date, which URLs changed and how you will measure the effect later.

Prioritise by business impact too. A broken quote-request page or a server error across the entire site is urgent. A small decline in clicks on one seasonal information article may warrant careful comparison first. That keeps development focused on the most important user problem, rather than the scariest graph.

Frequently asked questions about falling Google traffic

Sources and further reading

Related guides