How the Website Visibility Check works

What it fetches

When you submit an address, our server makes at most five requests to that website: the page itself (following up to five redirects), /robots.txt, /sitemap.xml (or the sitemap declared in robots.txt), /llms.txt, and the plain http:// address to see whether it redirects to HTTPS. It identifies itself as EvyVisibilityLab/1.0. It never submits forms, logs in, or executes the page’s JavaScript.

What it reports

Only what the responses show. Each finding names its evidence — a tag, a header, a robots rule, a measured number — so it can be checked independently. Severity reflects the likely effect on being found and chosen; it is a judgement, labelled as such, not a score.

What it cannot observe

• Rankings, impressions and traffic (these need Search Console access).
• Whether AI assistants currently cite the site.
• Core Web Vitals from real visitors; our timing is a single server-side measurement.
• Content that appears only after JavaScript runs.
• Pages other than the one checked.

Who builds it

The Lab is built and run by EVYCOMPANY. We use it in our own client work; if you want the findings implemented, see the AI Visibility + Conversion Sprint.

Safety

The checker only contacts public internet addresses on standard web ports. Private, local and reserved network addresses are refused, and every redirect is re-checked.