Technical SEO audit of up to 25 pages from your sitemap

On-page checks across up to 25 sitemap pages, with a plain list of what to fix.

  • Public site and sitemapNo keyA sitemap the crawler can read.
  • API keyNo keyNone required.
25
sitemap pages
0
keys needed
2
checks it skips: links, speed
1
run replaces the last
Search Growth · Technical auditIllustrative composite

Technical audit · 25 pages crawled

6 findings shown
CheckPagesWhere
Blocking Missing canonical4/guides/repotting, /guides/soil-mix, +2
Blocking robots.txt blocks /guides/1site-level
Should fix Title longer than 60 characters6/blog/watering-schedule, +5
Should fix Duplicate meta descriptions3/features/reminders, +2
Minor Images without alt text9/blog/succulents, +8
Minor Missing Open Graph image2/about, /pricing

Does not check broken links or page speed. Up to 25 sitemap pages per run.

Illustrative product composite. Filter by severity. Pages and findings are invented.

How an audit runs

  1. Point it at a public site

    Run the audit for the active site.

  2. Crawl 25 pages

    Pages are taken from the sitemap, up to 25, and each is checked against the list.

  3. Read the findings

    Findings are grouped by check with the affected pages, so you can fix a template once and clear many pages.

  4. Fix, then rerun

    Rerun after changes to confirm the findings are gone.

What it needs
Public site and sitemapNo keyA sitemap the crawler can read.
API keyNo keyNone required.
What it will not do
  • Report Core Web Vitals or speed. Use a speed tool for that.
  • Fix anything. It reports findings; changes happen in your CMS.
  • Score your site as a guarantee of ranking. A clean audit removes obstacles, nothing more.

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

The audit crawls up to 25 pages from your sitemap and checks the fixed list of on-page signals that most often go wrong: titles, descriptions, headings, canonicals, indexing directives, image alt text, social tags, structured data and duplicates. It reports problems and counts, and it is explicit about what it does not check.

What you get

A fixed, named checklist

Missing or badly sized titles and descriptions, H1 problems, noindex, missing canonical, images without alt text, viewport, lang, Open Graph, thin content, structured data, duplicate titles and descriptions.

Site-level checks

robots.txt blocking and a missing sitemap are reported as site-level findings, not buried per page.

No key required

It reuses the sitemap crawler, so it works on a self-hosted instance with no search provider.

What changes

Before

  • On-page problems found one page at a time, if at all.
  • Duplicate titles and missing canonicals hide in templates.
  • No shared list of what to fix.

With BlogFactory

  • Up to 25 sitemap pages checked against a fixed list.
  • Findings grouped by check so one template fix clears many pages.
  • Site-level robots.txt and sitemap problems shown separately.

OutcomeA fix list. Links and speed are not checked.

Limits to know

  • Checks up to 25 sitemap pages, not the whole site.
  • It does not check broken links or page speed.
  • It reads server-rendered HTML. Content added only by JavaScript may not be seen.

Questions

Does the audit check broken links or page speed?

No. It does not check either, and the product says so. It covers the on-page signals listed above.

How many pages does it crawl?

Up to 25 pages from your sitemap per run.

Do I need an API key?

No. The audit reads public pages and your sitemap directly.

Can it see my staging site?

Only if it is public. Private and internal addresses are refused by design.

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.