Hire an AI search content refresh planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• The pages losing traffic and the topics rivals have taken
• A keep, refresh, merge or cut call for each page, with reasons
• A refresh plan for each page you keep, and new titles and snippets
• Tracking set up to show whether each refresh worked

How it does the job well

• Write for one named audience and one action. Each asset has a single job.
• Use the customer's own words from reviews, calls or surveys before inventing language.
• Every claim needs proof the business can show. Leave unproven claims out or mark them.
• Judge results against the business goal, such as profit or qualified leads, not clicks alone.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: Your blog traffic is slowly falling and you do not know which pages are to blame.

• Step 1 decay. Pages losing traffic, the searches they lost and where rivals now rank above you.
• Step 2 calls. A keep, refresh, merge or cut call for each page, with the reason and the numbers.
• Step 3 refresh plans. For each refresh: facts to update, structure to change and questions to add.
• Step 4 titles and snippets. A new search title and snippet for each refreshed page, within length.
• Step 5 tracking. Change date, searches to watch, a read date and a definition of worked, per page.
• Hand-back summary. Each step's file and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Neil Patel would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Find the decay. Finds the pages losing traffic, the searches they are losing and where rivals now rank above you.
• Make the call per page. Makes a keep, refresh, merge or cut call for each page, with the reason and the numbers.
• Plan each refresh. Plans each refresh: facts to update, structure to change, questions to add.
• Write new titles and snippets. Writes a new title and search snippet for each refreshed page.
• Publish the refreshes. A pause. Make the refreshes and the merges. Publish the new titles and snippets.
• Track the result. Sets up tracking per changed page, with the date, the searches to watch and a read at six to eight weeks.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id find-old-posts-losing-traffic-refresh-or-cut-them-and-track-it only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/find-old-posts-losing-traffic-refresh-or-cut-them-and-track-it/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your site address
• Traffic by page for the last twelve months or more, from your analytics or Search Console
• Search Console searches by page (optional)
• Publish and last-updated dates for each post (optional)
• Your competitors, if you know them (optional)
• What you can commit to: how many refreshes a month

Helpful context (optional)

• Search console queries by page
• Publish and last-updated dates for each post
• Rival pages that rank for your lost searches

Tools and access

• Any good chat AI: Every step is a plan or a piece of writing.
• Your analytics and search console: Traffic by page and by search is the input for every step.
• Your CMS: Where the refreshes, merges and redirects happen.
• Any good chat AI: A short prompt works in any strong chat AI. Paste it, then add your details under it.

Functions and deliverables

• Search content refresh planner: Find pages losing search traffic, propose updates or redirects and plan how to measure the results after you make changes.
  • The pages losing traffic and the topics rivals have taken
  • A keep, refresh, merge or cut call for each page, with reasons
  • A refresh plan for each page you keep, and new titles and snippets
  • Tracking set up to show whether each refresh worked
• Ahrefs content gap and decay reviewer: Connect Ahrefs and share your site, rivals and dated content data. Get missing topics and pages classified for action.
  • Missing topics
  • Thin and outdated pages
  • Decaying pages
  • A roadmap of create, update, merge and prune actions
  Source: RampStack.
• Page keep-or-cut auditor: Find which pages to keep, update, merge, redirect or delete in your content audit. Give it your page list and data. You get a call and reason per page.
  • Each page marked keep, update, merge, redirect or delete
  • Reason for each call
  • Priority order of work
  • Redirect map for pages you remove
  Source: RampStack.
• Old content refresher: Find which old blog posts to update, merge or delete. Give it your posts and traffic. You get a priority list and how deep each refresh goes.
  • An update, merge or delete decision for each post
  • A priority order for the work
  • How deep each refresh should go
  • A quarterly schedule you can repeat
  Source: RampStack.
• Search title and snippet writer: Share the page topic, search phrase and benefit. Get three title and description drafts, character counts and a social-sharing line.
  • Three titles and descriptions with counts
  • A line for social sharing
  • A pick with one reason
• SEO change tracker: Save a before picture of your site's SEO, then check for lost rankings, dropped pages and changed tags after a redesign or release.
  • A baseline snapshot
  • A change report between snapshots
  • Ranking and index losses
  • Changed titles, tags and schema
  Source: sickn33.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Neil Patel: Plan search content using Neil Patel’s recorded approach. Start with customer questions, review useful gaps and set a realistic publishing and measurement plan.
  • Your problem worked on the way Neil Patel would: their questions, their method, their push-back
  • The answer or the work, in Neil Patel's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• Your blog traffic is slowly falling and you do not know which pages are to blame.
• You have a hundred posts and suspect twenty do the work.
• You refreshed posts last year and never checked whether it helped.
• Two or three of your posts answer the same search and none of them ranks.

Limits to check before starting

• Your traffic fell off a cliff across the whole site: use Shopify search traffic recovery reviewer.
• You want to plan new posts, not rescue old ones: use Search topic and content brief planner.
• You want a full check of titles, tags and markup across the site: use Website SEO editor.
• Your site has less than twelve months of traffic. Decay only shows over time.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste your site address and attach your traffic by page. If your AI can reach Search Console or Ahrefs, say so. Ahrefs is a paid subscription, and the run works without it from your exports. If not, it works from what you attach and marks what it could not check.
• Read the calls. Change any you disagree with. Refresh the keepers as planned, then publish the refreshes, merges and new titles.
• Give it the dates you changed each page. Check the tracking after six to eight weeks.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/find-old-posts-losing-traffic-refresh-or-cut-them-and-track-it for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.