Codex can investigate technical SEO more precisely when it can read both repository code and Google's stored index information. A GSC connection provides that second evidence source. This guide pairs URL inspection with canonical and robots code review, while preserving the distinction between source code and the version Google last indexed.
What do you need before connecting?
Use an installed Codex CLI with remote HTTP MCP and OAuth support. Run the setup on the same Codex host where you will use the tools. A local CLI configuration does not by itself configure a separate cloud task. You need no Google service-account JSON or API key for this hosted OAuth route.
- A Google login with access to the Search Console property you intend to query.
- A LoomaScale account with Google Search Console connected; a GA4 connection does not grant Search Console access.
- The exact property returned by discovery: a domain property such as sc-domain:example.com or a URL-prefix property such as https://www.example.com/.
How do you connect Codex to GSC?
1. Connect GSC in LoomaScale
Create or sign in to your LoomaScale account, then open Connections. Choose Google Search Console, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.
2. Add the source-specific MCP server to Codex
Run these commands in your terminal. The first saves the remote server and the second starts browser authorization. The server name is specific to this Google source, so another source can be added without replacing it.
codex mcp add loomascale-gsc --url https://api.loomascale.com/mcp/gsc
codex mcp login loomascale-gsc3. Finish OAuth and check the active Codex connection
Complete LoomaScale authorization in the browser using the account with your Google connection, then return to the terminal. Run codex mcp list to check the saved server. Start or reopen a Codex session and use /mcp to inspect its active tools. A saved entry is configuration evidence; the account lookup below verifies data access. Codex's supported local clients share MCP configuration for the same host. Consult OpenAI's current documentation for your desktop or IDE surface; do not assume a different host inherited your login.
4. Verify access with an actual account lookup
Use LoomaScale to call gsc_list_sites. List my Search Console properties with their exact site URLs and permission levels. Ask me which property to use. Do not guess a domain or submit anything to Google.
Match the returned property to the site you manage. A domain property and a URL-prefix property can cover different URL sets, so keep the exact returned identifier. After selection, request a small performance report with explicit dates and search type. Check the actual tool result before interpreting a table: an explanation of Search Console without a tool call is not a connection test.
How do you investigate an indexing mismatch with Codex?
Choose a small set of URLs that belong to the selected property. Retrieve Google's indexed inspection result and inspect the relevant route, canonical and robots behavior in the repository. If you also have a built export, check it separately. Current code and Google's last crawl may represent different versions of a page.
Use LoomaScale and my selected Search Console property. Ask me for up to five affected URLs, then inspect their indexed status and Google-selected canonical. Read the repository routes and metadata that should serve those URLs without editing files. Compare indexability and canonical intent with Google's stored result. State which evidence is historical and which comes from current code. Propose verification steps; do not request indexing or change files.
A canonical mismatch can reflect an old crawl, redirect behavior or a different deployed build; it is not enough to locate one canonical string in source. Verify the actual served response when needed, then assess a focused fix. URL Inspection through this connection reads Google's stored view and does not run a new live URL test.
Which MCP endpoint does this guide use?
https://api.loomascale.com/mcp/gscThe service-specific endpoint exposes GSC tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.
What can Codex read or change in GSC?
LoomaScale's Search Console tools retrieve organic clicks, impressions, CTR, average position, query and page opportunities, sitemap status and Google's indexed URL-inspection result. When you ask in chat, they can also submit, resubmit or delete a sitemap and add or remove a property in your Search Console list; removing a property needs explicit confirmation, and an added property stays unverified until you verify it in Search Console. They cannot request indexing or change a website's content. Connections made before November 16, 2026 need a reconnect to grant the write permission. Performance rows describe Google Search visibility, while GA4 sessions describe measured visits. Google's Search Analytics API returns leading rows within its limits and does not guarantee every data row; a missing query is not proof that it received no searches.
Why is the connection or data missing?
If authorization is missing, run codex mcp login loomascale-gsc again. If the entry is configured but absent in the active session, restart that session and inspect /mcp. Check the URL and host if the tools still do not load. The main LoomaScale plugin and the service-specific server are alternative connections; installing both can expose duplicate tool sets.
For a missing site, check the connected Google email and Search Console access. For unexpected totals, keep the same property, dates, filters and search type as the interface you compare with. Recent data may be incomplete; name the period you used. URL Inspection reports Google's stored index view, rather than a new browser crawl of the current page. A successful connection does not improve rankings or cause a page to be indexed.
Related connection guides and official references
Use GSC in another assistant
- How to Connect ChatGPT to GSC
- How to Connect Claude to GSC
- How to Connect Claude Code to GSC
- How to Connect Grok Build to GSC
Connect another Google source to Codex
Official setup references
Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.
