DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to fail a build when a site's AI readiness regresses with Geo Score

Score the site on every push and fail the build on a regression or a zero gate.

Who it is forA web developer or DevOps engineer who wants AI readiness checked alongside other tests on each deploy.

The problemA robots.txt or rendering change can quietly remove a site from AI crawlers, and nobody notices until citations drop.

The outcomeEach push is scored, and the build fails if the score regresses or a gate check drops to zero, with a job summary written for the run.

What you need first

  • Python with pip, to install geo-score==1.8.3 from PyPI (the release pinned in the README)
  • A website domain to score; no key is needed for the free score
  • For citation checks (levels 2 and 3): your own API key for at least one of OpenAI, Perplexity, Gemini, Anthropic or OpenRouter

Steps

  1. Add the Geo Score GitHub Action to your workflow using the repository's action.yml, pointed at your site.
  2. Set the target domain and any threshold the action accepts, as described in action.yml.
  3. Push a change and open the job summary to read the score and check table.
  4. Keep the check as a required status so a regression blocks the merge.

Prompt for your agent

Using the geo-score repo at jianruntech/geo-score, add its GitHub Action to a workflow that scores <target-domain> on each push. Expected output: a build that passes with the score in the job summary and fails on a regression or a gate at zero. Verify that a deliberately broken robots.txt line causes the build to fail.

Caveat. The action checks public pages only and scores the site as crawlers see it, so changes that exist only behind a login will not appear in the score.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page