When the old website holds you back more than it helps.
A website rarely goes bad all at once. Usually several things add up: services have grown, contacts have changed, important content sits scattered around, or the site only half works on a phone.
Then a relaunch makes sense. Not because every company has to keep looking new, but because prospects should quickly understand what your company offers, who it works for and how to reach it.
First work out what can stay.
A relaunch does not start with colours and typefaces. First we look at the existing site:
- Which content is still accurate and useful?
- Which pages are missing, even though clients ask for them?
- Where do visitors fail to find important information?
- Which technical foundations need renewing?
- Which existing rankings and URLs should you protect?
That turns a gut feeling into a plan that holds. Good content gets kept or reworked. Anything surplus goes.
Structure before styling.
Many midmarket websites have grown over the years. You often notice it in nested menus, near-identical service pages, or copy that makes sense internally but not to a new prospect.
We sort the offering so the site works without prior knowledge. Services get a clear place. References, sector knowledge and contacts sit where they help with the decision. The styling supports that order, it does not replace it.
Have your current website reviewed
Go to the formSEO belongs in the relaunch, not at the end.
A relaunch can cost you visibility when existing URLs disappear or content is rewritten without a plan. That is why SEO is part of the work from the start.
That includes a clean page structure, understandable page titles, sensible internal links and redirects for important old URLs. Where new content is written, we aim it at concrete search queries instead of stuffing text with terms.
Technology that stays out of the way day to day.
A new website has to run reliably and stay maintainable later. That does not call for an unnecessarily complicated solution.
Homepagely builds websites to fit the project. Depending on what is needed, that means a lean CMS, custom features, forms, load times or connecting existing systems. You talk directly to the developer responsible for the build.
The process stays manageable.
After a first conversation you get a realistic assessment of scope, priorities and technical approach. Then come concept, content and design. Development only starts once the foundation is in place.
Before going live we check the site on different devices, set up redirects and agree what should be looked after after launch. A relaunch is not an off-the-shelf package. The effort follows your starting point.