Privacy Policy — alexturik AEO Checker
alexturik AEO Checker analyzes the active tab to evaluate how ready a page is for AI crawlers. This page describes exactly what it processes, and what it never sends anywhere.
Last updated: 2026-08-09
alexturik AEO Checker is a Chrome extension that analyzes the active tab's HTML to evaluate optimization signals for AI crawlers (GPTBot, ClaudeBot, PerplexityBot, and similar). This page describes what data the extension processes and how.
What we do not collect#
The extension does not collect, transmit, store, sell, or share any personally identifiable information, browsing history, page content, URLs you visit, or analytics events. There is no remote server, no account system, and no third-party tracking embedded in the extension.
There is no telemetry of any kind — not even anonymous usage counts. The extension has no code path that makes a network request to a server I control, which is a stronger statement than a promise not to use one.
What happens when you scan a page#
When you click the alexturik AEO Checker icon, the extension reads the active
tab's HTML and headers entirely within your browser to compute the AEO Score.
It also performs same-origin requests to the page's /robots.txt and
/llms.txt files for the same purpose. All processing happens locally; the
results are displayed in the popup and discarded when the popup closes.
Concretely, one scan reads:
| Source | Used for |
|---|---|
| The page's rendered DOM | Title, meta description, headings, JSON-LD, alt text |
| Response headers | X-Robots-Tag, content type, canonical Link |
/robots.txt on the same origin |
Which AI crawlers are allowed |
/llms.txt on the same origin |
Whether a machine-readable site map exists |
Nothing from that list is retained. Closing the popup destroys the result; there is no history view, and re-opening the popup re-runs the scan.
Storage#
The extension uses no chrome.storage, no cookies, no IndexedDB and no
localStorage for page data. If a future version stores anything, it will be
your own display preferences, kept locally on your machine, and this policy
will be updated before that version ships.
Outbound links#
"Read more" buttons in the popup link to articles on alexturik.com. These links include UTM parameters so the website's analytics can attribute traffic to this extension. No personal data is transmitted — only standard campaign tags. The destination site's own privacy policy applies once you click through.
Permissions used#
- activeTab — to read the DOM of the tab you explicitly invoke the extension on, on user gesture only.
- scripting — to inject the analysis function into that tab when you open the popup.
The extension deliberately does not request broad host permissions such as
<all_urls>. Without them it cannot read a page until you click its icon on
that page, so it has no technical ability to observe your browsing in the
background.
Children#
The extension is a developer tool with no content directed at children and no mechanism for collecting information from anyone, including children under 13.
Changes to this policy#
Material changes will be reflected here with an updated date at the top of the page, and — where the change affects what the extension processes — in the release notes on the AEO Checker page.
Contact#
Questions: mail@alexturik.com
FAQ#
Does the extension send the pages I visit to a server?#
No. There is no server. The analysis runs in your browser, the result is shown in the popup, and it is discarded when the popup closes. The extension contains no code that transmits page data anywhere.
What does it do with my robots.txt and llms.txt?#
It fetches them from the same origin as the page you are scanning, reads which AI crawlers are allowed and whether a machine-readable index exists, and folds that into the score. The files are public by definition and the responses are not stored.
Does it work on pages behind a login?#
Yes, because it reads the DOM already rendered in your tab. That is also why it never transmits anything: a tool that could read an authenticated page and also phone home would be a credential-exfiltration risk, so it does not phone home.
Which permissions does it request, and why so few?#
Only activeTab and scripting. Together they let the extension read a page
after you click its icon on that page, and nothing else. It does not request
<all_urls>, so it cannot observe browsing in the background.