GUIDES / WEB

Websites that keep working as they grow, and enquiries that get answered.

Web architecture is the structure underneath a site: URLs, templates, schema, links and speed. Lead capture is what passes each enquiry to the right person. This area covers both, for businesses whose website has to bring in work.

WHAT THIS AREA COVERS

Most website problems start in the structure underneath the design.

As a site grows, adding pages gets harder: URLs stop following a pattern, internal links fall behind, schema is added unevenly, key templates slow down and the contact form stops reaching the CRM. A useful test is whether adding the next page is as easy as adding the last one; when every new page needs a fresh discussion about template, schema, links and speed, the structure has stopped scaling.

The area fits a growing site with several page types, more than one language or active lead capture, where the next round of growth would multiply problems that already exist. It also fits a traditional business whose website is an old brochure that brings no contacts.

  • URL structure and page templates that survive growth
  • Schema and internal links that help search and AI engines
  • Contact forms and CRM follow-up treated as part of the site
Abstract composition of a site structure

CATEGORIES

Two areas under web.

Architecture & performance

URL structure, page templates, schema, internal linking, speed, and when a headless or hybrid set-up is worth it.

Read the topic →

Lead capture

Forms, qualification, assignment, the CRM connection and follow-up, from the first visit to the first conversation.

Read the topic →

GUIDES

Web guides.

Structure on one page, enquiries on the other

Schema, internal links and the choice of CMS sit on the architecture page; lead scoring, CRM choice and lost enquiries on the lead capture page.

FREQUENTLY ASKED

Questions about web architecture and lead capture.

How does lead capture fit into web architecture?
Each form belongs to a page template and sends its enquiries straight into the CRM with an owner assigned, so adding a page never adds a form nobody watches.
What should a site review check first?
Whether the URL rules and page templates can hold the pages still to come, since schema, links and speed all sit on top of them. Where each form sends its enquiries is checked in the same pass.
When should a site be rebuilt rather than fixed?
Rebuild when the URL structure, content model or core templates block the next stage of work and carrying them costs more than migrating. Fix in place when the structure is sound and the problems are local, which is the more common case.
How often should a growing site be reviewed?
Before each major addition, such as a new language, section or template; checks on every release catch the smaller issues in between.
How do web architecture and GEO relate?
The architecture is the base: templates, schema and links. GEO is how the content on top of it is written. Both make a page easier to cite, and projects often touch both.

SERVICES

When the site needs work.

Web architecture

Site structure, templates and a check before each release, with written notes your team can follow.

See service →

Lead systems

Capture, sorting, assignment and follow-up of enquiries, connected to the CRM you already use.

See service →

GEO content

When the site needs content planned so that AI search engines can cite it.

See service →

Tell us what needs doing.

Amazon work, a question for a consulting session or a process worth automating. We reply with the service that fits.