Hire an AI content traffic decline reviewer

Everything it can hand back

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

• The pages that lost ground since last month, with the sums
• A keep, update, merge, redirect or delete call for each, with the reason
• Up to five rewrite drafts, each with a list of facts to check
• New titles and descriptions for pages that are seen but not clicked
• A list of pages to re-read next month

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

• Updating a page that lost traffic because the topic itself faded. Say so and cut or merge instead.
• Deleting pages that still have links pointing at them, without a redirect plan the owner approves.
• Rewriting many pages at once. Small batches show what worked.
• Using this on a small site with fewer than about 20 content pages. A quick read by hand is faster.
• Trusting a draft's facts. Every fact on the check list needs a real source before it goes live.
• Generic copy that could fit any brand.

What a good result looks like

An example, not your task: You have a blog, guides or many content pages, at least about 20, and traffic seems to be sliding.

• What slipped. Each page that lost ground since last month, with traffic now, traffic before and the change.
• Calls this month. Update, merge, delete or needs a different answer for each losing page, with the reason.
• Drafts to approve. Up to five page rewrites, each with a list of facts to check and any new title.
• Quarter sort. On a quarter month, the count of pages to keep, update, merge, redirect and delete.
• Watch next month. Pages updated this month, to re-read once the change has had time to show.
• content-keeper/pages.md. One row per page with its call, the date, what was done and its traffic then.

How the work is checked

• Each page's traffic change is shown with the sums.
• No page on the must-keep list was proposed for delete or merge.
• No page updated last month was updated again without a new reason.
• Every draft has its facts-to-check list, and none is marked ready with an unchecked fact.
• 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

• See what slipped. Compares each page's search state with last month's saved copy. On the first run it saves a base to compare with later.
• Sort every page. On the first run and every third month, calls every page keep, update, merge, redirect or delete.
• Find the losers. Finds pages whose traffic fell by more than a third against the 90 days before, using keyword data if you connected it.
• Choose a path for each. Decides update, merge or delete. A page updated last month that still fell is flagged, not updated again. Must-keep pages are never cut.
• Draft the fixes. Rewrites up to five pages answer first, with a list of facts to check, and writes new titles for pages seen but not clicked.
• Hand back for approval. Lists every call and draft. Nothing goes live until you say yes.

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 monthly-content-decay-keeper 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/monthly-content-decay-keeper/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

• A list of your content pages with titles, dates and types
• Traffic or search clicks and impressions for the last 90 days and the 90 days before
• A keyword data connection such as Ahrefs (optional)
• Pages you must always keep (optional)

Helpful context (optional)

• A list of pages you must never merge or delete
• A note of any page you changed last month

Tools and access

• Claude Code: It can keep the content folder and page file, read last month's files and run every step on a schedule.
• Google Search Console: Export clicks and impressions by page for the last 90 days and the 90 days before.
• Any good chat AI: Rewrites and checks sections under the rules. Always edit the result in your own voice.
• Google Search: People Also Ask boxes give the FAQ questions to add at the bottom.

Functions and deliverables

• Content traffic decline reviewer: Find pages losing traffic and decide what needs review. Get a short fix list, draft updates and unchecked facts.
  • The pages that lost ground since last month, with the sums
  • A keep, update, merge, redirect or delete call for each, with the reason
  • Up to five rewrite drafts, each with a list of facts to check
  • New titles and descriptions for pages that are seen but not clicked
  • A list of pages to re-read next month
• 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.
• 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.
• 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.
• 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.
• Answer-first page rewriter: Share a blog, guide or FAQ page. Get sections rewritten answer first, with facts still needing a source.
  • Rewritten sections with an answer-first opening
  • A list of facts that still need a source or number
  • An FAQ block and a comparison table where they fit
• Title and meta tag writer: Turn page details and keywords into title options, meta descriptions, and social tags with length checks.
  • Title tag options
  • Meta description options
  • Open Graph and Twitter tags
  • Length checks
  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

• You have a blog, guides or many content pages, at least about 20, and traffic seems to be sliding.
• You want one steady monthly check instead of a big clean-up once a year.
• You want to know which old pages to update, merge or cut, and in what order.

Limits to check before starting

• You have fewer than about 20 content pages: read your traffic by hand in Google Search Console, it is faster.
• You want to publish changes straight to your site: this agent only drafts, so ask a person on your team to publish.
• You need to keep a page that lost traffic for a legal or product reason: leave it off the list, or mark it must-keep so it is never cut.

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.

• Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to run this month's check.
• Attach your page list and the two traffic exports.
• Read the calls and the drafts. Check every fact on each list, then publish what you approve.
• Run it again next month. It reads the saved page file and last month's search state.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/monthly-content-decay-keeper 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.