SEO

Audit or draft an llms.txt

Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.

The playbook

An llms.txt is a short markdown file at the site root that tells AI assistants what the site is and which pages to read first. It is the AI-era equivalent of a curated sitemap. Adoption by crawlers is uneven, so it is a cheap bet rather than a guarantee, but a good one takes an hour and a bad one misleads every assistant that does read it.

Sequel supplies the traffic data that decides what belongs in the file. Fetching the existing file and the pages uses your own browsing.

Steps

  1. Fetch what exists. Request /llms.txt and /llms-full.txt. A 404 on the first means you are drafting; skip to step 4. If it exists, keep going.

  2. Validate the structure. The spec expects: one H1 with the site or project name, a blockquote with a one-paragraph summary, optional prose, then H2 sections each containing a list of - [Title](url): description entries, with an optional final section named Optional for lower-priority links. Report deviations.

  3. Validate the links and the coverage. Fetch every listed URL and check it returns 200, is not noindex, and is the canonical form. Then pull google_search_console.query with dimensions: ["page"], 90 days ending 3 days ago, rowLimit: 300, and list the top 50 pages by clicks that the file does not mention. Those are the omissions that matter.

  4. Draft, if missing. From the same Search Console call, take the top pages by clicks and group them into sections that match how the site is organised (documentation, guides, product, pricing, blog). Fetch each chosen page to write a one-line description from its title and meta description in your own words. Keep the main file under about 100 links; push the rest to Optional or to llms-full.txt. Do not include gated, private, login or utility URLs.

  5. Report. For an audit: the structural findings, the broken or non-canonical links, and the missing top pages. For a draft: the complete file in a markdown code block, ready to save at the site root, plus a note on where it goes and that it does not replace the XML sitemap. Continue with ai-crawler-access-check if the crawlers that would read it are blocked.

Gotchas

  • Do not promise citations. The file helps assistants that read it; not all do. Present it as low-cost hygiene.
  • Curate, do not enumerate. A file listing every URL is a sitemap with extra steps. The value is the selection and the descriptions.
  • Keep it maintained. A stale llms.txt pointing at moved pages is worse than none. Suggest regenerating it when the top pages change.
  • Markdown versions of pages are a separate convention. Some sites also serve .md copies of pages; that is optional and not required for llms.txt to be useful.
  • Search Console lags 2 to 3 days. End the window 3 days back.

Sequel CLI

Install Sequel skills into your agent

One command connects your agent to Sequel and installs the Sequel skill, so it knows this playbook exists and reads it when a question matches. The CLI signs you in, provisions a scoped API key and writes the config for you.

Already have an MCP client?

https://api.sequel.sh/mcp

Point it at this URL and sign in when prompted, or send an API key from Settings as a Bearer token. Skills come with it; nothing else to install. Manual setup per client

  1. 1

    Install the Sequel CLI

    One line installs the latest CLI with whatever package manager you have.

    curl -fsSL https://sequel.sh/install | sh
  2. 2

    Sign in

    Authenticate in your browser and pick an organization.

    sequel login
  3. 3

    Install into your agent

    Writes the MCP config and installs the Sequel skill file for agents that support skills. Pick an agent from the list, or target one directly by its slug.

    sequel install
    • Claude Code
      sequel install claude-code
    • Claude
      sequel install claude
    • Cursor
      sequel install cursor
    • VS Code
      sequel install vscode
    • Windsurf
      sequel install windsurf
    • Zed
      sequel install zed
    • Codex
      sequel install codex
    • OpenClaw
      sequel install openclaw
    • Hermes
      sequel install hermes

More like this

Other SEO skills

Analyze high-ranking landing pages

See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.

Audit internal links to important pages

Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.

Audit redirect chains and loops

Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.

Audit referring domain quality

Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.

Audit titles and meta descriptions

Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.

Backlink profile health check

See who links to the site and whether the backlink profile is healthy: referring domains, authority distribution, anchor text mix, dofollow share and concentration risk from Ahrefs, optionally compared against a competitor.

Put this playbook to work

Connect a source, ask the question, and the agent follows these steps. Free to start.