FAQs

Keep them. Those are research tools — they tell you what to go after. They will not tell you that last night's deploy dropped the canonical off your category pages. PixyScan watches the site you already have and tells you what changed since it was last fine. Different job, works alongside.

An audit is checking for smoke once a year. This is the smoke detector. A single audit gives you a list you will mostly already know; the value here is the second scan and every one after it, because that is when a finding means something changed.

The crawl, yes. What a script does not have is memory of your last ninety deploys, a maintained library of 113 checks as Google shifts, or the judgement to separate a real regression from a cosmetic change. And somebody owns it forever. That is what you are paying us for.

Most teams do not — until a release introduces one and nobody is watching. Connect one site free and leave it for two weeks. If nothing worth knowing turns up, walk away.

No. PixyScan is an SEO crawler, not a performance tool. It does not run Lighthouse and does not report LCP, INP or CLS. Use PageSpeed Insights or your RUM provider for those.

Not yet, and we are not going to pretend otherwise. Today you see regressions when you open a scan: the comparison against the previous run on the same branch is waiting for you, and scan history keeps every run. Notification delivery is the next thing on this list, not a shipped feature.

Partly, and here is the exact line. You can trigger a scan from CI with a per-site token, poll it, and read a result that includes a pass/fail against your score threshold — enough for your pipeline to fail the build. What does not exist is a GitHub app that posts a comment on the pull request or blocks the merge itself. Your script makes that call.

PixyScan reads the server-rendered HTML, which is what a crawler sees first. That is deliberate: several checks exist precisely to catch metadata that only appears after JavaScript runs. If your title is injected client-side, PixyScan will tell you.

Yes — that is what branches are for. Every scan records the branch it ran against, and a scan is only ever compared with the previous scan on the same branch. A preview run never becomes production's baseline.

Per site. Not per credit, so re-scanning costs nothing extra and you never hesitate before checking. Not per seat, so invite everyone — the tool is more useful the more people watch it.