Add seo-geo-skill to Tools & Services / Optimization - #88
Open
asale-user wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds one entry to Tools & Services > Optimization.
seo-geo-skill is an open-source (MIT) set of agent skills that run an SEO audit from inside a coding agent instead of a hosted dashboard: crawlability and indexability, Core Web Vitals lab signals, structured data detection and generation, hreflang, image audits, and a drift comparison between deploys. It also covers the newer question of whether AI answer engines (ChatGPT, Perplexity, Gemini, Google AI Overviews) can reach a page and are likely to cite it.
The execution layer is a single Rust static binary, so there is no Python or pip in the install path, and it installs into Claude Code, Codex, Cursor and 75+ other agents. Most checks need no account and no API key.
Note: the diff also shows a whitespace-only change on the OptimalUX line above - the editor stripped a pre-existing trailing space. Happy to revert that if you would rather keep the diff to a single line.
Disclosure: I am the author.