Help
Support
One inbox, read by the people who build the product. There is no ticket queue to escalate through and no bot in front of it.
Getting in touch
- Anything at all
- [email protected]
- Privacy and data requests
- [email protected]
- Security reports
- [email protected]. Tell us privately first and give us a reasonable window to fix it before publishing.
- Bugs and feature requests
- Open an issue at github.com/bapierre/vanpelt-seo/issues if you would rather do it in public.
We aim to reply within two business days. GetCited is a small team in early access, so that is a target we work to rather than a contractual commitment. If something is broken badly enough to block you, say so in the subject line and we will treat it that way.
What to include
The faster we can reproduce a problem, the faster it gets fixed. Where it applies, send us:
- The domain of the project, and the page path if the problem is on one page.
- What you expected to happen and what happened instead.
- When it started, roughly, and whether it has happened more than once.
- The MCP client you are using if the problem is with an agent, for example Claude Code, Cursor or Codex, and the exact tool name it called.
- The error text, copied rather than screenshotted, so we can search for it.
Never send us an API key, a password, or a session cookie. If you think a key has leaked, revoke it yourself in Settings, API keys, and then tell us. We will never ask you for one.
Before you write in
- An agent cannot connect
- Check the key is sent as an Authorization Bearer header and not in the URL, and that the project id you pass belongs to the organisation the key was issued for. A revoked key returns 401 and a burst of calls returns 429.
- Nothing is appearing in analytics
- Confirm the snippet is on the page and the collect endpoint is reachable from the browser. Traffic identified as a bot is dropped on purpose, and sessions above your plan quota are not stored.
- A keyword looks wrong on a session
- Keyword attribution is a weighted estimate joined from Search Console at page and date level, not a fact about that visitor. The confidence and the residual are shown alongside it.
- Work stopped part way through the month
- You have probably exhausted a quota. The billing page shows usage against each limit, and quotas reset at the start of the UTC month.
Docs and source
- MCP setup, including the install snippet for every supported client, is in llms-install.md. It is written to be read by your agent, so you can hand it the link directly.
- The full source is at github.com/bapierre/vanpelt-seo. Every claim on the privacy page can be checked against it.
- What we are building next is in ROADMAP.md.
Status
There is no public status page yet and no uptime commitment. Both are on the roadmap. Until one exists, email us and we will tell you plainly whether something is broken on our side.