seo-index-sweep

Featured

Weekly, browser heavy. Unions every sitemap each property declares without a browser, builds the candidate set from URLs not already in the indexing ledger, then drives the member's own search performance console to inspect each candidate and request indexing inside an account wide allowance. Spends what is left on sitemap health, which is unmetered. It inspects, requests, and views or submits sitemaps inside that console and does nothing else there, ever, and it never removes a sitemap.

AI & Automation 432 stars 135 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Index sweep **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SEO_ROOT»/scripts/guard.mjs" seo-index-sweep`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/seo-index-sweep.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract. You are the discovery engine for «BUSINESS NAME». A new article can sit undiscovered for weeks if a search engine is left to find it alone. Your job this run: find every published URL that has never had a request spent on it, ask for each one inside the allowance, and keep every declared sitemap fresh, which costs nothing and is where most of the leverage actually is. Read `«SEO_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, `recipes/BROWSER-RECIPES.md`, and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins. **Two thirds of this run needs no browser at all.** The sitemaps are ...

Details

Author
markfulton
Repository
markfulton/ai-employees
Created
3 weeks ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

seo-rank-review

Weekly, browser heavy, read only on every screen. Fixes a scoring window that neither double counts nor loses an hour, reads the member's search performance console and analytics property, verifies each range actually applied before reading a figure, reconciles every number against what this Employee published, writes the week's scoreboard and the short rolling state file every other routine reads, and files what it found as cards rather than doing the work itself. It types nothing on any screen, changes no setting, publishes nothing, and never touches a credential.

432 Updated today
markfulton
AI & Automation Featured

seo-intake-and-map

Monthly, browser conditional. On its first run it discovers the member's properties from the sites they name, writes the three strategy files, creates every ledger and folder the kit reads, files the opening cards, and registers the eight scheduled jobs. Every month after that it re-reads the evidence rather than its own previous conclusions, rebuilds the topic map and the internal link map, corrects any property fact it can prove wrong, and records every change with the path of the evidence that forced it. It holds publishing and spending unless you released the channel, and it never touches a credential.

432 Updated today
markfulton
AI & Automation Featured

cos-market-sweep

Weekly, heavy browser lane, read only toward the world with no exception. Works the surfaces on its own watchlist through one contiguous browser phase, captures one dated observation per real change with a verbatim quote and the exact URL, refuses to report any change against a surface it has no baseline for, and writes one capped weekly page. It types nothing that changes anything, takes no action on LinkedIn ever, sends only where you released the channel, spends only where you released it, and never touches a credential.

432 Updated today
markfulton