Digital Agency for Canterbury Businesses

Website Projects Are Rarely One Discipline

A website involves design, development, content, search and usually marketing. Most projects treat these as a sequence: design it, build it, fill it with words, then work out how to promote it.

The sequence is convenient to manage and it produces predictable problems. Decisions taken early, on grounds that made sense at the time, turn out to constrain everything downstream — and by the time that becomes apparent, changing them is expensive.

The alternative is not that everyone does everything at once. It is that the disciplines talk to each other at a few points where their decisions genuinely intersect.

Where Design Constrains Development

Design decisions carry build implications that are not always visible on the artboard.

A layout that assumes a fixed amount of text will break when a service description runs longer. An interaction that works in a prototype may be impractical to build, or expensive to build well. A design produced without reference to how the site will be structured can end up requiring bespoke work for pages that should have shared a template.

None of these is a designer's error. They arise when design and Webflow development are separated by a hand-off rather than a conversation. Raised early, they change the design slightly. Raised at build stage, they change it considerably — usually without the designer present.

Where Development Constrains Search

Structural build decisions shape search performance long after launch.

Which pages exist and how they relate. What the URLs are. Whether content is reachable without interaction. What happens to the pages the new site replaces. Whether the sitemap reflects what you actually want indexed.

These are settled during development, frequently without anyone considering search at all, and they are awkward to revisit afterwards. Involving search marketing during the build is usually a modest commitment — a conversation about structure, a check on URLs and redirects, a review before go-live — and it prevents most of what otherwise needs correcting later.

Content Determines Structure, Not the Reverse

Templates are often designed before anyone knows what will go in them, and the content is then cut to fit.

This is where substance quietly disappears. A page that needed eight hundred words to answer a genuine question gets two hundred because the layout accommodates two hundred. It looks better and does less.

Establishing what each page actually needs to say — before the template is finalised — avoids that. It also surfaces gaps early: pages nobody had planned for, questions nothing on the site answers, services with no page at all.

Campaigns Need Somewhere to Land

Paid campaigns are usually planned after a site is finished, and the destination is whatever exists.

An advertisement makes a specific promise; the click arrives at a general page that does not repeat it. The campaign then gets judged on performance when the problem was the landing page.

Where paid media is considered during the project, pages can be built to receive campaigns rather than borrowed from elsewhere. What campaigns subsequently learn about which messages work is also useful back on the website itself.

Measurement Before Launch, Not After

Analytics is the item most often left until someone asks a question the data cannot answer.

Deciding before launch what counts as a meaningful action — an enquiry, a call, a quote request — and making sure those are recorded costs very little at build stage. Added afterwards, tracking can only describe the future, and the period you most want to understand is the one you did not measure.

Agreeing Responsibilities Early

Most of the problems above are communication failures rather than technical ones.

A designer trims content to improve a layout, not knowing a page depended on it. A developer restructures URLs sensibly, unaware redirects were needed. A marketer plans campaigns for pages that were never built. Nobody behaved unreasonably; nobody was told.

Establishing at the start who decides what, and at which points the disciplines need to consult, prevents most of it. Three conversations usually suffice: structure at planning, URLs and templates during the build, and a checklist before launch.

Keeping the Site Adaptable

A website's requirements change after launch. New services, new pages, new campaigns, information that needs updating.

How adaptable the site is to that was determined during the build — whether templates can accommodate new page types, whether content can be edited without a developer, whether the structure has room to grow. Sites built as a fixed artefact tend to need replacing sooner than sites built with change in mind.

Working With a Kent-Based Digital Agency

Maidstone Digital is based in Maidstone and works with businesses in Canterbury, elsewhere in Kent and further afield. We do not have premises in Canterbury. Most work is carried out remotely and reviewed through shared data and regular conversation, though we are happy to meet where useful.

This page covers our broader digital services. If your specific interest is organic search — particularly what makes website content genuinely useful rather than generic — our SEO services for Canterbury businesses page covers that subject in detail.

Canterbury Digital Agency FAQs

When should SEO be involved in a website project?

At planning, before structure and page decisions are settled. That is when input costs least and matters most — which pages exist, what they are called, what happens to the current ones. A check during the build and another before launch usually covers the rest. It need not be a large piece of work.

Can you work alongside our existing designer or developer?

Yes. We can take on part of a project and coordinate with whoever handles the rest, or advise on the decisions that affect the parts we would be responsible for. What matters is that someone has visibility of how the pieces connect, and that responsibilities are agreed before work starts rather than assumed.

Why do website projects so often need rework?

Usually because decisions were made in isolation. A layout that cannot hold the content, a structure that ignores how people search, campaigns with nowhere suitable to land. Each is reasonable in isolation and creates work for someone else. Raising these while the project is still flexible costs a conversation; raising them afterwards costs a rebuild of something.

Should content be written before or after the design?

At least in outline, before. Knowing what each page needs to say lets the design accommodate it. Designing first and fitting content afterwards tends to shorten pages to suit layouts, which removes exactly the substance that made them worth visiting.