Website redesign

Your website exists. Let’s make it say and do more.

If the site looks acceptable but organic traffic is thin, visitors are confused, or inquiries never arrive, I start with the gap between what the business does and what the site communicates.

The first pass

Before I redesign, I read the site as a customer and as a crawler.

I look at the offer, navigation, mobile reading experience, existing search queries, page titles, headings, internal links, canonicals, structured data, loading behavior, and contact path. That tells us whether the problem is the words, the design, the technical setup, or a combination.

01

Keep what earns its place

Useful content, strong URLs, customer language, and working integrations should not disappear just because the visual design changes.

02

Fix the missing explanation

Each important page should tell a visitor what the service is, who it is for, how it works, and what to do next.

03

Carry search equity forward

I map existing URLs, plan redirects where necessary, and check the new HTML and sitemap so the launch does not strand old pages.

The goal

A site with a clear reason to exist on every page.

A homepage can introduce the whole business. Service pages can answer specific buying questions. A work page can show proof. Contact should be easy to reach. Underneath, the metadata, canonical URLs, links, and structured data should agree with what people see.

Not sure a rebuild is needed?

That is worth finding out before spending money. Sometimes the right fix is focused copy, search structure, or analytics work on the site you already own.

Explore SEO work ↗

A redesign with continuity

The old site leaves a trail. Plan where it goes.

Before a new structure goes live, I inventory the pages and assets people already reach. Pages that still answer a real question can be improved. Pages that move need a destination. Pages that disappear need a deliberate decision.

URL continuityA page move is part of the build.

The map helps preserve useful paths for visitors and crawlers. It becomes a launch checklist, then a way to catch errors afterward.

01Current URL
02New destination
03Redirect and verify

What we decide together

Which pages stay, which need new copy or design, what proof belongs on each, and which actions matter most. I also ask who will maintain the site and how updates will be made.

What I check at launch

Mobile reading and navigation, forms and contact routes, redirects, canonicals, index directives, sitemap entries, social previews, and the HTML returned by the new site. Search changes can take time, so the handoff includes what to watch next.

Where the work can begin

A redesign is not one fixed kind of job.

When the site gets visits but few inquiries

I would follow the path from landing page to contact. The offer may be buried, the proof may arrive too late, or the next step may ask too much. That can call for a focused page change before a larger rebuild.

When people cannot find the site

I would check which pages are indexed, what searches they appear for, and whether the content matches those searches. The answer might be a clearer service page, repaired crawl signals, or a better page map. We decide the scope from the site itself.

See public work ↗

Start with the real problem

Show me the site you have now.

Send the URL and tell me what you expected it to do. I’ll start with the actual page, not a canned package.

Tell me about your site You work directly with Trevor.