Troubleshooting
Use these checks before you reconnect a source or recreate an agent connector. Searchata tool errors include a specific message and a corrective action when one is available.
No Bing sites appear
Confirm that the connected Microsoft account can open a verified site in Bing Webmaster Tools. Open Sources and reconnect Bing after Microsoft grants the account access.
No Search Console properties appear
Confirm that the connected Google account can open the property in Google Search Console. Reconnect Google in Searchata after Google grants the account access.
Searchata tools are missing
Confirm that Searchata is enabled for the current conversation or session. Restart a CLI agent after OAuth because some clients load MCP tools only when a session starts.
A tool reports an invalid property
Call google_search_console_list_properties for Google or bing_webmaster_tools_list_sites for Bing. Use the returned propertyId instead of a domain, URL, provider site URL, or an older stored identifier.
A quota or rate-limit message appears
Follow the retry time in the tool response for a temporary rate limit. If the workspace has reached its plan allowance, use the Searchata upgrade link returned by the tool.
Recent data is incomplete
Google Search Console can publish recent performance data later than older final data. Ask for final data or retry after Google updates the property.
CLI connection checks
Inspect the saved connector before you add or replace it:
codex mcp get searchata
claude mcp get searchataThe saved URL must be https://searchata.com/mcp.
Contact support
Include the agent name, tool name, visible error, and approximate UTC time. Do not send credentials or full search-data exports.