explaingit

paultaki/get-cited-by-ai

Analysis updated 2026-05-18

1Audience · developerComplexity · 2/5LicenseSetup · easy

TLDR

A Claude Code skill that checks if AI search demand exists for your site before recommending fixes to get cited by AI engines.

Mindmap

mindmap
  root((repo))
    What it does
      Checks AI citation demand
      Audits site for AI SEO
      Measures citation results
    Tech stack
      Claude Code skill
      Markdown workflow files
    Use cases
      Diagnose AI citation potential
      Audit a site or client site
      Benchmark against a vertical
    Audience
      SEO practitioners
      Site owners
      Claude Code users
    Evidence base
      26767 citations
      Mortgage vertical study
      Prediction ledger

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Check whether AI search demand exists before investing in AI SEO changes.

USE CASE 2

Audit a website's existing pages for what actually correlates with AI citations.

USE CASE 3

Benchmark a site against a specific industry vertical like mortgage.

USE CASE 4

Measure whether AI SEO changes actually increased citations afterward.

What is it built with?

Claude CodeMarkdown

How does it compare?

paultaki/get-cited-by-ai0xkinno/neuralvault0xlocker/d17-contracts
Stars111
LanguageTypeScriptSolidity
Setup difficultyeasyhardhard
Complexity2/54/55/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 30min

Clone into your Claude Code skills folder, then work through the six-step workflow manually.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

This is a Claude Code skill that helps website owners figure out whether they can actually get cited by AI search engines like Bing Copilot, and if so, what to fix first. The author runs six websites and pulled together 26,767 recorded AI citations across them, then compared pages that got cited often against pages that never got picked at all. Much of the usual advice about schema markup, FAQs, and llms.txt files did not hold up against that comparison. In fact, the author's highest citing page has no JSON-LD schema at all, while some uncited pages have more schema and FAQs than the cited ones. The core idea of this skill is to check demand first. Before recommending any on-page changes, it asks whether people are even asking AI the kinds of questions your site could answer. If nobody is asking, no amount of tweaking will get you cited, and the skill says so upfront instead of wasting your time. If demand does exist, it sorts possible fixes into things worth doing anyway, and the smaller set of changes that actually correlate with getting cited. It also gives you a way to measure whether your changes worked afterward. The workflow runs in six steps: a demand probe, splitting by which AI engine camp you are targeting, a site audit, an entity check, a benchmark against a specific industry vertical, and a final measurement step. A file called RULEBOOK holds every rule along with the evidence and receipts behind it, drawing on the citation counts, a controlled regression test, an 820,000 citation study of the mortgage industry, and a public ledger of predictions made before results were known. To install it, you clone the repository into your Claude Code skills folder, either globally or for a single project. The author is upfront about the limits of the underlying data: it only covers six owned websites across five industries plus one mortgage study, focused on Bing Copilot in English, and the findings describe what was measured on those specific sites rather than universal truths. The included measurement tools are meant to let you test the rules against your own site. The project is released under the MIT license.

Copy-paste prompts

Prompt 1
Run the demand probe from this skill against my website to see if AI citation demand exists.
Prompt 2
Use this skill to audit my site and tell me which fixes actually correlate with AI citations.
Prompt 3
Explain the Two-Camp Engine Model referenced in this skill's rulebook.
Prompt 4
Help me set up the measurement harness from this skill to track my site's AI citations.

Frequently asked questions

What is get-cited-by-ai?

A Claude Code skill that checks if AI search demand exists for your site before recommending fixes to get cited by AI engines.

What license does get-cited-by-ai use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is get-cited-by-ai to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is get-cited-by-ai for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.