WordPress SEO Fix Workflow: Gemini Drafts, Slack Approval

Fix WordPress SEO automatically—then get human approval in Slack

This WordPress SEO Fix Workflow reviews recently published WordPress posts, detects missing or overlong SEO titles and meta descriptions, drafts improved replacements using Google Gemini, and sends a before/after proposal to Slack for approval—only then updating your site via the WordPress REST API.

What this workflow does

• Runs daily on a schedule and fetches the latest WordPress posts using the WordPress REST API.
• Limits scope by keeping only posts published within a configured time window, and it skips URLs already logged in an n8n Data Table (preventing re-proposals).
• Reads live HTML for each post and extracts SEO elements including title, meta description, canonical, robots, and H1.
• Flags issues for missing or overly long titles/meta descriptions, while calculating the available title character budget.
• Drafts fixes with Google Gemini using the post excerpt and constraints to generate a replacement title and meta description.
• Requests approval in Slack by posting a before/after proposal and waiting up to one day.
• If approved, updates WordPress via the REST API (post title and excerpt—used as the meta description), then logs the outcome. If skipped, it logs too.
• Weekly verification report: re-checks applied changes on the live site and posts results to Slack.

Use cases

• Keep new WordPress content compliant with SEO title/meta length standards without manual audits.
• Handle SEO improvements in a controlled process—drafting with Gemini, publishing only after Slack review.
• Guarantee changes are verified over time with the workflow’s weekly live-site report.

Technical details

• Core n8n nodes: if, set, code, html, slack, filter.
• Integrations: Slack (approval workflow + run summaries) and WordPress REST API (fetch + update).
• Logging: create an n8n Data Table named seo_fix_log to track processed/approved/skipped posts.