Custom websites
Original website strategy, content structure, responsive design, and maintainable custom development for service businesses that need a clearer digital front door.
Website redesign and SEO migration
Change the website without discarding what still works.
A redesign is both a creative project and a migration. PlinthWeb audits the current site, decides what to retain or improve, maps old URLs to the new structure, and coordinates launch checks so a better experience does not begin with avoidable search and measurement gaps.
Discuss a website redesign
Your context travels with you. Website redesigns will already be selected in the form. Add the current site, desired outcome, and timing.
- 01
Content, URL, search, analytics, and integration inventory
- 02
New information architecture grounded in the existing evidence
- 03
One-to-one redirects and controlled content migration
- 04
Pre-launch baselines and post-launch verification
Service paths
Choose the scope that matches the problem.
Technical SEO audit
A prioritized technical SEO audit of crawlability, indexation, page signals, internal links, structured data, performance, and measurement—not a raw export of warnings.
Managed website care
Managed website hosting and maintenance with accountable deployment, monitoring, recovery planning, dependency care, routine updates, and a defined support boundary.
01
Audit before replacement
Separate genuine problems from valuable existing assets.
The first pass inventories indexable URLs, important landing pages, content, backlinks visible in available tools, analytics trends, conversions, forms, integrations, and recurring customer questions. It also records technical issues and usability friction that the redesign should solve rather than simply restyle.
Pages are classified to keep, consolidate, rewrite, create, redirect, or retire. This produces a reasoned content and URL plan, preserves material that still serves visitors, and prevents the common mistake of judging every current page only by its visual age.
- Crawlable URL and content inventory
- Search and analytics baseline
- Conversion path and integration review
- Keep, improve, merge, redirect, or retire decisions
02
Migration details
Give every meaningful old URL a deliberate destination.
The new sitemap is reconciled against the current URL inventory. Where a page moves, a direct permanent redirect points to the closest relevant replacement; unrelated URLs are not swept toward the homepage. Canonicals, language versions, internal links, navigation, metadata, and structured data are updated for the new architecture.
Content migration includes the useful copy, media, download, attribution, and accessibility details the new pages still need. Domain, DNS, hosting, analytics, Search Console, consent, and form responsibilities are documented so launch work has owners rather than last-minute assumptions.
- Old-to-new URL redirect map
- Canonical, language, navigation, and internal-link updates
- Content and media migration checklist
- Domain, analytics, and integration responsibilities
03
Launch and observe
Verify the migration in production, not only in a spreadsheet.
Before release, the staged site is crawled and checked for blocked pages, broken links, redirect chains, missing metadata, accidental noindex directives, duplicate signals, form failures, and responsive regressions. A final launch checklist records the known baseline and the tests that must be repeated on the live domain.
After release, critical URLs, redirects, indexing signals, forms, analytics events, and search-platform reports are reviewed on an agreed schedule. Normal volatility is distinguished from actionable errors; no responsible migration can promise unchanged rankings, but it can reduce preventable loss and surface problems quickly.
- Staging crawl and pre-launch acceptance checks
- Live redirect, canonical, form, and event verification
- Search-platform and indexation review
- Documented issues and prioritized corrections
How the redesign moves
Four stages that keep design and migration connected.
The redesign and the SEO migration share one plan so structural decisions can be reviewed before they become launch problems.
- 01
Inventory and baseline
Crawl the current site and record useful content, URLs, performance, search, analytics, forms, and dependencies.
- 02
Plan and redesign
Define the future sitemap, page priorities, content changes, responsive system, and old-to-new URL relationships.
- 03
Build and rehearse
Develop and populate the new site, implement redirects and metadata, then crawl and test the staged release.
- 04
Launch and verify
Coordinate production changes and inspect live redirects, indexation signals, conversions, and emerging issues.
Website redesign and migration questions
Will a redesign hurt our search visibility?
Any material site change carries risk, especially when URLs, content, internal links, or technical signals change. An inventory, relevant redirects, preserved content value, controlled release, and post-launch checks reduce avoidable risk, but no provider can promise that rankings will remain identical.
Should every old URL redirect to the new homepage?
No. A moved URL should point to the closest useful replacement. Pages with no meaningful equivalent may be retired deliberately. Sending every removed page to the homepage creates a confusing visitor experience and weakens the meaning of the redirect map.
Can the domain stay the same?
Yes, and that is usually the simpler migration. If the domain also needs to change, the redirect, ownership, canonical, Search Console, email, and communication requirements expand and should be treated as an explicit part of the project.
How long do you monitor after launch?
The proposal defines a post-launch verification window based on the size and risk of the migration. Ongoing search monitoring and content improvement can continue under a separate monthly scope when the site needs sustained attention.
Related guides
Go deeper before choosing the next step.
How to redesign a website without discarding search equity
A redesign changes more than appearance. Preserve the URLs, content intent, internal links, metadata, and technical signals that already help people find the business, then monitor the migration.
Read guideBilingual website SEO: hreflang and canonical checklist
A bilingual site needs more than translated navigation. Pair equivalent URLs, localize the full page, align hreflang and canonicals, and test every language route as its own experience.
Read guideA technical SEO audit checklist for a small-business website
A technical SEO audit should explain which pages search engines can reach, understand, and index—and which fixes matter first. Use this sequence to turn crawler output into an accountable action list.
Read guidePlan the change
Bring the current site before deciding what replaces it.
Share the domain, redesign goals, known search concerns, analytics access, platform constraints, and target timing. We will identify the migration questions that belong in the scope.