Hi my friend!
I'm back from vacation! āļøšļø After almost two lovely weeks away, I'm back to work, back at the gym, and getting into my usual routine. And I missed talking to you!
Let's get back to business now:
Do you remember that Reddit rabbit hole I went down a few weeks ago?
I asked content marketers how they manage updates when they have hundreds (or even thousands) of articles, especially when product features, pricing, and integrations keep changing.
I promised to share what I learned, so here we go!
Here are a few interesting approaches people shared:
1. Tag articles based on what could make them outdated.
A few people suggested tagging every article based on what it mentions: pricing, features, integrations, competitors, etc.
Then, whenever something changes, you can quickly identify which articles need attention instead of reviewing your entire content library.
One person also pointed out that every tag needs an owner. Otherwise, you'll just end up with another backlog nobody touches. š
2. Use AI and automation to identify outdated information.
One marketer built an internal tool that scans their documentation and blog every week to identify outdated feature names.
Another uses Screaming Frog to crawl websites, converts the content into Markdown, and uses up-to-date product documentation to identify inconsistencies.
There's still some manual work involved, but these approaches can make the whole process much more manageable.
3. Audit based on what changes rather than on schedule
This one was particularly interesting!
One marketer shared that their team stopped doing annual content audits altogether.
Instead, they review content whenever one of three things happens:
A product changes: Their product release template includes a required question about which published pages mention the affected feature.
Rankings drop: They check Google Search Console weekly to identify articles losing positions.
Search results change: They monitor their most important commercial keywords and review their content when competitors start overtaking them.
They also decide whether an article actually needs updating, merging with another article, or removing entirely.
I particularly like the idea of including content updates directly in the product release process. It's such a simple way to improve communication between product and marketing teams.
And that's probably my biggest takeaway from this little experiment: the less you rely on remembering to review everything, the easier it becomes to maintain a large content library.
I think there's something here worth borrowing, even if you already have a solid content update process in place.
There are more interesting responses, so here's the full Reddit thread if you'd like to read through them.
Also, two new articles! š
While I was away, two articles I worked on for Searchable went live and I also promised to share these with you:
This one's about measuring AI visibility properly. Why checking ChatGPT once tells you very little, which metrics you should actually track, and how to build a reliable measurement process.
If you're still trying to figure out how GEO and AEO differ from traditional SEO (and whether you actually need three different strategies), this one's for you.
Lots more interesting AI search content coming soon!
Have a lovely weekend!
Kate š
