It Was a PHP Problem, Not a WordPress Problem, FFS!
So a week or so ago, a bug in PHP took websites offline all over the world. Within minutes, some LinkedIn wanker was telling you to bin your WordPress site. Sit down. We need to talk.
Hi, I'm Nikki Pilkington. My site is https://nikki-pilkington.com/ and in this episode of "SEO F**king What", I'm talking about the PHP mess, the WordPress panic, and why the people shouting loudest on social media are so often the last people you should be listening to. This was a PHP problem, not a WordPress problem, and for most small businesses on decent hosting it was fixed on the server while you slept. Moving your site to a different CMS would have fixed precisely fuck all.
Here's what I'm covering:
— What actually happened with PHP2Shell, and why your host probably sorted it without you lifting a finger
— Why PHP lives on the server and your CMS sits on top of it, so this was never a WordPress problem
— The "WordPress is dead, comment 'website' for the link" posts, and everything they conveniently left out
— Why your comment is their metric and your panic is their sales funnel
— Why none of this is new: same shite, different decade
— Five checks for the next panic, including the "who benefits" test and whether they named everything that got hit
— Why sometimes the right response is "noted, checked, we're fine"
— A few heartfelt wishes for the hustle bros. Lego is involved.
I also give you a proper piece of homework. Not the "might do that one day" kind. The actual do-it-this-week kind: get your host to confirm in writing that you're patched, write down who you'd call if your website broke tomorrow, and mute one panic merchant.
If a mate sent you one of those "move off WordPress now" posts, send them this episode instead.
Get found. Make money. And the next time LinkedIn tells you something's dead, ask them what they're selling.
Chapters:
00:00 The PHP Panic
00:50 What Actually Broke
02:54 Who Profits From The Panic
04:10 Your Panic Is Their Sales Funnel
06:56 How To Handle The Next Panic
Links mentioned:
Non-Wanky SEO Courses: https://nonwankyseo.com
Episode 11, on website migrations going wrong: https://seofuckingwhatpodcast.co.uk/episode/ffs-let-your-seo-help-with-your-fking-website-migration
Episode 2, on who actually owns your website stuff: https://seofuckingwhatpodcast.co.uk/episode/your-seo-sht-who-actually-owns-it
The PHP project's own announcements (the boring factual source): https://www.php.net/
Which PHP versions still get security fixes: https://www.php.net/supported-versions.php
Follow Nikki:
LinkedIn: https://www.linkedin.com/in/nikkipilkington/
Instagram: https://www.instagram.com/nikkipilkington/
Bluesky: https://bsky.app/profile/nikkipilkington.bsky.social
Transcript
So a week or so ago, a bug in PHP took websites offline all over the world.
Speaker:Within minutes, some LinkedIn wanker was telling you to bin your WordPress site.
Speaker:Sit down.
Speaker:We need to talk.
Speaker:This is SEO Fucking What.
Speaker:I'm Nikki.
Speaker:I've been doing SEO for over 30 years, since before anyone called it SEO, and
Speaker:I help people like you make money from your website by getting found on search.
Speaker:Today's episode started life as a LinkedIn post I wrote in a fit of rage, and I've
Speaker:got more to say than LinkedIn will let me.
Speaker:It's about the PHP mess, the WordPress panic, and why the people shouting
Speaker:loudest on social media are so often the last people you should be listening to.
Speaker:Right, a quick recap of what actually happened because the facts seem to
Speaker:have gone missing somewhere between the news and your LinkedIn feed.
Speaker:In the last couple of weeks, PHP released emergency security fixes
Speaker:for some seriously nasty flaws.
Speaker:The researchers who found them called it PHP2Shell.
Speaker:In plain English, the bugs could let an attacker run their own code
Speaker:on a web server without logging in.
Speaker:That's bad.
Speaker:I'm not gonna pretend it wasn't bad.
Speaker:Websites around the world were taken offline for a while as people patched.
Speaker:Government sites in France, Denmark, Finland, and the Netherlands.
Speaker:Wikipedia took systems down as a precaution.
Speaker:A Japanese airline, a railway company, and one of Japan's biggest
Speaker:banks suspended some services.
Speaker:And then what happened?
Speaker:The patches went out, the hosting companies applied them on their servers,
Speaker:and for most small businesses on decent hosting, that was it, sorted.
Speaker:It's possible you didn't have to lift a finger because this was fixed at a
Speaker:host level, not inside your website.
Speaker:PHP is a programming language.
Speaker:It's what an awful lot of the web is built with.
Speaker:The figure being quoted is, uh, that it runs around 70% of websites.
Speaker:WordPress uses it, so does Drupal, so does Joomla, so does Magento, which runs
Speaker:a huge number of online shops, by the way.
Speaker:The researchers showed the attack working on WordPress, Drupal, and Joomla,
Speaker:and they said outright that any PHP site on an unpatched version could be
Speaker:exposed, even a basic one-page site.
Speaker:So this was a PHP problem, not a WordPress problem, a PHP problem.
Speaker:Let me put it a little bit more simply.
Speaker:PHP lives on the server.
Speaker:Your content management system, whether that's WordPress or Drupal or
Speaker:Joomla or whatever, sits on top of it.
Speaker:This was a server problem, not a CMS problem.
Speaker:Moving your site to a different CMS on the same unpatched server
Speaker:would have fixed precisely fuck all.
Speaker:But what happened within minutes of it hitting the news?
Speaker:WordPress is dead.
Speaker:You need to move your website off WordPress now.
Speaker:This is exactly why we built our AI website platform.
Speaker:Comment "website" and I'll send you the link.
Speaker:For fuck's sake, did any of these posts mention Drupal, Joomla, Magento,
Speaker:government websites, a Japanese bank?
Speaker:Did they bollocks.
Speaker:Did any of them mention that your host was fixing it on the server while you slept?
Speaker:Of course not.
Speaker:Because "PHP has a bug, the host patched it, life goes on" doesn't sell anything.
Speaker:"WordPress is dead, and I've got the answer" does.
Speaker:To the people who don't know any better and are sharing this stuff,
Speaker:you're causing panic for no reason.
Speaker:Stop it.
Speaker:It's fucking embarrassing.
Speaker:To the people who do know better and posted it anyway, you look like a dick.
Speaker:And I think you know you look like a dick, and you've decided
Speaker:the engagement is worth it.
Speaker:And that's what I wanna talk about properly today because
Speaker:WordPress is a sideshow here.
Speaker:If WordPress vanished tomorrow, those same people would find
Speaker:something else to scare you with.
Speaker:This is about where small businesses get their advice and who's handing it out.
Speaker:Think about who's on the receiving end of these posts.
Speaker:You're running a business.
Speaker:You're doing your own marketing or paying for it out of money
Speaker:that's already stretched.
Speaker:You're chasing clients.
Speaker:You're chasing invoices.
Speaker:You're trying to work out what AI means for you this week because
Speaker:it changed again since last week.
Speaker:You're fighting to stay afloat, and a lot of you are doing it on your own.
Speaker:And then you open LinkedIn on your phone at 10 o'clock at night, and some bloke
Speaker:tells you your website is a security disaster, and you need to rip it out.
Speaker:Of course, that lands.
Speaker:Of course, you think, "Shit, should I be worried?" You'd be daft not to.
Speaker:It's the same pattern every single time.
Speaker:Sack your SEO, hire a GEO team.
Speaker:Stop blogging, vlog instead.
Speaker:Google's finished.
Speaker:It's all ChatGPT now.
Speaker:Comment "AI" and I'll DM you the guide that leads to the paid course.
Speaker:And do you know what?
Speaker:It fucking terrifies me.
Speaker:I see these posts with 250 comments, and every single comment says AI.
Speaker:250 business owners who've put their hand up and said, "Yes, please.
Speaker:Tell me what to do." And do you know what?
Speaker:Some of them will be fine.
Speaker:They'll read the guide, think, "Hang on, this is a load of bollocks," and move on.
Speaker:There are loads of smart people on LinkedIn who see straight through
Speaker:this crap, but some of them won't.
Speaker:Some of them will act on it.
Speaker:They'll move a perfectly good website to some shiny new platform,
Speaker:lose their redirects, lose their rankings, and spend a year wondering
Speaker:why the phone's stopped ringing.
Speaker:I've cleaned up after that more times than I can count.
Speaker:If you want the gory details on migrations going wrong, go back to episode 11.
Speaker:And what really gets me is this.
Speaker:It's not that these people don't know any better.
Speaker:I mean, some of them don't, fair enough, but most of them simply don't care.
Speaker:They don't care if you follow their advice and it wrecks your business.
Speaker:They'll never find out, and if they did, they wouldn't
Speaker:lose a minute's sleep over it.
Speaker:Your business is not their problem.
Speaker:Your comment is their metric.
Speaker:Your panic is their sales funnel.
Speaker:And none of this is new either.
Speaker:Those of you who've been around a while might remember Ecademy,
Speaker:the business networking site, years before LinkedIn got huge.
Speaker:Same shite, different decade.
Speaker:Hustle merchants turning up, scaring the hell out small business
Speaker:owners, and selling them the cure for a problem they've just made up.
Speaker:Platform changes, the playbook doesn't.
Speaker:So what do you do when the next panic hits?
Speaker:Because there will be a next one, probably by Thursday.
Speaker:I'll tell you exactly how I'd handle it right after
Speaker:this.
Speaker:Next time your feed is full of people screaming that something's
Speaker:dead, broken, or about to end your business, this is what you do.
Speaker:One, find out what actually broke.
Speaker:Before you touch anything, find one boring factual source.
Speaker:Not a LinkedIn post, the software's own announcement, your hosting company's
Speaker:status page, a proper tech news site.
Speaker:With PHP, the official line was clear within hours.
Speaker:Update PHP.
Speaker:Not change your CMS, update PHP.
Speaker:And for most people, the host did that for them.
Speaker:If the fix being sold to you is bigger than the actual problem,
Speaker:someone's selling you something.
Speaker:Two, ask the person who looks after your site one question.
Speaker:Message your host or your developer and ask, "Are we affected and
Speaker:are we patched?" That's it.
Speaker:A decent host will already have done it and will be able
Speaker:to tell you so in one line.
Speaker:If you run WordPress and want to see for yourself, go to Tools, then
Speaker:Site Health, then Info, then Server, and it'll show you your PHP version.
Speaker:If it's 8.1 or older, you're on a version that doesn't get proper
Speaker:support anymore, and that's worth a conversation regardless of last week.
Speaker:And if you can't work out who you'd even ask, that's your
Speaker:real problem, not WordPress.
Speaker:Episode two is all about who owns your website stuff.
Speaker:Go and listen.
Speaker:Three, run the "who benefits" test.
Speaker:Look at the bottom of the post that's scaring you.
Speaker:Is there a "comment X" with a link, or a product, or a free call
Speaker:that turns into a sales pitch?
Speaker:Then ask yourself what they get if you panic.
Speaker:If the answer is your money, treat the whole post as an
Speaker:advert because that's what it is.
Speaker:Four, check whether they named everything that was hit.
Speaker:This one's dead simple, and it catches loads of them out.
Speaker:If someone tells you a problem only affects the thing they happen to
Speaker:compete with and leaves out everything else that got hit, they're not
Speaker:informing you, they're positioning.
Speaker:The PHP post that only mentioned WordPress failed this test in about four seconds.
Speaker:And lastly, take advice from people who know your business, your web person,
Speaker:your SEO, your accountant, a business owner you trust who's been through it.
Speaker:People who'll still be around if the advice turns out to be shit and who'd
Speaker:have to look you in the eye, not someone whose only connection to you is that
Speaker:the algorithm shoved them in your face.
Speaker:And one more, not everything needs an action.
Speaker:Sometimes the right response to a scary post is noted, checked, we're fine,
Speaker:and you just get on with your day.
Speaker:Checking and moving on is part of running a business too.
Speaker:So this week, a few small jobs.
Speaker:Ask your host or whoever looks after your website to confirm that
Speaker:you're patched, and check your PHP version while you're at it.
Speaker:Get the answer in writing, even if it's a one-line email.
Speaker:Write down who you'd call if something properly broke on your
Speaker:website tomorrow, name and number.
Speaker:If that piece of paper is blank, sort that out before you do anything else.
Speaker:And mute one panic merchant.
Speaker:You know who I mean.
Speaker:That person whose posts make your stomach drop every time you open LinkedIn, and who
Speaker:has never once made your business better.
Speaker:Mute them, unfollow them, block them.
Speaker:Done.
Speaker:Your blood pressure will thank you.
Speaker:If this helped, make sure you're following SEO Fucking What in
Speaker:whichever app you're listening to so you don't miss the next one.
Speaker:And if a mate sent you one of those "move off WordPress now" posts,
Speaker:send them this episode instead.
Speaker:I'm not selling you anything today.
Speaker:No link, no course, no "comment PHP for my free guide".
Speaker:Just this.
Speaker:If you run a small business, be careful.
Speaker:Be careful who you listen to, and be really careful of anyone whose
Speaker:advice comes with a panic attached and a product at the bottom.
Speaker:You're doing a hard job, and you're doing better than the
Speaker:doom merchants want you to think.
Speaker:And if you're one of the hustle bros who spent the last couple of weeks
Speaker:scaring the shit out of small business owners so you could sell them something,
Speaker:I hope you step on Lego barefoot, in the dark, every fucking night.
Speaker:I hope every charger you own is two inches too short.
Speaker:I hope your socks are permanently damp.
Speaker:I hope your Wi-Fi drops every single time you try to post.
Speaker:And I hope one day you need proper, honest advice about something that
Speaker:really matters to you, and the only person you can find is someone exactly
Speaker:like you, you absolute arsehole.
Speaker:Until next time, get found, make money, and the next time LinkedIn tells you
Speaker:something's dead, ask them what they're
Speaker:selling.
