Fix titles that lose the click
Find pages in the top 5 with under 2% CTR and rewrite their titles and descriptions in the code.
The agent edits the metadata where your framework defines it.
top_pagespage_queries
Agents and MCP
Search Console in Cursor, next to the code it ranks.
Cursor
MCP
LopeBase
read only
Search Console
Your pages live in the repo you have open in Cursor. Add LopeBase over MCP and the agent can read Search Console for the same site, find the pages that rank but lose the click, and edit the title or content in the file that renders them.
One MCP entry, a one time sign in, and read only access to Search Console.
What it looks like in Cursor
One question, one tool call, and an answer built on your own Search Console numbers.
Which pages rank well but get few clicks? Fix their titles.
read_sourcegsc-acmetop_pages
| page | impr. | ctr | pos. |
|---|---|---|---|
| /pricing | 6,210 | 1.1% | 3.2 |
| /blog/net-30 | 3,120 | 1.6% | 4.4 |
| /features | 2,480 | 4.9% | 2.7 |
Two pages rank in the top 5 but get under 2% of clicks. I updated the title in app/pricing/page.tsx and content/blog/net-30.mdx to match what people search for. Review the diff?
From number to diff in one chat
The agent reads which pages underperform, opens the files that render them, and proposes the change.
Check before you ship
Ask which searches a page earns before you rename it, so a refactor never drops a ranking page by accident.
Every site you build
Working across several repos? Each one can ask about its own site, and any of them can compare them all.
Add LopeBase to Cursor
Three steps. The first is the same for every app; the rest is specific to Cursor.
- 01
Connect Search Console to LopeBase. Start free, add your site, press Connect with Google, and pick the Search Console property. Domain and URL prefix properties both work. Google is only asked for read access.
- 02
Add LopeBase to your Cursor MCP settings. Put the server below in
~/.cursor/mcp.jsonso every project can use it. Keep it out of the project's own.cursor/mcp.jsonif that file is committed. - 03
Sign in and open a new chat. Cursor opens a LopeBase page the first time; approve it for your workspace. Cursor only gives a chat the tools that existed when it started, so ask in a new Agent chat.
{
"mcpServers": {
"lopebase": { "url": "https://app.lopebase.com/api/mcp" }
}
}Prefer the terminal? Run npx lopebase in the project folder. It signs this computer in and starts Cursor Agent with the LopeBase tools ready.
Search Console prompts that work well in Cursor
Cursor's agent can change files, so these prompts end in a diff, not a report.
Guard a route change
I am renaming /blog to /articles. Which URLs get search clicks, and are redirects in place?
Catches lost traffic before you merge.
top_pages
Add the missing section
For /pricing, which searches does it show up for that the page never answers? Add a section.
The searches a page earns tell you what it should say.
page_queries
Merge competing pages
Find two pages that compete for one search, merge them, and add a redirect.
One stronger page usually beats two weak ones.
page_queriessearch_queries
What Cursor can read from Search Console
Seven datasets per site, read live from Search Console when you ask. Rankings and clicks cover the last 28 days, and tracked searches up to 90.
- search_performanceThe site's last 7 days in one row.clicks · impressions · ctr · position
- top_queriesThe top searches from the last 7 days.query · clicks · impressions · ctr · position
- search_queriesEvery search over 28 days, up to 1,000 rows.query · clicks · impressions · ctr · position
- top_pagesEach page's clicks and position over 28 days.page · clicks · impressions · ctr · position
- page_queriesWhich searches each page shows up for.page · query · clicks · impressions · position
- daily_searchOne row per day for the last 28 days.day · clicks · impressions · position
- queries_daily90 days of daily numbers for searches you name.query · day · clicks · impressions · position
More on each dataset: Search Console MCP. Connecting in the console: the Search Console connector.
Other ways to get Search Console into Cursor
LopeBase is not the only route. Here is how it compares with the usual one.
| Topic | A local MCP server | LopeBase |
|---|---|---|
| Setup | Clone or install a server, create Google Cloud credentials, and point mcp.json at a key file. | One url entry in mcp.json and a sign in. |
| Secrets in the repo | Easy to commit a key path or token by mistake. | Nothing secret in mcp.json. The sign in lives with Cursor. |
| Several sites | One server or credential per site, depending on the tool. | Every connected site, from any project. |
| Other data | Search Console only. | GA4, Bing, PostHog, Stripe, and uptime on the same server. |
| Best when | You want to fork and change the server itself. | You want Search Console data while you code, with no upkeep. |
Search Console and Cursor questions
Something else? Contact us.
Where does the LopeBase entry go in Cursor?
In ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. The entry is only a url, so it is safe in either, but most people keep it global.
Why can't my chat see the LopeBase tools?
Cursor gives a chat the tools that existed when it started. Open a new Agent chat after adding the server and signing in.
Does it work with Cursor Agent in the terminal?
Yes. Run npx lopebase in the project folder. It signs you in and starts Cursor Agent with the LopeBase tools.
Can the agent edit Search Console?
No. It can read Search Console and edit your code. Changes to your site go through your normal review and deploy.
Which frameworks does it work with?
Any. LopeBase reads Search Console by URL, and the agent finds the file that renders each URL in your repo, whether that is Next.js, Astro, Rails, or plain HTML.
Bring Search Console into Cursor.
EmDashFree for one product. No card. Agent access is on every plan.