weekly-checklisted
Install: claude install-skill sitetiller/ai-visibility-skills
# Weekly check: 20 minutes, one report
Goal: catch the things that silently break (robots.txt, sitemap, unintended page edits, indexing, bot access) and see the week's movement without reacting to noise. Run it on the same day each week, with the same key pages and the same flags, and keep each week's report so the next one can be compared.
## Inputs
- Domain and 5 to 10 **key pages** (home, top landing pages, pricing or product, the pages the user changed recently). Write the list down once and keep it fixed.
- Optional: Search Console and Bing access (`setup`), an access log, AI prompts file (`ai-tracker`).
- A folder where the weekly JSON and the report are saved, named by date.
## The routine
Each step has a time budget. If a step cannot run (no credentials, no logs), write "not run" in the report with the reason. Never fill the gap with a guess.
### 1. Crawler access (2 minutes)
```bash
npx sitetiller crawlers example.com --json > week/crawlers.json
```
Read `status`, `found`, `problems`, `sitemaps`, and each bot's `allowed` and `rule`. Compare with last week's file. `robots.txt` is the first thing a deploy can break.
### 2. Sitemap sample (3 minutes)
```bash
npx sitetiller sitemap example.com --sample 20 --json > week/sitemap.json
```
Read `found`, `urlCount`, `issues[]`, and for each `sample[]` row `status`, `noindex`, `redirectedTo`. Compare `urlCount` with last week. A sample is a sample: say "20 of N sampled".
### 3. Version drift on key pages (3 minutes)
```b