Skip to content
Back to search

seo-geo-weekly

MarketplaceWorks with Claude CodeGitHub

SEO + GEO (AI search visibility) loop for any website, as a Claude Code skill: Search Console + Bing Webmaster via Claude in Chrome, guided setup, weekly fixes, indexing, reports, weekly schedule.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fed3c3sa--seo-geo-weekly/badge.svg)](/listings/fed3c3sa--seo-geo-weekly)

HTML

<a href="/listings/fed3c3sa--seo-geo-weekly"><img src="/api/listings/fed3c3sa--seo-geo-weekly/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Option A: as a Claude Code plugin** (recommended, easy to update). Inside Claude Code:

/plugin marketplace add fed3c3sa/seo-geo-weekly
/plugin install seo-geo-weekly@seo-geo-weekly

**Option B: with the skills CLI.**

npx skills add fed3c3sa/seo-geo-weekly@seo-geo-weekly -g -y

**Option C: by hand.** Download `seo-geo-weekly.zip` from the [latest release](https://github.com/fed3c3sa/seo-geo-weekly/releases/latest) and unzip it into your skills folder:

mkdir -p ~/.claude/skills && unzip seo-geo-weekly.zip -d ~/.claude/skills/

- **Windows:** the skills folder is `%USERPROFILE%\.claude\skills\`. - **One project only:** use `<project>/.claude/skills/`.

Then restart Claude Code.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 21 lines
  1. {
  2. "name": "seo-geo-weekly",
  3. "owner": {
  4. "name": "fed3c3sa",
  5. "url": "https://github.com/fed3c3sa"
  6. },
  7. "metadata": {
  8. "description": "Marketplace hosting the seo-geo-weekly plugin for Claude Code.",
  9. "version": "1.0.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "seo-geo-weekly",
  14. "source": "./",
  15. "description": "SEO + GEO loop for any website from Google Search Console and Bing Webmaster data: guided setup, weekly diagnosis and fixes, indexing requests, reports, optional weekly schedule. Provides the seo-geo-weekly skill.",
  16. "category": "productivity",
  17. "version": "1.0.0",
  18. "keywords": ["seo", "geo", "search-console", "bing-webmaster", "ai-search"]
  19. }
  20. ]
  21. }
README.md · README · 181 lines
  1. # seo-geo-weekly
  2. **A Claude Code skill that improves your website's visibility in Google and Bing (SEO) and in AI answers (GEO): Google AI Overviews, ChatGPT search, Microsoft Copilot, Perplexity.**
  3. It works from your real data in Google Search Console and Bing Webmaster Tools, which Claude reads for you through the Claude in Chrome extension. It works on any site: a static site in a git repo, WordPress, Shopify, Wix, Webflow, Squarespace or Ghost.
  4. Starting from zero? The skill first walks you through everything that's missing:
  5. - installing and connecting Claude in Chrome;
  6. - signing in;
  7. - adding and verifying your site in Search Console and Bing;
  8. - submitting the sitemap;
  9. - setting up IndexNow.
  10. Claude does every step it can. You click only where your identity is needed: sign-ins, consent screens, your DNS or site admin. It never asks for your passwords.
  11. [![tests](https://github.com/fed3c3sa/seo-geo-weekly/actions/workflows/tests.yml/badge.svg)](https://github.com/fed3c3sa/seo-geo-weekly/actions/workflows/tests.yml)
  12. ![license](https://img.shields.io/badge/license-MIT-blue)
  13. ---
  14. ## Install
  15. **Option A: as a Claude Code plugin** (recommended, easy to update). Inside Claude Code:
  16. ```
  17. /plugin marketplace add fed3c3sa/seo-geo-weekly
  18. /plugin install seo-geo-weekly@seo-geo-weekly
  19. ```
  20. **Option B: with the skills CLI.**
  21. ```bash
  22. npx skills add fed3c3sa/seo-geo-weekly@seo-geo-weekly -g -y
  23. ```
  24. **Option C: by hand.** Download `seo-geo-weekly.zip` from the [latest release](https://github.com/fed3c3sa/seo-geo-weekly/releases/latest) and unzip it into your skills folder:
  25. ```bash
  26. mkdir -p ~/.claude/skills && unzip seo-geo-weekly.zip -d ~/.claude/skills/
  27. ```
  28. - **Windows:** the skills folder is `%USERPROFILE%\.claude\skills\`.
  29. - **One project only:** use `<project>/.claude/skills/`.
  30. Then restart Claude Code.
  31. ## Use
  32. Start Claude Code with Chrome attached (`claude --chrome`, or `/chrome` inside a session) and ask in your own words:
  33. - "Improve the SEO and GEO of https://www.mysite.com"
  34. - "Set up Search Console and Bing for mysite.com"
  35. - "Why doesn't my site show up when people search my name?"
  36. - "Run this week's SEO pass"
  37. - "Schedule the SEO run for mysite.com every Wednesday morning"
  38. **The first time:** Claude checks what's already in place and guides you through the rest. Then it takes a technical baseline of the site.
  39. **After that:** real Search Console numbers arrive 2 to 3 days after verification, so the first full data-driven run comes then. Run it weekly from there, or let the skill schedule itself.
  40. ## What happens each week
  41. 1. **Data:**
  42. - Search Console: 28-day totals, queries, pages, countries, daily rows, indexing;
  43. - Bing: search performance, plus **AI Performance**, the Copilot citations report;
  44. - clean, non-personalized search results for the queries that matter;
  45. - a technical audit of the live site.
  46. 2. **Diagnosis**, highest value first:
  47. - wrong facts;
  48. - indexing problems;
  49. - entity and brand signals;
  50. - questions that AI answers pick up;
  51. - near-duplicate queries;
  52. - titles and descriptions with poor click-through.
  53. 3. **A handful of true changes.** Every fact is checked against a primary source that day, and each change is recorded so next week can tell what worked.
  54. 4. **Gates:** automated checks of titles, descriptions, canonicals, structured data, FAQ sync, links, sitemap and robots.txt.
  55. 5. **An independent review** by a separate agent before anything is indexed.
  56. 6. **Publish**, but only what you authorized. Then request indexing on Google and Bing and ping IndexNow.
  57. 7. **A short report:** what moved, what changed and why, what to check next time, and the off-site steps only you can do (profile links, store listings).
  58. ## Run it every week on its own
  59. At the end of setup, Claude offers to schedule the loop. Your computer's own scheduler opens a visible Claude Code session with Chrome every week:
  60. - **macOS:** launchd;
  61. - **Linux:** cron;
  62. - **Windows:** Task Scheduler.
  63. The session runs the loop and sends a desktop notification with the result.
  64. ```bash
  65. S=<skill folder>/scripts/schedule.py # after install, also ~/.seo-geo-weekly/schedule.py
  66. python3 $S install mysite.com --day wed --time 10:07 # safe permissions by default
  67. python3 $S run mysite.com --test # one-minute check, with you watching
  68. python3 $S status # or: remove mysite.com
  69. ```
  70. You don't need to type these: Claude runs them for you during setup.
  71. Why not Claude Code's other schedulers:
  72. - **Cloud routines (`/schedule`):** they run on Anthropic's servers and can't reach your signed-in Chrome, so they can't read Search Console.
  73. - **`/loop`:** it lives only while one session stays open.
  74. Details are in [`references/scheduling.md`](skills/seo-geo-weekly/references/scheduling.md).
  75. ## What's inside
  76. ```
  77. skills/seo-geo-weekly/
  78. ├── SKILL.md the loop: setup check, data, diagnosis, editing, gates, review, publishing, report
  79. ├── references/
  80. │ ├── setup.md first-time setup, step by step, per platform and DNS host
  81. │ ├── consoles.md reading Search Console, Bing Webmaster and clean SERPs through Chrome
  82. │ └── scheduling.md the weekly schedule
  83. ├── scripts/ Python 3 + curl, no other dependencies
  84. │ ├── audit_live.py read-only technical + on-page audit of any live site
  85. │ ├── verify_site.py pre-publish gates for a folder of HTML (repo or build output)
  86. │ ├── seo_checks.py the shared page checks
  87. │ ├── compare.py this run's numbers vs the previous run's
  88. │ ├── indexnow.py tell Bing and others which pages changed
  89. │ └── schedule.py install / test / list / remove the weekly run
  90. └── templates/
  91. ├── site.md the site profile (mode, authorization, rules, queries, sources)
  92. └── report.md the weekly report
  93. ```
  94. You can run the scripts on their own too:
  95. ```bash
  96. python3 skills/seo-geo-weekly/scripts/audit_live.py https://www.example.com --max 40
  97. python3 skills/seo-geo-weekly/scripts/verify_site.py ./public --site https://www.example.com
  98. ```
  99. `audit_live.py` checks:
  100. - that http/https/www variants redirect once;
  101. - that missing pages return a real 404;
  102. - robots.txt, including which AI crawlers are blocked;
  103. - sitemaps and sitemap indexes, self-canonicals and noindex;
  104. - titles and descriptions, h1, lang and alt text;
  105. - that JSON-LD parses, with no dangling `@id`;
  106. - that FAQPage text matches the visible FAQ.
  107. ## Requirements
  108. - **Claude Code.**
  109. - **Claude in Chrome,** so Claude can read Search Console and Bing for you. It needs:
  110. - a paid Claude plan that includes it;
  111. - Claude Code signed in with `/login`;
  112. - Chrome or another Chromium browser listed in the [official guide](https://code.claude.com/docs/en/chrome).
  113. Without the extension the skill still works: you export CSVs from the two consoles and Claude does the rest.
  114. - **Accounts:** a Google account for Search Console, and a Microsoft, Google or Facebook account for Bing Webmaster Tools.
  115. - **Access to your site:** wherever it is edited (a repo, or your CMS admin), and ideally your domain's DNS.
  116. - **Python 3 and curl:**
  117. - macOS and most Linux have both;
  118. - on Windows, curl is built in; install Python from python.org and use `py` where the docs say `python3`.
  119. ## Principles
  120. - **Nothing invented.** Every fact on your site comes from a source checked that day. AI assistants repeat wrong facts.
  121. - **A few changes per week,** recorded, so you can tell what worked.
  122. - **Your accounts stay yours.** Claude never types passwords or 2FA codes. Off-site changes (LinkedIn, GitHub profile, store listings) are listed for you to do.
  123. - **Publishing follows your rules.** It publishes only what your site profile authorizes. Everything else is prepared and handed to you.
  124. - **Your data stays on your machine,** in `~/seo/<your-domain>/` by default.
  125. ## Development
  126. The scripts use only the standard library. To run the tests:
  127. ```bash
  128. python3 -m unittest discover -s tests -v
  129. ```
  130. CI runs them on Linux, macOS and Windows.
  131. Issues and pull requests are welcome. Two rules for changes to the skill text:
  132. - every rule should come from something that happened on a real site;
  133. - every claim about a product (Search Console, Bing, a CMS) should be checked against its current documentation.
  134. ## License
  135. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.