Docs

How do I use Gemini CLI for SEO and to show up in AI answers?

Use Gemini CLI as the hands, not the judge: write your page rules in GEMINI.md, connect an MCP server with httpUrl in .gemini/settings.json for live data and checks, and confirm each page on the published site before calling it done. Since June 18, 2026, many personal Google accounts use Antigravity CLI instead, so check which one your login runs first.

Facts

Can I still use Gemini CLI in 2026?

Yes, if you sign in with a paid Gemini API key or a Gemini Code Assist Standard or Enterprise license; other personal plans moved to Antigravity CLI on June 18, 2026.

How you sign inWhat runs since June 18, 2026
Paid Gemini API keyGemini CLI
Gemini Code Assist Standard or EnterpriseGemini CLI
Google AI Pro or UltraAntigravity CLI
Free Gemini Code Assist for individualsAntigravity CLI

Where do I put SEO rules for Gemini CLI?

Put them in GEMINI.md at the root of the site's repository; Gemini CLI sends it with every prompt, and /memory show displays what it loaded. If other coding agents share the repository, add AGENTS.md to context.fileName so one file serves all of them.

# GEMINI.md (project root)
## Rules for new content pages
- One H1 per page, phrased as the question the page answers
- Unique <title> and meta description; self-referencing canonical
- Content rendered on the server, not only after JavaScript runs
- JSON-LD only for what the page visibly says
- Add every new page to the sitemap
- Never change the home page or pages that already work

How do I connect an MCP server to Gemini CLI?

Run gemini mcp add with --transport http in the site's folder, then /mcp auth to sign in. The command writes to .gemini/settings.json; a remote server goes under httpUrl, because url means an SSE server:

# In your site's folder (default scope: this project's .gemini/settings.json)
gemini mcp add --transport http <name> <server-url>

# Inside Gemini CLI: sign in with OAuth, then list the servers
/mcp auth <name>
/mcp

// .gemini/settings.json (this project) or ~/.gemini/settings.json (every project)
{
  "mcpServers": {
    "<name>": {
      "httpUrl": "<server-url>"
    }
  },
  "context": {
    "fileName": ["AGENTS.md", "GEMINI.md"]
  }
}

What can Gemini CLI not check by itself?

Gemini CLI sees your code, not the live site. These checks need the published page or outside data:

QuestionWhere the answer is
Does the page render with content without JavaScript?Fetch the live URL, for example with curl
Are title, canonical and JSON-LD right?The live HTML, not the source file
Did Google index it?Search Console
Did AI crawlers read it, did AI assistants send visits?Server logs or an analytics tool that splits AI traffic

Step by step

  1. Check your sign-in. Confirm Gemini CLI still serves your account; if not, follow the Antigravity CLI path.
  2. Write the rules. Create GEMINI.md, or AGENTS.md listed in context.fileName, with your page rules.
  3. Connect the tools. Run gemini mcp add --transport http with the server's URL, then /mcp auth.
  4. Ask for one batch of pages. Ask for a few new pages, each answering one question, without touching existing pages.
  5. Check live. Deploy, open each published URL, check content, title and canonical, then watch indexing and AI visits.

Common mistakes

  • Writing a remote server under url, which Gemini CLI reads as SSE, instead of httpUrl.
  • Assuming Gemini CLI still works on a Google AI Pro or Ultra login after June 18, 2026.
  • Accepting the agent's summary that pages are live without opening the URLs.
  • Letting it rewrite the home page or pages that already bring traffic.

How easyIndex solves it

easyIndex connects to Gemini CLI with one command, gemini mcp add --transport http easyindex https://easyindex.app/api/mcp, then /mcp auth easyindex. It is more than a server to call: the method comes inside it, with step-by-step instructions and the current rules, so there is nothing to install or keep updated. Gemini CLI makes every change, and easyIndex never touches your site or repository.

Each page is audited when submitted and checked on the live site after publishing, and a step completes only on evidence easyIndex checks, not on the agent's report. The dashboard then shows AI-assistant visitors per page, which pages AI crawlers read and Search Console data, for US$ 30 per website a month after a 7-day free trial.

Frequently asked questions

Is this the same as getting recommended by Gemini?

No. Gemini CLI is a coding agent that edits your site; whether the Gemini app cites your site is a separate question with its own guide.

My Gemini CLI login stopped working. What now?

Move to Antigravity CLI: it reads GEMINI.md unchanged, but remote MCP servers go to mcp_config.json with url or httpUrl renamed to serverUrl.

Can Gemini CLI read AGENTS.md?

Yes, once you add AGENTS.md to the context.fileName list in settings.json.

Will Gemini CLI get my site cited by AI assistants?

No tool can promise that. It can build clear, crawlable pages; each assistant decides what it cites.

Continue reading

Last verified on .

Gemini CLI for SEO: MCP, GEMINI.md and live checks