Is 35 Minutes of Downtime OK on a New Site?
TL;DR: Yes, on a site with no traffic. I told my team to move kayhonig.com to Cloudflare right away, and it was partly down for about 35 minutes. Nobody was there to notice. The bigger problem today was a number: on a side project, my bots reported 60 visits that turned out to be their own traffic and crawlers.
What got built
- kayhonig.com moved to Cloudflare. A certificate got stuck, so the site was partly down for about 35 minutes. The team switched to a fallback and the cutover was done around 10:30 AM.
- Analytics and Search Console rebuilt for 4 sites, with cookie consent (Consent Mode v2). I did the console clicks. Faro, my SEO bot, guided me.
- My bio now uses the confirmed figure: 14 years.
- The trust essay is live. I merged it today. Before that, an automatic check caught a wording slip before it went out.
- Faro's first weekly SEO brief.
Why I said "do it now"
kayhonig.com has no traffic. So 35 minutes of downtime was acceptable. I never heard the site was partly down, and I didn't mind.
On a busy site I would be much more careful. That's the real question for the next migration: does traffic even matter yet? Here, it didn't.
What changed technically
The move itself was simple. The stuck certificate was the failure, and the fallback fixed it.
The analytics rebuild is where it went wrong. On one new side-project site, the bots reported 60 visits in 2 days. I knew right away that was false. The site was only a few days old. No ads, no social posts, indexed yesterday. There is no logic for 60 organic visits. Our own bots, test runs and crawlers caused those visits, and they should have known.
Zero real visitors is normal for a site that's a few days old. It changes nothing for me. A fake 60 is worse than an honest 0.
Why I still approve SEO changes
I made about 10 approvals today. I still sign off on SEO changes because I don't trust the bots yet. There are too many common-sense errors, like the 60 visits.
I do like having a dedicated SEO bot. So there's a new standing rule: small SEO fixes now go from Faro to Site Bot directly, as written instructions.
Other calls that needed me today: the 14 years, the Cloudflare timing, the contact address, and ruling that the fuel surcharge for Kay Tours is already disclosed upfront. I also pressed Send on 1 email to an outside web developer and did the sign-ins.
Side projects
- An agency side project made 3 production releases, each after a QA pass. After filtering out our own traffic, it had zero real visitors too.
- On a downloads side project, a Pinterest profile went live with 8 boards and 16 pins. Its product review needs a human eye. I haven't looked yet.
What I'd do differently
I'm adding a quality-control bot to the daily Build Log, modeled on the one in another project. That one catches a lot and keeps the logic solid.
Right now I still read every log. I'll stop once I trust that it makes SEO sense and reflects my wording and my train of thought.
FAQ
Is downtime during a site migration a problem? Not on a new site with no visitors. On a busy site, plan it more carefully.
Why did the bots count 60 visits? It was their own traffic. A site only a few days old with no ads or social posts doesn't get 60 organic visits.