Sitemap API for Content Discovery

Before you start

• A SitemapKit API key stored in a server-side environment variable.
• A target domain or sitemap URL and a clear success criterion for the content discovery workflow.

Implementation workflow

1. 1

   Define the workflow objective

   Start from this concrete goal: Discover all published content on any domain

2. 2

   Request the sitemap data

   Use the implementation example below from server-side code and pass the target domain or sitemap URL required by the workflow.

3. 3

   Validate and reuse the result

   Check the returned sitemap URLs and page records against the expected outcome for content discovery before sending the data to the next system.

Why use SitemapKit?

• See every page a competitor has published
• Track content volume and publishing frequency via lastmod
• Identify content categories from URL patterns
• Build content inventories for audits

Implementation example

curl -X POST https://sitemapkit.com/api/v1/sitemap/full \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"url": "competitor.com"}' | \
  jq '[.urls[] | select(.loc | contains("/blog/"))] | length'

# Output: 847 (total blog posts on competitor.com)

Continue with SitemapKit