Skip to content
Free technical SEO tools

Find what stops Google
from reading your pages.

Plenty of problems that look like content problems start lower down: a blocked folder, a redirect loop, text that only appears after JavaScript runs. These free tools check each layer and tell you what to change.

  • No sign-up
  • Corrected files to copy
Robots.txt Validator result for our own robots.txt: the rules for each crawler and the sitemap it lists

Where technical problems hide

None of these show up when you look at your site in a browser. That’s why they can go unnoticed for months.

1

robots.txt blocks more than you meant

One wrong Disallow line can hide a whole folder of pages from Google. It happens most often after a redesign or a move to a new platform.
2

Redirects that chain or loop

Each extra hop slows the page and loses a little of what links pass on. A loop stops Google completely. Old .htaccess files often carry rules nobody remembers adding.
3

Content Google never sees

When text, links or prices load with JavaScript, Google sees them later, or not at all if the script fails. Comparing the raw HTML with the rendered page shows you what’s at risk.
4

Pages too heavy to load fast

Unused CSS, code that was never minified and files that block the first paint slow a page down, most of all on phones. Slow pages lose visitors, and Google takes page experience into account.

Check your site in this order

  1. Check the crawl rules

    Paste your robots.txt into the validator. Fix anything that blocks pages you want found, and make sure it lists your sitemap.
  2. Check the redirects

    Paste your .htaccess file into the analyzer and test your key addresses. Every old address should reach its new page in one hop.
  3. Check the rendering

    Run the Render Analyzer on a page that matters. Move anything that only appears after JavaScript into the HTML.
  4. Trim the page

    Run the HTML & CSS Analyzer and remove what the page never uses. Then check the whole page with the SEO Health Dashboard.

Read the guides

Guide

Crawl budget

Why search engines skip some of your best pages, and how to point them at the ones that matter.
Read the guide
Guide

Core Web Vitals audit

How to measure loading, response and layout shift, and what to fix first.
Read the guide
Guide

Reading a technical audit

What each part of a technical SEO report means, step by step.
Read the guide

Want it done for you?

Some fixes are copy and paste. Others need someone who can change your templates and server setup. That’s the work we do.

Service

Technical SEO

We fix crawling, indexing, speed and site structure at the source, then confirm each fix in Search Console.
See the service
From $997

Core Web Vitals rescue

We find what slows your site, fix LCP, INP and CLS, and show the change in a before-and-after report.
See the product
Service

SEO-safe site migration

Changing platforms or domains? Every address mapped and redirected, with rankings checked before and after.
See the service

Technical SEO questions

Each tool checks one layer, on one page or one file. A full audit crawls the whole site and connects the problems, for example a redirect rule behind a drop in indexed pages. Start with the tools. If the results don’t explain what you see in Search Console, an audit will.

Not always. The Robots.txt Validator and the .htaccess Analyzer give you a corrected file to copy. Rendering and speed fixes usually need someone who can edit your theme or templates.

Yes. The .htaccess Analyzer works in your browser. The file isn’t sent to our server or stored.

After any redesign, platform move, new plugin or new redirect rules, and once a quarter otherwise. Most technical problems arrive with a change somebody made.

Check a page for 40+ problems at once.

The SEO Health Dashboard checks the server, crawl rules, schema and AI crawler access, and puts the fixes in order.

Start with SEO Clarity. You get a full audit of your site and a 30-day action plan, from $497.