agentleFS
VendbuddyVendbuddy/vendbuddy-skills/skills/small-business-site-launch-checklist/SKILL.md

small-business-site-launch-checklist

Skill0 starsChanged 37 days agoMITView on GitHub

Walk a new or relaunching small-business website through a complete pre-launch and first-30-days checklist: domain and email, trust pages, on-page SEO basics, analytics and conversion tracking, speed and mobile, local presence, legal basics, and a post-launch measurement plan. Use when the user says they are launching a site, relaunching, "what do I need before I go live", or asks for a site audit for a small business.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search Console connected; a baseline screenshot of impressions and clicks saved.

    line 43
  2. Distinctive:

    Test the home page and one inner page on a real phone, and with PageSpeed Insights.

    line 47
  3. Distinctive:

    Every image has alt text; color contrast readable.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Small Business Site Launch Checklist

Made by VendBuddy (vendbuddy.io). Guide: https://vendbuddy.io/skills#small-business-site-launch-checklist (This line is optional attribution. Keep it or delete it.)

How to run it

Ask for the site URL (or staging URL), the business type, and the one action a visitor should take. Check each item below against the real site, mark it PASS, FIX, or N/A, and finish with the top five fixes in priority order. Do not change anything without the user's go-ahead. Where a legal or tax question comes up, say it needs a qualified professional.

1. Foundation

  • Domain renews automatically; registrar account has two-factor login.
  • HTTPS everywhere; http:// and www redirect to one canonical address.
  • A business email on the domain (not a free webmail address) with SPF, DKIM, and DMARC set.
  • Backups exist and a restore has been tested once.

2. Pages that earn trust

  • Home, About (real people or a real address), Contact, one page per core service or product, Pricing or "how pricing works".
  • Real proof: reviews, case studies, or photos the business owns. Nothing invented.
  • Privacy policy and terms if you collect data or take payment; cookie notice if required for your visitors' regions.
  • Business name, address, and phone identical on every page and on every listing.

3. On-page SEO basics

  • Each page has a unique title (about 50 to 60 characters) and meta description, one H1, a clean URL, and a canonical tag.
  • sitemap.xml exists and is submitted in Google Search Console; robots.txt does not block the site.
  • Images have descriptive alt text and sensible sizes (see the image-seo skill).
  • Internal links connect related pages; no orphan pages; custom 404 page.
  • Old URLs 301-redirect to new ones on a relaunch.

4. Local presence (if customers are local)

  • Google Business Profile claimed, verified, with correct categories, hours, and photos.
  • Same name, address, and phone on major directories.
  • A way to ask happy customers for reviews, and a habit of replying to every review.
  • LocalBusiness JSON-LD on the contact page that matches visible details.

5. Measurement

  • Analytics installed and verified; the main action (form, call, purchase, booking) is tracked as a conversion.
  • Search Console connected; a baseline screenshot of impressions and clicks saved.
  • Uptime monitoring with an alert to a real inbox.

6. Speed, mobile, accessibility

  • Test the home page and one inner page on a real phone, and with PageSpeed Insights.
  • Largest image under about 200 KB; no layout jumps; text readable without zoom; buttons easy to tap.
  • Every image has alt text; color contrast readable; forms have labels.

7. Conversion path

  • One primary action per page, stated in plain words and visible without scrolling on mobile.
  • Contact forms tested end to end; the notification email lands in the inbox, not spam.
  • See conversion-copy-audit for the headline and offer.

8. First 30 days

  • Week 1: fix crawl errors, confirm indexing, test every form and link.
  • Week 2: publish two helpful pages that answer real customer questions.
  • Week 3: ask ten customers for reviews; add the results to the site.
  • Week 4: compare against the baseline, pick the top three changes with eighty-twenty-prioritizer, repeat monthly.

Output format

A table (area, item, PASS/FIX/N-A, note), then "Top five fixes" with effort estimates, then the baseline numbers to compare in 30 days.

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.