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.
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
We start at the URL you give and follow internal links, honouring robots.txt.
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.
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.
47 checks across 7 areas. Each links to its reference page with the test, the risk and the fix.
The ones that most often decide the grade:
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.
This scanner answers one part of the review. Continue with Tech Stack Scanner for cms, frameworks, analytics, cdn and hosting, then Common Crawl Rank for web graph centrality and pagerank positions. These are separate checks because a strong result here does not prove that the adjacent surface is healthy.
For the background behind these signals, read Website Security: What a Vulnerability Scan Looks For and How to Fix It and How to Read a Security Scan Report: Severity, False Positives and What to Fix First. The robots.txt present and usable check reference explains the exact test, evidence and remediation used in the report. The Scan.now methodology explains request limits, scan boundaries and what the scanner deliberately does not attempt.
The audit does not collapse every signal into one vague score. Findings remain grouped by the decision they support.
| Audit area | Examples examined | Question answered |
|---|---|---|
| Discovery and indexability | Status codes, redirects, robots directives, canonical targets and sitemap membership. | Can a crawler reach and index the intended URL? |
| Search presentation | Titles, descriptions, headings and structured data. | Can a search engine understand and present the page clearly? |
| Content signals | Main-text length, repeated titles, heading structure and language annotations. | Does the page provide a distinct and coherent subject signal? |
| Link architecture | Internal links, broken targets, incoming-link counts and sitemap-only pages. | Can users and crawlers navigate to important content efficiently? |
| Media and delivery | Image alternative text, response size, timing and render-blocking clues. | Are accessibility and delivery problems weakening the page experience? |
Fix blockers first, then repeated templates, then page-specific improvements.
The sampled pages expose no major crawl or metadata failure in the tested area. Track later crawls because content and templates change.
Blocked important URLs, broken canonicals, server errors or a repeated template defect can affect many pages and deserve priority.
Length and wording checks identify pages worth reviewing. They do not decide content quality or search intent by themselves.
Background reading written to go with these results.
13 min read · Updated Sep 13, 2026
Website Security: What a Vulnerability Scan Looks For and How to Fix It
A website vulnerability scan checks the parts of a site an attacker can reach without logging in: Transport security, HTTP headers,...
Read the guide
9 min read · Updated Sep 18, 2026
How to Read a Security Scan Report: Severity, False Positives and What to Fix First
A scan report is a list of findings with severities, and the hard part is deciding what matters. How severities are assigned, how to...
Read the guideAs 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.
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.
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.
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.
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.
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.
Sign up free to keep scanning
You have used today's scans without an account. Creating one is completely free — no card and no plan needed — and it takes one click with Google.
We ask Google for your email address and nothing else. Without an account, the browser and password checks keep working, and your free scans come back tomorrow.