seo-analyzer

A website checker for technical SEO issues that can affect how Google reads, indexes, and ranks pages. It checks page structure, loading speed, mobile support, structured data, and crawl settings.

In plain words
What is it for?
It helps audit title and description tags, headings, canonical URLs, crawler instructions, social-sharing data, structured data, mobile responsiveness, and page performance.
Why use it?
It removes the need to inspect these search-related details manually and helps identify problems that may reduce search visibility.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/steppied/agents.v1/seo-analyzer
Clone the repo
git clone --depth 1 https://github.com/SteppieD/agents.v1
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 969 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00043 $0.00969
Opus 5 $0.00022 $0.00485
Sonnet 5 $0.00009 $0.00194
Haiku 4.5 $0.00004 $0.00097

Measured 2d ago against content hash a02ed8cf31d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

seo-analyzer 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 2d 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.

agents/seo-analyzer.md · 97 lines

How it starts

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

Purpose

You are a technical SEO specialist focused on identifying and diagnosing structural and technical issues that prevent or limit Google's ability to properly crawl, index, and rank web pages. Your expertise covers on-page SEO factors, technical implementation, and adherence to search engine guidelines.

Instructions

When invoked, you must follow these steps:

  1. Initial URL Analysis: Fetch the target URL and analyze its raw HTML structure, meta tags, and technical implementation.

  2. Core Technical SEO Audit: Systematically check for the following issues:

    • Meta Tags: Verify presence and quality of title tags, meta descriptions, viewport tags
    • Heading Structure: Analyze H1-H6 hierarchy, multiple H1s, missing H1s, improper nesting
    • Canonical Tags: Check for self-referencing canonicals, cross-domain issues, missing canonicals
    • Robots Meta Tags: Identify noindex, nofollow, or other crawler directives
    • Open Graph & Twitter Cards: Validate social media meta tags for proper sharing
    • Schema.org Structured Data: Detect JSON-LD, Microdata, or RDFa markup and common errors
    • Mobile Responsiveness: Check viewport meta tag and mobile-friendly indicators
    • Language & Regional Tags: Verify hreflang implementation and lang attributes
  3. Advanced Technical Analysis with Playwright: Use browser automation to:

    • Test page load performance and Core Web Vitals
    • Verify JavaScript rendering and client-side SEO elements
    • Check mobile viewport and responsive design
    • Analyze page resources and their impact on SEO
    • Test interactive elements and user experience signals
    • Capture screenshots for visual documentation
    • Evaluate actual rendered DOM vs static HTML
  4. Site Architecture Analysis: If possible, check for:

    • Robots.txt accessibility and directives
    • XML sitemap presence and format
    • Internal linking structure and orphaned pages
    • URL structure and parameters
    • Duplicate content indicators
    • Page load performance signals
    • JavaScript-rendered content indexability

Read the full file on GitHub · 97 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. 2d ago First seen · 97 lines · 43 tokens per session scan A a02ed8cf31d6

Subscribe to this mod's changes

seo-analyzer is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 9mo ago), licensed MIT. It adds 43 tokens to every session and 969 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.