The pipeline runs in the order the pages do: audit the dataset before generating, audit the pages after, turn the findings into work orders, then publish and measure.
The order matters more than it looks. Most of what goes wrong with a
generated site is decided before a single page exists — two keywords with the
same intent become two pages competing with each other, and no amount of
auditing afterwards makes them one page again. That is what
plan is for, and it is the cheapest command
in the set to run.
Everything after it assumes pages already exist.
check is the full audit,
brief turns its findings into work orders a
person or an agent can pick up, and
doctor follows the pages through the
sitemap to what search engines actually indexed — the step that answers why
correct pages still earn nothing.
| Command | What it does |
|---|---|
indexgap init | Read the project and record what makes it different |
indexgap plan | Audit the dataset before a single page is generated |
indexgap check | The full audit of generated pages |
indexgap brief | Turn findings into work orders |
indexgap sitemap | Build a sitemap from what actually exists |
indexgap notify | Push new and changed URLs to IndexNow |
indexgap portfolio | One table across every project |
indexgap profiles | Show the built-in content profiles |
indexgap doctor | The crawl-to-index funnel |
indexgap cite | Measure whether AI search cites you |