Talk to a human, not a ticket queue.
Whether you have a question, found a bug, want to partner, or just want to argue about whether llms.txt matters — we'd love to hear from you.
Before you write us
A few quick answers that cover most messages.
How fast will I get a reply?+
Most messages get a human reply within one business day. Urgent support issues (paying customers, broken scans) are usually answered within a few hours.
Do you offer agency or reseller plans?+
Yes. We run a partner program for SEO and content agencies that includes white-labeled reports, bulk scanning, and joint launches. Mention 'partnership' in your message.
Can I get help running a scan or interpreting a report?+
Absolutely. Free scans are self-serve, but if you want a walkthrough or a custom audit on a complex site, we offer paid concierge sessions.
Where are you based?+
We're a distributed team across Europe and North America. Support is handled in English, French, German, and Spanish.
Don't need to talk? Run a scan instead.
The free scanner answers most "is my site AI-ready?" questions in under a minute.
Scan my site
Send evidence that makes the problem reproducible
Include the public page URL, the tool used, the exact action, time and the visible error or unexpected result. Describe what you expected and what actually happened. Screenshots can help, but remove personal information, tokens and private customer data. Never send passwords or API keys. There is no stated support-time guarantee in this guide.
Separate a site issue from an answer variation
A failed public fetch, malformed schema and a changing AI answer need different investigations. For answer-related questions, include the engine, language, prompt and source links. For a generated file, include the non-sensitive input and deployed URL so the published response can be checked.
Keep a record of what changed
Save the original URL, input, date and evidence before editing. Verify the deployed page or file, document the changes and repeat the same checks. Separate technical validity, correct answer representation and qualified visits; none should be used as a substitute for the others.
Evidence and next actions
| Check | Evidence to retain | Action |
|---|---|---|
| Access | Public status and useful response body | Fix barriers before rewriting |
| Accuracy | Visible facts and supporting primary sources | Correct unsupported statements |
| Markup | Valid syntax that matches the page | Remove invented reviews and properties |
| Outcome | Comparable responses and referral activity | Report observations without guarantees |
Implementation checklist
- Use the tool or guide matching the problem.
- Verify important facts against current primary documentation.
- Keep private data out of published files and support requests.
- Check changes on the real domain.
- Retain comparable before-and-after evidence.
A repeatable workflow
- 1Establish a baseline
Save the page URL, date, language, target market and exact questions before editing. Record what the page actually says and what each tested answer cites; a mention without a source link is not a citation.
- 2Make one coherent change
Resolve the clearest failure first, then check the published page rather than only an editor preview. Keep an implementation log so unrelated redesigns, campaigns or product changes are not mistaken for the effect of this work.
- 3Repeat and compare
Repeat the same questions and technical checks after deployment. Keep engines and measurement conditions consistent, report sample size, and inspect answer accuracy alongside citations. A single response is not a stable ranking.
More questions answered
- Does this guarantee an AI citation?
- No. A crawlable, accurate page can still be omitted. Retrieval, source selection and generated answers vary between products and requests; these checks improve the evidence available, not guarantee placement.
- How do I tell whether an improvement worked?
- Compare like-for-like checks and retain the underlying evidence. Track correct brand mentions, source-linked citations and qualified referral visits separately. Do not call a technical score a traffic forecast or attribute every change to one edit.