How does easyIndex work, what do I need, and how long until results?
easyIndex connects to your coding agent over MCP and runs the GEO method in 4 steps: setup, mapping, a batch of audited pages and a monthly cycle. You need a website in a code repository, a coding agent with access to it and a Google account for Search Console. AI crawler reads show up first; indexing and citations take longer.
- Your own agent does the work, in your own repository: nothing is changed behind your back.
- Every page is audited before it goes live and checked again on the live site.
- One dashboard shows visitors from AI assistants, AI crawler reads, Google indexing and which AI answers cite you.
- Every month your agent asks ChatGPT, Claude, Perplexity and Gemini up to 40 tracked questions in a private window; easyIndex checks what it submits.
Facts
- Anthropic introduced MCP, the open standard easyIndex uses to talk to coding agents, on November 25, 2024. (Anthropic: Introducing the Model Context Protocol)
- OpenAI's search crawler, OAI-SearchBot, takes about 24 hours to follow a change in robots.txt. (OpenAI: Overview of OpenAI crawlers)
- Search Console reports a site's clicks, impressions and indexed pages; easyIndex records the last 28 days as the starting point. (Google Search Console)
- Google's AI Mode had over 100 million monthly active users in the US and India by July 2025. (Alphabet Q2 2025 earnings call)
- The agent connects with one command: claude mcp add --transport http easyindex https://easyindex.app/api/mcp. (easyIndex)
What happens in each of the 4 steps?
The method runs in a fixed order, and a step completes on evidence easyIndex checks, not on the agent's report.
| Step | What your agent does | What easyIndex checks |
|---|---|---|
| 1. Setup | Installs the tracking script, the crawler forwarder and the sitemap | The script on the live site, a test crawler visit, Search Console and the sitemap |
| 2. Mapping | Learns the business, saves the official facts, proposes batch 1 | The site's audit and your approval of the plan |
| 3. Content batch | Writes the pages and the technical fixes, publishes them together | Every draft before it goes live, then every page live in every language |
| 4. Monthly cycle | Runs the AI citation scan and proposes the next batch from what the data shows | The scan's citations, which pages bring visits, which are read by AI, which are indexed |
Why does easyIndex check the live site instead of trusting the agent?
A coding agent reports its own work as done. easyIndex reads the published page itself, the way an AI crawler does, so a page counts only when it is really live, readable and carries the audited text.
What does easyIndex measure?
Visitors who came from ChatGPT, Claude, Gemini or Perplexity, per page; which pages AI crawlers read and when; and, from Google Search Console, clicks, impressions and indexed pages.
easyIndex also monitors AI citations. Once a month your agent asks ChatGPT, Claude, Perplexity and Gemini up to 40 tracked questions in a private window and records which sources each answer cited and at which position. easyIndex checks the submission and shows your AI visibility on the dashboard.
Which coding agents work?
Claude Code, Codex, Cursor, Antigravity, Gemini CLI and any other agent that supports MCP. The agent needs access to the website's repository and a way to deploy it.
Who is easyIndex for?
easyIndex suits:
- Companies whose website is built from code they control (Next.js, Express or any other stack)
- Agencies that manage clients' websites: one account holds several websites and invites people to share them
- Teams that already use a coding agent and want AI assistants to recommend them
Who is it not for?
A website edited only in a hosted builder, with no repository a coding agent can change, cannot follow the method today.
What shows up first, and what takes longer?
AI crawler reads appear soon after the tracking is installed. Google's indexing of new pages follows the sitemap; visits from AI assistants and citations come with time and depend on your market. The dashboard shows each one as it happens.
Step by step
- Create your account. Add the card on Stripe's page and your website's address. The first 7 days are free.
- Connect your coding agent. Run one command in Claude Code, Codex, Cursor, Antigravity or Gemini CLI, then click Authorize in the browser.
- Connect Search Console. Sign in to Google so easyIndex records your starting point and sends the sitemap.
- Ask your agent to use easyIndex. It calls next_step and follows each step until batch 1 is live.
Common mistakes
- Publishing pages one by one as they are written: the batch goes live together, after every page passed the audit.
- Letting the agent invent a price, a deadline or a customer: every fact needs a source.
- Skipping Search Console: without the starting point there is nothing to compare the results with.
- Starting without access to the repository or to deployment: the agent can write the pages but not publish them.
How easyIndex solves it
easyIndex turns GEO into steps a coding agent can follow and that a machine can verify, so the work is done in your repository, checked on your live site and measured on one dashboard.
Frequently asked questions
Does easyIndex work with WordPress?
Only when the site's code is in a repository your coding agent can change and deploy.
Does easyIndex write the pages?
No. Your coding agent writes them in your repository; easyIndex gives the shape and the rules, then audits the text.
How long does setup take?
The tracking and the sitemap are usually installed in one session with your agent; Search Console takes about two minutes of your time.
Can I skip Search Console?
No. It is part of the start; it records where Google started and receives the sitemap.
Continue reading
- What is easyIndex?
- How much does easyIndex cost?
- GEO tool, SEO tool, agency or doing it yourself: which is right for my company?
- How long does GEO take to show results?
- easyIndex FAQ
Last verified on .