SEO Content Optimization with Google Search Console and WordPress

This workflow connects to Google Search Console API on a weekly schedule and pulls performance data for the top 200 indexed pages. It identifies pages that have experienced a click-through rate decline of more than 15 percent or an average position drop of more than 3 spots in the last 28 days compared to the previous period. For each underperforming page, it sends the current page content, metadata, and Search Console query-level data to Claude Code via the n8n MCP server. Claude analyzes the content gap against top-ranking competitor snippets and generates a revised version with updated headings, improved keyword usage, enhanced meta descriptions, and internal link suggestions. The revised content is sent to a WordPress draft post that overwrites the original. An Airtable row is updated with the optimization date, Claude's summary of changes, and a projected impact score. The content team receives a Slack digest listing all updated pages, the reason for each change, and the estimated ranking improvement window.

BUSINESS PROBLEM

Content decay is a persistent SEO challenge — pages that once ranked on page one gradually lose positions as competitors publish fresher, more comprehensive content. Manual content auditing involves exporting Search Console data, analyzing each page individually, researching competitor content, rewriting, and publishing. A full content audit of 100 pages takes 20-40 hours. [ STAT ] Pages published more than 12 months ago see an average 28 percent decline in organic traffic year-over-year when not refreshed — Source, Ahrefs Content Decay Study, 2024. Most content teams lack the capacity to refresh more than 10-15 pages per quarter. This workflow automates detection, analysis, rewriting, and deployment, enabling weekly refreshes across the entire content library.

WHO BENEFITS

FOR content marketing managers SITUATION: responsible for maintaining 300+ blog posts with a team of two writers PAYOFF: shifts team focus from refreshing old content to creating new pillar pages. FOR SEO specialists SITUATION: manually audits 50+ pages per month to identify decay patterns PAYOFF: automated detection catches declining pages within 48 hours instead of waiting for monthly reports. FOR solo content creators SITUATION: runs a niche site with 150+ articles and no editorial support PAYOFF: keeps the entire content library competitively fresh with zero incremental time investment.

HOW IT WORKS

1. Schedule trigger runs every Monday at 6 AM UTC. Calls Google Search Console API to fetch last 28 days of performance data for all indexed URLs.

2. Compare node compares current 28-day period to the previous 28-day period. Flags pages with CTR drop greater than 15 percent or position drop greater than 3.

3. HTTP Request node fetches the full HTML content and current meta data of each flagged page from the WordPress REST API.

4. Claude Code MCP node receives the page content, current metadata, Search Console query-level data, and competitor SERP snippets. Returns a revised page body, new meta title, new meta description, and internal link recommendations.

5. WordPress node updates the existing post with Claude's revised content, new title, and new meta description. Sets post status to draft for human review.

6. Airtable node creates or updates a record with the page URL, optimization date, Claude's change summary, projected traffic impact, and review status.

7. Slack node sends a weekly optimization digest to the #seo channel listing each updated page, the detected issue, Claude's change summary, and a review link.

TOOL INTEGRATION

Google Search Console API requires a Google Cloud project with the Search Console API enabled and OAuth 2.0 credentials scoped to the verified site property. GOTCHA: The Search Console API returns data only for the last 16 months — the comparison node must use the exact same date range (28 days) for both periods. WordPress REST API requires an Application Password generated from the WordPress admin dashboard under Users > Application Passwords. GOTCHA: The WordPress REST API endpoint for updating posts (POST /wp/v2/posts/{id}) requires the Content-Type header set to application/json. Claude Code MCP receives the HTML content of each page. GOTCHA: Claude's output includes rewritten HTML but may strip WordPress block markup (Gutenberg blocks). Add a WordPress content filter step — n8n Function node can wrap Claude's output in a custom HTML block format so it renders correctly in the block editor. Airtable integration requires a personal access token with data.records:write scope. GOTCHA: Airtable rate-limits to 5 requests per second per base. If more than 10 pages need updating, add a 200ms delay between Airtable write operations.

ROI METRICS

1. Content audit time: 20-40 hours for 100 pages manually → 1 hour for workflow setup + automated weekly runs. 2. Pages refreshed per quarter: increases from 10-15 to 50-80 with automated detection and drafting. 3. Average traffic recovery: refreshed pages see 15-30 percent organic traffic increase within 60 days. 4. CTR improvement: Claude-rewritten meta descriptions average 0.5-1.2 percent CTR lift above originals. 5. Team capacity: frees 6-10 hours weekly that content teams redirect to new content production.

CAVEATS

1. (moderate risk) Claude may produce content that diverges from brand voice — set a system prompt with brand guidelines in the MCP tool call. Review drafts before publishing via the WordPress draft queue. 2. (moderate risk) Search Console data has a 2-3 day latency. A declining page may already be underperforming for several days before the weekly trigger catches it. 3. (minor) WordPress REST API writes update the post modified date, which can trigger unwanted cache invalidation. Configure a cache-control header on the WordPress CDN. 4. (minor) Google Search Console API has a daily quota of 200,000 rows per property. The workflow's top-200 page analysis is well within limits but bulk analyses must respect the quota.