Crawlability tools
One crawl answers five separate questions. Each has its own page here, so you can send a colleague the redirect chain without making them read the rest of the report.
-
robots.txt tester
Match one URL against your live robots.txt for ten crawler tokens at once, and see the rule line that decided each answer.
-
llms.txt validator
Fetch llms.txt and llms-full.txt, check the heading, the summary line, the sections and the links, and catch a file served as HTML.
-
Redirect chain checker
Follow every hop from the URL you enter to the page that answers, with the status code on each one and a flag for loops.
-
JavaScript rendering test
Compare the raw HTML against the rendered page and count what only appears after the scripts run.
-
Structured data check
Count the JSON-LD blocks on the page, report how many parse, and list the types a search engine would read.
Why five pages instead of one
Most of the time you already know which answer you want. Somebody changed the robots.txt and the traffic moved, or a marketing page went client rendered and stopped showing up. A single page with six cards on it makes you scroll past five answers to read one.
The engine behind each tool is the same. seoder fetches the URL once without running scripts, once in a browser engine, and once per crawler in the matrix with that crawler's own user agent string. The checks differ only in which part of that result they put on screen. A verdict you get from the redirect page is the same verdict the full report gives, measured the same way, in the same run.
Start with the full report when you are not sure
These checks interact. A page blocked in robots.txt has no rendering verdict worth reading, because nothing compliant fetched it. A redirect chain that ends on a 404 makes the structured data count zero for a reason that has nothing to do with your markup. When the symptom is vague, run the full report first and follow whichever card looks wrong.
Every verdict on this site is measured rather than inferred, and the method page says exactly how, including request counts, timeouts and the things the tool refuses to do. If a result surprises you, read that page before you change anything on your server.
Common questions
What is the difference between these and the full report?
Nothing in the measurement. Each tool runs the same fetch and shows one part of the answer, so a narrow question gets a short page instead of six cards. The home page shows all of it at once.
Do the tools need JavaScript in my browser?
No. Each form posts to the checker and gets back a page rendered on the server. With scripts on, the report lands in place and the URL stays put, which is the only difference.
Is there a limit on how often I can run a check?
Yes, per address and per target host, so nobody can point the tools at one site all day. A repeat check of the same URL inside a short window may return the previous result.