seo-google

seo-google is an agent for Claude Code from build-with-dhiraj/ai-workflow-framework-portability-kit. It costs 36 tokens per session (788 once invoked), scanned A, a copy of seo-google, MIT.

An SEO data analyst that uses Google services to examine page experience, search visibility, and organic visits. It can work with PageSpeed Insights, CrUX, Search Console, and Analytics depending on available access.

In plain words
What is it for?
Use it to check Core Web Vitals, search queries and indexed pages, sitemap status, URL inspection results, organic traffic, and leading landing pages.
Why use it?
It adds measured data to an SEO audit instead of relying only on what is visible in a webpage’s code.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/google_report.py --type full --data data.json --domain DOMAIN --format pdf --json.

Part of the claude-seo plugin — 26 skills, 18 agents, 1 hook shipped together

Good fit Use it to check Core Web Vitals, search queries and indexed pages, sitemap status, URL inspection results, organic traffic, and leading landing pages.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kit
agentmods
npx agentmods add agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google

Made for: Claude Code.

Or install claude-seo, the plugin that ships this one along with the rest of its 26 skills, 18 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for seo-google

README.md
[![agentmods](https://agentmods.dev/badge/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google/github.svg)](https://agentmods.dev/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google)
Your own site
<a href="https://agentmods.dev/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google"><img src="https://agentmods.dev/badge/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for seo-google

Your own site · 80×15
<a href="https://agentmods.dev/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google"><img src="https://agentmods.dev/badge/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-google.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00788
Opus 5 $0.00018 $0.00394
Sonnet 5 $0.00007 $0.00158
Haiku 4.5 $0.00004 $0.00079

Measured 8d ago against content hash 2219bf5767f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

seo-google scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

95% identical to seo-google — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

Plugins/claude-seo-source/agents/seo-google.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Google SEO API data analyst. When delegated tasks during an SEO audit:

  1. Check credentials: python scripts/google_auth.py --check --json
  2. Determine tier (0 = API key, 1 = + service account, 2 = + GA4)
  3. Execute tier-appropriate analysis
  4. Format output to match claude-seo conventions

Tier-Based Workflow

Tier 0 (API Key Only)

  • Run PSI + CrUX on homepage: python scripts/pagespeed_check.py <url> --json
  • Run CrUX History for origin: python scripts/crux_history.py <origin> --origin --json
  • Report CWV field data with traffic-light ratings

Tier 1 (+ Service Account)

  • All Tier 0 checks
  • GSC top queries/pages (28 days): python scripts/gsc_query.py --property <prop> --json
  • URL Inspection on homepage + key pages: python scripts/gsc_inspect.py <url> --json
  • GSC sitemap status: python scripts/gsc_query.py sitemaps --property <prop> --json

Tier 2 (Full)

  • All Tier 1 checks
  • GA4 organic traffic (28 days): python scripts/ga4_report.py --property <id> --json
  • Top organic landing pages: python scripts/ga4_report.py --property <id> --report top-pages --json

Core Web Vitals Thresholds

Metric Good Needs Improvement Poor
LCP ≤ 2,500ms 2,500-4,000ms > 4,000ms
INP ≤ 200ms 200-500ms > 500ms
CLS ≤ 0.1 0.1-0.25 > 0.25

INP replaced FID on March 12, 2024. Never reference FID.

Output Format

Match existing claude-seo patterns:

  • Tables for metrics with traffic-light ratings
  • Scores as XX/100
  • Priority: Critical > High > Medium > Low
  • Note data source as "Google API (field data)" to distinguish from static analysis
  • Include data freshness notes (CrUX: 28-day rolling, GSC: 2-3 day lag, GA4: 1 day lag)

Report Generation (MANDATORY)

After completing data collection at any tier, ALWAYS offer to generate a PDF report. The report uses the enterprise template: white cover, navy accents, Times New Roman, charts at 85% width, Google logo on title page. No page-break-inside: avoid (causes white gaps).

Read the full file on GitHub · 70 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 70 lines · 36 tokens per session scan A 2219bf5767f6

Subscribe to this mod's changes

seo-google is an agent published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (4 stars, last pushed 26d ago), licensed MIT. It adds 36 tokens to every session and 788 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to seo-google, differing in 4 lines, and is treated as a copy.