Skip to main content
HyperGSC sits between your Google Search Console account and an AI client. These terms explain what each part controls.

​
HyperGSC account

Your account owns Google connections, enabled property selections, agent authorization grants, usage, and saved research. Signing in to HyperGSC does not automatically connect Search Console.

​
Google connection

A Google connection lets HyperGSC read Search Console data available to a particular Google account. You can connect Google accounts and select the properties agents may access in Connections. Disconnecting removes that connection’s credentials and properties from HyperGSC. To revoke the underlying Google authorization, also remove HyperGSC from your Google account’s third-party access settings.

​
Search Console property

A property is the site boundary Google uses for reporting and permissions. Use the exact identifier returned by list_properties. An enabled property is one you have selected and saved in HyperGSC. Discovering a property does not enable it.

​
AI client and MCP server

The client is where you ask questions, such as Claude, ChatGPT, Codex, or Cursor. The MCP server at https://hypergsc.com/mcp publishes tool schemas and runs authorized requests. The agent chooses tools to answer a question. HyperGSC checks current permissions, property access, plan, and usage when a tool executes.

​
OAuth authorization

An OAuth grant authorizes a specific client after browser sign-in and consent. Review the requested permissions before approving the connection. Your enabled property selection determines which sites the client can read.

​
Report and research record

A diagnostic report stores the observations from its original run. Reading it does not refresh the underlying data. A saved keyword or SEO change is a record stored in HyperGSC. Optional projects:write consent allows these writes. Recording an SEO change does not apply that change to your website.

​
Availability and usage

A tool can appear in discovery even when your account cannot currently execute it. Read get_capabilities and get_usage to distinguish a missing permission, plan restriction, exhausted allowance, or property setup issue. Next, connect Search Console or explore the MCP overview.