#girldad, Agency Founder @mtmadagency, Entrepreneur, Coffee Lover. Host of the @page2podcast.
Connecticut, USA
Joined December 2023
- Tweets224
- Following190
- Followers30
- Likes98
Jon Clark retweeted
Interesting from Apollo's Torsten Slok -> Outside of tech there has been no financial payoff to US companies for using AI, now viewed as a margin-hurting cost center, as VC-backed firms burn more tokens
"The question looking ahead is whether, even as models become commoditized, mainstream corporate America can turn increasingly cheap intelligence into higher revenue growth and higher profit margins. That may be harder than it sounds."
"AI may be a great calculator, but in business, intelligence is mostly judgment. Judgment depends on context, and the answer varies with which human or which model you ask. Perhaps most importantly, AI does not understand accountability, trust, culture, unwritten rules, ethical trade-offs or fairness, all of which shape reputational risk and ultimately drive revenue growth and profit margins."
apollo.com/wealth/insights-n…
Jon Clark retweeted
We believe voice is the most natural way to interact with intelligence, so we created Dessa, the most authentic full-duplex speech model ever built. Talking with it feels like talking with a person…full of emotion, nuance, pauses, and a natural cadence.
block.xyz/dessa
This is gold. Just replicated across a set of 100+ current/legacy clients and found 3 sites on vulnerable versions of PHP!
A critical PHP security hole dropped at 10am today. In 3 minutes I had checked every client. AI what a time to be alive.
WordPress, Drupal, Magento: all exposed. Roughly 40% of the internet.
Our team posted about it in Slack. My first thought:
"Why not check every client we've ever had?"
Not just current clients. Every one. Past clients too.
So I fired up claude code..
→ Pulled all 639 client companies out of our CRM
→ Checked every website: headers, page code, blogs
→ Compared each one against today's patched versions
→ Sorted the results into a list, with the evidence for every site
The scan took 2.5 minutes. I got a CSV.
What it found:
• 208 sites showing signs of PHP
• 5 running versions that are confirmed vulnerable right now
• 3 of those on versions so old they'll never get an official fix
This makes me think of 3 things I love about AI:
1 - You can scale caring about your clients, former clients, etc in ways that were almost impossible PRE-AI
2 - You have to start asking your AI "why not check everyone" or "what would it take to check everyone" vs how do I check my 1-2-3 clients?
3 - Also while people are bombarding my inbox with low value sales emails, why not keep an eye on ways to actually help people?
Jon Clark retweeted
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
If you’re taking servers offline for PHP patches, @googlesearchc has some
helpful reminders for site owners.
Key takeaways:
• If maintenance takes PHP offline, serve a 503 from a layer that stays up, such as a CDN rule or a temporary server.
• Keep robots.txt responding normally during downtime.
• Cap 503 windows at one to two days. Longer closures risk dropping affected URLs from the index.
Jon Clark retweeted
Phrase and exact match got considerably worse over 5 years. Google's shortening the cycle to push brands onto your shortlist earlier - makes sense at scale, produces garbage queries for you. What's the weirdest match you've seen lately? Full episode with @AnthonyHigman
Jon Clark retweeted
Security called me at 6:12 AM today.
"Patch every PHP server immediately."
I asked what happened.
"Two critical vulnerabilities. Remote code execution. No authentication required."
Cool.
How many PHP servers do we have?
According to inventory: 12
According to reality:
Nobody knows.
We found one running WordPress.
Three running old internal tools.
One under someone's desk.
Two inside vendor appliances.
A forgotten employee directory from 2016.
And a server named:
PHP-OLD-DO-NOT-TOUCH
Naturally, that one runs payroll exports.
Then we found a PHP 5.6 box.
I asked who owned it.
The documentation said:
BRIAN.
Brian left in 2019.
We called Brian.
He said:
"Oh wow, that's still running?"
Excellent.
By 8 AM, leadership joined the incident call.
CEO:
"Can hackers actually get in?"
Security:
"Potentially yes."
CEO:
"Without a password?"
Security:
"Yes."
CEO:
"Then why do WE need passwords?"
Not the lesson.
Finance asked if we could wait until the weekend to patch because downtime affects revenue.
Security explained that the alternative was letting strangers execute code on our servers.
Finance asked for a cost comparison.
At 9:17, someone suggested temporarily taking the vulnerable websites offline.
Marketing refused.
"Our campaign is live."
So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.
We finally patched everything we could find.
Then our scanner discovered another PHP server.
Hostname:
TEMP-PHP-2014
Uptime:
4,512 days.
Nobody knows what it does.
Nobody owns it.
Nobody can shut it down.
But every time we block network access, the warehouse stops printing shipping labels.
Security has classified it as critical infrastructure.
It is running PHP 5.4.
The vulnerability has existed longer than half our employees.
The emergency patch took four hours.
Finding out what PHP actually runs took eleven.
The internet isn't held together with code.
It's held together with servers everyone is afraid to turn off.
Google searches are up. Clicks to websites aren't keeping pace. And now rank tracking itself is breaking.
On the latest episode of @Page2Podcast, we talked with @marcustober (Searchmetrics founder, now SVP Enterprise at @semrush) about why. 🧵
5/ And his favorite AI visibility fix is almost too simple.
A ~30-year category leader had top SEO visibility but trailed in AI.
They added plain, neutral homepage copy about who they are and what they do. AI visibility jumped almost instantly.
6/ Full episode with Marcus: youtu.be/w-xVVd1RiH4
Honest question: how often have you audited your homepage (or your clients' homepages) to see if they actually say what the company does?
Jon Clark retweeted
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.
PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
Jon Clark retweeted
The hardest client conversation right now: the traffic isn't coming back. SEO was rankings + traffic. AI search is visibility + downstream conversions. Attribution as we knew it is gone. How are you explaining that to leadership?
Jon Clark retweeted
New episode is out now: @marcustober on why rank tracking is harder than ever. Google removed num=100, obfuscated the referrer, and he believes AI agents send 1,000x more requests than scrapers ever did. How has your rank tracking data changed?