GEO/AEO Tracker
Run a self-hosted AI visibility dashboard and review which answer sources link to your site for a fixed set of prompts.
Community support
Upvotes come from SearchEngineAnswer members. GitHub stars and reader reviews are counted separately.
Claim this tool if you maintain it.
- Best for
- AI visibility
- Setup required
- Use Node.js 20.9 or newer for the dashboard. A local demo can run with an empty environment file. Configure an authorized provider key to collect live results.
- Costs to check
- MIT-licensed software. Hosted data collection and optional model analysis use separately billed providers. Start with the sample dataset to evaluate the interface.
- License in catalog
- MIT
GitHub repository
- GitHub stars
- 334
- Forks
- 77
- Last push
- 2026-11-11
- Primary language
- TypeScript
GitHub snapshot from . Stars count GitHub bookmarks. Reader ratings appear separately below.
How to install GEO/AEO Tracker
-
Clone the repository at a reviewed version such as v1.9.0 and install its npm dependencies. Copy .env.example to .env for the local setup.
git clone --branch v1.9.0 https://github.com/danishashko/geo-aeo-tracker.git cd geo-aeo-tracker npm install cp .env.example .env npm run dev - Start the development server and open localhost on port 3000. With the live data key unset, confirm the dashboard identifies the bundled records as sample data.
- For live tracking, configure the Bright Data key for an authorized project after checking endpoint availability and the per-call budget. Configure optional model providers only if the intended test needs analysis features.
First tutorial for GEO/AEO Tracker
- Inspect the sample view. Choose one example that mentions a brand and inspect the source URLs to see whether the site receives a link.
- For a live trial choose a single non-sensitive prompt and one supported engine. Save the visible response and its citations, then check the actual destination of any citation counted for your domain.
- Repeat using the same wording and engine after a fixed interval. Compare mention, direct citation and request success in separate fields before drawing a conclusion from the dashboard score.
The CLI-focused v1.9.0 was released November 11, 2026. This profile uses the maintained documentation. An engine provider's unavailable or failed response belongs in the coverage log.
Where GEO/AEO Tracker fits
Use this project when you want to inspect a self-hosted visibility workflow before committing to recurring prompt collection. The bundled sample makes it possible to review the interface first.
- When to choose another tool
- Try a saved manual observation when you need to verify one specific source link. Compare site-level impressions in Search Console when the question is measured exposure in Google's supported AI features.
- First evaluation
- Open the local demo and find a row with a brand mention and another with a cited URL. Confirm that the interface distinguishes the two and clearly marks sample data.
- How to interpret the result
- Run a narrow paid test only after checking provider coverage and caps. Keep the prompt, date, selected engine, emitted sources and any failed requests. A score based on one prompt or an incomplete response set is a limited sample.
Reviews and discussion
Reader reviews
Be the first to share your experience with this tool.
Discussion
Ask a question or share a setup tip.
Flag an outdated detail
Include the field that needs updating and a source link. Copy your draft, then use the corrections policy to contact the editorial team.
Write a review or join the discussion