Search traffic emergency

Website Traffic Dropped Overnight: The First Hour, Before Anyone Touches the Site

The chart was fine at dinner and flat at breakfast. The urge now is to change something, anything, before lunch. Resist it for one hour. An overnight cliff usually has a dull, findable cause, and most of the expensive damage happens while people guess.

November 20, 2026 · 11 min read

acmepoolsupply.com · Search Console, Performance
Clicks from Google, day by day, one fictional store
The theme update went live with noindex still on
Clicks from Google Search, daily-77%
Nov 3Tuesday theme update ships the staging noindexNov 14
Illustrative: a sample overnight drop on a fictional pool supply store, caused by one leftover tag

The short answer

When website traffic drops overnight, spend the first hour ruling causes out in a fixed order: confirm the drop is real by comparing analytics with Search Console, confirm the site loads and returns a normal response, check for a noindex tag or a robots.txt block, then open the Security Issues and Manual Actions reports and Google's Search Status Dashboard. Change nothing until one of them explains the date.

On this page
  1. A cliff is a clue and a slope is a project
  2. Sixty minutes, six checks, one notebook
  3. Six suspects and the evidence that convicts each one
  4. Panic moves that turn a one-line fix into a month
  5. When Google holds the stopwatch, not you
  6. Call us today, or keep your money: an honest sorting
  7. Three cheap alarms so the next drop wakes you, not your customers

A cliff is a clue and a slope is a project

Look at the shape before you look at anything else. A line that slides for six months is a strategy problem: stale pages, sharper competitors, a site that got slower one plugin at a time. Our website traffic dropped guide walks through those causes in full, including seasonality and AI answers taking clicks. This page is for the other shape, the one that looks like a step. Monday was normal. Tuesday is half.

A one-night step is usually mechanical. Something stopped counting, stopped answering, stopped letting Google in, or got flagged. Google's own guide, Debugging drops in Google Search traffic, sorts causes into algorithmic updates, technical issues, security issues, spam issues, seasonality and site moves. Most of those six can flip in a single night. Seasonality cannot. That narrows the field before you have opened a single report.

There is a timing wrinkle worth knowing this month. When we checked on November 17, 2026, Google's Search Status Dashboard listed the November 2026 core update as an active ranking incident that began on November 10. An update in progress can move rankings any day of its run, so a drop this week has a plausible suspect that is nobody's fault. It is still the last suspect you should accept, not the first, because the mechanical causes are cheaper to find and faster to fix.

Sixty minutes, six checks, one notebook

Open a blank note and write the time. Every check below either clears a suspect or convicts one, and the note becomes the brief for whoever fixes it, you or us. Do them in this order. The early checks are fast and catch the commonest causes.

  1. 1

    Minute 0: freeze the site and list the last 72 hours

    Ask everyone with a login to stop publishing, updating and tinkering. Then list every change since the drop began: a deploy, a plugin or theme update, a new consent banner, a hosting move, a DNS edit, a redesign. The date of the drop is usually the date of one of these.

  2. 2

    Minutes 5 to 15: is the traffic gone, or the counter

    Google says the best place to start is the main chart in the Search Console Performance report. Search Console's numbers come from Google, not from a tag on your pages. If clicks there held steady while analytics fell to nearly zero, your visitors are still arriving and the tag broke. Calls and orders tell the same story.

  3. 3

    Minutes 15 to 25: is the site answering at all

    Load the home page and a top product or service page on your phone, on cellular, not office Wi-Fi. Run the free is my site down check. A site that throws 500 or 503 errors overnight loses visitors first and crawl attention second.

  4. 4

    Minutes 25 to 35: did the site tell Google to go away

    View the page source of your home page and search it for noindex. Open yoursite.com/robots.txt and look for a Disallow line covering the whole site. Then open the Page indexing and Crawl stats reports in Search Console, both of which Google's guide points to.

  5. 5

    Minutes 35 to 45: the two reports nobody opens until today

    In Search Console, open Security Issues and Manual Actions. Google says a manual action means a human reviewer found pages that break its spam policies, and that you will see a count of them at the top of the report. An empty report clears both suspects in a minute.

  6. 6

    Minutes 45 to 60: check Google's side of the street

    Open the Search Status Dashboard and match any listed ranking update against your date. Search your five most valuable services in a private window and note who now sits where you sat. Then stop and read your notebook before deciding anything.

Two glowing cyan lines on a deep blue and violet grid, an upper level and a lower one, joined by a short vertical step down
A drop shaped like a step usually has a mechanical cause that one hour of checks can find.

Six suspects and the evidence that convicts each one

Most overnight drops resolve into one of six causes. Each leaves a different fingerprint, and the fingerprint decides who should fix it and how fast. Read across the row that matches what you saw.

Reading an overnight traffic drop by its fingerprint
SuspectWhat you seeWhere to confirmFirst move
Broken trackingAnalytics near zero, Search Console clicks steady, phones still ringingPage source, analytics real-time view, consent banner settingsRestore the tag; no SEO work needed
Outage or server errorsPages slow or failing, errors in Crawl statsIs my site down check, hosting status, server logsGet the site answering with normal responses
A stray noindexPages vanishing from results, often after a launch or updatePage source, Page indexing reportRemove the tag, then watch the Page indexing report
robots.txt blockCrawl activity collapsing, pages listed as blockedyoursite.com/robots.txt, Crawl statsRestore the last good file
Hacked siteWarnings in results, odd pages indexed, spam in search snippetsSecurity Issues reportContain the site before anything else
Manual action or updateClean technical checks, a notice or a dated update that matchesManual Actions report, Search Status DashboardFix every affected page, or wait out the rollout

The first four cost you traffic every hour they stay, and the fix is usually small once found. A noindex tag left over from a staging copy is a single line. A robots.txt file that says Disallow: / is two. Our pages on robots.txt blocking Google and a site Google deindexed cover the repair step by step, and a site not indexed by Google covers the slower cousin.

Server errors deserve a word of their own. Google's page on network and server errors says 5xx and 429 errors make its crawlers slow down, in proportion to how many URLs fail, and that already indexed URLs are kept but eventually dropped if the errors persist. Google gives no number of days. Every hour of a broken server is an hour you are asking for that outcome. If the site is down rather than ranking lower, go straight to website down: what to do first.

Panic moves that turn a one-line fix into a month

By ten in the morning, someone will have a plan. Possibly an agency will have emailed to say it noticed your traffic and has a recovery package ready, which is impressive, since you only noticed yourself at eight. Here are the moves that feel decisive and usually make things worse.

  • Changing URLs or restructuring the site. Google's guide warns that changing the URLs of existing pages can cause ranking fluctuations. You would be adding a second problem on top of the first.
  • Taking the site offline to fix it in private. Google's page on how to reduce the crawl rate says not to return error codes like 503 for longer than 1 to 2 days, as of November 2026, because a URL that keeps failing for multiple days may be dropped from the index.
  • Restoring last month's backup over today's site. It may erase the evidence of what changed, and the content added since. Save a full copy of the current site first, always.
  • Rewriting every page by Friday. If the cause is a tag, a file or a server, new copy fixes nothing and muddies the before and after.
  • Asking Google for a review before every page is fixed. Google says fixing some pages does not earn a partial return, and that resubmitting before a site is clean can lengthen the next review.
  • Buying links or a recovery guarantee. Nobody can guarantee a recovery, Google included, and bought links are a manual action waiting to happen.
A traffic chart tells you when something happened. It never tells you why.

If the drop lines up with a deploy on a Next.js or React site, the fastest safe move is often a rollback to the build that worked yesterday, covered in Next.js site down after a deploy. If it lines up with a WordPress update, the same logic applies to the plugin or theme that changed. Undo the change, confirm the traffic path, then find the cause on a copy.

When Google holds the stopwatch, not you

Some causes end the emergency at diagnosis, because the next step runs on Google's calendar. A manual action requires fixing every affected page, then selecting Request Review in the report. Google's manual actions help page says most reconsideration reviews can take several days or weeks, as of November 2026, and link-related requests may take longer. A hacked site goes through the Security Issues review, which Google's Security Issues help page says can take from a few days to a few weeks, also as of November 2026.

A core update is slower still. Google's debugging guide says that after a large drop, it may take months for its systems to decide a site is producing helpful content over the long term, and it says plainly that there is no guarantee changes to your site will produce a noticeable result. That is not an emergency. It is a project, and it deserves calm work on the pages that lost, not a weekend of rewriting. Our SEO visibility recovery service is built for that slower job.

Call us today, or keep your money: an honest sorting

We respond the same business day, during the hours listed on our contact page. That covers diagnosis and the technical repair. It does not cover a promise about when rankings return, because no one controls that. Here is how we would sort your situation if you called.

Worth an emergency call today

  • The site throws errors, loads blank or times out
  • A noindex or robots.txt block went live and you cannot find or remove it
  • Search Console lists a security issue, or strange pages appear in results
  • A deploy or update shipped the night of the drop and nobody can undo it
  • Orders and calls fell along with the traffic

Not an emergency, so do not pay for one

  • Search Console clicks are steady and only analytics fell: fix the tag
  • Every technical check is clean and an update is rolling out
  • The drop matches the same week last year
  • Traffic fell but leads did not
  • You want a content strategy, which is a monthly program, not a rescue

For WordPress, the technical fixes are fixed-price Fix it now repairs, paid online: site down or white screen $249, malware cleanup $349, WordPress error fix $149. We start within one business day of payment, with a full refund if we can't fix it. The white screen repair page carries the checkout, and WordPress repair covers the rest. Every other platform is from $575, depending on complexity, with a written estimate before any work starts. The emergency website repair page lists what we need from you, and emergency pricing explains what moves the number.

Three cheap alarms so the next drop wakes you, not your customers

Most owners learn about an overnight drop days later, from a quiet phone. An alarm costs less than that week. Google Cloud's uptime check documentation, one vendor's example, describes checks that pass only when the page contains content you require, plus alerts before a certificate expires. A check that looks for your phone number in the page catches a blank template that still returns a normal response.

  • An uptime check that requires real content on your home page and one money page, with alerts to two people.
  • A weekly two-minute look at the Page indexing report, so a noindex is caught in days, not months.
  • A written rule that no deploy, plugin update or DNS change ships on a Friday afternoon without someone checking the site after.

If you would rather someone else watched, our hosting and maintenance plans start at $55 a month. The free website health check is a quick outside look in the meantime. DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. You can see our work, browse the rest of the emergency repair section, or call (210) 346-0848. If the drop came with a security warning, read hacked website: the first hour before you do anything else.

Questions owners ask in an emergency

A drop to nearly zero in one night is usually mechanical: the analytics tag broke, the site went down, a noindex tag or robots.txt rule told Google to stay away, or the site was flagged for a security issue. Compare analytics with Search Console first. If Search Console clicks held, only the counting broke.

It could. Google's Search Status Dashboard listed the November 2026 core update as an active ranking incident that began November 10, 2026. But rule out tracking, outages, noindex, robots.txt, security issues and manual actions first. Those are cheaper to find and fix, and an update is only a fair conclusion when every technical check comes back clean.

Google gives no recovery date. You fix every affected page, request a review, and Google says most reconsideration reviews take several days or weeks, as of November 2026, with link-related requests sometimes longer. Fixing only some pages does not earn a partial return, so finish the job before you ask.

Not as a first move. Save a full copy of the current site, then find what changed. A restore can erase the evidence and any content added since the backup. If the cause was a specific update or deploy, rolling back that one change is usually safer than replacing the whole site.

Usually not. If leads, orders and calls held steady while analytics fell, the tag or a consent setting probably broke, and visitors are still arriving. That needs fixing soon, because decisions made on broken numbers go wrong, but it does not need an emergency rate.

For WordPress, technical repairs are fixed-price Fix it now jobs: site down $249, malware cleanup $349, error fix $149, with a full refund if we can't fix it. Other platforms are from $575, depending on complexity, with a written estimate before work starts. We respond the same business day.

Keep reading

Free · No obligation

Find out why the traffic fell

Tell us the date of the drop and what changed that week. We reply the same business day with what we would check first and, if it is technical, a fixed price or a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote