Turning a nearly 300-post portfolio into a refresh queue
How NisonCo connected Google Search Console and WordPress to find underperforming content, prioritize updates, and turn portfolio maintenance into a repeatable workflow.
- posts in the reported portfolio
- Nearly 300
- performance signal
- Google Search Console
- content system
- WordPress
The context
Publishing more content does not solve the maintenance problem. Across a mature client portfolio, NisonCo needed a reliable way to identify pages that were slipping, decide what deserved attention, and carry approved changes back into WordPress.
What the workflow had to solve
- Find the few updates with meaningful upside inside a large library of existing posts.
- Use first-party search performance instead of treating every old page as equally urgent.
- Separate pages worth refreshing from pages that should be consolidated, redirected, or left alone.
- Move from analysis to a reviewable change without losing the original URL or editorial context.
How the workflow worked
Connect performance to inventory
The optimizer joins Google Search Console signals with the WordPress content library so changes in clicks, impressions, queries, and positions can be evaluated at the page level.
Prioritize before rewriting
Search Console signals help the team review pages with declining or underused search visibility first, instead of refreshing every post on an arbitrary calendar.
Suggest or implement the update
The workflow can propose optimization changes or carry them into the connected CMS, depending on the level of human control the team wants.
What the source supports
- One workflow could analyze nearly 300 posts across the reported client portfolio.
- Search Console became a prioritization input rather than a reporting dashboard checked after the work was done.
- WordPress connectivity made refreshes an executable workflow, not a spreadsheet of recommendations.
- The workflow became the foundation for Perennial's Content Refresh product.
What this taught us
A content library should be managed like a portfolio. Use real performance data to decide where the next hour of editorial work is most likely to matter.
Want to see the other workflow?
Put the workflow against a real page
Bring one content problem to the demo. We will show what Perennial can automate, what still needs human judgment, and how it would reach your CMS.