Add Japanese WordPress Internal Links with Gemini + Slack Approval (n8n)

Automatically add Japanese internal links to WordPress posts—approved by your editor in Slack

This n8n workflow uses Google Gemini to find relevant Japanese posts, then sends vetted internal-link suggestions to Slack for editor approval before it updates your WordPress post and logs the link pairs in n8n Data Tables.

What this workflow does

• Receives a WordPress post ID via an authenticated webhook call or a manual n8n form submission.
• Fetches the WordPress post from the WordPress REST API using Basic Auth, then extracts numbered paragraphs and existing links from the raw HTML.
• Generates Japanese keywords with Google Gemini, searches the WordPress REST API for related posts, and also checks an n8n Data Table for matching “priority pages” based on keyword hits in the post body.
• Filters and ranks candidates by excluding the current post, already-linked targets, and previously logged link pairs—then prioritizes results using priority status, search frequency, and prior linking frequency.
• Proposes internal links (paragraph + anchor + target) with Gemini, validates that the anchor appears exactly in the paragraph, and ensures it’s not inside existing links or cut across Japanese word boundaries.
• Requests approval in Slack with a checkbox message (with a 1-day wait). If the editor selects links, the workflow reloads the post to confirm it hasn’t changed, inserts the chosen anchors, updates the post, and records the link pairs in n8n Data Tables.

Use cases

• Scale internal linking for Japanese WordPress content while keeping editorial control via Slack.
• Increase SEO relevance by linking to priority pages based on n8n Data Table rules.
• Reduce manual workload for content teams: Gemini drafts, editors approve, n8n applies updates.

Technical details

• Integrations/nodes: if, set, code, Slack, webhook, n8n Data Table, WordPress REST API (Basic Auth), Google Gemini.