Client Website
Ops & SEO Playbook

One copy per client Project

1. Pin this to each client's Project knowledge (one Project per client). Every chat inside that Project then shares this context.
2. Fill in the Client Snapshot below — that's the only client-specific part. Everything after it is the same standard process for every client.
3. Anywhere you see a {{placeholder}}, replace it with that client's detail.

Fill this in per client

How a Balar site fits together

Our default build stack is Astro (static) → Cloudflare → Resend — fast, cheap to host, excellent for SEO, with a clean Git-driven deploy. The process below applies to any client on this stack (and mostly transfers even if a client is on something else).

Git is the change log

No separate "changes" spreadsheet needed — commit history is the audit trail, and Cloudflare keeps every deploy for one-click rollback.

1. Small copy tweaks: edit → commit (clear message) → push. Live in ~90 seconds.
2. Bigger changes (new page, design): work on a branch → Cloudflare builds a preview URL → review / send client the preview → merge to go live.
3. Broke something? Roll back to any previous deploy in Cloudflare — no code.

Commit messages a human can scan: Add {{suburb}} location page, Update {{service}} copy, Fix footer phone link.

Data-driven pages

On our Astro builds, location/service pages are generated from data files — add one entry and the page, schema, sitemap, hub and footer links all update. Keep each page's copy unique (own intro + FAQ); near-duplicate local pages get ignored by Google.

House standard: Resend, hardened

For lead/contact forms our default is Resend via a Cloudflare Worker — best developer experience, native Cloudflare fit, and a free tier (3,000/mo, 100/day) that covers a typical lead form with room to spare. The job is hardening, not switching.

Hardening checklist (every form)

• Cloudflare Turnstile on the form, verified in the Worker — stops bot spam.
• Honeypot field — drop the submission if a hidden field is filled.
• Store every lead (Cloudflare D1 / Google Sheet / CRM) — never rely on email alone.
• Autoresponder to the customer so they know it worked.
• Correct headers — send from a verified domain address; set reply-to to the customer.
• API key in environment variables, never in the repo.

// POST /api/quote — Cloudflare Worker / Astro endpoint (pattern)
export async function POST({ request, env }) {
  const data = await request.formData();
  // honeypot + Turnstile check, then:
  await fetch("https://api.resend.com/emails", {
    method: "POST",
    headers: { Authorization: `Bearer ${env.RESEND_API_KEY}`,
               "Content-Type": "application/json" },
    body: JSON.stringify({
      from: "Leads <leads@{{domain}}>",
      to: ["{{client inbox}}"],
      reply_to: data.get("email"),
      subject: `New enquiry — ${data.get("service")}`,
      text: `${data.get("name")} · ${data.get("phone")}`
    })
  });
  return Response.redirect("/thank-you/", 303);
}

Do these once per launch

The routine that keeps clients ranking

House SEO toolkit entry point: balar-seo-toolkit. On-page audits & reports also via balar-on-page-seo / balar-report.

KPIs for every client

How we run clients with Claude

• One Project per client — its own memory & knowledge, kept separate from other clients.
• Pin this playbook + the client's brief/blueprint to that Project's knowledge (once).
• New chat per task — "Monthly content", "Q3 audit", "Add {{suburb}} page". Fresh chats in the same Project stay fast and keep the context.

Quick reference (Astro / Cloudflare default)

npm install
npm run build       # build to ./dist
npm run dev         # local preview
npx wrangler deploy # push to Cloudflare