Use Codex with mowteng to ask about your Search Console clicks, queries and indexing. Connect once, then start with a question about your own site.Connect Codex
Add the remote server, then run the login command:
codex mcp add mowteng --url https://mowteng.app/mcp
codex mcp login mowtengSign in with the Google account that can access your Search Console property. Leave the Search Console permission ticked so the tools can read its data.
mowteng uses one remote MCP URL and Google sign-in. There is no Google Cloud project, API key or OAuth client of your own to set up. The connection guide explains the shared setup.
Start with your properties
Use Codex to investigate a live page before choosing a code or content change. Specify the Search Console property and the public URL. The remote connection supplies search data; you do not need to put a Google API key or OAuth client configuration into your repository.
List my Search Console properties, then show which pages on the busiest one lost the most clicks in the last 28 days.
Confirm the property the assistant chose before acting on the report. Ask it to include the earlier period, the current period and the click change for each page.
Turn the result into a useful next check
For a release review, compare equal date ranges before and after publication, then examine the queries behind the largest page changes. A change in clicks is evidence to investigate, not proof that the release caused it. Ask Codex to call out differences in impressions and average position before recommending an edit.
Use content decay analysis for declining pages, or ask for striking distance keywords when you want a list of queries close to page one. You can also inspect an individual URL to check its indexing and canonical.
Troubleshoot access and keep changes deliberate
If no properties appear, check whether you used the Google account that owns the site. See no properties showing. If access was not granted, reconnect with the Search Console permission ticked.
Search data is fetched live for each request and never stored by mowteng. Write actions, such as submitting a sitemap, are marked so assistants ask before running them. mowteng never edits your site pages. Review any proposed page changes in your own workflow.