Tips Tuesday – AI SEO Workshop, Future WordPress Updates, Better Passwords

Tips this week include:

• AI SEO Workshop this week
• How to get your DIY SEO Everywhere discount
• Update on WordPress Lawsuit news
• The future of the WP 6.8 Release – and beyond
• How password reuse compromises your security

We’ve got a short one today – giving you more time to get out and enjoy the nice spring weather!

Course Happenings

AI SEO Workshop This Week

As promised, I’ve been busy revamping the DIY SEO course with new workshops that go far beyond Google and into every way we can get new eyeballs and traffic to our content.

We’re starting with a series on AI SEO, as many of us are getting traffic from multiple AI search results.

This week we’ll cover all of the different AI search engines and we’ll be testing 2 different types of queries on each of them – for evergreen content, and current content to see how each of them performs.

And, we’ll have a look at how AI summarizes our posts too.

Get Your Discount

There’s still time to get in on the $100 course discount. Just contact me to get yours!!

And let’s get more traffic to your site!!!

WordPress Tips

WordPress Lawsuit News

This Post Status report has the latest updates on the ongoing lawsuits involving WordPress.

Here are a few highlights:

• WordPress secured the trademarks for the terms “WordPress Hosting” and “Managed WordPress”. 
• The U.S. Patent Office has rebuked that and said that both of these terms were merely descriptive and cannot be trademarked. Automattic plans to fight that ruling.
• So, if you use either of those in your business or agency, I suggest you change them to something like “care plans for WordPress”, which should be safe to use. Or, you can stand pat and see what becomes of the Patent Office challenge.
• Core Commenters in WP development are burning out due to the lack of volunteer help. Matt is calling it a “back to basics” transition.

The Future of the WP 6.8 Release

The Beta 2 rolled out last week. And normally I would expect the Beta 3 out today and then the RC1 (first Release Candidate) to come out the following week.

But that may not happen this time.

As I reported to you last week, Matt pissed off so many of the volunteer devs that he decided to bring this 6.8 release in house, and under his control with the Automattic staff he pays.

Well, as you saw above in that Post Status article, those folks are burning out – fast.

In fact, this past week Matt shared the core committers channel on WordPress Slack where they discussed delaying the 6.8 update – and making it the only one for 2025.

Then only have 6.9 as the only release in 2026.

I’d be THRILLED for that to happen.

In fact, this nutty, frequent release schedule they’ve been running for the past several years is what has hurt my WP training business so much. And it has costs 100s of 1000s of dollars for anyone who makes to tutorials to keep them up to date. Some of us solopreneurs simply can’t afford to do it.

So, maybe instead of jumping all over the place with 3 releases a year, why not focus on just Gutenberg and ensure every single block meets the same functional standard of every other block? If they had done that in the first place, it would not have taken 6 years to bring Gute up to a working standard.

And, they can focus on bug tickets that have been open for the last 5-10 years too, and ensure all underlying code is 100% functional for everyone.

Plus, I’ve fought the battles with volunteer devs pressing against 100s of other devs and affected businesses saying no to a new feature, all to get their ego-driven pet project into core.

So, I know all the folks who want WP to remain Open Source, volunteer driven are going to be disappointed.

But, I think the rest of us – you know the millions of end users, are going to be breathing a sigh of relief if Matt takes development this way and just slows everything down to something more focused.

At least that is my hope of what he may have planned for it.

Security Tips

How Password Reuse Compromises Your Security

Cloudflare has a new feature that detects use of stolen passwords. They call it Leaked Credentials.

And what they’ve found by monitoring this critically important aspect of your site security is that nearly half of all passwords are used on multiple platform logins.

Simply put, folks are using the same password for all of their online accounts.

Folks, that’s the worst thing you can do!!!

Be sure that all of your passwords meet these criteria:

• Unique to each account
• At least 16 characters that contain special characters, numbers, and capital letters

Consider using a password vault.

You’ll find that me and most of my clients use on the BlogAid Resources page.