Service Site Architect . Agency OS

What it does

Plans the skeleton of a website for a local service business: plumbers, dentists, law firms, contractors, clinics, any business that serves an area. It decides which pages exist: one per service, one per problem people actually search for, one per town in the service area, plus the hubs, contact, legal and utility pages. It sets how those pages link to each other, the section order inside each page type, the title and heading patterns, the image naming and alt text pattern, and the schema. Bundled scripts then turn the plan into page skeletons with every section, FAQ slot, schema block and link in place, check that the build matches the plan, and audit the structure. You get a plan in plain language you can hand to any builder, and a scaffold ready for copy.

Say this to start

This skill has no button. You start it by saying what you want. Any of these will do it:

> plan the site structure for my plumbing business

> how many pages should this site have

> service pages and city pages for [business]

> internal linking plan for a contractor site

> plan a new website for my client's dental practice

When to reach for it

a new website for a business that serves customers across a town or region
a client's five-page site ranks for nothing and you are about to rebuild it
you need a page plan a builder can follow without guessing
you want pages for the problems customers search for, not only the service names
you are building a site to rank in a local market and rent or sell the leads

When NOT to use it

If you actually want	Use this instead
a diagnosis of a site that already exists	`seo-site-audit`
the design and styling of the planned pages	`frontend-design`
opt-in pages, sequences and CRM	`funnel-architect`
a one-page cinematic scroll site	`cinematic-websites`
keyword volumes and difficulty	`keyword-research`
many pages from a template and a dataset	`programmatic-seo`

Before you start

What you need	Why
The real list of services the business sells	the page list is built from it; the starter lists per trade are only a seed	Required
The service area: which towns, and how far	one location page per town the business really serves, not a quota	Required
Whether customers visit a premises	it changes the schema; a service-area business that publishes a street address it does not trade from risks a Google Business Profile suspension	Required
A workspace: `_default` for your own site or `client--*` for a client build	the plan and the scaffold are written there, and an existing plan is never overwritten without asking	Required
If this replaces an old site: the old site's URLs	every old page with traffic or links needs a redirect before launch	Required
Avatar and offer from the foundation builds	keeps the service list matched to what the business sells to the people it serves	Optional
`keyword-plan.md` from keyword-research	page targets follow the keywords the workspace already chose	Optional
`verified-claims.md` with real proof	years in business, review counts, ratings and awards are only filled in from the registry	Optional
python3 on a shell	runs the scaffold, verify and audit scripts; without it you get the plan and the exact commands to run later	Optional

How it runs

Settle the two forgotten inputsThe service radius, and whether customers come to a premises. Both change what gets built.
Plan the page matrixServices, problem pages and application pages, one page per town, a services hub, an areas hub, contact, about, privacy, terms, thank-you and 404. The plan is written up as architecture.md in plain language.
Scaffold every pageA script builds each page skeleton with its section order, FAQ slots, schema and links already in place.
Fill the copyThe one step with no script. Each page is written in the workspace voice, with claims only from your verified claims, then put through the claims check and the voice check.
Verify against the planA script confirms the built site is the site that was planned: every page present, every link where it should be.
Audit the structureChecks titles, headings, schema, duplicate alt text and orphaned pages, and lists what to fix.
Log and learnThe plan and the audit are added to assets.md with the service-site-architect tag, and your feedback goes to learnings.md.

What you get

architecture.md: the page list, the link structure, the section order per page type and the schema decisions, ready to hand to a builder
A machine copy of the plan the scripts read
Page skeletons for every planned page in site/dist/, with schema and links in place and marked slots for the copy
Business, website and FAQ structured data, with the visible FAQ and its markup generated from one source so they cannot drift
A structure audit of the finished build
For a rebuild: the redirect mapping step, flagged as the highest-risk part of the project

Honest limits

Read this before you rely on it

The page counts and word-count floors come from one measured reference build. They are a strong starting point, not proof that the pattern ranks. Your own search data is the evidence.
Some of its rules are labelled as bets, not facts, with a date to review them. The skill says which is which.
It plans and scaffolds. It does not design the pages; styling goes to frontend-design.
It never fills in years in business, review counts, ratings, licence numbers or "best in town" claims. Those stay as marked gaps until you supply real evidence.
For health, legal and financial businesses, the word counts should be re-checked against the sites that actually rank in that market.

Where people go wrong

The mistake	Do this instead
Padding the site to a page count with near-identical pages	Merge pages that have nothing distinct to say. The count should follow what the business actually covers.
Publishing a street address for a business that travels to customers	Tell the skill up front. It uses the town, region and service area instead.
Launching a rebuild without redirecting the old URLs	Map every old page with traffic or links to its new page and redirect it before launch.
Writing "serving the area for 20 years" on a new site	Leave the slot empty until there is evidence. Write about how the work is done instead.
Keeping trade sections such as "DIY versus professional" on a clinic or law firm site	Swap those sections for ones that suit the business.

Worth knowing

People search for their problem, not your service name. Someone with a stained ceiling types "water stain on ceiling", not the name of the trade. Pages built around problems like that are the part of the plan most competitors never write.