Contact
Contact
How to reach LLMention: corrections to a score, audit requests, privacy requests and press. A real address, answered by the person who maintains the tool.
One address for everything, read by the person who maintains the tool. Audit requests get a reply within one business day; everything else as fast as it can be answered properly.
A score you believe is wrong
The most useful message you can send. Say which check and which URL; the full method is public so a disagreement can be specific, and a wrong check gets fixed rather than argued about.
Report a wrong score →A manual audit
Send the pages you care about. You get a reply within one business day with a scope note, and no payment is taken before you agree to it. The scope and price are on the pricing page.
Request an audit →A data request
Access, correction, deletion or an objection under the GDPR, or a scan result page you want taken down. No form is needed and you do not have to give a reason.
Make a data request →Anything else
Press, corrections to a guide, or a question about the method. If a claim on this site cannot be sourced, that is worth knowing and worth reporting.
Send a question →There is no contact form
Deliberately. A form would mean storing your message on a server that otherwise keeps nothing about visitors, which would contradict the privacy policy for no real benefit. Email also means you get a copy of what you sent and a reply you can keep.
Who you are writing to
LLMention is an independent project, not a company with a support desk. Who maintains it, what it deliberately does not do, and where the source lives are all on the about page. If a claim on this site cannot be traced to a source, or a check produces a result you believe is wrong, that is the message worth sending.
What not to send
Please do not send credentials, API keys, personal data about other people, or anything confidential. Nothing in the product needs it, and email is not a secure channel for it.
Other pages that may answer it faster
- Methodology — every check, its weight and its exact rule, including what the score cannot see.
- Pricing and the refund policy — what the paid audit covers and when it is refunded.
- Guides — how to allow AI crawlers, deploy an llms.txt file, and add the structured data.
What to send, and what happens next
One address handles everything, so here is how to make a message easy to act on.
| Reason for writing | What to include | What comes back |
|---|---|---|
| A score you think is wrong | The check id and the URL | The check is fixed, or you are told why it stands |
| An audit request | The pages you want reviewed, up to five | A scope note with the price and your withdrawal rights, before anything is charged |
| A data request | Which right you are exercising | A reply within one business day |
| Anything else | As much or as little as you like | A reply from the person who maintains the tool |
Questions about contacting us
What should I send if I think a score is wrong?
The check id and the URL. The method is published precisely so that a disagreement can be specific, and a check that is wrong gets fixed rather than argued about.
How quickly is a message answered?
Within one business day for anything about a score, an audit request or a data request. There is one inbox rather than a routing form, so nothing lands in a mailbox nobody reads.
Can I request a re-scan of a page I have fixed?
Yes, and there is no queue to join: run the scan again. Scores are produced per request and nothing is cached between runs.