Find pages that compete
Find searches where two or more of my pages both show up, and tell me which to keep.
Two pages splitting one search often both rank worse than one would.
LopeBase is a Claude connector for your sites. Connect Google Search Console to it once, and Claude can read every query, page, click, and position you have, then reason through what to fix, what to write, and what changed.
Works in Claude on the web, the desktop app, and Claude Code. Read only.
One question, one tool call, and an answer built on your own Search Console numbers.
Are any of my pages competing for the same search?
read_sourcegsc-acmepage_queries
| query | page | impr. | pos. |
|---|---|---|---|
| invoice reminder email | /blog/reminders | 1,940 | 13.2 |
| invoice reminder email | /templates/reminder | 1,610 | 15.8 |
| net 30 meaning | /blog/net-30 | 3,120 | 6.4 |
Two pages split invoice reminder email, and both sit on page two. The template page answers the search better. Merge the blog post into it and redirect the old address.
Up to 1,000 queries or page and query pairs per ask, so Claude can spot patterns a top ten report hides.
Add your style guide or content plan to a Claude project, and Claude checks its ideas against your real search data.
LopeBase is a reviewed Claude connector. Add it from the directory in a couple of clicks, with no address to copy.
Three steps. The first is the same for every app; the rest is specific to Claude.
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.
Add the LopeBase connector. LopeBase is listed in Claude's connector directory: open it there and press Connect. Or, in Claude's settings under Connectors, add a custom connector with the address https://app.lopebase.com/api/mcp.
Approve it and ask. Claude opens a LopeBase page. Approve it for your workspace and the connector works in Claude on the web and in the desktop app, in any chat or project.
Find LopeBase in the Claude directory
Working in a terminal? Add the same server to Claude Code:
$ claude mcp add --transport http lopebase https://app.lopebase.com/api/mcp
Custom connectors depend on your Claude plan; the directory listing is the quickest route. Claude Code signs in the same way the first time it calls a LopeBase tool.
Claude is good at careful reading and long answers. Give it the bigger questions.
Find searches where two or more of my pages both show up, and tell me which to keep.
Two pages splitting one search often both rank worse than one would.
Pick the best striking distance search and write a brief for a page that could win it.
Claude reads the search, the current page, and what already ranks for you.
For /pricing, list every search it appears for and what the page is missing.
A page level view of the searches a single address earns.
Pick the next article topic for acme and draft it in our voice.
next_article_topic starts from search quick wins; submit_draft sends it to your review queue.
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.
More on each dataset: Search Console MCP. Connecting in the console: the Search Console connector.
LopeBase is not the only route. Here is how it compares with the usual one.
| Topic | A local MCP server | LopeBase |
|---|---|---|
| Setup | A Google Cloud project, the Search Console API turned on, a credentials file, and a config entry. | Connect with Google, then add LopeBase from Claude's directory. |
| Where it works | Usually the desktop app on the computer that runs it. | Claude on the web, the desktop app, and Claude Code. |
| Credentials | A key file on your disk that the server reads. | Stored encrypted by LopeBase. Claude only sees rows. |
| Several sites | Depends on the server and how you set up access. | Every Search Console property you connect, each by name. |
| Best when | You want full control and are happy to run it yourself. | You want Search Console in Claude today, without maintaining anything. |
Something else? Contact us.
Yes. Search for LopeBase in the directory and press Connect. You can also add it as a custom connector with the address https://app.lopebase.com/api/mcp.
No. Connect with Google in LopeBase handles access. A service account still works if your team prefers one.
Yes. Run claude mcp add --transport http lopebase https://app.lopebase.com/api/mcp, or run npx lopebase in the project folder, and Claude Code signs in the first time it uses a tool.
No. LopeBase only asks Google for read access. Claude cannot submit sitemaps, remove pages, or change settings.
Tables of search numbers: queries, pages, clicks, impressions, CTR, and position. Never a password, a token, or anything about individual searchers.
Free for one product. No card. Agent access is on every plan.