Illustrative workflow demo — not a live crawl
Architecture
Hub and service URL pattern looks consistent in this sample.
Preview only — a real audit inspects your live IA and redirects.
SEO service / 02
SEO website development
Most websites get SEO sprinkled on at the end. We build in the opposite order: research what your customers search, architect one page per intent, then build to the technical standards Google rewards. The method is documented and you can inspect it.
- Architect one page per search intent before design polish.
- Keep the method inspectable — research documents stay your asset.
Search architecture matrix
Illustrative workflow demo — sample architecture
| Intent | Keyword group | Target page | Funnel | Status | Objective |
|---|---|---|---|---|---|
| Commercial | service + city | /services/…/ | Consider | Indexable | Enquiry |
| Comparison | option A vs B | /compare/…/ | Evaluate | Linked | Clarify fit |
| Informational | how / cost / guide | /resources/…/ | Learn | Supporting | Trust |
| Transactional | package / quote | /website-packages/…/ | Decide | Canonical | Proposal |
No live ranks or traffic figures — structure only.
Technical site scan · preview
See the checks an architecture audit covers
This module is a staged preview of audit themes — it does not crawl your website. For a real inspection, use the fixed-price SEO audit packs.
Illustrative workflow demo — not a live crawl
Metadata
Titles and descriptions should be unique per intent destination.
Preview only — we do not fetch your live meta tags here.
Illustrative workflow demo — not a live crawl
Indexation
Thank-you and template routes commonly need noindex controls.
Preview only — confirm against your robots and Search Console.
Illustrative workflow demo — not a live crawl
Performance
Client JS and hero weight are the usual mobile LCP risks.
Preview only — field metrics come from a real measurement pass.
Illustrative workflow demo — not a live crawl
Structured data
Schema must match visible content; ratings require real permissioned data.
Preview only — validators run against your published HTML.
Illustrative workflow demo — not a live crawl
Internal links
Money pages need contextual paths from hubs and related content.
Preview only — link graphs are built from your crawl.
Problems this architecture prevents
Select a common failure mode. Each panel explains why it matters and what we change — sample themes, not a live audit of your domain.
Illustrative workflow demo — sample findings
Duplicate intent detected
- Why it matters
- Two pages chasing the same search job split authority and confuse crawlers.
- What is affected
- Service and location pages competing for the same query cluster.
- Recommended action
- Assign one primary destination per intent; redirect or retarget the duplicate.
Illustrative workflow demo — sample findings
Thin service page
- Why it matters
- Pages without clear problem, proof and next step rarely earn commercial queries.
- What is affected
- Generic “services” copy with no deliverables or exclusions.
- Recommended action
- Rebuild around intent, scope and conversion — not filler paragraphs.
Illustrative workflow demo — sample findings
Internal-link gap
- Why it matters
- Important pages that are hard to reach from the hub crawl poorly and convert less.
- What is affected
- Money pages orphaned from homepage and related guides.
- Recommended action
- Add contextual links from hubs, related blocks and nav where they belong.
Illustrative workflow demo — sample findings
Missing structured data
- Why it matters
- Valid schema helps machines understand page type — it is not a ranking trick.
- What is affected
- Service and FAQ pages without Organisation / WebPage / FAQ where appropriate.
- Recommended action
- Add honest schema that matches visible content; never fabricate ratings.
Illustrative workflow demo — sample findings
Slow mobile render
- Why it matters
- Heavy client JS and unbudgeted assets raise LCP and abandon mobile visitors.
- What is affected
- Hero media, third-party scripts, unoptimised fonts.
- Recommended action
- Enforce a performance budget; keep ranking HTML server-rendered.
Illustrative workflow demo — sample findings
Indexation conflict
- Why it matters
- Conflicting robots, noindex and sitemap entries waste crawl budget.
- What is affected
- Staging URLs, thank-you pages, or templates leaking into the index.
- Recommended action
- Align robots, canonicals and sitemap from one route registry.
Common symptoms
- Your previous site was designed beautiful-first and found never.
- “SEO packages” delivered reports, not rankings or enquiries.
- Pages compete with each other because nobody mapped intent.
- Technical problems (speed, duplication, thin pages) cap everything.
- You cannot tell method from magic when providers pitch SEO.
Methodology you can inspect
Demand research through measurement — each stage leaves an artefact you can review.
- Demand research
- Intent model
- Site architecture
- Technical build
- Indexation
- Measurement
01 / Demand research
Research sheet
Keyword and competitor notes specific to your market — not a generic keyword dump.
02 / Intent model
Keyword map
One destination page per commercial intent, with funnel stage and objective.
03 / Site architecture
Sitemap plan
URL structure, hubs and internal-linking rules before design polish.
04 / Technical build
HTML / schema panel
Server-rendered pages, clean metadata and schema that match visible content.
05 / Indexation
Search Console status
Sitemap, robots and a monitored window after launch — not a set-and-forget checkbox.
06 / Measurement
Conversion events
Analytics and conversion events wired to real enquiry paths.
What is included
01 / Research and mapping
Research and mapping
- Keyword and competitor research specific to your market
- Keyword-to-page map: one destination page per search intent
- Site architecture, URL structure and internal-linking plan
02 / Technical build
Technical build
- Technical build: server-rendered pages, clean HTML, fast Core Web Vitals
- Unique metadata and appropriate schema markup throughout
- XML sitemap, robots and indexation controls
03 / Launch and measurement
Launch and measurement
- Search Console setup with a 90-day indexation support window
- The full research and mapping documents — your asset, not our secret
What's not included
Clear exclusions protect your budget — ranking guarantees are never on the list:
- Link building and outreach campaigns
- Ranking guarantees — no honest provider offers them
- Ongoing content production (available as a support plan)
Pricing and packages
This service pairs with Professional business website package. Indicative ranges sit on our pricing page. Prefer a fixed diagnostic first? See the SEO audit packs.
Frequently asked questions
What exactly is an SEO-first website?
It is a website whose page list, URLs and content structure are derived from researched search demand before design begins — one page per commercial intent, technically built so Google can crawl, render and rank it. Our guide explains the method in plain language.
Do we still need monthly SEO after the build?
The build gets the foundation right, which is where most sites fail. After that, growth comes from content added against the keyword map and from Search Console-driven improvements — available as a support plan, but never a forced subscription.
Related pages
Talk it through with the person who would build it
Tell us what you need and get a straight answer — clear scope, indicative pricing and a fixed quote after one scoping conversation.