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

How to check a live site's SEO foundation in one run with SEO Ops

Give the agent a URL and get a crawler's-eye pass/fail report on 26 structural SEO checks.

Who it is forA marketing or web lead who wants to know whether search engines and AI retrieval can fetch, read, and index a site, without access to its code.

The problemManual SEO audits are slow and tied to a specific framework, and it is hard to tell which structural problems are blocking crawlers.

The outcomeA pass/fail report with evidence for each of the 26 checks, based only on the live HTTP and HTML output of the site.

What you need first

  • A public URL for the site to check (the checker only needs the URL)
  • Claude Code or Codex, or another agent that can install an Agent Skill from a GitHub URL
  • Python, to run scripts/run.py if you run the checker directly

Steps

  1. Copy the install prompt Install https://github.com/tigerless-labs/seo-ops as a skill. into your agent, or run /plugin marketplace add tigerless-labs/seo-ops then /plugin install seo-ops@seo-ops in Claude Code.
  2. Start a new session if the skill does not appear.
  3. Type /seo-ops check example.com in the agent input box, replacing example.com with the target site.
  4. Confirm with the agent that the target is a live site, not a code review, when it asks.
  5. Read the red items in the report and the evidence attached to each one.

Prompt for your agent

Using the tigerless-labs/seo-ops skill, check the SEO foundation of <target-url> as a live site. Return the pass/fail report for the 26 checks with evidence for each red item. Verify that the report lists every check as pass or fail and does not guess at checks it could not run.

Caveat. The checks cover structure and machine-readable signals only, so a passing report does not judge the quality of the content on the page.

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