AdvisorSEOSupport
One address, answered by people who work on AdvisorSEO
Write to support@advisorseo.ai for anything: a question about how something works, help with your account, billing, or a request to delete the data we hold for you. There is no separate queue and no form to fill in first.
When to expect a reply
We aim to reply within one business day, Monday to Friday. A message sent at a weekend is answered on the next business day. That is what we aim for rather than a promise, and a message that needs us to reproduce something on a real site can take longer.
Reporting a security concern
Report a suspected vulnerability or any other security concern to support@advisorseo.ai with Security in the subject line. We acknowledge security reports within one business day, and we ask that you do not publish the details until a fix has shipped, so that customers are not exposed in the meantime.
Never include a secret in an email. Do not send passwords, WordPress Application Passwords, or access tokens to us or to anyone else. We will never ask you for one. If you believe a credential has been exposed, revoke it first — a WordPress Application Password is revoked under Users → Profile → Application Passwords — and then tell us.
Before you write
Several of the most common questions are already answered in the documentation, and reading the relevant page is usually faster than waiting for a reply:
- Connecting AdvisorSEO inside Claude or ChatGPT — the connector address, the sign-in, and choosing the workspace the connection belongs to.
- Installing the lead-capture snippet — where the snippet goes on your own site, and what it does and does not collect.
- Disconnecting, and revoking access — removing the connection, and revoking the WordPress Application Password you supplied.
What to include so we can help
Four things turn a message we have to ask questions about into one we can answer straight away:
- The website involved. The site URL as you added it.
- What you asked for, in plain words — the request you made, roughly as you phrased it.
- What happened — what came back instead, including the exact wording of any error message.
- Roughly when — a date and a time, with the timezone. That is what lets us find the run.
Screenshots help. Credentials never do — see the note above.