What we do when
we visit your website

Wakaris analyzes public web pages and explains what it observes across nine areas. An analysis is requested by a person entering a URL; Wakaris doesn’t crawl the internet on its own or build an index.

Each analysis fetches the page just like a browser would, renders it and runs a set of read-only checks: HTTP headers, HTML, loaded resources, load times, markup, visible text and public files such as robots.txt, sitemap.xml and llms.txt. The result is a report of findings, each with the evidence that backs it up.

The user-agent and IP are shown above. If they change, they are updated here before they go into use.

If you see that user-agent in your logs, someone has asked Wakaris to analyze that page. We don’t know or share who, unless that person decides to share the report.

In terms of requests, analyzing one page is the same as one visit with a browser: the page and the resources it loads, plus the public files that get checked.

If the page doesn’t respond or returns an error, the analysis stops and the report marks it as “no pulse”.

Wakaris reads your robots.txt and follows what it says for WakarisChecker, and also the * group if you don’t name us.

With one nuance worth knowing, because it’s where we differ from a crawler: the specific address a person pastes to analyze is fetched anyway, because they asked for it —the same approach as PageSpeed—. What robots.txt stops is us looking for other pages on your site. If you want to cut it off completely, block the user-agent on your server or firewall, or ask us to exclude you.

If you can’t edit robots.txt, or you want to exclude one specific page rather than the whole domain, add this tag to the page’s <head>:

When the analysis finds it, it stops and doesn’t produce a report for that page. It only affects the page that carries it; to exclude the whole domain, use robots.txt or the contact form.

If you’d rather your website couldn’t be analyzed on Wakaris, you have three options, from fastest to slowest:

1. The meta tag above, on each page you want to exclude. Immediate, and no server access needed.
2. The robots.txt rule, for the whole domain. Immediate.
3. The contact form, if you can’t do either, giving the domain and a way to check that you manage it. We’ll confirm with your reference number once it’s done.

For each analysis we store what’s needed to show the report to whoever requested it: the URL, the date, the HTTP response, the rendered page, the loaded resources and the results of the checks. We don’t store form content or any data the page doesn’t expose publicly. Details on retention and processing are in the privacy policy.

If a client shares a Wakaris report with you, you’ll see each finding with its evidence: what was measured, the value obtained and the reference value. Wakaris explains; it doesn’t dictate how you should work. Findings are observations about what the page exposes at the time of the analysis, and you can mark any that don’t apply as a false positive.

This document is updated whenever the user-agent, the IP or the behavior of the analysis changes.

• September 17, 2026 · First version.