Crawl a Website and Find Every SEO Problem

Crawls your site the way a search engine does, following internal links and your sitemap, and reports everything holding it back: missing, short, long and duplicate titles; thin main content; indexability, descriptions, headings, broken and orphaned links, image alt text, speed, structured data and international targeting. It is a sample rather than a full crawl, and the report says which fraction of your site it covered.

A sample, not a full crawl: We start at this URL, follow internal links and read the sitemap, up to the page budget you choose. On a large site that is a fraction of the pages, and the report says which fraction. How we scan · Acceptable use

How it works

  1. Enter your site

    We start at the URL you give and follow internal links, honouring robots.txt.

  2. Up to your chosen budget is crawled

    30, 100 or 250 pages, seeded from your entry point and your sitemap. Each is recorded with its status, redirect chain, timing, size, headings, links and metadata.

  3. Read the issues, most serious first

    Short or overlong titles and thin main content are labelled as review signals; site-wide problems such as duplicate titles and orphan pages only appear across a crawl.

What this tool checks

47 checks across 7 areas. Each links to its reference page with the test, the risk and the fix.

Full reference

Titles, headings and content

13 checks

Indexing and crawlability

10 checks

International targeting

3 checks

Links and site structure

7 checks

Images and page weight

3 checks

Structured data and social

4 checks

Technical SEO and speed

7 checks

The ones that most often decide the grade:

What a multi-page SEO audit measures

The crawler combines page-level checks with site-wide patterns that cannot be seen from a single URL.

Technical SEO is partly about individual pages and partly about relationships across a site. A missing title is visible on one page, while duplicate titles, orphaned sitemap URLs and inconsistent canonicals appear only when many pages are compared. The audit preserves both levels of evidence.

Scan.now begins with the entered URL, follows same-site links, reads sitemap URLs and honours robots.txt until the selected page budget is reached. Each response is recorded with indexability, metadata, headings, main-content signals, links, images, structured data, language annotations, size and timing. The report states coverage instead of implying that a bounded sample represents the whole site.

Discover URLsCombine the start page, internal links and sitemap entries.
Inspect every pageRecord indexability, metadata, content, links, media and technical signals.
Compare the crawlFind duplicates, orphans and recurring template-level problems.

SEO audit sections and the questions they answer

The audit does not collapse every signal into one vague score. Findings remain grouped by the decision they support.

Audit areaExamples examinedQuestion answered
Discovery and indexabilityStatus codes, redirects, robots directives, canonical targets and sitemap membership.Can a crawler reach and index the intended URL?
Search presentationTitles, descriptions, headings and structured data.Can a search engine understand and present the page clearly?
Content signalsMain-text length, repeated titles, heading structure and language annotations.Does the page provide a distinct and coherent subject signal?
Link architectureInternal links, broken targets, incoming-link counts and sitemap-only pages.Can users and crawlers navigate to important content efficiently?
Media and deliveryImage alternative text, response size, timing and render-blocking clues.Are accessibility and delivery problems weakening the page experience?

How to prioritise SEO findings

Fix blockers first, then repeated templates, then page-specific improvements.

Healthy sampled pattern

The sampled pages expose no major crawl or metadata failure in the tested area. Track later crawls because content and templates change.

Indexing or site-wide problem

Blocked important URLs, broken canonicals, server errors or a repeated template defect can affect many pages and deserve priority.

Editorial review signal

Length and wording checks identify pages worth reviewing. They do not decide content quality or search intent by themselves.

Turn the crawl into an SEO work plan

  • Resolve indexability, canonical, redirect and server-error problems before rewriting metadata.
  • Fix repeated issues in the shared template rather than editing hundreds of pages individually.
  • Use affected URL lists to assign work and verify each pattern in a follow-up crawl.
  • Increase the crawl budget when the reported coverage leaves important directories unsampled.

What this result does not prove

  • The audit is a bounded sample and explicitly reports its coverage of discovered and sitemap URLs.
  • JavaScript is not executed, so client-only content may look absent in the server response.
  • Automated checks cannot judge usefulness, expertise, intent satisfaction or whether a page deserves to rank.

Guides for this tool

Background reading written to go with these results.

Frequently asked questions

How many pages do you crawl?

As many as the budget you pick: 30, 100 or 250. Breadth-first from the URL you enter, plus URLs taken from your sitemap, honouring robots.txt throughout. On a large site that is a small sample, and the report states the percentage it covered rather than implying it saw everything. The point is to find the patterns your templates repeat, which a sample shows perfectly well.

Is this the same as Lighthouse?

It overlaps deliberately. Lighthouse audits one page in a real browser and measures rendering; this crawls many pages and finds the problems that only exist across a site. The per-page SEO audits here follow Lighthouse's, and the crawl-wide issue model follows SEOnaut's.

Will the crawl slow my site down?

No. Requests are paced, run four at a time at most, and stop at the budget you chose. Even at 250 pages it is a fraction of the load a search engine crawler places on the same site in a day.

Do you run JavaScript?

No. We read the HTML the server sends, which is what a crawler indexes first. If your content only exists after hydration, this scan shows you what a crawler sees before it runs your scripts, which is usually the more useful view.

Can it find orphan pages?

Only where you have a sitemap. Following links can reach nothing but linked pages, so a crawl on its own can never find a page with no links to it. We seed the crawl with sitemap URLs and report the ones that turned out to have no inbound link from any page we saw. Without a sitemap the check is skipped rather than passed, because passing it would mean claiming something we did not test.

Why does word count matter?

It does not, on its own. It is a proxy for whether a page covers its subject, and it is reported so you can look. A 90-word contact page is fine; ninety 90-word pages generated from a template are the pattern search engines act on.