Keep new sitemap pages indexed with Google Search Console, Bing, and IndexNow
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 20 nodes and runs on a schedule (every day at 09:00). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every day at 09:00).
- Fetch Sitemap XML (HTTP Request): calls an HTTP API
- Parse Sitemap URLs (Code): runs custom JavaScript code
- Compile Telegram Message (Code): runs custom JavaScript code
- Verify URL Submission (Data table): row not exists
- Dispatch Telegram Digest (Telegram): uses Telegram
- Determine URL Priority (Code): runs custom JavaScript code
- Route by Priority Level (Switch): routes items into 2 branches
- Note Cornerstone Submission (Data table): create or update (row)
- Record Content Submission (Data table): create or update (row)
- Gather Cornerstone URLs (Aggregate): combines items into one
…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)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Data table
n8n-nodes-base.dataTable - Switch
n8n-nodes-base.switch - No Operation, do nothing
n8n-nodes-base.noOp - Aggregate
n8n-nodes-base.aggregate - Merge
n8n-nodes-base.merge - Telegram
n8n-nodes-base.telegram
From the author
Quick overview This workflow runs daily to fetch your sitemap, deduplicate previously submitted URLs using an n8n Data Table, and submit new pages to Google Search Console, Bing Webmaster Tools, and IndexNow, then sends a Telegram digest with submission…