HomeWhat we fixWebsite Design & Development

Website Design & Development

A site that looks good and is actually findable

Most redesigns lose rankings. Not because the new design is worse, but because nobody thought about search until after launch — URLs changed with no redirects, content got shortened to look cleaner, headings became styled divs, and the pages that used to rank quietly stopped. Six months later traffic is down and nobody can explain why. We build the two together, or fix a site that was built the other way round.

14 years in SEOBuilt to be foundYou own everything

See what your current site is doing

We'll check what's working, what's broken, and what a rebuild would need to preserve — before anyone touches anything.

Free · About a minute · No account needed

Why scan before buying? Because sometimes you don't need a rebuild. A site that looks dated but performs well is usually cheaper to fix than replace, and we'd rather tell you that than sell you a project.
What we find

What usually goes wrong

Every item below is something our scanner genuinely checks. Run it and you'll see which of these are on your site — in your own report, in these exact words. Most sites have four or five, and none of them are visible when you look at the site yourself.

Images are the reason your site is slow

Someone uploads a photo straight from a camera or a stock library. It's 4,000 pixels wide and several megabytes. The browser scales it down to fit a 390-pixel phone screen — but it downloads the whole thing first.

This is the single most common performance problem on the web, and it's entirely fixable. Correct dimensions, modern formats, lazy loading for anything below the fold. None of it changes how the site looks. All of it changes how fast it arrives.

The reason it persists is that it's invisible to whoever built the site. On a desktop with fast broadband and a warm cache, a 4MB image loads instantly.

What this looks like

A site's homepage hero was a 3.8MB image being served at full size to every visitor including mobile. Resizing it correctly and converting the format took twenty minutes and cut mobile load time roughly in half. Nothing about the design changed.

Checked by: Image Optimization · Page Load Time

Third-party scripts load before your content

Analytics, chat widgets, tracking pixels, review embeds, a font service, maybe a popup tool. Each was added for a reason. Together they mean the visitor waits for six external services before seeing anything.

The fix isn't removing them — most are genuinely useful. It's loading them after the content rather than before it, so the page becomes usable while the extras are still arriving.

The version of this that hurts most is when a script blocks rendering entirely: the page is blank, the content has already downloaded, and the browser is waiting on something that has nothing to do with what the visitor came for.

What this looks like

A site loaded a chat widget, two analytics scripts and a font service before rendering any content. On a mid-range phone the page was blank for 3.4 seconds while all four resolved. Deferring three of them dropped that to under a second, with no loss of function.

Checked by: Page Load Time

Your rankings didn't survive the last redesign

This is the expensive one, and it's common enough that it deserves its own line.

A redesign happens. URLs change structure because the new CMS organises things differently. Content gets shortened because the design looks better with less text. Headings become styled divs because the designer wanted a specific size. Old pages get dropped because nobody could see why they mattered.

Every one of those decisions is reasonable in isolation and quietly catastrophic together. Six months later the traffic is down forty per cent and the agency that built it has moved on.

What this looks like

A company rebuilt their site and lost roughly half their organic traffic within four months. The causes were mundane: 60 URLs changed with no redirects, service pages cut from 1,200 words to 300, and every H1 replaced with a styled div. Each choice made sense to whoever made it. Nobody was thinking about search.

Checked by: Redirect Chains · Content Depth / Word Count · H1 Present

A beautiful site that machines can't categorise

Your site can look excellent and still tell a search engine almost nothing about what it is. Structured data is how a site states plainly what kind of business it is, where it operates, what it sells — and design agencies rarely add it because it's invisible.

This matters more now than it did. AI systems answering questions about businesses lean heavily on structured data, because prose written for humans is ambiguous and schema isn't. A site with no schema is a site those systems have to guess about.

The symptom is being described nearly correctly, or not being mentioned at all. Neither is visible from your own site.

What this looks like

A newly built site — genuinely well designed, fast, clean — had no structured data of any kind. No Organization schema, no LocalBusiness, nothing on service pages. Search engines could read the words but had no explicit statement of what the business was or where it operated.

Checked by: Structured Data (Schema) · Entity Clarity

Content got shortened to look cleaner

Modern design favours whitespace and brevity, and that's usually right for visual hierarchy. It's frequently wrong for pages that need to rank.

A service page cut from 1,400 words to 250 looks better. It also stopped answering the questions that brought people to it, and it now competes against pages that still answer them. The design improved and the page stopped working.

There's a real tension here — nobody wants a wall of text — and the resolution is structure, not deletion. Progressive disclosure, clear sections, accordions where they suit. Keep the substance, present it better.

What this looks like

A redesign reduced six service pages from an average of 1,300 words to under 400. The pages looked significantly better and the client was happy with them. Within three months, five of the six had dropped off page one for their main terms.

Checked by: Content Depth / Word Count · Heading Hierarchy

Mobile was designed last

Most sites are still designed on a large screen and adapted downward. Most visitors arrive on a phone. That mismatch produces the familiar symptoms: text that needs zooming, buttons too small or too close together, forms that are painful to complete, and a layout that technically works but clearly wasn't the priority.

Google indexes the mobile version, so the mobile experience is the one being assessed — not the desktop version that looked good in the design review.

The commercial cost is larger than the ranking cost. A form that's awkward on a phone loses buyers who would have completed it on a laptop, and you never find out.

What this looks like

A site's contact form had five fields including a dropdown that didn't work properly on iOS. On desktop it converted fine. Mobile completion was under a fifth of desktop, on roughly triple the traffic. Nobody had tested it on a phone.

Checked by: Mobile Viewport · Page Load Time

How we fix it

Found is only half the job

Other agencies build the site and hand it over. Here's exactly what we do, including the steps, so you can judge whether we know what we're doing.

What we foundHow we fix it

Oversized images

Full-resolution uploads served to phones.

We fix image delivery properly

Correct dimensions, modern formats, lazy loading — with no visible change to the design.

2–3 daysEvery package
See exactly how
  1. Audit every image for actual file size versus displayed size
  2. Resize to the dimensions actually needed, with retina variants where they matter
  3. Convert to modern formats with fallbacks for older browsers
  4. Add lazy loading for anything below the fold
  5. Set up the build or CMS to handle this automatically for future uploads
  6. Re-measure and show you the before and after

Step 5 is the one that lasts. Fixing existing images without fixing the upload process means it's back within a year.

Render-blocking scripts

Third-party services loading before your content.

We defer what doesn't need to block

Content first, extras after — with nothing removed unless you want it gone.

2–4 daysGrowth & above
See exactly how
  1. Trace what actually loads and in what order, measured rather than assumed
  2. Identify scripts installed but no longer used — there are almost always some
  3. Defer or async everything that doesn't need to run before content appears
  4. Self-host fonts where that's faster than a third-party service
  5. Re-measure and show you what each change bought

We tell you what each script costs and let you decide. Some are worth their weight; that's your call, not ours.

Rankings lost in a rebuild

URLs changed without redirects, content cut, headings removed.

We recover what's recoverable

Redirects mapped, content restored, structure rebuilt — and we tell you honestly what won't come back.

1–2 weeksGrowth & above
See exactly how
  1. Pull the old URL structure from archives and Search Console history
  2. Map every old URL to its closest current equivalent and add 301s
  3. Identify which pages lost substantial content and restore the substance
  4. Rebuild heading structure where it was replaced with styled divs
  5. Resubmit and monitor recovery over the following weeks

Recovery is usually partial and it takes months. We'd rather say that upfront than let you expect a full return that may not come.

No structured data

Nothing states what the business is in machine-readable form.

We add and validate the schema that applies

Organization, LocalBusiness, Service, FAQ — whichever genuinely fits, validated rather than assumed.

3–5 daysEvery package
See exactly how
  1. Determine which schema types genuinely apply — adding types that don't fit does more harm than good
  2. Write them with your real details rather than a template with placeholders
  3. Add per template so it applies site-wide, not only where someone remembered
  4. Validate through Google's testing tools per template type
  5. Cross-check every detail against your Google Business Profile so nothing contradicts

We only add schema that accurately describes the page. Marking up things that aren't there is a manual-action risk and we won't do it.

Content cut too far

Pages shortened for visual reasons, now too thin to rank.

We restore substance without ruining the design

Structure instead of walls of text — accordions, progressive disclosure, clear sections.

1–2 weeksGrowth & above
See exactly how
  1. Compare current content against what the page had before, and against what ranks now
  2. Identify the questions the page should answer but no longer does
  3. Restore or rewrite that substance
  4. Present it with structure — sections, accordions, disclosure — so it doesn't read as a wall
  5. Rebuild heading hierarchy so both readers and crawlers can follow it

This is where design and SEO genuinely conflict, and it's resolvable. The answer is almost never "less content." It's better-organised content.

Mobile as an afterthought

The version most of your traffic uses, designed last.

We fix mobile properly, tested on real devices

Tap targets, forms, layout and speed — checked on actual phones, not a resized browser window.

1 weekGrowth & above
See exactly how
  1. Test on real devices across sizes, not a desktop browser at a narrow width
  2. Fix tap targets that are too small or too close together
  3. Rework forms for mobile input — correct keyboard types, sensible field order, no dropdowns that misbehave
  4. Address mobile-specific performance, which is usually worse than desktop
  5. Verify the mobile version has the same content as desktop, since that's the version being indexed

Resizing a desktop browser is not mobile testing. Half the problems only appear on an actual device.

Before you try this yourself

Common mistakes

What we usually find when someone has already been through this.

Redesigning without a redirect map

The most expensive mistake in this category. New CMS, new URL structure, no 301s — and every page that used to rank returns a 404. The traffic loss shows up weeks later, once Google has recrawled, by which point the connection to the launch isn't obvious.

Treating page speed as a score to chase

The number isn't the goal; the experience is. It's possible to score 98 by deferring things the page genuinely needs, producing a page that measures well and feels broken. Optimise what visitors actually feel.

Building on a platform that fights you

Some page builders generate markup that's genuinely hard to make fast or semantic. If the platform is the constraint, no amount of optimisation fixes it — that's a real conversation to have before building, not after.

Cutting content because the design looks better with less

Design reviews happen on a screen with no visitors. The page that looks cleanest is frequently the page that answers the fewest questions. Structure the content; don't delete it.

Our Process

Scan. See. Fixed.

01

We look at what you have

The scan shows what's working, what's broken, and what a rebuild would need to preserve. Sometimes it shows you don't need a rebuild at all.

About a minute

02

You see what's actually wrong

Every issue ranked by impact and effort. If the honest answer is "fix these six things rather than rebuild," that's what the report says.

Yours to keep, free

03

We build or fix

Whichever the scan says you need. Search considered from the start rather than retrofitted, and you approve the plan before anything is touched.

From $50/month

04

We check again and show you

The same checks, run again. What cleared, what changed, and where you stand compared to before.

Proof, not promises

Not every site needs rebuilding. A dated site that performs well is usually cheaper to improve than to replace, and we'd rather tell you that than sell you a project you don't need.

What's included

What's included

Packages differ in how much work we do — not in how much of the picture you get.

The full scan

  • Every check across four areas
  • Full site crawl
  • Real performance measurement on mobile
  • Structured data audit
  • Content depth analysis
  • Google Business Profile lookup

The work itself

  • Image delivery fixed and automated for the future
  • Scripts deferred with nothing removed without your say-so
  • Redirects mapped and recovery attempted where rankings were lost
  • Schema added and validated
  • Content restored with proper structure
  • Mobile tested on real devices

The proof

  • Before-and-after score comparison
  • Real performance measurement on the same pages and conditions
  • Exactly which issues cleared
  • Full dashboard access
  • Every tool unlocked
  • Scan history kept permanently

What does it cost?

It depends on whether you need a rebuild or a repair — which is why we scan first. Plans start at $50/month, and every one includes the full scan above.

FAQ

Before you scan

See what your current site is doing

Every check, your off-page signals, and a plan you can act on. Free, about a minute, no account needed.

Scan My Site Free