Rank Math bulk title & description optimizer for WordPress
Bulk WordPress SEO Meta Optimizer with Rank Math & AI
This n8n workflow, along with its companion WordPress plugin (rank_math_tools.zip), automates the bulk optimization of your WordPress posts' Rank Math SEO titles and descriptions using AI.
Stop manually crafting metas and let AI supercharge your SEO efforts efficiently!
How it works:
This workflow streamlines your SEO process through several automated steps:
- Fetches Post IDs: Retrieves all published post IDs from your WordPress site using a secure, custom API endpoint provided by the companion plugin.
- Gathers Post Content: For each identified post, it accesses the existing title, slug, and main rendered content to provide context for the AI.
- AI-Powered Meta Generation: Leverages an AI model of your choice via OpenRouter (defaulting to Claude 3.7 Sonnet) to generate an optimized SEO title and meta description. This generation is guided by a detailed, customizable prompt within the "Create Meta Infos" node, allowing you to define the style, tone, and SEO strategy.
- Updates WordPress Metas: Sends the newly generated SEO title and description back to your WordPress site via another custom API endpoint. The companion plugin then updates the specific Rank Math fields for each post.
- Refreshes Modified Date: The companion plugin automatically updates the post's 'last modified' date in WordPress whenever meta information is changed, which can be a positive signal for search engines.
- Selective Processing: An "IF" node ("Should I Rewrite") intelligently determines whether a post's metas need updating based on predefined conditions (e.g., empty metas or placeholder content), optimizing resource usage.
Setup Steps:
Get up and running in approximately 15-25 minutes by following these high-level steps. Detailed instructions are available in the comprehensive documentation provided with your purchase and within the sticky notes inside the n8n workflow itself.
- Install the Companion WordPress Plugin:
- Download the
rank_math_tools.zipfile. - Upload and activate it on your WordPress site.
- (Estimated time: 2-5 minutes)
- Download the
- Configure WordPress API Authentication:
- In your WordPress admin area, go to your user profile and create a new Application Password.
- Ensure the user has at least an "Editor" role.
- Copy the generated password.
- (Estimated time: 2-5 minutes)
- Set Up n8n Credentials:
- In n8n, create a new "WordPress API" credential using your WordPress username, the Application Password you just copied, and your site's Base URL.
- Create a new "OpenRouter Api" credential using your OpenRouter API key.
- (Estimated time: 5-10 minutes, assuming you have your OpenRouter key ready)
- Import and Configure the n8n Workflow:
- Download the
Bulk_Wordpress_Meta_Data_Optimizer_Gumroad.jsonworkflow file. - Import it into your n8n instance.
- Link your newly created WordPress and OpenRouter credentials to the respective nodes in the workflow.
- Verify and update your WordPress site URL in the "settings" node (ensure it has a trailing slash
/). - Review the "Limit" node – it's pre-set to process only 5 items for safe initial testing.
- (Estimated time: 5-10 minutes)
- Download the
Benefits:
- Full SEO Meta Automation: Drastically reduce manual effort by automatically generating and updating SEO titles and descriptions for all your posts.
- Bulk Processing Power: Efficiently handle meta optimization for hundreds or thousands of WordPress posts.
- Highly Customizable AI Output: Fine-tune the AI's generation style, keyword focus, and direct response techniques by editing the detailed prompt within the "Create Meta Infos" node.
- Improved SEO Consistency & Quality: Ensure all your articles have relevant, compelling, and optimized meta tags, adhering to best practices.
- Signal Freshness to Search Engines: The automatic update of the post 'last modified' date upon meta change can help improve crawl frequency and SEO.
- Resource-Efficient Updates: The "Should I Rewrite" node prevents unnecessary processing and API calls for posts that already have satisfactory meta information.
- Save Time & Focus on Content: Free up valuable time to concentrate on creating great content, rather than on repetitive SEO tasks.
To understand exactly how to use and customize this workflow in detail, please refer to the comprehensive step-by-step documentation provided with your purchase.
For professional n8n automation services for your business, contact: Phil | Inforeole
WordPress Rank Math Bulk Title & Description Optimizer
This n8n workflow automates the process of generating and updating SEO titles and descriptions for WordPress posts using AI, specifically tailored for Rank Math SEO. It fetches a list of posts, generates optimized meta information, and then updates the posts in batches.
Description
This workflow streamlines the SEO optimization of WordPress content. It leverages AI to create engaging and keyword-rich titles and descriptions for your posts, then automatically applies these changes to your WordPress site through the Rank Math API. This is particularly useful for bulk optimizing existing content to improve search engine visibility without manual effort for each post.
What it does
- Manually Trigger: The workflow is initiated manually, allowing you to control when the optimization process begins.
- Fetch WordPress Posts: It retrieves a specified number of WordPress posts (defaulting to 100).
- Limit Posts (Optional): An optional step to limit the number of posts processed, useful for testing or incremental updates.
- Loop Over Posts: Each fetched post is processed individually in batches.
- Prepare Data for AI: For each post, it extracts relevant information like the post title and content, and constructs a prompt for the AI model.
- Generate SEO Meta with AI: It uses an AI chat model (OpenRouter) and a structured output parser to generate an optimized SEO title and description based on the post's content and existing title.
- Conditional Update Check: It checks if the AI successfully generated both a title and a description.
- Update WordPress Post (If Valid): If both an SEO title and description are generated, the workflow updates the corresponding WordPress post with the new Rank Math SEO title and description.
- No Operation (If Invalid): If the AI fails to generate both, the post is skipped without updating.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- WordPress Account: Access to a WordPress site with the Rank Math SEO plugin installed and configured.
- WordPress Credential: An n8n credential configured for your WordPress site (API access required).
- OpenRouter API Key: An API key for OpenRouter (or another compatible AI chat model configured within the "OpenRouter Chat Model" node).
- LangChain Nodes: Ensure you have the
@n8n/n8n-nodes-langchainpackage installed in your n8n instance.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure WordPress Credential:
- Locate the "Wordpress" node.
- Click on "Credentials" and select or create a new WordPress API credential.
- Provide your WordPress URL, username, and application password (generated in WordPress under Users > Profile > Application Passwords).
- Configure OpenRouter API Key:
- Locate the "OpenRouter Chat Model" node.
- Click on "Credentials" and select or create a new OpenRouter API credential.
- Enter your OpenRouter API key.
- Review and Adjust (Optional):
- "HTTP Request" (Fetch Posts): You can adjust the
per_pageparameter in the URL to fetch more or fewer posts. - "Limit" Node: Modify the "Limit" node if you only want to process a specific number of posts (e.g., for testing).
- "Edit Fields" (Set): Review the prompt for the AI model to ensure it meets your SEO requirements. You might want to fine-tune the instructions given to the AI.
- "Loop Over Items": The batch size can be adjusted here.
- "HTTP Request" (Fetch Posts): You can adjust the
- Execute the Workflow: Click the "Execute Workflow" button to start the optimization process.
Important Notes:
- It is highly recommended to test this workflow on a staging environment or with a small number of posts first to ensure the generated content meets your quality standards before running it on your live site with many posts.
- The AI's output quality depends heavily on the prompt provided in the "Edit Fields" node and the capabilities of the chosen LLM. You may need to experiment with the prompt to get the best results for your specific content.
- The workflow is designed to update Rank Math SEO titles and descriptions. If you are using a different SEO plugin, this workflow might not be directly compatible without modifications.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.