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 are the least visible cause of lost traffic: the content can be excellent while some pages are missing from the index because of a blocking directive, return a server error, or lead through a broken link. As long as these problems are not directly visible, they go unnoticed for months, with only a drop in metrics and no clear reason. A regular audit turns scattered symptoms into a concrete list: which addresses do not respond, where a redirect is broken, which pages fell out of the index. Each finding can then be dug into with a dedicated tool: indexing with the page indexation checker, redirects with the redirect checker, and the crawl rules themselves with the Robots.txt and sitemap validator.
After the first full run and fixing the problems found, it is enough to repeat the check once every month or two, or after significant changes to the site: a domain switch, a migration to a new platform, a major restructuring of sections. A daily audit is overkill for most sites – technical problems do not crop up that often.
An audit crawls the whole site and looks for systemic problems – repeated errors on pages of the same type, for example. A one-off check answers a question about one specific address and runs faster.
Nothing technically blocks the check, but the audit crawls several pages of a domain, so it should only be run on sites you own or have explicit permission to check.
No. A technical audit removes barriers that stop a search engine from processing a site correctly, but it does not replace work on content and on how relevant pages are to the queries they target.
It works through several sections of the site in sequence and checks each one from several angles, while a dedicated tool queries a single address on a single parameter.
Your first report requires no sign-up.