Tradly Search Insight tools let an authorized assistant work with supported Google Search Console data connected to your Tradly workspace. Ask about search queries, geographic performance, saved recommendations, or the indexing status of a URL.
Search Console tools are part of the general Tradly MCP endpoint:
https://mcp.tradly.app/api/mcpThe user must connect Google Search Console and map the relevant property to an authorized analytics project. Keyword and geographic reports use synchronized data, so they may not include changes Google recorded after the latest sync.
Example Search Console questions
Review queries and search opportunities
Show the latest Search Insight digest and summarize the main search trends it reports.
From the synchronized rows for my mapped property, which search queries have the most impressions and clicks?
Find queries with strong impressions but a low click-through rate. Show the values you used to rank them.
What keyword opportunities and recommendations are already saved for this workspace?
Which countries have search impressions but relatively few clicks? Explain how you selected the opportunities.
Show the latest Search Console sync status and tell me when the data was last updated.
Which property is mapped to my Tradly analytics project? List the available properties if more than one is connected.
Check a URL and sitemap
Inspect
https://example.com/products/blue-shirtin the Search Console property that owns it. Summarize its indexing and crawl status.
Is
https://example.com/guides/size-chartindexed? Tell me the latest coverage result and any reported crawl issue.
Submit the publicly verified sitemap for my mapped property. First confirm the property and sitemap URL you will submit.
Sync Search Console data for
https://example.com/from October 1 through October 31, 2026, then report whether the sync started successfully.
URL inspection reports the status Google provides for that URL. It does not force Google to index a page; the Search Console API does not provide a general request-indexing operation for arbitrary URLs.
Connect Search Console data
- Add
https://mcp.tradly.app/api/mcpas a remote MCP server and authorize the intended Tradly tenant. - Connect Google Search Console through the available Tradly Search Insight workflow.
- Confirm that the Google property is accessible and mapped to the correct analytics project.
- Synchronize the desired date range before asking about recent query or geographic performance.
- Start with a read-only question, then verify the property and date range in the answer.
Submitting a sitemap and starting a sync write data or trigger an external operation. Use them only when you intend to make that change and have access to the matching permission. Inspecting a URL and reading saved reports are read operations.
Search Console data versus site analytics
Search Console describes Google Search activity: queries, impressions, clicks, geographic performance, and indexing reports. Site analytics describes activity measured after people arrive, such as sessions, page views, engagement, and conversions. The two systems can use different time ranges and definitions.
For visits, conversion paths, AI referrals, and page performance, see Tradly analytics MCP.
Troubleshooting common results
| Result | What to check |
|---|---|
| No property is listed | Confirm the Google account used for the Search Console connection can access the property. |
| No mapped project appears | Save the property-to-project mapping in Tradly. |
| Search rows look old | Check the latest sync status and run a sync for the required date range. |
| URL inspection reports no data | Verify the exact URL and the Search Console property that owns it. |
| Sitemap submission is blocked | Confirm that the sitemap is public and that its property is verified and mapped. |