RecometricBot

What it is

RecometricBot is the crawler operated by SEOKLIKK Kft. for Recometric, a tool that measures how often a local business is recommended by AI assistants. It identifies itself with a user-agent starting RecometricBot/1.0 and a link back to this page.

Why it requested your page

Somebody entered your website address into Recometric. That is usually the site owner measuring their own visibility, but it can also be a Recometric customer who listed you as a competitor they want to be compared against.

When that happens we make an ordinary HTTP request to the address and read its public content: the title, the meta description, the headings and the visible body text. That text is used to work out what the business does, so the questions we put to the AI assistants describe the right kind of business, and to run a technical audit of the page.

What it does not do

• It does not crawl your whole site. A measurement makes a small number of requests to the address that was entered, not a walk of every page.
• It does not sign in and does not try to. We request only what is reachable without credentials, and we do not attempt to bypass any access control, paywall or rate limit.
• It does not submit forms, click through checkout or write anything. Every request is a read.
• It is not an AI training crawler. We do not collect your pages to train a model. The text is used for that one measurement and stored with its result.

How to block it

1. At your own server or CDN. Block or deny requests whose user-agent contains RecometricBot. That happens on your own infrastructure before we ever see a response, so it works immediately and does not depend on us honouring anything you publish. A blocked request is simply recorded as a page we could not read; nothing is invented in its place, and no measurement is fabricated from a page we did not fetch.

2. Ask us. Write to us at hello@recometric.ai or through the contact page and tell us which domain. Include the log line if you have it, so we can match the request. This is the path that works even if you cannot change your own server or CDN configuration.

Rate and timing

Requests are driven by customer activity, not by a schedule of ours: they happen when a scan runs for a business whose address points at your site. Each request times out quickly and we do not retry aggressively, so the load on your server is comparable to a handful of ordinary visitors.

The rules around all of this

Section 5 of our Terms sets out what we fetch and requires the person entering an address to be entitled to submit it. Our Privacy Policy lists what we collect and every processor the fetched content is shared with.