Website Redesign & Modernization

<p>This is the replatform engagement. The deliverable is a modern site on Laravel 12, Livewire 3, and Tailwind 4, with every URL the old site exposed that has earned traffic, links, or citations preserved through a 301 redirect map. Dead plugins, abandoned themes, and content workflows the team has outgrown are left behind. The Search Console crawl stats after migration look like the site continued; they do not look like a brand-new domain.</p> <p>The parent — <a href="/services/web-development">Website Creation & Redesign</a> — sets the four-artifact perimeter; this page is the redesign shape of the work. Greenfield builds are scoped on the sibling <a href="/services/web-development/new-website-build">New Website Build</a> page.</p> <h2>Audit before anything</h2> <p>Every replatform engagement opens with a written audit. Information architecture as the old site exposed it. URL structure including every traffic-earning path. Schema currently emitted by the old site. Redirect history (the old site may already have redirects from a previous replatform — those have to be preserved through the new one, not lost). Core Web Vitals on the old site as a baseline. Plugin inventory and the workflows each plugin currently handles. The audit ships before any code changes.</p> <h2>The 301 map</h2> <p>The 301 redirect map is the single most important deliverable in a replatform. Every URL that the old site exposed and that has earned traffic, links, or citations gets mapped to the closest equivalent URL on the new site. URLs that no longer have an equivalent get a 410 (gone) rather than a soft 404. The map is implemented in code, tested before launch, and verified against Search Console crawl stats across the first two crawl cycles after launch.</p> <p>This is the part most replatforms get wrong. The marketing team launches; the URLs change; the 301 map is "we will add it next week"; traffic drops thirty percent in sixty days; the recovery takes a quarter. I will not ship a replatform without the 301 map verified before launch.</p> <h2>Content migration</h2> <p>Content is migrated programmatically — from WordPress export, from a Wix scrape, from a database extract — into the new Laravel data model. Editorial workflows that mattered are brought forward; ones that did not are left behind. Media (images, videos, PDFs) are migrated with new URLs and 301s from the old ones. Schema is regenerated from the new database — not copied from the old templates.</p> <h2>What I ship</h2> <ul> <li><strong>Written audit.</strong> Information architecture, URL inventory, schema audit, redirect history, Core Web Vitals baseline, plugin inventory.</li> <li><strong>301 redirect map.</strong> Every traffic-earning URL, in code, tested before launch.</li> <li><strong>Laravel 12 build.</strong> Modern design, Livewire 3, Tailwind 4, Pest 4 tests, Pint style.</li> <li><strong>Content migration.</strong> Programmatic, with media URLs preserved through the 301 map.</li> <li><strong>Schema graph regenerated.</strong> From the new database, validated against the Rich Results Test.</li> <li><strong>Search Console verification.</strong> Crawl-stats monitoring across the first two crawl cycles post-launch.</li> <li><strong>30-day post-launch support window.</strong> For the inevitable redirect edge cases that surface after the first crawl cycle.</li> </ul> <h2>Where it fits</h2> <h3>WordPress install with 40 plugins</h3> <p>The plugin debt is unmanageable. Three abandoned themes. Performance is dragging search visibility. The buyer wants a clean rebuild that does not lose the SEO equity the site has earned.</p> <h3>Wix or Squarespace ceiling</h3> <p>The builder has hit a ceiling — the workflows the business needs (intake, gated content, member areas, structured catalogs) are not possible inside the builder. The buyer wants the modern site without losing search visibility.</p> <h3>Custom legacy PHP</h3> <p>The site is on a custom PHP framework the original developer wrote in 2014 and no longer supports. The hosting target is end-of-life. The buyer wants a clean modern build with the existing content migrated and the URL structure preserved where it has earned its position.</p> <h2>How I work</h2> <p>Discovery runs two to three weeks — the audit is the long pole. Implementation runs in two-week sprints, with the staging site mirroring the existing URL structure before the 301 map is layered in. The 301 map is tested in staging, not in production. Launch is a one-day event with the crawl-stats monitoring wired up beforehand. The principal carrying the work is described <a href="/about">on the about page</a>.</p> <h2>Engagement model</h2> <p>Discovery runs two to three weeks. Implementation runs eight to fourteen weeks depending on content volume and workflow complexity. Handover includes the deployed site, the 301 map in code, the schema graph, the Search Console monitoring, the runbook, and a 30-day post-launch support window. To scope a redesign, <a href="/contact">get in touch</a>.</p>