Skip to content

Daily

Get told about sitemap errors

If Search Console reports errors or warnings on your sitemaps, you get an email that day.

Runs
Daily
Apps
Google Search Console
AI
Not needed
Access
read

Send this to your assistant

Create a ClickRuntime automation: every day at 9am, check the sitemaps for example.com in Search Console and email me if any show errors or warnings.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A publisher migrates her site to a new CMS and the new sitemap generator produces a file with URLs returning 404 and a few pages blocked by robots.txt. Google Search Console shows the sitemap with a red Couldn't fetch status, but she only looks at that screen when something already seems wrong. New articles stay unindexed for weeks, and ad revenue slips because pages that nobody can find earn no clicks.

Every day, ClickRuntime lists the sitemaps registered for your Search Console property and reads the errors and warnings counts that Google reports for each. If any count is above zero, or a sitemap has stopped being processed, you get an alert naming the sitemap and the numbers, so you can open it and fix the cause.

It suits publishers, online shops and agencies that manage sites after a redesign or CMS change.

What you get out of it

  • New pages get discovered

    A sitemap with errors can slow down how quickly Google finds new URLs. Seeing the issue the day it appears helps your fresh articles and products reach search results without waiting weeks.

  • Migration problems exposed

    Site moves often break the sitemap without any visible symptom on the website itself. A daily check turns an invisible technical fault into an email while the migration team is still available to fix it.

  • No habit of opening Search Console

    Most owners look at Search Console rarely. An alert that arrives only when there is a fault means you do not have to remember to check, and quiet days stay quiet.

  • Warnings handled before they become errors

    Warnings such as URLs blocked or redirected tend to grow over time. Spotting them early keeps the file clean, which makes indexing reports easier to read and trust. Smaller problems are far cheaper to clear than a pile-up.

  • Protects revenue from organic search

    If search brings in orders or ad impressions, indexing problems cost money quietly. A small daily check is inexpensive insurance against losing weeks of visibility to a mistake in a file.

How it works

What happens, step by step

  1. Every day, ClickRuntime lists the sitemaps you've submitted to Google Search Console.

  2. It checks each one for errors or warnings.

  3. If any have problems, you get an email that day naming each sitemap, its error and warning counts, and when Google last read it.

Before it runs live

  • Connect Google Search Console

What you get

RunsDaily
Get told about sitemap errorstoday, 9:00Succeeded
Email · Sitemap problemshttps://example.com/sitemap-products.xml: 3 errors, 0 warnings (last read 2026-10-19)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Run it at a different time, more or less often, or only on weekdays
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other Google Search Console steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
sitemap_error_check.pyexample
from urllib.parse import quote
from clickruntime import on_trigger, credentials, http, notify

SITE = "sc-domain:example.com"

@on_trigger
def run(event):
    resp = http.get(f"https://www.googleapis.com/webmasters/v3/sites/{quote(SITE, safe='')}/sitemaps",
                    headers={"Authorization": f"Bearer {credentials.connection('google', 'work')}"})
    resp.raise_for_status()
    bad = [s for s in resp.json().get("sitemap", []) if int(s.get("errors", 0)) or int(s.get("warnings", 0))]
    if bad:
        lines = [f"{s['path']}: {s.get('errors', 0)} errors, {s.get('warnings', 0)} warnings "
                 f"(last read {s.get('lastDownloaded', 'never')[:10]})" for s in bad]
        notify.email_me(f"{len(bad)} sitemaps with problems on example.com", "\n".join(lines))
    return {"problems": len(bad)}

FAQ

Common questions

What do errors and warnings mean in a sitemap report?
Errors are problems that stop Google from reading the file or some of its URLs, like invalid XML or unreachable addresses. Warnings are lesser issues, such as URLs that redirect. Both counts come from Search Console for each submitted sitemap.
Does it check sitemaps I have not submitted?
It lists the sitemaps submitted to Search Console for the property. If a sitemap is only referenced in robots.txt, submit it in Search Console as well so that Google reports on it and the check can see it.
How soon after a fix will the alert stop?
Google has to fetch the sitemap again before the counts update, which can take from hours to several days. You can resubmit the sitemap in Search Console to speed this up. Alerts stop once the reported errors return to zero.
What permissions does it need?
read. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Get told about sitemap errors” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.