# Website Rebuilds > Modern website rebuilds that preserve SEO value, improve performance, and replace fragile legacy sites - static, WordPress, or hybrid. Source: https://larsik.com/services/website-rebuilds/ Service # Website Rebuilds When a site is dated, slow, or held together with fear, a rebuild can be the cleanest path forward - if SEO, content, and day-to-day workflows survive the move. I rebuild sites from concept to launch, including static-first projects like this one, with redirects and migration treated as first-class work. How I work with you You want a modern site that still feels like your business, keeps the rankings you earned, and is easier to maintain. I map what must survive, choose an honest stack, and explain trade-offs in plain terms - WordPress vs static, what can wait for phase two, and how cutover will work. [Start a project with me](/contact/)[See my work](/gallery/) ## Who it's for Owners of older, hand-coded, or fragile sites that no longer match the business - and anyone who has been burned by a redesign that wrecked SEO. ## Problems I solve - →Outdated sites that are slow and hard to maintain - →Rebuilds that destroy existing SEO and rankings - →Legacy or hand-coded systems nobody wants to touch - →Sites that no longer reflect the brand or offer - →Fear of downtime or a messy launch - →Unclear whether to stay on WordPress or go static ## What you get - ✓Content inventory and migration plan - ✓Modern rebuild (static, WordPress, or hybrid) - ✓Redirect mapping to preserve SEO value - ✓Performance and accessibility built in - ✓Launch checklist and Search Console verification ## Rebuild vs patch: how I decide Not every tired site needs a full rebuild. If the stack is sound, SEO is intact, and the pain is speed, security, or a few broken flows, we patch and harden first — often cheaper and lower risk. A rebuild earns its keep when editing is painful, the theme/plugin pile cannot be unwound safely, design and information architecture no longer match the business, or every fix creates two new problems. I will recommend the smaller path when it is honest. Protecting URLs, content, and redirects is part of any rebuild - not an afterthought. That is also why [technical SEO](/services/technical-seo/) and [PageSpeed work](/services/pagespeed-performance/) often sit next to a rebuild. ## A rebuild should feel like progress, not risk People usually arrive here after years of patching. The site looks tired, editing is painful, or performance and security feel shaky. The fear underneath is simple: "If we rebuild, will we lose Google?" We inventory what must survive, choose an honest stack, and plan cutover — so launch day is a switch, not a surprise. ## Stack choices grounded in how you work Marketing sites with infrequent updates often thrive as static-first builds. Teams that edit daily, run memberships, or need complex [WooCommerce](/services/wordpress-woocommerce/) usually stay on WordPress - cleaned up and faster. I will not push a fashionable stack that fights your workflow. The goal is a site your team can actually run. ## Built by someone who still maintains products I develop sites end to end and I still ship and maintain my own products. That habit shows up in rebuilds: clearer structure, fewer fragile hacks, and documentation so you are not stuck after launch. ## How I work 1. 1 ### Inventory what matters URLs, rankings, content, forms, integrations, and analytics - I map what must survive the rebuild before any design or code work starts. 2. 2 ### Choose the right stack Static-first, WordPress, or hybrid depending on how you edit content, what you integrate with, and how fast the site needs to be. 3. 3 ### Migrate with redirects Content import, URL mapping, and 301 redirects so search engines and bookmarks land in the right place on day one. 4. 4 ### Launch and verify Performance, accessibility, forms, and Search Console checks after go-live - so the new site is faster without losing visibility. ## Related client projects [ ![meneto.com skift til WordPress fra håndkodet løsning](/images/gallery/menetocom-skift-til-wordpress-w400.webp) ### meneto.com skift til WordPress meneto.com meneto.com skift til WordPress fra håndkodet løsning View project → ](/gallery/)[ ![New website and development strategy for Resolvent.](/images/gallery/resolvent-ny-hjemmeside-og-strategi-for-udvikling-w400.webp) ### Resolvent resolvent.com Resolvent - Ny hjemmeside og strategi for udvikling View project → ](/gallery/) ## Related services - [WordPress & WooCommerceCustom WordPress and WooCommerce development, plugins, integrations, and cleanup - from a developer who has built on WordPress since 2008 and runs his own products.](/services/wordpress-woocommerce/) - [PageSpeed & PerformanceWordPress and WooCommerce PageSpeed optimization: Core Web Vitals, faster load times, and real-user performance - without breaking checkout or forms.](/services/pagespeed-performance/) - [Technical SEOTechnical SEO for WordPress and business sites: crawlability, indexation, structured data, Search Console cleanup, and a clear fix list from someone who has done this since 2008.](/services/technical-seo/) ## Related reading - [WordPress Core Web Vitals: fix what actually mattersImprove LCP, INP, and CLS on WordPress and WooCommerce - field data first, real bottlenecks, and changes that do not break checkout.](/blog/wordpress-performance-core-web-vitals/) - [Technical SEO: what to fix first on WordPressA practical order for technical SEO - crawlability, indexation waste, Search Console triage, schema, and internal links before more content or ads.](/blog/technical-seo-what-to-fix-first/) ## Common questions Should I rebuild or keep patching?+ Patch when the foundation is sound and problems are localized (speed, a few plugins, security hardening). Rebuild when the theme/plugin stack fights every change, editing is painful, or the site no longer matches the business. I will recommend the smaller path when it is honest. Will I lose my Google rankings in a rebuild?+ Not if we do it right. Redirect mapping, preserved URLs where possible, and careful migration are core parts of every rebuild I do. Static site or WordPress?+ It depends. Marketing sites with infrequent updates often benefit from static-first builds. Sites that need daily editing, memberships, or complex WooCommerce usually stay on WordPress - but faster and cleaner. Can you rebuild while the old site stays live?+ Yes. I typically build on staging and switch over when ready, with a planned cutover window and rollback plan. Do you handle design too?+ I am a developer, not a branding agency. I can work from your design, improve an existing layout, or collaborate with your designer - the rebuild focus is structure, speed, and reliability. How do you keep the process understandable?+ Milestones in plain language: inventory, stack decision, staging preview, redirect plan, launch. You always know what we are protecting and what comes next. ## Tell me about your project