LLMs SEO2GEO
Products
llms.txt
AI-ready site structure
SEO Intelligence Live
Multi-market SEO for agencies
FAQs
Language
EN PT
Get Started
For site owners

Our crawler

Saw this agent in your access logs? Here we explain plainly who triggered the visit, what we collect, and how to request that your domain be excluded.

How we identify ourselves

User-Agent: SEO2GEO/1.0 (+https://llms-seo2geo.com/bot)

This is the primary agent. After a 401, 403, 406, or 429 response, the system may retry once with a browser User-Agent. We disclose that exception here so you can identify our traffic accurately.

Who triggers it

A user who submits the URL; we do not autonomously discover sites.

Scope

Public pages on the same domain and associated sitemaps only.

Retention

Crawl reused for 24 h; temporary files are deleted separately; the report may persist.

Network behaviour

Up to 1 simultaneous requests, a 10 s timeout per request, and no authentication.

01

What we do

We analyse a site when somebody hands us that site's address in our form. We do not discover sites on our own, we do not follow links to other domains, and we do not come back out of habit: a new request for the same domain within 24 hours reuses what we already read.

What we do with what we read

We produce an SEO diagnosis and an llms.txt file for whoever requested the analysis. We do not resell the content or use it to train models. Generated files are temporary; the report may retain URLs, titles, metadata, and audit results.

02

Limits of each visit

  • 01 At most 25 pages per analysis
  • 02 At most 1 requests in flight at once
  • 03 HTML only. PDFs, images and files are discarded without being read.
  • 04 We consult robots.txt to discover the sitemap; Disallow rules are not currently used as an opt-out mechanism.

03

Data we may record

The report is created from public content returned by your server.

  • URLs, response codes, and technical crawl information
  • Titles, descriptions, headings, text, and structured data needed for analysis
  • Scores, detected issues, and a summary of analysed pages

We do not try to access authenticated areas, submit forms, or purchase content.

04

Controls for site owners

The most reliable way to prevent future analyses is to request domain exclusion.

  1. 01

    Send the domain and, if possible, a technical contact through our contact page.

  2. 02

    We confirm the request and add the domain to the refused-destination list.

  3. 03

    For immediate containment, apply server or WAF rules and contact us in parallel.

Request exclusion through our contact page and include the domain. Once it is added to our block list, new analyses will be refused. You may also block the primary User-Agent, taking the browser retry described above into account.

Talk to us Privacy Policy Terms of Service

See the Privacy Policy for purposes, retention, and rights, and the Terms for the responsibilities of anyone submitting a URL.

Keep exploring

About the project

Learn about the product approach and principles.

What is llms.txt

Learn about the format and the context it can provide.

Request an analysis

Define the site, market and scope of your request.