aeotime

Account & billing

Troubleshooting & FAQ

Fixes for common aeotime issues: missing mentions, empty dashboards, failed runs, Google connection errors, crawler tracking and API errors.

Updated

An AI-readiness audit, check by check · illustrative
On this page

My dashboard is empty

  • No trial or subscription yet. Tracking runs during the trial and on paid plans. Open Billing.
  • No active prompts. Add or activate prompts on the Prompts page.
  • The first run is still going. The overview shows progress. Large prompt sets take longer.
  • Date range. Try 30 or 90 days, and clear the engine filter.

An answer mentions us but it isn't counted

aeotime matches your brand name and aliases. Add the exact form the engine used — short name, product name, old name, name without spaces — under the project's Settings (brand aliases). New answers are matched with the updated list.

A competitor is missing from share of voice

Only confirmed competitors count. Check Competitors for suggested brands waiting for confirmation, and add aliases for competitors with several names.

A run failed or an engine shows errors

Engines occasionally time out or rate-limit. aeotime retries automatically; failed answers are excluded from metrics rather than counted as "not mentioned". If a whole run fails, start another with Run now. If it keeps failing, contact us.

The site audit can't read my site

The audit fetches your site like a crawler would. If it fails:

  • Check the site is public (no password, VPN or IP allowlist).
  • Check your firewall or CDN isn't blocking automated requests.
  • Make sure the domain in the project matches the live site, including www if you redirect to it.

Google connection errors

See Connect Search Console & GA4.

AI crawler tracking shows nothing

  • Confirm the snippet is deployed on the live site and uses the current key (rotating the key stops the old one).
  • On Next.js, middleware only runs on matched routes — make sure your pages are included.
  • Bots may not have visited yet. Uploading a recent access log shows past visits immediately.

API or MCP returns 401 or 402

  • 401 — the key is missing, mistyped or revoked. Create a new one under API & MCP.
  • 402 — the workspace has no active subscription.

Still stuck?

Contact us with your workspace name and what you were doing. We reply within one business day.

Still stuck? We answer within one business day.

Contact support