Architecture
Macro topic, clusters, pages, micro-intents and internal links.
A semantic site build, from the first intent to measurement.
A site is designed as a system: the business goal, the topical map, the URL structure, the content, the code, the images, the structured data and the analytics all have to say the same thing.
What is included?
Content
Direct answers, sources, tables, stated limits and calls to action.
Implementation
Semantic HTML, accessibility, responsive CSS and a cohesive JSON-LD graph.
Launch and measurement
Sitemap, robots, validation, a Search Console and analytics plan, and a baseline period.
Which projects is it for?
It makes most sense for local businesses, aggregators, specialist services and e-commerce projects that hold verifiable data and want an architecture that stays maintainable.
It makes least sense where the content does not yet exist and no data supports it. A well-built structure around empty pages is still empty pages.
The delivery flow is described in detail on the process page.
What is decided before any code is written
- The measurable business function. What has to happen on the site for it to be worth building.
- The evidence you hold. Local data, prices, tests and experience — the things that cannot be paraphrased from elsewhere.
- The demand threshold that decides whether a query gets its own URL.
- The terminology. One agreed name per concept, before the first page is written.
- The baseline period against which anything will later be measured.
Skipping these produces a site that has to be restructured after the first month of data, which is more expensive than deciding them at the start.
Send your project for review
Describe the project and you will get a proposed next step, not a generic package.