> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypergsc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix HyperGSC connection and reporting problems

> Troubleshoot missing Search Console properties, Google reconnection, MCP authorization, connector access, unavailable tools, and reporting differences.

Start by identifying which connection failed: your HyperGSC login, the Google connection, the AI client's authorization, or a particular report.

## My AI client shows no properties

Open HyperGSC **Connections** and confirm:

1. The intended Google account is connected.
2. That account has access to the property in Search Console.
3. You used **Refresh properties** after a new property or access change.
4. The property is selected and **Save changes** was applied.
5. The enabled selection fits your current plan.

Then ask the client to call `get_capabilities` and `list_properties` again. Newly discovered properties are disabled until selected.

## Google needs reconnecting

Google can expire or revoke credentials. Reconnect from **Connections**, complete consent with the correct account, refresh properties, and review the saved selection.

Signing in to HyperGSC is separate from connecting Google Search Console.

## The MCP client cannot authorize

Check that the server URL is exactly:

```text theme={null}
https://hypergsc.com/mcp
```

Complete the browser sign-in and consent flow. A cloud-hosted client needs a publicly reachable HTTPS server; a laptop's localhost URL will not work for it.

If authorization has expired, reconnect your assistant and complete browser sign-in again. For Claude, open the [HyperGSC directory connector](https://claude.ai/directory/hypergsc). If a research write needs `projects:write`, reconnect with that consent.

## A tool is visible but unavailable

The catalog includes tools across plans. Ask for `get_capabilities` and `get_usage` to distinguish a scope, plan, quota, Google-access, or provider-readiness restriction.

For a downgrade that leaves too many properties selected, reduce the selection before making more Search Console requests.

## The numbers differ from Search Console

Compare the property, inclusive dates, search type, filters, dimensions, and data freshness. Pacific-time boundaries can differ from your local calendar day.

A bounded query table may not match unfiltered totals. Missing rows are unknown. Read the [data and metrics guide](https://docs.hypergsc.com/reference/data-and-metrics.md) before interpreting the difference.

## An indexing fix does not appear yet

URL Inspection reads Google's stored observation. Check its timestamp and compare the current page separately. A sitemap entry is not proof that the page is indexed.

## Contact support

Email [help@hypergsc.com](mailto:help@hypergsc.com) with the client name, tool name, reporting dates, and the exact error code. Include a sanitized request identifier if available. Leave sign-in tokens and Google credentials out of the message.

For technical error handling, see [errors and limits](https://docs.hypergsc.com/mcp/errors-and-limits.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.