One job, done thoroughly

Why it exists

Most SEO tools give you a score. A number out of a hundred, a coloured dial, and a list of category names — with no way to get from any of it to the file you have to edit. So the report gets skimmed, filed, and never acted on.

PixyScan is built the other way round. Every finding names the check, the URLs that fail it, and what was found on each one. The score exists to show a trend, not to be the answer.

How it works

The crawler starts at your site's address, reads robots.txt and your sitemaps, and follows internal links within the limits you set. For every page it fetches it runs 112 checks across 14 groups — on-page SEO, HTML head tags, structured data, images, links, crawl behaviour, security headers, international SEO and AI-crawler directives.

It reads the HTML your server returns and does not execute JavaScript. That is a deliberate choice: a search crawler sees that HTML first, and several checks exist precisely to catch metadata that only appears once JavaScript has run.

What it deliberately does not do

• Page speed. No Lighthouse, no Core Web Vitals, no performance score. Use PageSpeed Insights or your RUM provider — they do it properly, and PixyScan would only do it badly.
• Alerting. Nothing emails you when a scan finds a regression. Scheduled scans keep the data fresh and scan history shows what changed, but delivery is not built and we are not going to imply otherwise.
• Rank and keyword tracking. PixyScan looks at your site, not at search results.
• Compliance badges. No SOC 2, no ISO 27001. Your data is scoped to your workspace and visible only to the people you invite — that is a statement about access control, not a certification.

When a check gets it wrong

We would rather hear about it than have you work around it. Every guide in the help centre says how that check is evaluated, so you can tell a real finding from a misfire — and tell us when it is the latter.