Workflow for submitting changed sitemap URLs using Google Indexing API and Bing IndexNow

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This n8n template saves you hours of manual SEO work by automatically parsing your sitemap and submitting updated URLs to Google and Bing (IndexNow). Who’s it for Site owners, SEOs, and marketers w...

Best for

Content Creation automation workflows
Market Research automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.xml, n8n-nodes-base.splitout, n8n-nodes-base.sort, n8n-nodes-base.code

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Geoffroy.

Original n8n.io source

1.1 Workflow description

Title: Workflow for submitting changed sitemap URLs using Google Indexing API and Bing IndexNow
Workflow name: Workflow for submitting changed sitemap URLs using Google Indexing API and Bing IndexNow

This n8n template saves you hours of manual SEO work by automatically parsing your sitemap and submitting updated URLs to Google and Bing (IndexNow).

Who’s it for

Site owners, SEOs, and marketers who want a single automation to notify Google (Indexing API) and Bing (via IndexNow) whenever site URLs are added or updated. No more need to update it manually. Hours saved

What it does

This workflow parses your sitemap.xml, and for each URLs that have been changed on the last X days (this is a setting from Config node), submit them to Google and Bing via IndexNow. Before submitting to Google it checks the status. For IndexNow it just submits based on the last updated date it can find on the sitemap.

How it works

Parses your sitemap(s)to generate a list of urls ordered by lastmod date.
Create a batch of the urls updated in the last X days (settings DAYS_BACK from the "Config" node)
For Google, it first aks the current indexing notification status of this exact URL. If the sitemap shows the page was modified after the last submission, the workflow sends a new "URL_UPDATED" notification to Google. If Google has no record (404), it means the URL was never submitted and the workflow treats it as new and submits it.
For Bing through IndexNow, it only sends “recently changed URLs” based on the sitemap’s <lastmod> and the variable DAYS_BACK from the Config Node, by batches of 500 (current limit recommendation by Bing). IndexNow doesn't have an API to check the status of the url.

Requirements

Google Indexing API credentials (Service Account with https://www.googleapis.com/auth/indexing scope, added as Owner in Search Console).
IndexNow API key: you can create it here https://www.bing.com/indexnow/getstarted.

How to use

Edit the "Config" node with your data & preferences (everything explain in the workflow).
Edit the "Check status (Google)" and "URL updated (Google)" node with your Google service account credentials.
Execute the workflow to test it
Set up a cron with the "Schedule Trigger" node depending on your needs

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking "Test workflow"

Type / Role: n8n-nodes-base.manualTrigger - manualTrigger
Config choices: Version 1

Block 2 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.1

Block 3 - Config

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.3

Block 4 - Get sitemap.xml

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 5 - Convert sitemap to JSON

Type / Role: n8n-nodes-base.xml - xml
Config choices: Version 1

Block 6 - Get content-specific sitemaps

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 7 - Get content of each sitemap

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 8 - convert page data to JSON

Type / Role: n8n-nodes-base.xml - xml
Config choices: Version 1

Block 9 - Force urlset.url to array

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.3

Block 10 - Split Out

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 11 - Sort

Type / Role: n8n-nodes-base.sort - sort
Config choices: Version 1

Block 12 - Assign mandatory sitemap fields

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.3

Block 13 - Filter: lastmod within DAYS_BACK

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 14 - Loop Over Items (Google)

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 15 - Check status (Google)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 16 - is new? (Google)

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2

Block 17 - URL Updated (Google)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 18 - Wait (Google jitter)

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1

Block 19 - Split In Batches (IndexNow ≤500)

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 20 - Build IndexNow payload

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 21 - IndexNow Submit

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 22 - Wait (IndexNow jitter)

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1

Block 23 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 28 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Workflow for submitting changed sitemap URLs using Google Indexing API and Bing IndexNow
Complexity	advanced
Nodes	28
Categories	Content Creation, Market Research
Author	Geoffroy
Published	20 Sept 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/8778/8778.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Content Creation workflows Market Research workflows

Frequently asked questions

What does Workflow for submitting changed sitemap URLs using Google Indexing API and Bing IndexNow do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, Market Research use case.

Geoffroy

4 workflows

Nodes

n8n-nodes-base.manualtrigger n8n-nodes-base.scheduletrigger n8n-nodes-base.set n8n-nodes-base.httprequest n8n-nodes-base.xml n8n-nodes-base.splitout n8n-nodes-base.sort n8n-nodes-base.code

Complexity

advanced

Published 20 Sept 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/8778/8778.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Send daily LinkedIn post drafts with Tavily, Groq Llama 3.3 and Gmail

## Quick overview This workflow runs daily at 8 AM to rotate through a topic list, research it with Tavily web search, generate a LinkedIn post and image prompt with Groq (Llama 3.3 70B), create a Pollinations.ai image URL, and email you the post with the image attached via Gmail. ## How it works 1. Runs every day at 8:00 AM on a schedule. 2. Selects today’s topic from a rotating list based on the day of the year. 3. Searches the web with Tavily to fetch up-to-date results for the selected topic. 4. Uses a Groq-hosted Llama model to write a LinkedIn post and a matching image prompt grounded in the Tavily results. 5. Builds a Pollinations.ai image generation URL from the image prompt and downloads the generated image file. 6. Emails the post text with the image attached via Gmail, and sends a text-only fallback email if image generation or download fails. ## Setup 1. Add a Groq API credential to the Groq Chat Model node. 2. Create a Tavily API key and configure HTTP Header Auth with `Authorization: Bearer <YOUR_TAVILY_KEY>` for the Tavily Search request. 3. Connect a Gmail OAuth2 credential and update the recipient email address in both Gmail send steps. 4. Edit the topic list in the topic-selection code step if you want different rotating themes. ## Requirements - Groq API key (free tier available) - Tavily API key (free tier — 1,000 searches/month) - Gmail account (OAuth2) ## Customization - Edit the topic list inside the "Pick Today's Topic" code node to change what subjects the post rotates through. - Change the Groq model in the "Groq Chat Model" node if you want a different LLM (e.g. a smaller/faster or larger Groq model). - Adjust the schedule trigger if you want a different posting time, or swap the Gmail "send to" address to deliver the draft to someone else for review. ## Additional info This workflow emails you a draft for manual review before posting — it does not post to LinkedIn automatically. If image generation fails, a text-only fallback email is sent instead so you never miss the post text.

View

Generate VEO3 videos from form ideas with ChatGPT, fal.ai, Drive and Gmail

## Quick overview This workflow collects a video idea via an n8n Form, uses OpenAI to turn it into an optimized prompt, generates an 8-second VEO3 video with native audio via fal.ai, saves the MP4 to Google Drive, and emails the Drive link via Gmail. ## How it works 1. Receives a submission from an n8n Form with the requester’s email, a plain-English video idea, and a selected style. 2. Uses OpenAI (via an AI Agent) to convert the idea and style into a structured VEO3 title and detailed prompt returned as JSON. 3. Cleans and parses the AI JSON, creates a filename-safe title, and sets the generation parameters to 16:9 and 8 seconds. 4. Submits the prompt to fal.ai’s queue endpoint for the fal-ai/veo3 model and gets a request ID. 5. Polls fal.ai every 30 seconds until the job status returns COMPLETED. 6. Retrieves the final MP4 URL from fal.ai, downloads the video, uploads it to Google Drive, and emails the Google Drive web link to the requester via Gmail. ## Setup 1. Create a fal.ai account, generate an API key, and replace `YOUR_FAL_AI_API_KEY` in the fal.ai HTTP request headers. 2. Add an OpenAI API credential in the OpenAI Chat Model node and select the model you want to use. 3. Connect Google Drive OAuth2 and replace `YOUR_GDRIVE_FOLDER_ID` with the target folder ID where videos should be saved. 4. Connect Gmail OAuth2 for sending emails, then activate the workflow and use the Form URL (path `veo3-video-generator`) to submit requests.

View

Generate presentation decks from prompts with Encelade

## Quick overview This workflow starts a presentation generation job in Encelade from a prompt and outline hints, polls Encelade for completion, and outputs the finished deck link (or stops with an error if generation fails). ## How it works 1. Starts when you manually execute the workflow in n8n. 2. Sends the topic, slide count, audience, tone, theme settings, and outline hints to Encelade to generate a 6-slide presentation. 3. Waits 20 seconds and then checks the Encelade session status using the returned session ID. 4. If the session phase is not finished, it keeps waiting and rechecking until the phase changes. 5. When the phase is "done", it returns the generated deck link and project PID. 6. When the phase is "failed", it stops the workflow and raises an error with the failure details. ## Setup 1. Install and configure Encelade credentials in n8n for the Encelade node. 2. Update the generation inputs (topic, page count, outline hints, audience/tone, theme mode, and media provider) to match the deck you want to create. 3. Ensure the workflow has enough time to complete by adjusting the 20-second wait interval if your Encelade generations typically take longer.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Workflow for submitting changed sitemap URLs using Google Indexing API and Bing IndexNow

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

This n8n template saves you hours of manual SEO work by automatically parsing your sitemap and submitting updated URLs to Google and Bing (IndexNow).

Who’s it for

What it does

How it works

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - When clicking "Test workflow"

Block 2 - Schedule Trigger

Block 3 - Config

Block 4 - Get sitemap.xml

Block 5 - Convert sitemap to JSON

Block 6 - Get content-specific sitemaps

Block 7 - Get content of each sitemap

Block 8 - convert page data to JSON

Block 9 - Force urlset.url to array

Block 10 - Split Out

Block 11 - Sort

Block 12 - Assign mandatory sitemap fields

Block 13 - Filter: lastmod within DAYS_BACK

Block 14 - Loop Over Items (Google)

Block 15 - Check status (Google)

Block 16 - is new? (Google)

Block 17 - URL Updated (Google)

Block 18 - Wait (Google jitter)

Block 19 - Split In Batches (IndexNow ≤500)

Block 20 - Build IndexNow payload

Block 21 - IndexNow Submit

Block 22 - Wait (IndexNow jitter)

Block 23 - Sticky Note1

Block 24 - Sticky Note

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions