Website Redesign

A controlled redesign for websites that no longer match the business.

If your company has outgrown its website, 760 Studios can restructure the content, sharpen the design, preserve search foundations, and rebuild the site for better speed and trust.

Start a project See pricing

Website redesign canvas showing current pages, search preservation notes, redirects, and new page structure.

Visual direction

A redesign needs preservation decisions before visual change, especially when existing pages have value.

Current site crawl

URL inventory

Every known public URL is classified before the redesign changes structure or content.

URL map

Decision: Keep, improve, merge, redirect, remove, or unpublished decision for each URL
Signals: Title, description, canonical, heading, content owner, supporting detail assets, and internal links
detail: Search Console, analytics, backlink, enquiry, and buyer-value notes where available

Redesign checklist Project brief

Why it matters

A redesign should not mean throwing away everything that works. The right process protects useful content, improves weak sections, and launches the new site with fewer surprises.

Commercial gains

Outdated visuals
Unclear messaging
Weak mobile experience
Slow pages
Poor conversion
Messy content structure
Migration risk

What 760 Studios builds

UX and content audit
Current-site crawl checklist
Sitemap restructuring
Redirect and preservation planning
Responsive redesign
Frontend implementation
Launch QA

Service fit

Revenue leaks this service fixes.

The work targets the commercial weak points that make buyers pause: unclear positioning, slow routes to action, weak trust signals, and pages that fail to make the offer obvious.

Who it is for

Businesses whose current site no longer matches their execution detail
Teams relaunching without wanting to lose useful search signals
Companies with old content, weak supporting detail, unclear enquiry paths, and migration risk

Before 760 Studios

Outdated visuals and content that no longer explain the offer
No current URL inventory, redirect plan, or metadata preservation notes
Useful pages, supporting detail, internal links, and search signals at risk during the rebuild

After the work

Safer relaunch plan with a URL inventory, redirect map, and content preservation decisions
Sharper design and page hierarchy backed by before and after comparison
Metadata, internal links, crawlability, forms, analytics, and launch QA checked before handover

Service process

Crawl the existing site and record live URLs, page purpose, content value, metadata, internal links, supporting detail, and conversion paths
Decide which content to preserve, rewrite, merge, remove, or redirect before design work hides it
Create a redirect map for changed or retired URLs and keep canonical targets stable
Rebuild key pages with preserved metadata where it still fits, improved copy, visible supporting detail, and responsive layouts
Run launch QA across redirects, sitemap, robots, metadata, forms, analytics, accessibility, speed, and mobile

Deliverables

Outputs that can be inspected, confirmed, and launched.

The deliverables make the offer visible: sharper messaging, better structured layouts, cleaner journeys, and production-ready work.

Deliverable

Controlled redesign route

A relaunch plan that protects useful content, URLs, metadata, supporting detail, and conversion routes before visual change.

Keep, improve, merge, redirect, remove, or unpublished decision for each known URL
Page title, meta description, canonical, heading, content owner, supporting detail assets, and internal links
301 redirect map for changed or retired URLs
Sitemap, robots, canonical, schema, form, analytics, mobile, accessibility, and redirect launch QA

Deliverable

Labelled redesign comparison

Before and after material is generated, recreated from confirmed inputs, or clearly labelled as a planned example instead of raw archive supporting detail.

Before: current page job, weak content, dated trust signals, metadata risk, and conversion friction
After: preserved useful content, easier to understand sections, improved supporting detail, responsive layout, and safer launch checks
Screenshot rules for confirmed, labelled, and separated detail
Legacy material kept out of supporting detail claims unless it is confirmed

Output examples

Example outputs for a better structured website.

These examples show the structure, page rhythm, visual authority, and conversion thinking a focused engagement should produce.

Audit and migration artefact

Redesign preservation map

A labelled map of useful URLs, content decisions, redirect needs, supporting detail gaps, and launch risks.

Migration checklist

Redirect and launch QA checklist

A release artefact for redirects, sitemap, robots, canonicals, metadata, Open Graph, schema, forms, tracking, mobile, accessibility, performance, and 404 behaviour.

Labelled planned example, not raw archive screenshots

Before and after comparison

A recreated comparison showing what changed without implying unapproved client supporting detail or relying on raw archive captures.

Project boards

Visible strategy, structure, and delivery decisions.

These panels turn the service into visible routes, components, handover notes, and delivery decisions that show the shape of the work.

Launch protection

Redirect and QA checklist

The launch checklist is designed to catch migration issues before they become search, lead, or trust problems.

Relaunch QA

Redirects: 301 redirects for changed URLs, no redirect chains, and no orphaned priority pages
Signals: Sitemap, robots, canonicals, metadata, Open Graph, schema, forms, tracking, and 404 behaviour
QA: Mobile, keyboard, accessibility, performance, and browser checks on priority routes

Pricing Process

Labelled planned example, not raw archive screenshots

Before and after comparison

The comparison is recreated as a labelled planning artefact so buyers can inspect what changed without using raw archive screenshots.

Comparison

Before: Current page job, weak content, dated trust signals, metadata risk, and conversion friction
After: Preserved useful content, easier to understand sections, improved supporting detail, responsive layout, and safer launch checks
Screens: Screenshots, if supplied later, must be confirmed, labelled, and separated from unverified archive captures

Buyer confidence

Questions clients expect answered before a call.

Service pages should build confidence before the buyer speaks to the studio.

Will a redesign damage useful search signals?

The redesign starts with current URLs, content value, metadata, links, and redirects so visual change does not ignore preservation risk.

Do you use old archive screenshots as supporting detail?

No. Before and after material is either newly generated, recreated from confirmed inputs, or clearly labelled as a planned example. Raw archive screenshots are not used as client supporting detail.

Can a redesign reduce migration risk?

Yes, when it starts with a URL inventory, content preservation decisions, redirect mapping, metadata review, responsive design, and launch QA rather than only visual taste.

Investment route

Website Redesign

For existing websites that need a better structured brand presence, cleaner content, sharper SEO structure, and a higher-execution detail relaunch.

See pricing and packages Plan a better structured redesign

from £6,500 / 5-10 weeks

Best for: Businesses replacing an underperforming site while protecting useful content, URLs, and search equity.

Best served elsewhere: Projects where existing content, URLs, or analytics cannot be reviewed before launch.

You provide: Current URL list, priority pages, content assets, analytics context, and migration constraints.

FAQs

Questions about Website Redesign.

Straight answers help clients understand the working rule before a call.

What should be protected before redesign?

Useful URLs, indexable pages, content, backlinks, supporting detail, enquiry paths, metadata, internal links, and conversion data should be reviewed before rebuild.

Can a redesign reduce risk?

Yes, when it starts with a URL inventory, content preservation decisions, redirect mapping, metadata review, responsive design, and launch QA rather than only visual taste.

Do you use old archive screenshots as supporting detail?

No. Before and after material is either newly generated, recreated from confirmed inputs, or clearly labelled as a planned example. Raw archive screenshots are not used as client supporting detail.

Next step

Choose the route that accelerates the project.

Start with the brief when the project is live, pricing when the investment route matters, or client work when you want to see the studio's working rule before enquiring.

Start a project

Use this when the buyer has a live project and wants a scoped next step.

Start a project

See pricing

Use this when the buyer needs to compare engagement routes first.

See pricing