DNS TTL settings can tank your traffic after a host move
The office smells like burnt coffee and dry air-conditioning, the cursor blinks on line forty-three of your migration checklist, and somewhere in a data centre three states away your site is half-live on two servers at once.
DNS TTL settings can tank your traffic during a WordPress host migration
Google crawls your old IP for days after you switch hosts if you ignore time-to-live rules.
Most operators treat DNS propagation as a black box: update the A record, wait twenty-four hours, hope for the best. But time-to-live (TTL) values control how long ISPs and search engines cache your old IP address—and the default setting on most DNS providers is 3,600 seconds (one hour). That’s fine for normal operations. It’s disastrous during a migration.
When you switch WordPress hosts without lowering your TTL in advance, Google’s crawlers can spend three to five days hitting your old server intermittently, returning 404s or timeout errors. Those errors signal instability. If enough crawl attempts fail, Google throttles your crawl budget and drops pages from the index. Your traffic falls before your new host is even fully online. The fix is simple but non-obvious: lower your TTL to 300 seconds (five minutes) at least forty-eight hours before you point your domain at the new host. After the migration completes and traffic stabilises, raise it back to 3,600 or higher to reduce query load.
The mechanic is straightforward once you see it, but most migration checklists bury DNS as step twelve, after database exports and plugin audits. It should be step one. Timing matters more than tooling here—no amount of caching or CDN config will save you if half your inbound search traffic is still resolving to a decomissioned server.
TACTIC
Full-page caching breaks when logged-in users hit your site
Most WordPress caching plugins serve a single static HTML snapshot to every visitor. That’s fast—until someone logs in. Suddenly they see stale content, cached admin bars, or worse: someone else’s session data. WP Rocket, W3 Total Cache, and LiteSpeed all handle logged-in users differently, and the default settings prioritise speed over segmentation. If you run membership content, gated archives, or even just let a few editors access wp-admin while readers browse, you need separate cache rules for authenticated sessions. Otherwise you’re trading performance for broken UX—or leaking private data into public cache.
WORTH READING
Newsletter ad networks pay net-60—plan your cash flow accordingly
Most newsletter ad networks—Swapstack, Paved, Sparkloop Ads—operate on net-60 payment terms. That means you run the ad today, send the report next week, and get paid two months after the campaign closes. For solo operators running on tight margins, that delay turns a $2,000 sponsorship into a cash flow problem: you’ve already paid your ESP bill, your hosting bill, and possibly a freelance writer before the revenue arrives. If you’re booking multiple sponsors per month, staggered payment schedules compound. The math isn’t hidden, but it’s rarely mentioned in pitch decks. Know the terms before you commit inventory.
FROM THE ARCHIVE
Newsletter platform pricing jumps in blocks, not per subscriber
ConvertKit charges $66/month for up to 3,000 subscribers and $100/month for 3,001 to 5,000. That’s a thirty-four dollar jump for a single new subscriber. Most operators think ESP pricing scales smoothly—it doesn’t. Beehiiv, MailerLite, and Kit all use tier-based billing, and crossing a threshold can double your monthly cost overnight. If you’re sitting at 2,980 subscribers and running a referral campaign, you might want to pause sign-ups until the start of the next billing cycle. The pricing pages show the tiers, but the implications only become obvious when you’re three subscribers away from a step-change in your overhead.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.