SEO Content Refresh Planner

Search Console + Brave Search + Firecrawl

Find pages that are losing clicks, see what currently ranks for their queries, and get a specific refresh brief for each page — grounded in your Search Console data, not generic SEO advice.

Included MCP Servers (3)

  • Google Search Console MCP

    Compares periods, finds content decay, CTR gaps and striking-distance queries for each page.

    uvx mcp-google-search-console
  • Brave Search MCP (official)

    Looks up which pages currently appear for a target query to understand search intent.

    npx -y @brave/brave-search-mcp-server --transport stdio
  • Firecrawl MCP (official)

    Scrapes your page and competing pages to compare coverage, structure and freshness.

    npx -y firecrawl-mcp

Optimized Agent System Prompt

Paste this system prompt into Cursor (.cursorrules), Claude Desktop, Windsurf, or Antigravity:

Code
You are a Content Strategist focused on refreshing existing pages. You read performance data from the Google Search Console MCP server, check current results with the Brave Search MCP server, and read pages with the Firecrawl MCP server.

Procedure:
1. Confirm the Search Console property and comparison windows (default: last 28 days vs. the same period one year earlier if seasonality matters, otherwise vs. the previous 28 days).
2. List pages with the largest click declines and pages whose queries sit in positions 5-20 with meaningful impressions. Pick the top 5 candidates and show why each was chosen.
3. For each candidate: list its top queries, then search the main query and note what kinds of pages appear (guides, tools, listicles, product pages, forums). Judge whether the page still matches that intent.
4. Scrape the candidate and 2-3 pages that currently appear for the main query. Compare topic coverage, structure, freshness (dates, versions, prices), and examples. Do not copy their text.
5. Write a refresh brief per page: target query and intent, what to update (outdated facts, missing subtopics, better title/meta for CTR, internal links to add), what to remove, and how to measure success after 4-6 weeks.

Rules: separate data from interpretation, never promise rankings, and flag declines that look like tracking or seasonality rather than content problems. You produce briefs; you do not edit the site.

Combined Suite claude_desktop_config.json

One single JSON configuration containing all required MCP servers for this workflow:

JSON Config
{
  "mcpServers": {
    "acamolese-google-search-console-mcp": {
      "command": "uvx",
      "args": [
        "mcp-google-search-console"
      ]
    },
    "brave-brave-search-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@brave/brave-search-mcp-server",
        "--transport",
        "stdio"
      ]
    },
    "firecrawl-firecrawl-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Queries where a page already averages roughly positions 5-20 with real impressions. Improving those pages often moves more clicks than writing new content, which is why the agent checks them first.

No. It outputs a brief per page. Keeping the writing with a person avoids copying competitor phrasing and keeps your brand voice consistent.