Skip to content

Connect Search Console to Codex

  • Can I rerun this in CI?

Have Codex use your Search Console data to find pages competing for the same query, then rerun it any time with codex exec. Lemonado connects them in about 1 minute, no API keys needed.

MCPhttps://mcp.lemonado.io/mcp

Why connect Search Console to Codex?

Codex runs in your terminal, its IDE extension and scripts, so what it finds once can be rerun with codex exec instead of redone by hand. Connected through Lemonado, it reads your Search Console queries, pages, position and CTR, so it can find pages competing for the same query with today's numbers.

  • All your Search Console data

    Queries and pages, ready to ask about.

  • Always today's numbers

    Countries and devices, synced from Search Console automatically, so answers use today's numbers.

  • Connect all your tools

    Questions like "Are we paying for free clicks?" use Search Console and GA4, Google Ads at once.

How to connect Search Console to Codex

Before you start

  • A Google Search Console account you can sign in to
  • Codex installed
  • A Lemonado account (the free trial works)
  1. 1

    Connect Google Search Console in Lemonado

    In Lemonado, open Connectors, find Google Search Console and sign in. Choose the property you check in Search Console. Domain and URL-prefix properties hold different data.

  2. 2

    Turn on external access

    In the company's settings, open External tools, turn the connection on, choose which sources it can reach and copy the server URL.

    text
    https://mcp.lemonado.io/mcp
  3. 3

    Add Lemonado to your config

    Add this to ~/.codex/config.toml.

    toml
    [mcp_servers.lemonado]
    url = "https://mcp.lemonado.io/mcp"
  4. 4

    Log in

    Run the login command and finish the sign-in in your browser.

    bash
    codex mcp login lemonado
  5. 5

    Ask Codex about Search Console

    Run codex mcp list, or /mcp inside Codex, to see the server and its tools. Try "Pull last week's Search Console numbers, save them to data/google-search-console-weekly.csv and give me the codex exec command to refresh it." Or ask: "What do people search for?" or "Which titles lose clicks?"

What can Codex do with Search Console?

Codex reads your Search Console data from your terminal and turns one-off questions into commands you can rerun with codex exec.

Codex logoCodex

Pull last week's Search Console numbers, save them to data/google-search-console-weekly.csv and give me the codex exec command to refresh it.

Saved data/google-search-console-weekly.csv. Run the same prompt with codex exec in a scheduled job and the file refreshes with each week's numbers.

Source: Google Search Console + your code

Reading this as an AI agent?

Everything an agent needs to set this up, in plain text. Paste this page's link into Codex and ask it to connect you, or copy the block.

For agents · markdown
# Connect Google Search Console to Codex (Lemonado MCP)

- Server URL: https://mcp.lemonado.io/mcp
- Transport: Streamable HTTP
- Auth: OAuth; the user signs in to Lemonado in the browser. No API keys.
- In Lemonado: connect the Search Console property. Choose the property you check in Search Console. Domain and URL-prefix properties hold different data.
- In Codex: ~/.codex/config.toml

```toml
[mcp_servers.lemonado]
url = "https://mcp.lemonado.io/mcp"
```

If you are Codex, run the setup yourself:

Add the Lemonado MCP server to my Codex config. Append this to ~/.codex/config.toml:
[mcp_servers.lemonado]
url = "https://mcp.lemonado.io/mcp"
Then run codex mcp login lemonado so I can sign in, and check that codex mcp list shows it. Once I've signed in, list the Google Search Console accounts Lemonado can reach.

First question to try: "Pull last week's Search Console numbers, save them to data/google-search-console-weekly.csv and give me the codex exec command to refresh it."

More: https://lemonado.io/integrations/google-search-console · https://lemonado.io/llms.txt
FAQ

Frequently Asked Questions

Yes, through Lemonado. Connect your Search Console property in Lemonado, add Lemonado in ~/.codex/config.toml, and Codex can find pages competing for the same query with your live data.

Run codex mcp list. If lemonado shows as not logged in, run codex mcp login lemonado again. In Lemonado, check that Google Search Console is connected and External tools is on for the company. Search Console data runs about two days behind, so the last couple of days will look empty. Also check you picked the domain property if that's the one you use.

Yes, if both are connected in Lemonado. One connection reaches every source you allow, so you can ask things like "Which Google Ads keywords do we already rank top 3 for organically?"

MCP is included in Lemonado's paid plans and in the free trial, so you can try it before you pay.

See plans and pricing

Still have a question?

Shoot us an email at hello@lemonado.io.

Try for free

Stop fighting with data. Start feeding your AI.

Connect your data to AI and free your team from reporting and busywork.

Try Lemonado free