Playbooks

A playbook is a procedure we run the same way every time, so the result doesn’t depend on who’s having a good day. These are the seven we use on every website we build, maintain, or rescue. We publish the actual steps because the work holds up when you can see it: copy any playbook and run it yourself with our free AI website prompts, or hand it to us and we’ll run it for a flat fee. Nothing here is gated, and none of it is theory — it’s what we do on real client projects every week.

1. The Build Playbook: from prompt to a live site

Most broken AI sites were rushed at exactly this stage. The fix is boring and it works: treat the spec as the project, and the AI as the fast typist.

1. Write the spec, or start from one of our free prompts, so every page and section is named before the AI types a word.
2. Generate with a capable model — see which AI is best for the job.
3. Review every section against the spec: copy, mobile layout, forms, and links, not just the hero.
4. Swap in your real content and images; delete every placeholder.
5. Test on an actual phone and run a Lighthouse pass.
6. Deploy to a host you control, so the code is yours from day one.

Do it yourself with the prompt library and our start-to-ship walkthrough. Or we build it: static sites and WordPress, flat fee, code handed over on GitHub.

2. The SEO Playbook: earn rankings and AI citations

SEO isn’t a plugin you switch on. It’s a loop you run.

1. Map the queries people actually type, one clear intent per page.
2. Answer the question in the first two lines of each page, then go deep.
3. Get titles, meta descriptions, headings, and internal links right.
4. Add the schema that fits — FAQ, Product, LocalBusiness — so search engines and AI can quote you.
5. Make it fast and accessible; both feed rankings.
6. Measure in Search Console, then re-run the loop on what’s close.

The full step-by-step is our how to vibe your SEO guide, backed by the on-page checklist and the get-cited-by-AI playbook. Or we run it as a service: SEO optimization and AI-search optimization.

3. The Speed Playbook: pass Core Web Vitals

A gorgeous site that loads in six seconds loses. Speed is measurable, so we measure it.

1. Measure LCP, INP, and CLS on a real mid-range phone, not your laptop.
2. Compress and lazy-load images, and serve modern formats like WebP.
3. Cut unused CSS and JavaScript; defer whatever’s left.
4. Cache aggressively and serve through a CDN.
5. Reserve space for images and embeds so nothing jumps as it loads.
6. Re-measure, and keep the numbers in the green.

Or we do it: speed optimization, with the before-and-after numbers to prove it.

4. The Launch and Security Playbook: go live without a mess

Launch day is where quiet problems get loud. This is the checklist that keeps it quiet.

1. Final content and link check — no lorem ipsum, no dead links.
2. Force HTTPS and set sensible security headers.
3. Lock down logins, remove default files, and disable in-dashboard file editing on WordPress.
4. Set up backups you have actually tested restoring.
5. Connect analytics and Search Console, and submit the sitemap.
6. Submit the contact form yourself and confirm the email really arrives.

Nervous about the safe-for-business question? Read is vibe coding safe. Or let us handle launch and hardening inside a care plan.

5. The Maintenance Playbook: keep it alive

An AI-built site is a car, not a painting. It needs oil changes.

1. Scheduled off-site backups, automatically.
2. Update core and plugins on a cadence, staged before production.
3. Uptime and form-delivery monitoring, so you hear it from us, not a customer.
4. A monthly security scan.
5. A quarterly content and speed review.

The honest costs are in WordPress maintenance cost and what breaks on AI-built sites. Or we carry it: care plans from a flat monthly fee.

6. The Rescue Playbook: triage a broken AI-built site

When a vibe-coded site breaks, panic makes it worse. Work the steps.

1. Take a full backup before you touch anything — you can’t make it worse from a snapshot.
2. Reproduce the break and read the actual error message, not the vibe of it.
3. Roll back the last change if you have a clean restore point.
4. Fix the root cause, not the symptom the AI keeps papering over.
5. Add the missing test or guardrail so the same break can’t return.

Walk it with our calm triage guide and the five common mistakes. Or we triage it: rescue and cleanup, diagnostic credited toward the fix.

7. The Migration Playbook: get off a locked platform

The day you outgrow a builder that won’t export your site is the day this matters. Plan it, don’t panic it.

1. Inventory every page and asset, and list exactly what the platform won’t let you export.
2. Rebuild on portable foundations — a static site or WordPress you can host anywhere.
3. Move the content, and recreate whatever couldn’t come across.
4. Keep the same URLs, or 301-redirect the old ones so you don’t lose rankings.
5. Cut over DNS, verify everything, and keep the old site running until the new one is confirmed.

See why lock-in bites in our hosting ranking and the 10Web review. Or we move it for you: migration, from a flat fee.

Where to start

New to the vocabulary? Keep our vibe coding glossary open in a tab. Ready to build? Grab a free prompt. Want it done right the first time? Tell us what you need on the hire page — flat fee, a deadline we hit, and the code is yours.