---
name: build-agency-website-for-vertical
description: "Build an agency site for the trade you serve. Show real people, useful services and a clear next step."
category: Digital Plumbing
stage: —
definitive_article: https://blitzmetrics.com/agency-site-playbook/
status: needs-work
---

# Build an agency website for a vertical

Does your agency site show whom you help and why they should trust you? This guide helps an owner build a site for one clear trade. Start with the founder’s real story, the work you sell and proof you can use.

**The path:** Market and proof → Nine site parts → Supported build → Public QA.

**Use this when:** a named operator needs an agency site for a defined market under the network’s reviewed agency-site playbook.

## Inputs
- The confirmed agency name, exact domain, market, offer and explicit trade carve-outs from the current project record.
- Verified founder story, real media, actual service methods and client evidence cleared for public use. Current roster/engagement controls scope; the client tracker supplies money/routing facts rather than replacing the roster.
- Authorized site/host access and any actual domain/hosting purchase scope, plus supported deployment and rollback procedures.
- The reviewed network intake destination, accountable receiving owner and current task/relationship records so this build does not duplicate another active worker.

## First-run prompt

> Build the scoped agency site using the current playbook and real supplied proof. Implement its nine relevant components, truthful service-method links and shared network intake. Preserve trade carve-outs and existing authority. Verify ordinary public pages and receipt of the contact path before claiming launch.

## Steps
1. Resolve the exact market, agency identity and allowed trades from the project record. Explain its role: the spotlight site develops industry coverage, the agency serves clients, the founder’s personal site establishes their identity, and client sites provide real proof. Do not invent that all four already exist.
2. Verify or acquire the exact authorized domain and provision through the current supported hosting route. Read the actual price, term, renewal and security choices; the article’s old roughly-eleven-dollar, one-session and four-nameserver example is not a current universal contract. Preserve valid existing hosting and domain protection.
3. Plan the nine components: a real founder hero and clear promise; founder About story; services linked to maintained methods; industries and carve-outs; approved client wall; actual results and reporting anatomy; shared audit intake; entity and measurement setup appropriate to the plan; and the source’s three launch articles on origin, reporting philosophy and method. Mark any evidence gap before writing claims.
4. Build the hero and About page from the founder’s real sources. Keep the opening at grade 5, with a meaningful photo or useful diagram in the first desktop and phone viewport. Use evidence-based scenes and precise relationships; no trophy-name paragraph, invented mentorship or unverified result belongs in the copy.
5. Build service and industry pages around the work actually offered. Link each method to its maintained owned guide and organize the pages with the SEO Tree and public Money Tree where applicable. Add verified client examples only under current scope and permission; private tracker data and inactive-client assumptions must not become public logos.
6. Connect the reviewed shared network audit intake and its actual receiver. Add the correct Person/business identity records, profile links and chosen measurement setup through their existing sources. Use supported components; do not rebuild or replace the shared intake merely because a generic template includes a form.
7. Prepare the three source-defined launch articles using actual founder content, truthful reporting examples and maintained method links. Publish the authorized work through the supported source. Check every scoped canonical public route, real 404 behavior, links, phone contact, media, page openings and trade carve-outs; cache-busters alone do not prove the normal page is current.
8. Verify the contact path and intended receiver using the agreed test scope. Save the nine-component coverage, page inventory, source/deployment/rollback state and exact QA evidence. Write the run’s meta article and post the project summary only within the current communication scope. Send any durable improvement to its owning master source for review, then propagate accepted changes.

## Definition of done (QA checklist)

- [ ] The site reflects its actual agency, founder, market, offer and explicit carve-outs.
- [ ] All nine playbook components have meaningful content or precise evidence-backed open items; missing proof is not replaced by filler.
- [ ] Real media, client claims, relationships and service-method links meet the maintained source rules.
- [ ] Ordinary public pages pass the declared first-screen, link, functional and contact checks, with source/deployment state recorded.
- [ ] The actual intake receiver, run write-up and next owner are verified; historical cost, runtime and deployment examples are not presented as current guarantees.

## Example(s)

**Fictional teaching example.** Cedar Trade Marketing serves fence installers and explicitly excludes roofing. Its founder supplies a real interview and approved photos; two clients permit specific case summaries. The nine-part page map includes a founder hero/About, fence services with method links, an industry carve-out page, the two-case client wall, a labeled reporting example, the approved shared audit link, identity/measurement setup and three launch articles. During lesson QA, a template mentions roofing. That defect is removed and rechecked rather than hidden by a high component count. The example is a build plan, not a live agency or two real client results.

## Handoff and Content Factory context

Give the site inventory and real contact-test evidence to the operator and site QA owner. Follow the maintained [Website QA Audit](https://blitzmetrics.com/website-qa-audit/) and use [create clear conversion path](https://local-service-spotlight.github.io/task-library/?task=create-clear-conversion-path#task-create-clear-conversion-path) if intake remains confusing. Retain network-source ownership for improvements.

This setup supports the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. This check does not automatically execute all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run once per new site or a scoped substantial rebuild. Ongoing reporting, relationships and site reviews use their existing owners and reconciled schedules; this guide does not launch another weekly agent.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Gate
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 3 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Record only the property IDs, access and checks required by this task in the client register. Pass the verified result to the task that needs it.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/agency-site-playbook/
- Exact task: [Build an agency website for a vertical](https://local-service-spotlight.github.io/task-library/?task=build-agency-website-for-vertical#task-build-agency-website-for-vertical)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Digital Plumbing training](https://blitzmetrics.com/digital-plumbing/)
- [SEO Tree](https://blitzmetrics.com/seo-tree/)
- [Entity linking](https://blitzmetrics.com/entity-linking/)
- [Website QA Audit](https://blitzmetrics.com/website-qa-audit/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Real founder/client proof, trade boundaries, current intake and host-specific setup must be supplied. The current article’s historical procurement and fleet-command anecdotes need upstream qualification. No site, domain or client operation was performed by this draft.