Bring the evidence down to the article
I connected the article inventory with Search Console and GA4, then added keyword context. Matching by URL slug helped reconcile the library with historical blog URL changes.
TRANSAK · CONTENT OPERATIONS & SEO ANALYTICS
Know which articles deserve the next refresh.
TL;DR
Turn a large article library and separate analytics reports into a practical queue for updating content.
Delivered: An article-level decision tool for finding refresh opportunities, inspecting the evidence, and maintaining a usable content inventory.
Problem
A substantial content library creates a recurring decision: which article should the team update next? Publication age alone cannot answer that. An older article may still perform well, while a newer one may be losing valuable traffic.
Freshness records, search queries, and engagement data needed to refer to the same article. Changes to URLs and the live catalogue also meant the refresh queue needed to distinguish active content from pages that had been replaced or removed.
Process
Prioritise a decision, not another report
I combined freshness, traffic, and decline into a refresh-priority score. Editors could inspect an article’s queries, trends, and search intent before deciding what to change.
Keep the queue aligned with the live site
I added live, replaced, and removed states to the catalogue. The default view excluded retired pages from refresh totals and priorities, supported by a repeatable catalogue reconciliation process.
Results
An article-level decision tool for finding refresh opportunities, inspecting the evidence, and maintaining a usable content inventory.
- Inventory
- What is live, replaced, or removed?
- Evidence
- How is this article performing and for which queries?
- Priority
- What should the team review and update next?
Connected performance
Search visibility, engagement, keyword context, and freshness could be reviewed together for each article.
An actionable update queue
Priority sorting, current-versus-prior-period trends, and query drill-downs supported the editorial decision.
A maintained catalogue
Status-aware reporting and exports kept removed or replaced content from distorting the active backlog.
Evidence & scope
The July implementation record documents the joined performance layer and refresh model. September catalogue work records the status filters and reconciliation workflow. This case describes the delivered internal system; client dashboard access is not exposed here.
Scope. A prioritisation system is the outcome in this case. It does not establish a measured ranking recovery or hours saved from subsequent editorial work.
GET IN TOUCH
Let’s talk about
your search strategy.
Send me your website and what you want to achieve.
We’ll work out where I can make a difference.