← ClaudeAtlas

seo-gsc-brand-vs-nonbrandlisted

Analyze branded vs non-branded traffic split using Google Search Console data. Shows what percentage of organic clicks come from brand name searches vs generic queries. Requires user to confirm brand terms before analysis. Use when user says "brand vs nonbrand", "branded traffic", "brand queries", "non-brand traffic", or "branded vs generic".
YogeshKu7877/claude-seo-skills · ★ 4 · Data & Documents · score 80
Install: claude install-skill YogeshKu7877/claude-seo-skills
# GSC Brand vs Non-Brand — Brand Traffic Split Analysis @skills/seo/references/mcp-degradation.md @skills/seo/references/gsc-api-reference.md Analyzes what share of organic traffic comes from branded queries vs generic queries. IMPORTANT: This command REQUIRES user-provided brand terms before making any API call. The `analyze_brand_queries` tool needs a `brandTerms` array — never guess brand terms. ## MCP Check Before calling any GSC tool, verify the MCP is connected: 1. Use ToolSearch with query `+google-search-console` 2. If tools returned — note the actual tool name prefix, proceed to Inputs 3. If no tools returned — display the GSC MCP error template from `references/mcp-degradation.md` and stop: ``` ## Google Search Console MCP Not Available The `/seo gsc brand-vs-nonbrand` command requires the GSC MCP, which is not currently connected. **What you can do:** - Use `/seo technical <url>` for crawlability and indexability analysis (no live data) - Use `/seo audit <url>` for a full static SEO audit **To connect GSC MCP:** - Install and configure a Google Search Console MCP server (see README for setup) - Add it to ~/.claude/mcp.json at user scope (NOT project scope) - Verify GSC property access before running commands (domain vs URL prefix format) - See references/gsc-api-reference.md for property format details ``` ## Inputs - `site`: The GSC property URL. Accept both formats: - Domain property: `sc-domain:example.com` - URL prefix: `https://example.com` o