LangQuang for Claude
LangQuang connects Claude to Google Search Console, Google Analytics 4, and PageSpeed Insights. You ask about your site's search performance in plain language, and Claude queries your own Google data to answer, then saves the result as a shareable report.
Each user signs in with their own Google account. Requests run against the properties that account already has access to, using that account's token. LangQuang does not hold a shared service account or see data from properties you have not connected.
What you need before connecting
- A LangQuang account created at dash.langquang.com/register
- A Google account with access to at least one Search Console property or GA4 property
- Claude on any plan that supports connectors
PageSpeed Insights and CrUX tools work without connecting Google, since both read public data. Search Console and GA4 tools need a connection.
Connecting
- 1
Add LangQuang as a connector in Claude, using the server URL
https://lq.mcp.langquang.com/mcp - 2
Claude opens LangQuang's sign-in page at dash.langquang.com/login. Sign in, or create an account from the link on that page.
dash.langquang.com/login - 3
Approve the connection. Claude receives a token scoped to your LangQuang account.
- 4
Open the dashboard at dash.langquang.com and go to Connections. Connect Google Search Console, Google Analytics, or both. Google's consent screen asks for read access to your Search Console data, plus write access if you want to submit sitemaps from Claude.
dash.langquang.com
Ask Claude to run list_sites to confirm the connection. It returns the Search Console properties your Google account can reach.
Managing more than one client
Agencies can connect several Google accounts to one LangQuang account, each under a label. Run list_connections to see the labels, then pass client_label to any Search Console or GA4 tool to pick which account to query. Tools default to the connection labeled default.
Tools
23 tools, grouped by what they read. Nineteen are read-only. The four that write are marked below; Claude asks for confirmation before running those.
Search Console
| Tool | What it does |
|---|---|
list_sites | Lists the Search Console properties you can access |
search_analytics | Clicks, impressions, CTR, and average position for a property |
list_sitemaps | Sitemaps submitted for a property, with fetch and index status |
get_sitemap_details | Full error and warning text for one sitemap |
submit_sitemapwrites | Submits or resubmits a sitemap so Google refetches it |
inspect_url | Index status for a single URL: coverage, verdict, mobile usability |
check_urls_health | Index and 404 status for a list of URLs |
fetch_as_googlebot | Requests a public URL with Googlebot's user agent and reports the response |
fetch_as_googlebot sends an HTTP request from LangQuang's server with Googlebot's User-Agent string. It does not use Google's crawler or your API quota. Use it to check whether a firewall is blocking Googlebot specifically. It accepts GET and HEAD, and only fetches publicly reachable addresses.
Analytics 4
| Tool | What it does |
|---|---|
list_ga4_properties | Lists the GA4 properties you can access |
ga4_report | Runs a GA4 report with the metrics and dimensions you name |
ga4_top_pages | Top pages by views, with engagement figures |
ga4_traffic_sources | Traffic by channel and source |
ga4_conversions | Key event counts and conversion rate, by event name |
ga4_realtime | Active users in the last 30 minutes |
ga4_compare_periods | Compares a metric set against the preceding period |
Page speed
| Tool | What it does |
|---|---|
run_pagespeed | Runs a PageSpeed Insights Lighthouse audit for a URL |
crux_history | Chrome UX Report field data over the last 40 weeks |
run_pagespeed returns lab data from a single synthetic run. crux_history returns field data from real Chrome users, bucketed good, needs improvement, and poor. The two disagree often, and the field data is the one that affects ranking.
Reports
| Tool | What it does |
|---|---|
list_report_templates | Lists templates available to create_report |
create_reportwrites | Builds a new report in your dashboard |
create_interactive_reportwrites | Builds a full interactive Search Console report |
update_reportwrites | Changes an existing report |
Reports are snapshots. A report holds the figures as they stood when Claude built it, so a link you send a client shows the same numbers when they open it. Reports are private until you share them. Sharing generates a per-recipient link you can revoke.
Diagnostics
| Tool | What it does |
|---|---|
list_connections | Lists your labeled client connections for a service |
seo_playbook | Maps a described problem to an ordered sequence of tool calls |
seo_playbook helps when you describe a symptom rather than name a metric. Asking why traffic dropped last month routes to a sequence that checks search performance, then index coverage, then page speed, instead of guessing which to query first.
What you can ask
“Which queries lost the most clicks on example.com in the last 28 days?”
“Compare this month's organic sessions to last month.”
“Is https://example.com/pricing indexed?”
“My sitemap says it failed to fetch. What's wrong?”
“Why did traffic drop in August?”
“Build a client report for example.com covering the last quarter.”
Rate limits
Google sets the limits, not LangQuang. Search Console allows roughly 2,000 URL inspections per day per property, so keep check_urls_health lists short. PageSpeed Insights is rate limited per key and can reject bursts of requests.
Data handling
LangQuang stores your Google OAuth access and refresh tokens so your connection survives between sessions. Search Console and GA4 figures are fetched per request and are not retained beyond the request, except where you save them into a report you created.
Full detail, including retention and deletion requests, is in the privacy policy.
