Pages with a 4xx code
/promo/2023 → 404Robots and visitors reach a page that does not exist, and crawl time is wasted.
Replace the links with working ones or set up a 301 redirect.
Enter an address. We crawl the pages, find technical errors and show where each one is, why it matters and how to remove it.
Example: fictional site
This is the real auditor interface on a demo site.





Demo report: the site, issues and assistant dialog are fictional.
A domain or a specific page will do. No sign-up needed.
We collect pages through links and the sitemap. The server load is low: up to 2 requests per second.
The check runs in the background. The result is available in the browser, as PDF and CSV.
116 issue types in 11 categories. The report also shows domain data, speed and AI readiness.
Check your siteTitle, description, H1: missing, length, duplicates.
HTTP and HTTPS, www and non-www, version consolidation.
4xx and 5xx codes, redirects, robots.txt blocks.
Noindex, canonical and conflicts between them.
Availability, format and wrong URLs in the sitemap.
Pages without inbound links, broken links, anchors.
HTTPS, mixed content, external links.
Thin pages, duplicates and placeholder text.
Alt, dimensions, broken and oversized files.
Hreflang: language codes, reciprocal links, x-default.
Presence of structured data on pages.
A few examples from the catalog. The report explains every issue it finds this way.
/promo/2023 → 404Robots and visitors reach a page that does not exist, and crawl time is wasted.
Replace the links with working ones or set up a 301 redirect.
/old → /old/ → /new/Several hops in a row slow down loading and complicate crawling.
Set up a direct redirect to the final address.
/sale/ · noindexThe sitemap asks to index the page while the meta tag forbids it.
Remove the page from the sitemap or drop noindex.
canonical → 404You name a main address for search engines that does not open.
Point canonical to a working URL with a 200 code.
title × 11Pages with the same title are harder to tell apart in search results.
Give each page a unique title.
https → http://…/logo.pngAn HTTPS page loads files over HTTP, and the browser may block them.
Move all resources to HTTPS.
A site can look great to Google and still be closed to AI crawlers. The audit shows this with a separate score.
We check technical readiness: robots.txt rules, text in the source HTML and markup. This does not guarantee a place in AI answers.

See what holds your site back without deep SEO knowledge: explanations are in plain language, and you can ask the AI about anything unclear.
Get the technical picture fast: URLs and actual values for every issue, plus CSV export for your own work.
Show clients the issues and the results of your work: PDF, a public report link and a comparison with the previous audit.
Start without signing up. For a large site, the limit can be raised.
20 pages
50 pages
500 pages
Technical errors quietly cost traffic: a page can have great content and still stay out of the index because of noindex, return a server error or hide behind a redirect chain. Such problems stay invisible for months while the numbers drop. An audit turns scattered symptoms into a concrete list: which addresses do not respond, where a redirect is broken, which pages are closed to search and how to fix it.
Up to 20 pages without signing up and up to 50 with a free account. On a paid plan, one audit covers up to 500 pages. You choose how many pages to check this time with the slider under the address field.
A small site is usually checked in a few minutes. One audit is limited to 10 minutes without signing up, 30 minutes with a free account and an hour on a paid plan. You can close the tab: the check continues in the background and the report is saved.
No. We send no more than 2 requests per second and follow robots.txt by default, so a typical site will not notice the load. If you need to check closed sections of your own site, robots.txt can be ignored with the switch under the address field.
Start with the “What to fix” block: it collects the three issues that affect the score the most. Then go by severity: errors first, then warnings and notices. Each issue card has an explanation, instructions and a list of addresses, and you can ask the AI assistant about anything unclear. The report exports to PDF and CSV, and a public link can be shared with your developer.
After the first run and the fixes, checking once every one or two months is enough, plus after noticeable changes: a release, a move to a new CMS or domain, or a restructuring of sections. A repeat audit is compared with the previous one and shows which issues are gone and which are new.
An audit crawls many pages and finds problems between them: duplicate titles and content, pages without incoming links, sitemap and mirror errors. For a question about one specific address, focused tools are faster: HTTP status checker, page indexation checker or robots.txt and sitemap validator.
Technically nothing blocks the check, but the audit crawls several pages of the domain. Run it on your own sites or on those you have permission to check, such as a client’s site.
This cannot be guaranteed: rankings also depend on page content, links and competitors. The audit removes technical obstacles that stop search engines from crawling, indexing and showing the site properly. It is the necessary foundation, not a replacement for work on content.
Your first report requires no sign-up.