Your First Day with Yeet: Dashboard, GA4, and Agents

Short answer up front: yeet is not Search Console-only. If GA4 is connected in Settings, yeet uses it for sessions, engagement, and AI referral traffic. GSC powers most early SEO cards because that is where queries, CTR, and positions live. Different questions, same product.

This guide is the blog version of the in-product docs:

• Your First Day (hour-by-hour)
• Getting Started (full map + MCP for every major agent)

The loop you are joining

1. Connect GSC properties (and GA4).
2. Watchers read search + traffic + AI-visibility signals.
3. Findings become optimization cards.
4. You or your agent ships a fix (prompt or PR).
5. Verifier checks the live page and waits on GSC/GA4 when needed.

SEO, AEO, and GEO are equal pillars — ranks, answer engines, and generative citations.

Hour 0: connect the right switches

In Settings:

• Toggle GSC properties to Connected for sites you want optimized. Hidden means ignored.
• Connect matching GA4 properties so session drops and AI referrals can show up.
• Optional but powerful: GitHub (for PRs), API key (for MCP), auto-indexer.

Pick one dogfood site for day one. Leave the rest connected in the background.

Two ways to work (same backend)

Human path

1. Open Dashboard.
2. Open a FIX card. Confirm the site badge matches your dogfood site (titles can mention other brands as keywords).
3. Copy the fix prompt into Cursor/Claude, or Apply via PR if GitHub is linked.
4. Let verifying run — GSC/GA4 lag is normal.

Agent path

Create an API key, then add MCP:

{
  "mcpServers": {
    "yeet-seo": {
      "command": "npx",
      "args": ["-y", "yeet-seo-mcp"],
      "env": {
        "YEET_SEO_API_KEY": "yseo_...",
        "YEET_SEO_API_URL": "https://yeet.ani.computer"
      }
    }
  }
}

Works for Cursor, Claude Code, Claude Desktop, OpenClaw, Hermes, and most MCP clients. Codex: use MCP if your build supports it; otherwise REST GET /api/v1/help and POST /api/v1/skills.

Then say: “what can yeet do” — the agent should call help and show the menu.

Recommended skill order:

onboard → scan → index → aeo → optimize → create → seo_report

Continuous optimize

Once MCP works, say:

Use yeet and continuously optimize for SEO, AEO, and GEO — fix existing pages and write new content.

Yeet asks setup once, then returns a daily/weekly seo_report checklist. See Continuous Optimize.

End-of-day checklist

• At least one GSC property Connected (+ GA4 if you have it)
• Cards visible or a scan / Run now kicked
• One fix shipped or PR opened
• MCP connected (or REST help bookmarked)
• You know verifying can take days

FAQ

Why did early cards look GSC-heavy? Because query/CTR/position opportunities are the fastest high-signal loop. GA4 often corroborates later (sessions, AI referrals).

I disconnected a site but still see its brand in titles. Check the site badge — keyword text ≠ property.

Is yeet Ahrefs? No. It is an agent control plane on your owned data + research providers, not a global backlink index.

Quick FAQ

Where are the official docs? First Day · Getting Started · Integrations.

What should my agent say first? “what can yeet do” then “onboard my site”.