Frequently Asked Questions

SeoSitemap.app is a free, automated bulk SEO auditing tool. It extracts all URLs directly from your sitemap.xml and scans them simultaneously for common technical and on-page SEO issues, saving you hours of manual work.

Our crawler analyzes H1 heading structure (missing, empty, or duplicate H1s), metadata (Title tag length, Description, Canonical availability), and link health (checking for 200 OK status, 404 broken links, and Time To First Byte speed).

No, SeoSitemap.app is completely free to use and requires no registration. However, you can optionally support the project through donations if you find it helpful!

Yes! While the tool is optimized for bulk sitemap scanning, you can simply paste a direct page URL, check the "Analyze single URL only" box, and our tool will audit just that specific page.

No. We respect your privacy. All scans are executed in real-time and the results are returned directly to your browser session. We do not persistently store your scan history or export data on our servers.

To prevent overloading your server and ours, the crawler uses a concurrency limit (processing pages in small batches). If your server responds slowly (high TTFB), the overall scan time naturally increases.

Try the obvious paths first: /sitemap.xml, /sitemap_index.xml or /sitemap-index.xml. If those return 404, open /robots.txt — most sites declare their sitemap location there with a "Sitemap:" line. WordPress, Shopify, Wix and most popular platforms generate a sitemap at /sitemap.xml automatically.

The scanner picks the first 500 URLs from the sitemap and audits those. You will see a "Limit Reached" notification in the UI so it is clear we truncated. If your site is bigger than that, you can run multiple targeted scans against different sitemap-index files (one per section), or wait for the paid tier we are planning.

Not at the moment. The scanner fetches pages anonymously — the same way Googlebot does. Authenticated areas, staging sites behind HTTP basic auth, and pages that require cookies are out of scope. If you need to audit a private environment, deploy it to a publicly-reachable URL first or use a tool that runs locally on your machine.

It does not actively read robots.txt before fetching a page (it is your sitemap and your site, so you have authorised the access by running the scan). It does read each page's meta robots tag once fetched, and surfaces noindex/nofollow as a warning in the results.

Treat it as a relative gauge rather than an exact figure. It reflects the readable body text a search engine sees, so it is reliable for comparing your own pages against each other and flagging thin ones. Two caveats: languages without word spaces (Chinese, Japanese, Thai) come out under-counted, and any text injected by client-side JavaScript after the page loads is not counted. For the full per-page breakdown, run the Content Analyser.

Time-to-First-Byte is the time between our serverless function starting the HTTP request and receiving the response headers. It includes DNS resolution, TCP handshake, TLS negotiation and the server's "think time", measured from our infrastructure. It does not include downloading the body or rendering the page in a browser.

Ad units are gated behind a feature flag and only render when AdSense is approved for the account. While we wait for re-approval the slots produce no markup at all — you should never see an empty grey rectangle. If you do, please let us know via the contact page.

Not a public one yet. The internal /api/analyze and /api/sitemap endpoints are rate-limited and protected against SSRF, and they are not documented for third-party use. If you have a use case for programmatic scanning, get in touch via the contact page and we will consider it.