Skip to content

Add geo-check to Agent Skills - #632

Open
vasco-branco06 wants to merge 1 commit into
jqueryscript:mainfrom
vasco-branco06:add-geo-check
Open

Add geo-check to Agent Skills#632
vasco-branco06 wants to merge 1 commit into
jqueryscript:mainfrom
vasco-branco06:add-geo-check

Conversation

@vasco-branco06

Copy link
Copy Markdown

One bullet at the end of Agent Skills.

The list already carries several GEO and SEO skills, so the honest framing is
what this one does differently rather than that it is new.

geo-check measures instead of advising. No model sits in the scoring path. Every
point traces to the robots.txt line or the markup that earned it, so a site
scores the same twice and a result you disagree with is checkable rather than an
opinion. It reports Access and Readability as two scores and never averages
them, because a site can be perfectly reachable and impossible to read, and a
blended number hides whichever half is broken.

It also draws a line most tools miss: blocking GPTBot is a training opt out and
costs nothing in ChatGPT results, while blocking OAI-SearchBot removes you from
them entirely. Those two directives sit one line apart. Blocking training
deducts zero points here, on purpose, because it is a legitimate business
decision rather than a defect.

Validated across 906 real sites, with the per site evidence in the repository.
That validation found three bugs in the tool itself first, including a user
agent substring match that would have silently reported six citation crawlers as
blocked on any site writing User-agent: bot.

MIT, runs locally, no API key. Also a CLI and a GitHub Action.

https://github.com/vasco-branco06/geo-check

Audits whether AI crawlers can reach and read a website, scoring Access and
Readability separately rather than blending them. Every point traces back to the
robots.txt line or the markup that produced it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant