Use Cursor with mowteng to ask about your Search Console clicks, queries and indexing. Connect once, then start with a question about your own site.Connect Cursor
Use this Cursor install deeplink. Confirm the server installation, then sign in with Google when Cursor asks. Leave the Search Console permission ticked.
cursor://anysphere.cursor-deeplink/mcp/install?name=mowteng&config=eyJ1cmwiOiJodHRwczovL21vd3RlbmcuYXBwL21jcCJ9The configuration points to the remote server at https://mowteng.app/mcp.
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
Bring search evidence into the conversation where you are planning a page change. Start by identifying the property and URL that correspond to the page you want to investigate. A repository filename is not a Search Console property, so use the published site address in the request.
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
Before asking for an implementation, ask Cursor to explain which query and page rows support the proposed change. A page near page one may need a clearer answer to the query rather than a larger rewrite. Review the evidence, choose the change, then use a later period to assess its effect.
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.