Skip to main content
Glama
lv24-seo

lv24-seo

LV24 SEO — SEO insights for humans and AI agents

lv24-seo-optimizer

ci PyPI npm license python

Free-first SEO control plane for humans and AI agents.

Your site's SEO, without a dashboard. Pull Search Console, Yandex Webmaster and Metrika, Bing, CrUX and your own crawl into one history — then get a weekly diff by email, an MCP server and a CLI that agents can actually use. No paid platform, no SERP scraping, no vendor account.

🚀 Start

🧠 Use

🛠 Operate

Install · See it work · Docs

CLI · MCP tools · Skills

Scheduling · Data limits · Security

One tool that pulls Google Search Console, Yandex Webmaster, Yandex Metrika, Bing Webmaster, Chrome UX Report and PageSpeed Insights into a single normalized model, crawls your site for technical SEO regressions, and turns all of it into scheduled email reports, MCP tools, CLI commands and agent skills.

No paid SEO platform required. Everything in the default path has a free tier.

┌──────────── data sources (free) ────────────┐      ┌──── surfaces ────┐
│ GSC · Yandex Webmaster · Metrika · Bing ·    │ ───▶ │ CLI (--json)     │
│ CrUX · PSI · your own crawl + nginx logs     │      │ MCP server       │
└──────────────────────────────────────────────┘      │ Skills / AGENTS  │
                                                      │ Email / Telegram │
                                                      │ SQLite history   │
                                                      └──────────────────┘

From provider APIs and bounded crawl to reports, CLI, MCP and opt-in delivery

Why another SEO tool

  • Free-first fusion. Existing MCP servers wrap one vendor each and hand raw vendor shapes to the model. We join GSC + Bing + Yandex + Metrika per property, and we say out loud what the APIs cannot give you (Yandex has no query×page join, GSC caps at 50k rows/day, data lags 2–3 days). Bounded provider responses expose coverage, freshness and limitations; unknown totals stay unknown.

  • Comparable periods. The headline compares current and previous GSC windows. Yandex, Metrika, Bing, CrUX field data and PSI lab data keep separate sections. Opt-in delivery applies the configured significance thresholds and skips content already sent for the period.

  • Agent-native. A small, stable MCP tool surface (read-only by default), a JSON envelope on every CLI command, and skills that encode audit → plan → fix → verify against a real repository.

  • Zero spend. Public-repo CI, SQLite storage, SMTP/Telegram delivery, no SaaS in the default path. Paid-provider integrations are research/planned work, not dependencies or shipped adapters.

Related MCP server: seo-stack-mcp

Status

Beta (v0.5.0). Working today: six provider adapters (GSC, Yandex Webmaster, Yandex Metrika, Bing/IndexNow, CrUX, PSI), a 30-rule crawler, SQLite history, analysis (deltas, opportunities, indexing triage, multi-engine fusion, nginx log stats), report builders + HTML/text/Markdown renderers, SMTP/Telegram delivery with idempotency, the full CLI, the MCP server (11 tools, 3 resources, 3 prompts) and scheduler generators. Canonical source ids, GSC-only headline deltas, partial provider isolation and window/daily storage separation are enforced with regression tests.

Still honest gaps before v1.0: GSC service-account auth (OAuth token only today), sitemap submit / Yandex recrawl return an explicit WRITE_DISABLED (IndexNow really submits), and raw_retention_days is reserved (no raw archives are written yet). See docs/plans/2026-11-10-implementation-plan.md for the wave status.

Install

# Python (recommended)
uvx --from lv24-seo lv24-seo doctor
pipx install "lv24-seo[secrets]"       # or: uv tool install "lv24-seo[secrets]"

# Node users: thin launcher over the same CLI
npx @lv24/seo doctor --json
lv24-seo init --property https://example.com   # writes seo.toml + data/
lv24-seo auth set --provider gsc --stdin       # token to the OS keychain (needs lv24-seo[secrets])
lv24-seo gsc query --start 2026-11-01 --end 2026-11-07 --dimensions query,page
lv24-seo report weekly --days 7 --out reports/
lv24-seo report diff --markdown                 # week-over-week diff of stored snapshots
lv24-seo stats --days 7 --json                  # read-only per-provider dashboard snapshot
lv24-seo crawl --json                           # issues + sitemap↔crawl coverage diff
lv24-seo export skills --out ./skills          # packaged agent skills from the wheel
lv24-seo mcp serve                             # stdio MCP server
lv24-seo install --client claude|opencode|vscode|cursor

npx @lv24/seo requires uv (or an installed lv24-seo binary): the npm package is a launcher, not a second implementation.

See it work

$ lv24-seo doctor

[OK  ] python: 3.13.12
[OK  ] platform: Windows 11
[OK  ] config: C:\work\seo.toml
[OK  ] cwd_writable: C:\work
[FAIL] tokens: not configured yet (gsc / yandex / metrika / bing / crux)

doctor checks the runtime, config, data dir and token presence only — no network calls.

$ lv24-seo report weekly --days 7 --json --out reports/

# Writes report.json and report.html; the JSON envelope carries:
# meta.sources          successful providers
# meta.sources_failed   isolated source failures
# meta.complete         false for missing, capped or sampled inputs
# meta.limitations      caveats to read before interpreting the numbers
# No configured tokens: an explicit no-data report, with complete=false.

The same data is available as MCP tools (seo_weekly_report, gsc_search_analytics, yandex_query_stats, seo_indexing_triage, …) and as three skills that encode audit → plan → fix → verify.

What it will do

Surface

Examples

Reports

weekly search performance + delta, indexing triage, striking-distance opportunities, content decay, technical regressions

MCP tools

gsc_search_analytics, yandex_query_stats, yandex_indexing_state, seo_crawl_site, seo_weekly_report, seo_report_diff, seo_indexing_triage, seo_opportunities, seo_recrawl_request (gated), seo_sitemap_submit (gated)

CLI

init, doctor, auth, gsc, yandex, crawl, report, stats, schedule, export, mcp serve

Skills

seo-weekly, seo-indexing-triage, seo-technical-audit — decision trees + tool recipes + output contracts (install from the wheel: lv24-seo export skills --out ./skills)

Automation

cron / systemd timer / Windows Task Scheduler generators and a GitHub Actions recipe

Supported sources

Source

Free tier

Used for

Write operations

Google Search Console

yes (access token; service-account flow planned)

queries, pages, countries, devices; URL Inspection adapter

sitemap submit disabled

Yandex Webmaster

yes (OAuth)

queries, indexing history, diagnostics

recrawl disabled

Yandex Metrika

yes

sessions and users; filtered reports through adapter

—

Bing Webmaster + IndexNow

yes

queries, crawl issues, instant URL ping

IndexNow submit

Chrome UX Report

yes (API key)

origin-level field CWV

—

PageSpeed Insights

yes

lab audits per URL

—

Your site

—

crawl, robots, sitemap, JSON-LD, hreflang, links

—

nginx access logs

—

Python analysis helpers; no log-ingest CLI command yet

—

Documents

For AI agents

Read AGENTS.md first. It is the canonical contract: repo layout, how to run things, what is read-only, how to propose a change. Machine-readable helpers:

  • schemas/tools.json — generated tool schemas (works without MCP)

  • llms.txt — doc map for LLM crawlers

  • skills/*/SKILL.md — portable skills (Claude Code, OpenCode, Codex)

  • MCP Registry: io.github.LevapVeeskela/lv24-seo

License

Apache-2.0. See LICENSE and TRADEMARKS.md. Data pulled from Google/Yandex/Bing belongs to the property owner — this project never resells it.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Agent-first SEO toolkit with 24 MCP tools for keyword research, rank tracking, site audits up to 50k pages, competitor analysis, content gap detection, domain reputation, backlink intelligence, Google Search Console integration, and AI-powered strategy generation with Claude, GPT, and Ollama. SQLite-backed and bring-your-own-key.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      The complete open-source SEO data stack for AI agents, integrating Google Search Console, Google Analytics 4, Bing Webmaster Tools, and Microsoft Clarity with built-in analyst tools like cannibalization check, low-hanging fruit, and content gap analysis, all self-hosted and free.
      50 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Google Search Console, Bing Webmaster Tools, and PageSpeed Insights, allowing queries for analytics, sites, sitemaps, inspections, crawl issues, and page speed analysis via natural language.
      1,377 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Syncs Google Search Console performance data into a local ClickHouse database and exposes prepared SEO analysis tools to AI agents. Enables diagnosing traffic drops, finding striking-distance keywords, detecting cannibalization, auditing indexing, and generating weekly SEO reports through natural language.
      MIT