CLAUDE SEO V2.2.4:
RUNTIME. RELIABILITY. COMMUNITY.

Claude SEO v2.2.4 is the current public release. It follows the guidance and consistency work in v2.2.3 with a maintenance pass focused on runtime setup, discovery safety, API correctness, portability, and community attribution. The official tag resolves to commit 6b63c8b.

The release is deliberately practical. It does not add a new scoring category or another marketing abstraction. Instead, it repairs the paths that determine whether an audit can be installed, discover a site safely, collect complete data, and explain degraded results honestly.

What changed in Claude SEO v2.2.4?

The release notes group the work around reliability. A managed cross-platform Python runtime now has explicit setup and diagnostic commands. Sitemap discovery is protected against server-side request forgery while checking robots.txt and common content-management-system locations. Google Search Console and Bing workflows were corrected where pagination, limits, totals, completeness, or removed endpoints could produce incomplete or broken output.

• Managed runtime: explicit /seo setup provisioning and a read-only /seo doctor check.
• Safer discovery: SSRF-safe sitemap discovery through robots.txt and common CMS paths.
• Complete GSC data: fixes for pagination, exact limits, dimensionless totals, and completeness reporting.
• Supported Bing workflows: removed link endpoints were replaced with bounded alternatives.
• Cross-platform repairs: fixes for DataForSEO permissions, Banana paths, Windows portability, SPA rendering, JSON-LD extraction, and FAQPage guidance.

Why the managed runtime matters

Plugin installation and dependency provisioning are separate operations in v2.2.4. That boundary is useful because installing a plugin should not silently run package managers or download a browser. After installation, /seo setup creates the isolated environment in Claude's persistent plugin data. The /seo doctor command inspects the environment without changing it.

/plugin marketplace add AgriciDaniel/claude-seo
/plugin install claude-seo@agricidaniel-claude-seo
/seo setup
/seo doctor

The official v2.2.4 installation guide documents plugin, manual, and Windows paths. Python 3.10 or newer, Git, and Claude Code remain prerequisites.

This setup model also makes failure states easier to explain. If the core environment is missing, setup can be run again. If only the browser component is unavailable, the installer reports a degraded result and raw-fetch analysis remains available. Users can see which capability is missing instead of treating every runtime problem as the same installation failure.

Manual installs remain documented for Unix-like systems and PowerShell. The Windows path uses a normal Git clone instead of piping a remote script directly into a shell. That choice keeps the installation inspectable and works with Claude Code's own security guardrails.

What changed in data collection?

Google Search Console completeness

Search Console integrations are only useful when users can distinguish complete totals from limited or paginated samples. Version 2.2.4 fixes pagination, exact row limits, dimensionless totals, and completeness reporting. These changes reduce the chance that a valid API response is summarized as a complete dataset when additional pages or dimensions remain.

Sitemap and Bing safety

Sitemap discovery now checks declared and common locations through the shared SSRF-safe request path. Bing Webmaster link endpoints that are no longer available were replaced with bounded supported workflows. The release notes do not claim to recreate removed data. They describe a safer fallback with explicit limits.

Rendering and extraction

Single-page application rendering and JSON-LD extraction received direct fixes. Those changes matter because client-rendered pages and structured-data blocks can otherwise look empty or malformed to an auditor even when a browser displays them correctly. The release also corrects current FAQPage guidance after Google retired FAQ rich results for all sites.

The smaller portability fixes support the same goal. DataForSEO permissions now match the operations the extension performs, Banana references resolve through the documented paths, and Windows-specific assumptions were removed where they could break an otherwise valid workflow. Each item is narrow, but together they reduce the number of platform-dependent results that users have to diagnose manually.

How was the release verified?

The public release reports 410 passing tests. Strict consistency and portability checks report zero errors and zero warnings. Secret and personal-data scans are clean. Those checks validate the repository and release process; they do not guarantee search rankings or replace testing on a user's own environment.

Community maintenance is part of the release

Version 2.2.4 follows a full review of open issues and pull requests. Contributor and issue-reporter acknowledgements are now complete, and the maintainer email was removed from public package and citation metadata. That cleanup makes attribution more complete while reducing unnecessary personal information in distributed files.