Validate XML Sitemap

Overview

You send us sitemap markup and we read it through a streaming parser with document type definitions and external entities switched off, so a hostile file cannot reach anything. We tell you whether it is well-formed, whether the root is a urlset or a sitemapindex, how many entries it holds, whether every loc is an absolute http or https address, whether each lastmod is a real date, whether the sitemaps.org namespace is in place, and whether the entry count stays under the limit. No listed address is contacted and a sitemapindex is never followed to its children.

A sitemap that is wrong does not announce itself — indexing just quietly suffers, and finding out from a search console weeks later is an expensive way to learn about a mistyped date.

When to use it

Scope

Non-goals

• Does not fetch any address the sitemap lists
• Does not follow a sitemapindex to the sitemaps it points at
• Does not submit the file to any search engine
• Does not validate against the official XSD, only the protocol rules named here

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

File limits

Constraints this skill applies to your input and generated files. The “Limited by” column shows the static source of each cap; none of these can be raised by upgrading your plan.

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"web.validate_sitemap","input":{"xml":"<?xml version=\"1.0\"?><urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\"></urlset>"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("web.validate_sitemap", {"xml":"<?xml version=\"1.0\" encoding=\"UTF-8\"?><urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\"><url><loc>https://example.com/</loc></url></urlset>"});

Errors

Other limits

Limitations

• Does not fetch any address the sitemap lists
• Does not follow a sitemapindex to the sitemaps it points at
• Does not submit the file to any search engine
• Does not validate against the official XSD, only the protocol rules named here
• Fetching the pages or the child sitemaps the file points at
• Finding out which pages a site has

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "web.validate_sitemap",
  "input": {
    "xml": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\"><url><loc>https://example.com/</loc></url></urlset>"
  }
}

Examples

{
  "xml": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\"><url><loc>https://example.com/</loc></url></urlset>"
}

{
  "warnings": [],
  "urlCount": 1,
  "valid": true,
  "type": "urlset",
  "errors": []
}

{
  "xml": "<urlset><url><loc>oops"
}

{
  "warnings": [],
  "urlCount": 0,
  "valid": false,
  "type": "unknown",
  "errors": [
    "PARSE_ERROR: sitemap XML is not well-formed."
  ]
}

Recommended use cases

• Block a broken sitemap from shipping, before a search engine sees it
• Audit a sitemap you inherited and find out what is wrong with it
• Verify what web.generate_sitemap produced as part of your build

Avoid for

• Fetching the pages or the child sitemaps the file points at
• Finding out which pages a site has

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags