Find the topics a competitor covers and you do not, from their sitemap

Read a rival's public sitemap and list the topics you have not covered.

  • Competitor domainNo keyA site with a public sitemap.
  • Product profileNo keyRecommended, so topics can be ranked by fit.
  • API keyNo keyNone required.
3
sitemap sources tried
0
keys needed
12
gaps shown first
0
private pages read
Search Growth · Competitor content gapIllustrative composite

Competitor content gap

https://leafnote.example

142 article URLs read from 188 sitemap URLs. You already cover 31.

Read from the public sitemap only. It shows what a competitor published, not how it ranks.

Illustrative product composite. The competitor domain, counts and topics are invented.

How a gap analysis runs

  1. Enter a domain

    Type the competitor's domain without https://.

  2. Read the counts

    The summary shows how many article URLs were read from how many sitemap URLs, and how many you already cover.

  3. Scan the gaps

    Each gap shows a topic and an intent badge, with a link to the source page so you can see how they cover it.

  4. Plan what fits

    Add the topics that serve your audience.

What it needs
Competitor domainNo keyA site with a public sitemap.
Product profileNo keyRecommended, so topics can be ranked by fit.
API keyNo keyNone required.
What it will not do
  • Read a competitor's traffic, rankings or backlinks. Those sit behind paid indexes this feature does not use.
  • Fetch non-public pages or private addresses.
  • Write a competitor-derived article for you. Gaps become plan items you review.

BlogFactory never publishes live. Agents propose, people approve, and the furthest an agent goes is a CMS draft.

More: what you get, what changes, limits and questions

Give BlogFactory a competitor's domain. It reads robots.txt and the public sitemap, finds the article URLs, turns their slugs into topics, ranks them by how well they fit your product, and marks the ones you already cover. You see where the gaps are without a paid index or a login.

What you get

Sitemap-based, no key

Follows robots.txt, sitemap.xml and sitemap indexes. Only public pages are read; private and internal hosts are refused.

Ranked by product fit

Topics are scored against your saved profile and labelled by intent, so alternatives and buying-intent gaps rise above generic guides.

Already covered detection

Topics that match your posts, plan items or indexed pages are counted as covered instead of listed as gaps.

What changes

Before

  • You browse a rival's blog by hand and lose track of what you already cover.
  • Gaps are a feeling, not a list.
  • No way to tell a fit from noise.

With BlogFactory

  • Their public sitemap read for article topics.
  • Gaps ranked by product fit, intent labelled, covered topics removed.
  • Each gap links to the rival page and adds to your plan in one click.

OutcomeA ranked list of topics you have not covered.

Limits to know

  • Topics come from URL slugs and titles in the sitemap, so odd slugs give odd topics.
  • A sitemap lists what exists, not what ranks or earns traffic.
  • Sites without a public sitemap, or that block the crawler, return no gaps.

Questions

Does the content gap tool need an API key?

No. It reads the competitor's public robots.txt and sitemap directly.

Is reading a competitor's sitemap allowed?

Sitemaps are published for crawlers. BlogFactory reads them like any crawler and refuses private and internal hosts. You remain responsible for how you use the topics.

Does it show which competitor pages rank?

No. A sitemap lists pages, not their rankings. Use the rank tracker for your own positions.

Can an agent run it?

Yes, through the read-only find_content_gaps MCP tool, which takes a competitor domain and changes nothing.

Draft-only, whether you self-host or use Cloud.

Cloud starts at $5 a month and AI usage is bring-your-own. The open-source core is free to self-host. The authority boundary is identical in both.