Redesign & Relaunch
Your website is already known, but its services, design, or technology date from an earlier stage. In a redesign, I first check what needs to be kept before content and interface are reorganized.
A relaunch becomes relevant once outdated services still shape the site, key pages are hard to use on mobile, or changes to the existing system get riskier every time.
I capture important URLs, existing content, contact functions, metadata, and technical dependencies. This stock-take separates what's usable from what needs to be rebuilt.
For URLs that go away, we decide whether a redirect is needed. Approved content isn't discarded in passing.
The new page order follows the current offer rather than the old navigation. Design makes the differences between services, proof, and contact visible.
Before launch, old and new URLs are reconciled, redirects are set, and key contact paths are tested. Metadata and indexing rules follow the approved page structure.
This preparation reduces avoidable errors. It's not a guarantee that external search systems will react the same way as before.
Missing redirects, duplicate pages, outdated sitemaps, and untested forms can cause problems after a relaunch.
I document these points before publishing and separate fixable tasks from the reactions of external services, which can't be promised.
Send me the current address and tell me what no longer works. The publicly live website Die Mediatorin shows my role in design and implementation; I'm not claiming any effect beyond that.