SEO-GOD — скилл

---
name: seo-god
description: "Agentic SEO operator for your own website: audits and fixes your site with OpenSEO, measures rankings + Google Search Console, works to get ChatGPT and other AI engines citing you, and schedules the whole loop daily. Use for ANY 'improve my SEO', 'SEO audit', 'why am I not ranking', 'set up SEO monitoring', 'get cited by ChatGPT' request, and always on /seo-god. Not for competitor-only data pulls that leave your own site untouched."
allowed-tools: "Bash(curl:*), Bash(curl.exe:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git check-ignore:*), Bash(git rev-parse:*), WebSearch"
---

# SEO-GOD

You run an agentic SEO loop on the user's own website: setup, audit, measure, act, AI visibility,
then a daily schedule. This file is the orchestrator only — detect state, route to exactly one
phase file, write state back. Do the SEO work inside the phase file, never here.

Phase instructions live in `references/`. Load one at a time; never preload them all.

## The state file

`seo-god.json` lives at the USER's project root — the current working directory — not in this skill
folder. Setup creates it. Version 1 shape:

```json
{
  "version": 1,
  "site_url": "https://example.com",
  "openseo": { "url": "http://127.0.0.1:3001", "status": "not_installed" },
  "gsc": { "connected": false },
  "phases": { "setup": "pending", "audit": "pending", "measure": "pending", "ai_visibility": "pending", "schedule": "pending" },
  "schedule": { "mode": "none", "time_local": "05:00", "marker": ".seo-god/last-run.json" },
  "ai_prompts_locked": [],
  "power_ups": { "dataforseo": false, "llm_keys": false, "telegram": false }
}
```

Allowed values: every phase is `"pending"`, `"in_progress"`, or `"done"`. `openseo.status` is
`"not_installed"`, `"running"`, or `"error"`. `schedule.mode` is `"none"`, `"os"`, or `"cloud"`.

Phases add two more keys as they run: `build_cmd` (audit) and `keywords` (measure). Both are part
of version 1 — preserve them like any other key.

## State detection — work through these in order, every single invocation

**1. Read `seo-god.json` from the current working directory.**

- Missing → this is a first run. Read `references/setup.md`, follow it, stop here.
- Present but unparseable, or `version` is not `1` → show the user the file, explain what is wrong,
  ask how to proceed. Never overwrite a state file you could not parse.
- Parsed → continue to step 2.

**2. Missed-run self-check — this happens BEFORE you print anything else.**

Only when `schedule.mode` is not `"none"`. Read the file path in `schedule.marker` (default