Traffic dropped after client site migration?

Yeah, that smells like migration fallout more than “just Google being weird.” If GA looks fine but leads are down, I’d be looking at: – landing page indexation / canonical weirdness – redirect chains or a couple bad 301s – crawl rate dropping after the host move – robots / firewall / WAF blocking Googlebot or slowing it down – template changes that broke internal linking or nav depth I’ve seen the “GSC is all over the place” part a bunch after moves. Sometimes it’s just the usual lag, but the crawl delay thing is the part that makes me suspicious. If bot access got a little slower or inconsistent, Google can take its sweet time sorting it out. Also worth checking if the new host is serving slightly different headers, compression, TTFB, whatever. People love saying “same site, new host” like that means anything. It doesn’t. If it’s only been since the weekend, I wouldn’t panic yet, but I also wouldn’t assume it’s nothing.

Technically, that’s not really accurate. technically, yeah, that’s not “just Google being weird” in my experience. Host moves can absolutely screw with crawl for a bit, even when GA looks normal and everyone pretends nothing changed. I’d be checking server logs before anything else. If Googlebot’s getting slowed down or tripping over some dumb WAF/timeout issue, GSC will look like a mess for a few days.

From my experience, yeah, I’d lean migration fallout too. The “GA looks fine but leads are down” part is usually where the annoying stuff is hiding. I’d check logs first like Mason said, but also the boring crap people skip: – any noindex/canonical weirdness on the new host – redirects that are technically working but slower / chained – WAF / bot protection being a little too “helpful” – pages loading fine for humans but timing out or stalling for Googlebot Had one client move hosts and everything looked normal until we noticed the new server was just trashing crawl requests under load. Took a few days to settle, but yeah, leads dipped before anything obvious showed up in GSC. If it’s only been since the weekend I probably wouldn’t freak out yet, but I also wouldn’t write it off as “Google being weird” either. That phrase gets used way too much around here. That’s how I look at it.

Yeah, I wouldn’t call that “just Google being weird” either. If GA’s still showing sessions but leads dropped, that’s usually some mix of crawl weirdness, bot blocking, or a quiet conversion tracking issue nobody wants to look at. After a host move I’ve seen Googlebot get slowed down by WAF rules more times than I can count. I’d be checking server logs and response times before touching titles or content. The crawl delay part especially makes me think the new host is either a bit sluggish or throwing up some nonsense for bots.

From what I’ve seen, yeah, I’d be looking at the move itself before blaming Google’s latest mood swing. If leads dropped and crawl got weird right after the host change, that’s usually not “nothing.” It’s usually some dumb migration crap that only shows up once bots start poking around. Personally,

Yeah, I’d still suspect the move more than “Google being weird.” If crawl delay changed right after the host switch, that’s the bit I’d care about. Seen this plenty where GA looks basically normal, rankings don’t crater, but Googlebot’s getting slowed down or filtered and the lead flow gets weird a day or two later. I’d want to know if the new host is: – adding WAF / bot rules – doing any weird 403/429 stuff – slower TTFB for bot traffic – serving different headers/canonicals than before Could also just be tracking lying to you, which happens more than people admit. But yeah, weekend migration + crawl delay + leads down doesn’t sound like nothing.

Yeah, I’d still put money on the migration before blaming “a Google week.” GA looking fine while leads tank is usually the part that gets ignored, which is annoying as hell. I’ve seen host moves where bot traffic got slowed just enough to mess with crawling and the conversion path, but not enough to make the whole site look obviously broken. I’d be checking logs / WAF / 403s first, not titles or content. If Googlebot’s getting treated like some random scraper, that’s usually where the fun starts. That’s been my experience anyway.

Honestly, yeah, I’d still chase the migration first. “GA looks fine but leads are down” is exactly the sort of annoying half-broken situation I’ve seen after host moves. Usually it’s not some mystical Google thing, it’s something dumb like bot traffic getting slowed, blocked, or served different crap than before. I’d be looking at logs for 403/429s, WAF rules, weird response times, and whether Googlebot’s getting the same headers/canonicals as real users. Also check if the new host is doing any caching or security nonsense on the backend that wasn’t there before. If crawl delay changed right after the move, that’s not a coincidence in my experience. Google’s “fine” until it isn’t, but weekend migrations love to leave little landmines.

Yeah, I’d still be looking at the move first. That “GA looks fine but leads are down” thing is exactly the kind of annoying half-broken mess I’ve seen after migrations. Usually it’s not some grand Google mystery, it’s something dumb in logs/WAF/caching and everybody wastes a day staring at rankings. That’s how I look at it.

Realistically, yeah, I’d still blame the move first. That “looks fine in GA but leads tank” crap is exactly what I’ve seen when something’s quietly off with crawl access or the new host is doing some dumb WAF/caching nonsense. Check logs before you start blaming Google’s latest mood swing.

Sure. Yeah, I’d still bet on the migration being the culprit before I start blaming another “Google week.” Crawl delay right after a host move is usually not just vibes. That’s how I look at it.

From what I see, Personally, yeah, I’d stop trusting GA for a day or two and look at logs/crawl stats first. Host moves love to “look fine” while bot access, redirects, or caching are quietly messing with the real stuff.

Technically, yeah, I’d still put money on the move before “Google being weird” again. GA looking fine while leads crater is usually the annoying part, not the reassuring part. I’d be checking crawl/logs, redirects, and anything the new host is doing with bot traffic before I start chasing ghosts.

Yeah, I wouldn’t brush that off as “just Google” either. Seen this too many times where GA looks basically normal and then the actual leads fall off a cliff because bot access or redirects are getting weird after the move. I’d be looking at server logs before anything else, honestly.

Well, realistically, yeah, “GA looks fine” is basically the most useless sentence in migration season. I’ve seen that exact thing where the charts don’t look awful but leads just quietly die for a few days. Usually ends up being something dumb like redirects, bot filtering, cache weirdness, or the new host doing some “helpful” nonsense with crawl traffic. Google being weird is always the fallback excuse, sure, but I’d still blame the move first.

Yeah, I’d still treat the move as the main suspect here. “GA looks fine” after a migration has burned me before — usually means absolutely nothing useful. I’d check logs and redirects first, not GSC noise.

Personally, Yeah, I’d still put money on the migration before I’d blame “a Google week.” Seen too many of these where the dashboards look basically normal and the actual business side is getting kneecapped by some dumb redirect / bot access / cache thing. Crawl delay after a host move is not exactly comforting either. If it’s still messy after a couple days, then maybe start side-eyeing GSC harder. But right now this smells like move fallout, not mystery algo drama.

Kind of feels like in my opinion, yeah, I’d still blame the migration first. GSC getting weird is basically background noise at this point, but if leads dropped and crawl’s lagging, that’s not “just Google being Google” in my experience.