Tool 08 / Technical

Technical SEO Checker.

Three checks every technical audit starts with: can Google crawl it, can Google find it, and how fast does it load.

Robots and sitemap checks run in your browser. The PageSpeed tab sends the URL you test to Google's PageSpeed Insights API.

Group applied

Matching rules (longest wins)

    How to use it

    Three steps. No signup.

    1. 01

      Robots.txt: paste your file, enter a path or URL and a user-agent, and see whether it's allowed — with the exact rule that decided it.

    2. 02

      Sitemap: paste your sitemap XML to check it parses, count URLs and see how many have a lastmod date.

    3. 03

      PageSpeed: enter a URL and run a mobile test. You can add your own free Google API key, but it's optional.

    FAQ

    About this tool.

    Something else on your mind? Ask us on WhatsApp.

    How does the robots.txt tester decide?

    It follows Google's rules: the most specific user-agent group applies, the longest matching path rule wins, and when an Allow and a Disallow match with equal length, Allow wins. Wildcards (*) and end anchors ($) are supported.

    Why doesn't the sitemap check test status codes?

    Checking whether each URL returns 200 needs a server-side crawler, because browsers can't fetch other sites freely. This check covers structure, URL count and lastmod coverage.

    Do I need a PageSpeed API key?

    No. Tests run on this site's key. If you add your own key, it's stored only in your browser's local storage and sent only to Google's API — restrict it to the PageSpeed Insights API in Google Cloud Console for extra safety.

    30-minute strategy call · $10

    Ready to plot your ranking trajectory?

    Tell us about your site and goals. We'll map the links, content and timeline you need, then send a custom quote.