Answer the near misses
Add a FAQ entry for each question we rank 8 to 20 for, with at least 300 impressions.
Turns page two questions into on page answers.
search_queries
Agents and MCP
Let Codex read Search Console before it touches a page.
Codex
MCP
LopeBase
read only
Search Console
Run one command in your project and Codex can read Google Search Console for your site: which searches you rank for, which pages earn clicks, and where you sit just off page one. Then it does the work in the repo.
One command sets it up. Your saved sign in stays on this computer, out of the repo.
What it looks like in Codex
One question, one tool call, and an answer built on your own Search Console numbers.
Find searches we're close to ranking for and add a FAQ entry for each.
read_sourcegsc-acmesearch_querieslimit 1000
| query | impr. | clicks | pos. |
|---|---|---|---|
| how long to keep invoices | 2,870 | 24 | 10.9 |
| can you invoice without a business | 1,420 | 9 | 12.3 |
| invoice vs receipt | 5,010 | 141 | 5.2 |
Two questions get real impressions from page two. I added answers for both to content/faq.md and linked them from the invoicing guide. Tests pass; ready for review.
Data in, changes out
Codex reads the rows, decides what to change, and edits the files, all in one task.
Nothing secret in the repo
npx lopebase keeps your sign in in your user folder, and Codex starts LopeBase through it.
Specific, not generic
SEO advice from a model alone is guesswork. With your real queries, Codex works on the searches you can actually win.
Add LopeBase to Codex
Three steps. The first is the same for every app; the rest is specific to Codex.
- 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
Run
npx lopebasein your project folder. It signs this computer in, then registers LopeBase with Codex asnpx lopebase mcp, which forwards to the hosted server with your saved sign in. No token ends up in the repo. - 03
Start Codex and ask. Codex now lists the LopeBase tools. Ask in plain words; it picks the dataset and reads the rows.
$ npx lopebaseWorks on macOS, Linux, and Windows with Node 18 or later. If the saved sign in expires, Codex says so; run npx lopebase login and carry on.
Search Console prompts that work well in Codex
Codex runs a task end to end. Hand it the whole job.
Clean up after a redesign
Compare our top pages with the routes in this repo and list any that now 404.
Catches ranking pages lost in a refactor.
top_pages
Tighten internal links
For our five pages closest to page one, add links from our strongest pages.
Uses clicks to find the pages worth linking from.
search_queriestop_pages
Write the next article
Pick the next article topic and write it to match the rest of the blog.
next_article_topic skips what you already wrote.
next_article_topicsubmit_draft
What Codex 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 Codex
LopeBase is not the only route. Here is how it compares with the usual one.
| Topic | A script on the API | LopeBase |
|---|---|---|
| Setup | A Google Cloud project, the API turned on, a credentials file, and code to call it. | npx lopebase and Connect with Google. |
| Upkeep | Yours when the API or your credentials change. | Ours. Codex keeps calling the same tools. |
| Choosing the data | Codex writes a new query for each question. | Seven ready datasets, including page plus query pairs. |
| Other sites | One more credential per site. | Every connected site from the same sign in. |
| Best when | You need a report no dataset covers. | You want Codex to fix SEO with real data, today. |
Search Console and Codex questions
Something else? Contact us.
What does npx lopebase change on my computer?
It saves your sign in to your user folder and registers LopeBase with Codex as npx lopebase mcp. It reads dependency and config file names in your project only after you say yes, and never your .env file.
Does this work in the Codex IDE extension?
LopeBase works with any Codex surface that reads your Codex MCP settings. The command line is the path we set up and test.
What if the sign in expires?
Codex reports that LopeBase rejected the token. Run npx lopebase login and ask again.
Can Codex break anything in Search Console?
No. LopeBase only has read access to Search Console, and Codex can only read through it.
Does Codex see other people's data?
No. The sign in belongs to one LopeBase workspace and only reads that workspace's sites.
Give Codex the search data it needs.
EmDashFree for one product. No card. Agent access is on every plan.