AgriciDaniel · Pegarose · Jul 22, 2026
@@ -1,6 +1,6 @@
 {
   "name": "codex-seo",
-  "version": "1.9.6+codex.5",
+  "version": "2.2.4-codex.0",
   "description": "Comprehensive SEO analysis skill suite for Codex. Includes technical SEO, content quality, schema markup, image optimization, sitemap architecture, GEO/AEO, backlinks, local SEO, maps intelligence, semantic clustering, SXO, drift monitoring, e-commerce SEO, Google APIs, and deterministic reporting workflows.",
   "author": {
     "name": "AgriciDaniel",

@@ -1,22 +1,22 @@
 cff-version: 1.2.0
-message: "If you use this software, please cite it as below."
+title: Claude SEO
+message: >-
+  If you use this software, please cite it using the metadata from this file.
 type: software
-title: "Codex SEO"
-version: "1.9.6+codex.1"
-date-released: "2026-04-27"
 authors:
-  - name: "AgriciDaniel"
-url: "https://github.com/AgriciDaniel/codex-seo"
-license: "MIT"
+  - alias: AgriciDaniel
+    given-names: Daniel
+    family-names: Agrici
+    website: 'https://agricidaniel.com'
+repository-code: 'https://github.com/AgriciDaniel/claude-seo'
+url: 'https://github.com/AgriciDaniel/claude-seo'
+license: MIT
+version: 2.2.4
+date-released: '2026-07-20'
 keywords:
   - seo
-  - codex
-  - codex-cli
-  - seo-audit
-  - python
-references:
-  - type: software
-    title: "codex-seo"
-    authors:
-      - name: "AgriciDaniel"
-    repository-code: "https://github.com/AgriciDaniel/codex-seo"
+  - claude-code
+  - ai-tools
+  - schema-markup
+  - e-e-a-t
+  - geo
@@ -1,21 +1,83 @@
-# Code of Conduct
+# Contributor Covenant Code of Conduct
 
-Codex SEO should be a useful, professional, and safe project space.
+## Our Pledge
 
-## Standards
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
 
-- Be respectful and direct.
-- Keep issues and pull requests focused on the project.
-- Assume good intent, but respond to impact.
-- Do not share private credentials, tokens, customer data, or exploit details in public threads.
-- Do not harass, threaten, spam, or derail maintainers or contributors.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
-## Reporting
+## Our Standards
 
-For security issues, follow [SECURITY.md](SECURITY.md).
+Examples of behavior that contributes to a positive environment for our community include:
 
-For conduct issues, contact the maintainer through GitHub. Include the relevant links, screenshots, and context. Reports will be reviewed by the maintainer and handled with the minimum disclosure needed to resolve the issue.
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Enforcement
 
-Maintainers may edit, hide, delete, or lock comments and issues that violate these standards. Repeated or severe violations may result in being blocked from project spaces.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at opening a GitHub Security Advisory at https://github.com/AgriciDaniel/claude-seo/security/advisories/new (see SECURITY.md). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
@@ -1,49 +1,80 @@
-# Contributing to Codex SEO
+# Contributing to claude-seo
 
-Thanks for contributing.
+Thanks for your interest in contributing! Here's how to get involved.
 
-## Ground Rules
+## Reporting Bugs
 
-- Keep changes focused and minimal.
-- Preserve project lineage and attribution to the upstream project.
-- Do not remove legal/disclosure language without maintainer approval.
-- Use clear commit messages.
+Open a [GitHub Issue](https://github.com/AgriciDaniel/claude-seo/issues) with:
 
-## Local Setup
+- Your OS and Python version
+- The full error output (copy from terminal)
+- The command or step that failed
+- The URL you were analyzing (if applicable)
 
-```bash
-gh repo clone AgriciDaniel/codex-seo
-cd codex-seo
-python -m pip install -r requirements.txt
-```
+## Suggesting Features
+
+Use [GitHub Discussions](https://github.com/AgriciDaniel/claude-seo/discussions) for feature ideas and questions.
 
-If you are working from a public fork, a normal `git clone` of that fork is fine. Keep credentials, `.env` files, `.mcp.json`, `output/`, and `.seo-cache/` out of commits.
+## Pull Requests
 
-## Validation Before PR
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/my-feature`)
+3. Make your changes
+4. Test with a sample URL before submitting
+5. Submit a PR with a clear description of what changed and why
 
-Run the same baseline checks used by CI:
+### Development Setup
+
+#### Option A: Local install
 
 ```bash
-bash -n install.sh
-bash -n uninstall.sh
-bash -n hooks/pre-commit-seo-check.sh
-python -m pytest tests/
-python -m compileall -q scripts hooks
+git clone https://github.com/YOUR_USERNAME/claude-seo.git
+cd claude-seo
+bash install.sh
 ```
 
-## Pull Request Checklist
+#### Option B: GitHub Codespaces / VS Code Dev Containers
+
+A `.devcontainer/devcontainer.json` is included so you can develop without any
+local setup. Two paths:
+
+- **GitHub Codespaces**: click **Code -> Codespaces -> Create codespace on
+  main** on the repo's GitHub page. You get a fully provisioned Python 3.12
+  environment with `requirements.txt` installed and Playwright + Chromium
+  ready, in about 60 seconds.
+- **VS Code Remote Containers**: with the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
+  installed, clone the repo locally then run **Dev Containers: Reopen in
+  Container** from the command palette.
+
+Both paths use the same image (`mcr.microsoft.com/devcontainers/python:3.12`)
+and post-create command (`pip install -r requirements.txt && playwright
+install chromium`). No additional setup needed for either.
+
+### Guidelines
+
+- All Python scripts should output JSON for Claude Code to parse
+- Shell scripts should use `set -euo pipefail` for safety
+- SKILL.md files must stay under 500 lines
+- Reference files should be focused and under 200 lines
+- Follow kebab-case naming for all directories and files
+- Keep dependencies minimal
 
-- Explain the problem and the fix.
-- Note any behavior changes.
-- Update docs when commands or workflows change.
-- Avoid unrelated refactors.
+### Code Style
 
-## Code Style
+- Python: Follow PEP 8 conventions. Use `ruff check` or `flake8` for linting before submitting
+- Shell: Use `set -euo pipefail` and quote all variables
+- Markdown: Keep lines under 120 characters where practical
 
-- Python: follow PEP 8 conventions. If you have [Ruff](https://docs.astral.sh/ruff/) installed, run `ruff check .` before submitting.
-- Shell scripts: use `shellcheck` where possible.
-- Keep formatting consistent with surrounding code.
+## Community Extensions (Pro Hub Challenge)
 
-## Security Fixes
+Claude SEO accepts community-built extensions through challenges and PRs.
+v1.9.0 integrated 5 challenge submissions and v1.9.7 added 9 community pull
+requests from 7 contributors. See [CONTRIBUTORS.md](CONTRIBUTORS.md) for the
+full credits.
 
-For vulnerabilities, follow `SECURITY.md` instead of opening a detailed public issue.
+To submit a community extension:
+1. Build your skill/agent/script following the patterns in this repo
+2. Keep SKILL.md under 500 lines, references under 200 lines
+3. All URL-fetching scripts must route through `scripts/url_safety.py` — the canonical SSRF / DNS-rebinding layer (`validate_url()`, `safe_requests_session()`); never fetch a user-supplied URL without it. (`google_auth.py` is OAuth token lifecycle only — not an SSRF guard.)
+4. Include `original_author` in your SKILL.md frontmatter metadata
+5. Submit a PR or post in the [AI Marketing Hub](https://www.skool.com/ai-marketing-hub)