Find technical issues in a clear, bounded sample

ForFoundersSEO teamsAgent builders

Sample your project's public HTML and review findings by URL. Check HTTP status, titles, descriptions, headings, robots directives, links and image alt attributes with the crawl coverage visible.

Start freeRead the workflow guide

1 to 15 page entries · HTTP HTML sample · Saved project reports

Site Audit

Acme · Fictional sample project

Site Audit · example.com

Partial sample

3 page entries · Incomplete access · Stop: finished

URL	HTTP	Indexable	Issues
/	200	Yes	No sampled issues
/repair	200	Yes	Missing description
/guides	429	Unknown	Rate limited; content not assessed

Scroll horizontally to inspect all columns.

HTTP HTML only · Local indexability · Full-site coverage not verified

Sample states only. These controls do not run research or contact a provider.

Site Audit illustration with fictional sample data. Switch states to see coverage and limitations.

From a bounded crawl to URL findings

1
Choose a sample
Open Site Audit for the tracked domain. Pick a limit from 1 to 15 page entries; the default is 10. Running and saving requires project write access.
2
Read the crawl coverage
Check complete or partial state and the stop reason before judging the findings. Request and time budgets can stop the crawl before the chosen page limit.
3
Inspect findings by URL
Open a page's details and review its content checks or fetch failure. Revisit the saved report later with the original timestamps and limitations.

See the page behind the warning

The result table connects a sampled URL to HTTP status, local indexability checks, link counts and issues. Page details show the returned metadata and sampled headings.

HTML checks Spot missing titles or descriptions, heading issues, noindex directives and missing image alt attributes.
Sampled links Broken-link findings compare sampled internal links with sampled HTTP errors. They do not prove every destination was fetched.
Unavailable content A failed fetch or persistent HTTP 429 does not establish that a page's title, description or headings are missing.

Read the Site Audit guide

Coverage is part of the result

A complete sample can still contain errors. A partial sample describes incomplete access or a budget stop, not a verdict that the entire website is defective.

Shared budgets Up to 20 HTTP requests and 15 seconds cover pages, robots reads, redirects and retries together.
Public-site scope The crawl respects applicable robots rules and restricts discovery and redirects. Query-string URLs and known nonpage assets are excluded.
Saved results Matching recent reports may be reused for five minutes. Reopening a saved report retains its original observation dates.

Revisit saved Agent Reports

What it does not do yet

This is a bounded HTTP sample, not a full-site crawl, JavaScript rendering or Lighthouse performance test.
Local indexability checks do not verify canonical correctness or actual search-engine indexing.
Robots restrictions, redirects, slow responses and rate limits can reduce coverage. Inspect state and stop reason before drawing conclusions.

Site Audit questions

Does a complete audit cover the whole site?

No. Complete means the eligible sample finished without unresolved access limitations. Page, request, time and body-size limits still apply.

Why can the result be partial?

A page limit, request limit, time limit, unreadable robots policy or unresolved fetch can leave a partial sample. HTTP 429 is incomplete access, not a missing-content finding.

Does Site Audit use a paid SEO provider?

It reads the tracked public website through the bounded HTTP crawler. It does not call a paid SERP provider. Request admission and project permissions still apply.

Next step

Keep the workflow connected

Agent Reports

Save an interpretation that carries the sample's coverage and limitations into the next decision.

Domain overview

Estimated traffic, keywords and top pages for any domain

Project Context

Business, audience, products, goals and rules for your agents

Put your next analysis in the project

Read the workflow guide, then use the same project context and saved results across the app and connected agents.

Start free

Read the workflow guide

Free and open source (AGPL-3.0). Export your data anytime, or run the same app yourself.

Start free

Find technical issues in a clear, bounded sample

ForFoundersSEO teamsAgent builders

Sample your project's public HTML and review findings by URL. Check HTTP status, titles, descriptions, headings, robots directives, links and image alt attributes with the crawl coverage visible.

Start freeRead the workflow guide

1 to 15 page entries · HTTP HTML sample · Saved project reports

Site Audit

Acme · Fictional sample project

Site Audit · example.com

Partial sample

3 page entries · Incomplete access · Stop: finished

URL	HTTP	Indexable	Issues
/	200	Yes	No sampled issues
/repair	200	Yes	Missing description
/guides	429	Unknown	Rate limited; content not assessed

Scroll horizontally to inspect all columns.

HTTP HTML only · Local indexability · Full-site coverage not verified

Sample states only. These controls do not run research or contact a provider.

Site Audit illustration with fictional sample data. Switch states to see coverage and limitations.

From a bounded crawl to URL findings

1
Choose a sample
Open Site Audit for the tracked domain. Pick a limit from 1 to 15 page entries; the default is 10. Running and saving requires project write access.
2
Read the crawl coverage
Check complete or partial state and the stop reason before judging the findings. Request and time budgets can stop the crawl before the chosen page limit.
3
Inspect findings by URL
Open a page's details and review its content checks or fetch failure. Revisit the saved report later with the original timestamps and limitations.

See the page behind the warning

The result table connects a sampled URL to HTTP status, local indexability checks, link counts and issues. Page details show the returned metadata and sampled headings.

HTML checks Spot missing titles or descriptions, heading issues, noindex directives and missing image alt attributes.
Sampled links Broken-link findings compare sampled internal links with sampled HTTP errors. They do not prove every destination was fetched.
Unavailable content A failed fetch or persistent HTTP 429 does not establish that a page's title, description or headings are missing.

Read the Site Audit guide

Coverage is part of the result

A complete sample can still contain errors. A partial sample describes incomplete access or a budget stop, not a verdict that the entire website is defective.

Shared budgets Up to 20 HTTP requests and 15 seconds cover pages, robots reads, redirects and retries together.
Public-site scope The crawl respects applicable robots rules and restricts discovery and redirects. Query-string URLs and known nonpage assets are excluded.
Saved results Matching recent reports may be reused for five minutes. Reopening a saved report retains its original observation dates.

Revisit saved Agent Reports

What it does not do yet

This is a bounded HTTP sample, not a full-site crawl, JavaScript rendering or Lighthouse performance test.
Local indexability checks do not verify canonical correctness or actual search-engine indexing.
Robots restrictions, redirects, slow responses and rate limits can reduce coverage. Inspect state and stop reason before drawing conclusions.

Site Audit questions

Does a complete audit cover the whole site?

No. Complete means the eligible sample finished without unresolved access limitations. Page, request, time and body-size limits still apply.

Why can the result be partial?

A page limit, request limit, time limit, unreadable robots policy or unresolved fetch can leave a partial sample. HTTP 429 is incomplete access, not a missing-content finding.

Does Site Audit use a paid SEO provider?

It reads the tracked public website through the bounded HTTP crawler. It does not call a paid SERP provider. Request admission and project permissions still apply.

Next step

Keep the workflow connected

Agent Reports

Save an interpretation that carries the sample's coverage and limitations into the next decision.

Domain overview

Estimated traffic, keywords and top pages for any domain

Project Context

Business, audience, products, goals and rules for your agents

Put your next analysis in the project

Read the workflow guide, then use the same project context and saved results across the app and connected agents.

Start free

Read the workflow guide

Free and open source (AGPL-3.0). Export your data anytime, or run the same app yourself.

Start free

Find technical issues in a clear, bounded sample

Partial sample

From a bounded crawl to URL findings

Choose a sample

Read the crawl coverage

Inspect findings by URL

See the page behind the warning

Coverage is part of the result

What it does not do yet

Site Audit questions

Does a complete audit cover the whole site?

Why can the result be partial?

Does Site Audit use a paid SEO provider?

Keep the workflow connected

Agent Reports

Domain overview

Project Context

Put your next analysis in the project

Find technical issues in a clear, bounded sample

Partial sample

From a bounded crawl to URL findings

Choose a sample

Read the crawl coverage

Inspect findings by URL

See the page behind the warning

Coverage is part of the result

What it does not do yet

Site Audit questions

Does a complete audit cover the whole site?

Why can the result be partial?

Does Site Audit use a paid SEO provider?

Keep the workflow connected

Agent Reports

Domain overview

Project Context

Put your next analysis in the project