Disclaimer

01Findings are observations, not advice

PixyScan reports automated observations about the HTML your server sends and the files it publishes. The written guide attached to each check is general technical guidance, not professional, legal or financial advice, and acting on it is your decision.

02No ranking or traffic promise

We do not promise any search ranking, any amount of traffic, or any appearance or citation in a search engine or AI answer engine. Nobody can, and a tool that says otherwise is selling something. Search engines and AI systems decide those things using signals we neither control nor have access to.

If you connect Google Search Console, PixyScan can measure how the pages a detected change touched did in search afterwards, compared with the rest of your site, and alert you when clicks drop after a deploy. These are comparisons of the figures Google reports, not findings about cause: search traffic moves for many reasons, including seasonality and Google's own updates, so a result can show a difference the change did not cause, or miss one it did.

03What the scan does not measure

So that nothing here is inferred from silence, PixyScan does not measure or report on any of the following:

• Traffic, conversions or revenue. Nothing is connected to Google Analytics.
• Search clicks, impressions or positions of its own. If you connect Google Search Console, from the Basic tier up, PixyScan shows the figures Google reports for your site, as Google reports them, on its Search performance screen and beside your scans. Scan findings and the health score do not use them.
• Keyword rank tracking, search volume, backlinks or competitor data.
• Content quality, accuracy, originality or plagiarism. Readability is a formula, not an opinion.
• Anything that only appears after JavaScript has run, unless the site is set to the browser engine - the default engine reads the HTML your server sends, and the browser engine is a Pro entitlement.
• Accessibility conformance. Some checks overlap with accessibility practice; none of them constitutes a WCAG audit.

04Accuracy and completeness

A scan reflects what was reachable at the moment it ran. Pages behind authentication, blocked in robots.txt, excluded by your own crawl rules, or beyond the page budget will not appear in the results, and their absence is not a statement that they are correct.

Checks can produce false positives and false negatives. If you find one, tell us - that is how the catalogue gets better, and it is why two checks were retired in August.

05External links

This website and the application link to third-party sites we do not control. We are not responsible for their content, their availability, or their policies.