Preview
What it is.
Ours, and we sell the service it runs inside. It runs an 18-section analysis across search results and AI answers on a page you already have, branching to a different check set for listicles.
You get a refresh plan for a page that slipped, with the same 18 sections every run so two audits compare. The branch is the design point, because the checks that improve a guide do very little for a ranked list.
What you get.
- An 18-section analysis across search results and AI answers
- Conditional branching for listicle against non-listicle pages
- A refresh plan for a page that already ranks
- A version history, so each change traces to a failure it corrected
How to set it up.
Classify the page type before you analyze anything. Listicle or not is the branch, and getting it wrong invalidates the output.
Settle the section count once. Ours runs 18, and a stable list is what makes two audits comparable.
Write the branch conditions into the skill so the same page type always gets the same checks, with no operator judgment in between.
Analyze search results and AI answers in the same pass, because a refresh now has to satisfy both.
Version the skill and record what each version corrected. Ours is at v16 and the history is the useful part.
For an installable alternative, seo-content-brief has an improve-existing-page mode that covers the refresh case.
Pricing Plans
Not sold as a skill.
It runs inside client engagements. The published account dates from April 2026.
Use cases
A page that slipped
A page that ranked has been sliding and a manual read finds nothing. Run the full section pass across search results and AI answers; the refresh plan traces each change to the check that failed.
Refreshing a ranked list
The page is a listicle and guide advice keeps getting applied to it. Classify the page type first; the branch routes it to the listicle check set, because the checks that improve a guide do little for a ranked list.
Refreshing dozens of pages
An archive refresh covers dozens of URLs and the audits need to compare. The same section list runs every time, so any two pages' audits read against each other.
Borrowing the design
You're writing your own refresh checklist. The page-type branch is the decision worth copying, and the version history shows what each revision corrected.
Best for
A page that slipped and you cannot see why
An 18-section pass finds more than a manual read, and the listicle branch stops you applying guide advice to a ranked list.
Refreshing a large archive
A stable section list makes the work comparable across pages, which matters when you are refreshing dozens of them.
Building your own refresh audit
The branch on page type is the design decision, and it is the one most refresh checklists get wrong.