Block noindex SEO regressions in deploy pipelines with webhook and Slack
Ready for 3.0What this workflow does
This workflow has 19 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Slack.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Settings (Edit Fields (Set)): sets 6 fields: urls, sitemap_url, max_urls…
- Pick The URLs To Check (Code): runs custom JavaScript code
- One Item Per URL (Split Out): splits a list into separate items
- Ask For robots.txt (HTTP Request): calls an HTTP API
- Ask For The Sitemap (HTTP Request): calls an HTTP API
- Fetch Each Page (HTTP Request): calls an HTTP API
- Read robots.txt (Code): runs custom JavaScript code
- Read The Sitemap (Code): runs custom JavaScript code
- Check Every Page (Code): runs custom JavaScript code
- Put The Checks Together (Merge): merges the data from its input branches
…plus 8 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Split Out
n8n-nodes-base.splitOut - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
Quick overview This workflow exposes a POST webhook your deployment pipeline calls to run an SEO smoke test against key URLs, robots.txt, and the sitemap, then posts results to Slack and returns HTTP 500 to block the deploy on critical indexing issues. How it…