Website redesign studio— faster sites, safer SEO migrations

Audit first. We keep what works, measure what doesn't, and move your rankings over with a complete redirect map. The person who audits your site designs the new one and writes its code.

010203040506
Part
CS-01 · Sheet 01 / 04
Deliverables
06 · handed over by operation
Tolerances
LCP ≤ 2.0 sCLS ≤ 0.05INP ≤ 200 msLighthouse ≥ 95WCAG 2.2 AASEO Complete
Stack
Astro · TypeScript · Headless CMS · Tailwind CSS · Vercel

01Audit → spec

Same content. Inside tolerance.

Drag the 45° line. On one side, the kind of findings an audit turns up. On the other, the same page rebuilt to a written spec.

Illustration · abstract blocks, not a client site

Audit · what it turns up

  • Unsized images that shift the layout as they load (CLS).
  • No single H1; headings picked by size, not structure.
  • Render-blocking scripts that delay the largest paint (LCP).
  • Broken internal links and pages that 404.
  • Three card styles doing one job.

Spec · what the rebuild commits to

  • LCP ≤ 2.0 s and CLS ≤ 0.05, written into the spec.
  • One H1 per page and a clean heading outline.
  • Space reserved for every image before it loads.
  • Every old URL on the 301 redirect map; metadata and schema kept.
  • One card component, placed on the 12-column grid.

02 · Fit

Who it's for.

  • AStartups and SaaS companies whose site is slow, dated or hard to update.
  • BBrands launching a new product or a rebrand.
  • CMarketing teams who can't publish a page without a developer.

Problems this solves

  1. D-01The site is slow on phones and fails Core Web Vitals.

    FixPerformance budgets are written into the spec and measured before launch.

  2. D-02Every new page needs a developer.

    FixA headless CMS and a component system your team can edit on its own.

  3. D-03A redesign could cost you your search rankings.

    FixURL audit, full redirect map, preserved metadata and schema, then monitoring in Search Console.

  4. D-04The design has drifted, page by page.

    FixOne design system in code: type, colour, components and motion.

03Routing sheet

What you get, operation by operation.

5 operations, in order. Each one hands over something you can check: 6 deliverables in total.

  1. Operation 10: Audit

    Every URL crawled and Core Web Vitals measured. A written list of what ranks, what converts and what's broken.

    Written notes, shared as you go

  2. Operation 20: Spec

    Pages, content model, budgets, redirect plan, timeline and price, agreed in writing before any design.

    • 01Written spec with performance, accessibility and SEO budgets
  3. Operation 30: Design system

    Type, colour, components and motion, built in code so the design survives development.

    • 02Design system (type, colour, components, motion) built in code
  4. Operation 40: Build + migrate

    Astro build with a headless CMS. Content moved, and every old URL mapped to its new home.

    • 03Astro build with a headless CMS your team can edit
    • 04SEO migration: redirect map, metadata, schema, sitemap
  5. Operation 50: Launch + measure

    Redirects verified, Search Console monitored, and a dated report of the numbers at handover.

    • 05Core Web Vitals and Lighthouse report at handover
    • 06Handover docs and a 30-day fix window

04Tolerances

The numbers this part ships inside.

Written into the spec before any design. Measured before handover, and dated in the report you keep.

Published budgets · 06 parameters · lab and manual checks
RefParameterToleranceInstrument
T-01LCPLargest Contentful PaintLab run on the production build of every key template, dated in the handover report.≤2.0s
T-02CLSCumulative Layout ShiftNo jumps from fonts, images or animation. Space is reserved before anything loads.≤0.05
T-03INPInteraction to Next PaintMeasured on the interactions the spec names: menus, forms, filters, the checkout.≤200ms
T-04LighthouseLighthouse performance scoreLab score on the key templates, recorded with the run date. Accessibility, Best Practices and SEO are scored too.≥95
T-05WCAGAccessibilityAutomated checks plus a manual keyboard pass, tested against the spec before launch.2.2 AA
  • Contrast
  • Keyboard
  • Focus
  • Labels
  • Reduced motion
T-06SEOSearch migrationEvery old URL mapped, metadata and structured data preserved, sitemap shipped with the build.Complete
  • Redirect map
  • Metadata
  • Schema
  • Sitemap

06Questions

Websites & redesigns: answers.

Short and factual. Anything else, just ask us.

05 questions · answered by the studio

Q.01Will a redesign hurt our Google rankings?

Not if it's migrated properly. Every redesign includes a URL audit, a full redirect map, preserved metadata and structured data, and post-launch monitoring in Google Search Console.

Q.02What does the audit cover?

Performance (Core Web Vitals), technical SEO (URLs, metadata, structured data, sitemap), accessibility and content structure. You get a prioritised list of what to keep, what to fix and what to drop.

Q.03Can our team edit the site after launch?

Yes. The site is built on a headless CMS with a component system, so your team can publish pages without a developer. Handover includes documentation.

Q.04How long does a website redesign take?

[Founder to confirm] Redesigns with an SEO migration typically take 6 to 10 weeks. The written spec fixes the timeline before work starts.

Q.05What do we get at handover?

A dated Core Web Vitals and Lighthouse report, handover documentation, full ownership of code and accounts, and a 30-day fix window.

07 · Work order

Open a work order.

Pick the part and the way you'd like to work. Your brief opens with both filled in, and we reply within one working day.

Order slipWO · CS-01 × EM-01
01 · Part
02 · Engagement model

Websites & redesigns, as a fixed-scope project.

Start this brief