agentleFS
PapiScholzPapiScholz/search-visibility-kit/skills/onboard-site/SKILL.md

onboard-site

Skill1 starsChanged 34 days agoMITView on GitHub

Checklist-driven onboarding of a new website into the full search-visibility stack (Search Console, GA4, IndexNow, Bing Webmaster Tools). Use when the user says "add a new site", "onboard example.com", "set up this website", or wants to repeat the setup for another project or client site.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. elevaiteworks/website-template★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this checklist for each new website.

    line 8
  2. Very specific:

    Search Console property: Check list_properties for the domain.

    line 14
  3. Very specific:

    GA4 access: Check get_account_summaries.

    line 15
  4. Distinctive:

    IndexNow: Run the indexnow skill's setup section: new key, key file in the site's static assets, verify it serves 200, submit the sitemap …

    line 17
  5. Distinctive:

    Baseline audit: Run the seo-audit skill and save the output as the site's baseline for future comparisons.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboard a new site

Run this checklist for each new website. The service account and MCP servers already exist (if not, run setup-google-access first) — onboarding a site requires zero Claude reconfiguration.

Checklist

Work through in order, verifying each step with tool calls where possible:

  1. Search Console property. Check list_properties for the domain. If absent, the user creates it at search.google.com/search-console (DNS verification recommended for domain properties) and adds the service account email under Users and permissions.
  2. GA4 access. Check get_account_summaries. If the property is missing, the user adds the service account (Viewer) under Admin → Property access management. Record the numeric property ID.
  3. Sitemap. list_sitemaps_enhanced — if no sitemap is registered, or last_downloaded is stale, submit it with submit_sitemap (confirm the live sitemap URL returns valid XML first).
  4. IndexNow. Run the indexnow skill's setup section: new key, key file in the site's static assets, verify it serves 200, submit the sitemap URLs.
  5. Bing Webmaster Tools. Have the user import the site from Search Console at bing.com/webmasters (one click, no manual verification). This is the only place IndexNow processing is visible.
  6. Baseline audit. Run the seo-audit skill and save the output as the site's baseline for future comparisons.

Verification

Close by confirming: GSC property listed, GA4 property readable, sitemap freshly downloaded or pending, IndexNow key file serving 200 with exact content, first submission acknowledged. Report any step that could not be verified as pending — never mark it done on assumption.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.