WordPress Yoast SEO Meta Updater via Custom API - n8n Workflow

This n8n workflow template is ideal for:

SEO Specialists: Programmatically managing meta descriptions and titles across a large WordPress site.
WordPress Administrators: Who require batch updates or external system integration for content management.
Developers: Looking for an example of integrating n8n with specialized, custom WordPress API endpoints.
Users of n8n: Seeking advanced n8n templates that showcase HTTP Request capabilities with authentication.

Manually updating SEO fields across many WordPress posts can be time-consuming. This specialized n8n workflow provides a solution by interfacing directly with a custom Yoast SEO API endpoint. By leveraging the versatility of the n8n platform, users can quickly define which post to target and what new title and description to assign.

This n8n template is crucial for automated SEO processes, provided the necessary custom plugin is installed on the WordPress site. It demonstrates how efficiently the n8n node framework can handle secure, authenticated API calls to perform specific backend operations, making it a valuable addition to any technical marketing stack utilizing n8n.

This n8n workflow is designed for testing and execution on demand. The logical flow is straightforward:

1. Trigger: The process begins with the "When clicking ‘Test workflow’" manual n8n trigger. While set up for testing, this foundation can be easily modified to use a scheduled n8n trigger or an external webhook.


2. Configuration: The flow moves to the Settings n8n node, where key operational variables, specifically the WordPress base URL, are defined and prepared for subsequent steps.


3. Action: The core logic resides in the HTTP Request - Update Yoast Meta n8n node. This node constructs an authenticated POST request targeting the custom /wp-json/yoast-api/v1/update-meta endpoint.


4. Payload Delivery: The request body contains the static postid, the desired yoasttitle, and the new yoast_description. The successful execution of this n8n node results in the immediate update of the specified WordPress post's SEO metadata via the Yoast framework.

To deploy and use this powerful n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON and import it directly into your n8n instance as a new n8n workflow.


2. Prerequisite Check (Crucial): Ensure you have the necessary custom plugin installed and active on your WordPress site that exposes the /wp-json/yoast-api/v1/update-meta endpoint.


3. Configure Credentials: Open the HTTP Request - Update Yoast Meta n8n node. You must set up a 'Wordpress account' credential (typically Basic Auth for API usage) corresponding to a user with permissions to edit posts.


4. Set URL: Modify the Settings n8n node (a Set n8n node) and replace https://example.com/ with your actual WordPress URL.


5. Customize Payload: In the HTTP Request n8n node, update the postid, yoasttitle, and yoast_description parameters to match the specific content you wish to modify.


6. Test: Execute the manual n8n trigger to test the n8n workflow. Once satisfied, you can change the trigger type if needed.

This n8n workflow utilizes three main n8n nodes:

When clicking ‘Test workflow’ (Manual Trigger n8n Trigger)
Function: Serves as the initiation point for testing the n8n workflow instantly.
Key Configuration: A basic n8n trigger that requires manual execution.

Settings (Set n8n Node)
Function: Defines global variables used later in the n8n workflow, ensuring easy configuration management.
Key Configuration: Sets the wordpress URL variable (e.g., https://example.com/).

HTTP Request - Update Yoast Meta (HTTP Request n8n Node)
Function: Executes the critical action: sending an authenticated POST request to the custom WordPress Yoast API endpoint to overwrite the SEO meta tags.
Key Configuration:
URL: Uses the dynamic expression ={{ $json["wordpress URL"] }}wp-json/yoast-api/v1/update-meta.
Method: POST.
Body Parameters: Specifies static data for postid, yoasttitle, and yoast_description.
* Authentication: Requires a predefined wordpressApi credential.