Local Content Writer runs eleven research stages before it writes a page.
Business Truth, industry research, service validation, search demand and website hierarchy analysis all finish before content generation starts. Each stage produces evidence the later stages depend on, so a page's content reflects a confirmed service, a validated entity and a defined intent rather than a keyword and a guess.
The pipeline in eleven stages
Every project runs the same sequence, in the same order. Skipping a stage or reordering it breaks the evidence chain the later stages rely on.
- Business TruthOwner-confirmed name, services, area, language and existing site. — See the full field list
- Entity & Industry ResearchMaps the trade's service families, activities, materials and terminology. — How industry research works
- Service ValidationSorts researched concepts into genuine services, families, synonyms and unresolved terms. — See the eight categories
- Service-Family ExpansionMaps the wider semantic family around each confirmed service before search demand is scored.
- Search Demand ResearchScores query classes against confirmed services rather than harvesting keywords blind. — See the eight query classes
- Missing-Service DiscoveryFlags services the business likely performs but hasn't listed. — How discovery works
- Website Hierarchy AnalysisEvaluates the proposed site as one connected structure, not isolated URLs. — See the hierarchy model
- Relationship AnalysisChecks which pages should link, merge or stay separate. — See linking rules
- Page IntentAssigns one primary intent to each page before a brief is written. — See intent classification
- Semantic Page PlanningBuilds the page brief the writer works from. — See a brief example
- Evidence-Backed Content CreationWrites the page from the brief, last in the sequence rather than first. — See how writing works
Why the order can't be shuffled
Service Validation depends on Business Truth; a concept can't be confirmed against a business that hasn't stated its services yet. Search Demand Research depends on Service Validation; a query only counts as relevant once it's tied to a real service. Website Hierarchy Analysis depends on both, because a URL can't be justified by demand for a service the business doesn't offer. Removing a stage doesn't speed the process up — it just moves the guessing further downstream, where it's harder to catch.
What you provide against what the system researches
Business Truth inputs versus the research each one unlocks
| You confirm | The pipeline then researches |
|---|
| Primary industry or niche | Service families, terminology and recognised classifications for that trade |
| Confirmed services | Search demand, service-family expansion and page-intent assignment for each one |
| Areas served | Which locations carry enough distinct demand and business truth to justify a page |
| Existing website | Current hierarchy, internal linking gaps and coverage against confirmed services |
Seven outcomes, not two
Website hierarchy analysis doesn't reduce every URL to keep or delete. Each one moves toward one of seven evidence-backed states.
The seven URL-level outcomes and what triggers each one
| State | What it means |
|---|
| KEEP | The page has a legitimate, distinct role in the site. |
| RENAME | The concept is valid; the naming doesn't represent its purpose yet. |
| MOVE | The page belongs elsewhere in the hierarchy. |
| MERGE | Independent evidence shows two URLs cover the same intent. |
| REMOVE | Evidence supports dropping the page from the architecture. |
| ADD | Research found a genuine service or content gap. |
| REVIEW | The evidence isn't strong enough for an automated call. |
URL similarity, keyword similarity and hierarchy proximity each raise a question. None of the three, alone, answers it. That's why REVIEW exists as a real outcome rather than a fallback.
Built across industries, not one trade
The same eleven stages run for a plumbing business or a solicitor's practice. What changes is the entity data each stage pulls in — not the sequence.
Roofing
- Service family example
- Flat roofing, pitched roofing, guttering, emergency tarping
- Local relevance driver
- Roof pitch and material norms tied to regional weather patterns
Legal / Solicitor
- Service family example
- Conveyancing, probate, family law, employment disputes
- Local relevance driver
- Jurisdiction boundaries and local court procedure, not postcode alone
Where a person still decides
Business Truth confirmation, REVIEW resolutions and any MERGE or REMOVE affecting a live page stay with a person. The pipeline produces the evidence; it doesn't remove the owner or the agency from decisions that carry consequences a wrong automated call can't undo.