SomethingClicksBot

If you found this page from a line in your server logs, this is the whole explanation. Something fetched a few pages of your website and left this address behind so you could find out what it was.

That is the only user agent we send, on every request, with no exceptions and no fallback to anything else.

What it is

A scanner. It asks your server for a page over HTTP and reads what comes back in the HTML: your business name, address, phone number, opening hours, structured data, the links between your pages, and the fields on a contact or booking form.

It does not run JavaScript. It does not fill in or submit forms, log in, sign up, or place an order. Every request is a plain GET, and it writes nothing to your site. It reads the pages, scores four things about them, and stops.

Who runs it

Something Clicks. We check whether AI systems can find, understand and act on a local business’s website, then fix what is broken. This scanner is the checking part. There is more on the About page, and the How It Works page covers what happens after a scan.

Why it fetched your site

Because a person entered your web address into the scan form on this site and asked for a report on it. Usually that is the owner, or somebody working on the site for them.

It is not a continuous crawl and it does not come back on its own. One scan fetches:

• Your homepage.
• Up to three more pages it recognizes as important — a services, contact, booking or about page, found from the links on your homepage.
• Your /robots.txt.
• Your sitemap, if robots.txt or your homepage points at one.

Then it is done. The whole scan is capped at eight seconds and each single request gives up after five, so if your server was slow that day, it left rather than retried.

It never pretends to be another crawler

The scanner refuses to start if the user agent it is configured with contains any of these names:

Googlebot · Bingbot · GPTBot · OAI-SearchBot · ChatGPT-User · ClaudeBot · Claude-SearchBot · Claude-User · anthropic-ai · PerplexityBot · Applebot · DuckDuckBot · YandexBot · Baiduspider · Slurp

The point of the scan is measuring how those crawlers see a site. Borrowing one of their names to find out would make every answer in the report untrue, so the check is a hard stop rather than a policy.

When a report says whether Googlebot or ClaudeBot can reach a page, that is read out of the rules in your own robots.txt. It is never established by sending their user agent.

If you would rather we did not

Blocking the user agent SomethingClicksBot at your server, CDN or firewall works. We will not switch to a different string to get around it — that is the same impersonation the check above exists to prevent.

Being straight about one limitation: a Disallow rule aimed at SomethingClicksBot in your robots.txt does not stop a scan today. A scan runs because someone asked for one on their own site, so the scanner reads robots.txt to report on what it says rather than checking it before fetching. If that matters for your site, tell us — the contacts below reach a person.

Reaching a human

No form, no ticket queue.