A made-up site with up to 1,000,000 pages
The test website ran on the same computer, so the times show SEOSage's own speed, not a web server's. Real websites usually answer more slowly, so a real crawl takes longer.
Benchmarks and capabilities
How fast SEOSage crawls, how big a site it can handle, and whether the results are right. Every number on this page was measured, on one ordinary laptop.
Download SEOSage See all features
201,022pages crawled in one project
20 minstart to finish, on an 8 GB laptop
1.0Mfindings, every planted problem counted exactly
16 KBof memory for each page crawled
How we measured
Tested on 3 and 4 October 2026 on a MacBook Air (Apple M2, 8 GB of memory) with other apps open, the way you would use it. The 200,000-page run used a development build of SEOSage 1.105.
Problems planted on purpose
We hid known problems in the pages (missing titles, broken links, redirects and more) to check that SEOSage finds all of them and nothing extra.
The whole job, not just the fetching
Times run until the finished crawl is done, including the link and duplicate checks that run after the last page.
We tried 1,000,000 pages
10 lakh pages on an 8 GB laptop. Here is what happened, including the part that did not go well.
- The first try ran at about 270 pages a second, then hit the laptop's memory limit at about 210,000 pages after 39 minutes. The speed fell to 2 pages a second, so we stopped it.
- The cause: each crawled page was costing about 21 KB of memory. We cut that by about a quarter, and a small check was wrongly flagging test sites that run on the same computer. Both are fixed.
- The result: a complete 201,022-page crawl in 20 minutes, with the same findings as before.
At about 16 KB a page, a million pages needs roughly 16 GB of free memory. That is our estimate; we have not run it on a bigger computer yet.
Stress test site127.0.0.1:8099 · 201,022 pages
▸ Start crawlToday ›Crawl finished in 20 minutes 4 seconds
Crawled 201,022Redirects 820Blocked 0Broken 1
Pages201,022
Errors4,401
Warnings808,787201,952 notices
Indexable100%200,201 pages
Findings1.0Macross 46 checks
How long a big crawl takes
One project, no page limit, the fastest crawl speed. Total time from start until the finished crawl is ready.
The first four rows were measured inside the app (everything until the result is saved and open in your project). The 201,022-page row is the crawling engine on its own: about 15 minutes reading pages and about 5 minutes on link and duplicate checks. We have not yet opened a result that large inside the app. The window stayed usable all the way up to 100,000 pages.
What you get at the end
The numbers below are from the 201,022-page crawl. Every finding is grouped by issue type, so you work through them one type at a time.
Top issues Each one opens the list of pages
Missing Title TagPages have no title, so search engines make one up.4,000 URLs
Missing H1 TagPages have no main heading.2,000 URLs
Thin ContentPages have very little text.6,667 URLs
Missing Meta DescriptionPages have no description for search results.5,000 URLs
Page links to redirectA link goes through a redirect instead of straight to the page.820 URLs
Page links to broken pageA link leads to a page that does not exist.400 URLs
Vague link textA link says only “click here”.200 URLs
Placeholder text on pageThe page still has “lorem ipsum” dummy text.40 URLs
Are the results right?
We planted each problem on a known number of pages in the 201,022-page site. SEOSage reported every one at exactly that number.
| Problem planted | Pages with it | Reported by SEOSage |
|---|---|---|
| Missing title tag | 4,000 | 4,000 |
| Missing meta description | 5,000 | 5,000 |
| Missing H1 heading | 2,000 | 2,000 |
| Missing language attribute | 2,062 | 2,062 |
| Thin content | 6,667 | 6,667 |
| Page links to a broken page | 400 | 400 |
| Page links to a redirect | 820 | 820 |
| Vague link text ("click here") | 200 | 200 |
| Placeholder ("lorem ipsum") text | 40 | 40 |
| Slow page (over 1 second) | 39 | 39 |
The same crawl found about 1.0 million findings in total across the 201,022 pages. Most are things every page of a test site shares, such as missing social tags.
It keeps getting faster and lighter
We run these tests on every big change.
| SEOSage version | What we measured | What changed |
|---|---|---|
| 1.101.7 | 29 minutes for 100,000 pages | Before the speed-up. |
| 1.101.9 | 8 min 35 s for 100,000 pages | About 3 times faster. Stays near 300 pages a second the whole way, with identical results. |
| 1.103.1 | 8 min 1 s for 100,512 pages | More than 40 new checks running, and the time did not go up. |
| 1.105 | 395 MB instead of 504 MB for 20,000 pages | About 25% less memory per page, with identical results. This is what let a 201,022-page crawl finish on an 8 GB laptop. |
Times are for the crawling engine on its own, except where we say otherwise above. Every change is listed in the changelog.
Good to know
What affects the numbers, and where the limits are.
The website sets the pace
SEOSage can read hundreds of pages a second, but a real website that answers in a fraction of a second will not. You choose the crawl speed in the project settings, so you can stay polite to a small server.
Memory is the real limit
Plan on about 16 KB of memory for every page. That is about 1 GB for 60,000 pages, so a 200,000-page crawl needs about 3 GB and a million pages needs roughly 16 GB. You can also limit a crawl with include and exclude rules.
The duplicate check has a time limit
Comparing every page with every other page is slow on a huge site. The duplicate-content check stops after 2 minutes and reports what it found when nearly every page has a near-identical title.
What a crawl checks
Every crawl runs these groups of checks. The full list is on the features page.
Titles, descriptions and headings
Missing, too short, too long or repeated on other pages, the same as the H1, and skipped heading levels.
Links and redirects
Broken pages and links, redirect chains and loops, orphan pages, links with no text or vague text, and links to other websites.
Indexing
Noindex, nofollow, canonical tags, the sitemap and robots.txt.
Images
Missing alt text, broken images, large files and old formats.
Speed and security
Slow and large pages, compression, mixed HTTP and HTTPS content and security headers.
Languages and structured data
Hreflang tags, schema markup, Open Graph and Twitter cards.
Try it on your own site
Free for 14 days, cancel any time.
Want a different test run? Tell us on the contact page or email hello@seosage.co.