Website relaunch: proofreading all your copy before go-live

Reviewed by Benjamin Lohrer, editor at corrected.eu · Last updated: 28 July 2026

From the navigation to the error page: miss nothing

A relaunch is the moment when text errors multiply: content is migrated, shortened and restructured, and in the end nobody reads the whole site. The errors are rarely in the main copy. They sit at the edges, and the edges belong to nobody on the project.

The edges belong to nobody

In a relaunch, responsibility is spread thin: the agency builds, the company supplies content, marketing checks the home page. For navigation labels, button texts, form hints, confirmation pages and system messages, nobody is explicitly responsible.

This is exactly where we find most of the errors: placeholder text from the layout that was left on subpages. Form hints carried over from the old website that refer to fields which no longer exist. Error pages that still carry the name of the previous project.

After go-live, your customers find these spots, and they rarely report them. They just click away.

What we check in full

• all pages, including rarely visited subpages and archive content
• navigation labels compared with the headings of the pages they lead to
• buttons, form hints, field labels and error messages
• page titles and meta descriptions for search engines
• confirmation pages, automatic emails and the error page
• legal texts, checked for completeness of the recognisable components

Comparing the navigation label with the page heading is especially worthwhile: if the menu item says "Services" but the page is headed "Our offer", visitors feel they clicked the wrong link. The same goes for buttons that read "Enquire", "Get in touch" or "Start now" depending on the page, even though the same form sits behind all of them.

Another thing that is regularly overlooked is the text that only appears after an action: the confirmation page after submitting, the automatic acknowledgement email, the notice for an empty search result. These are not looked at in the sign-off meeting because nobody submits a form there, and they often stay wrong for years without anyone noticing.

Process and delivery

You give us access to the staging environment or send an export of the content. We do not need access to the content management system.

You get back a structured list with URL, location and suggested correction, sorted by page. This lets you work through the changes directly without hunting for the passage in question. On request, we check a second round after go-live at a reduced scope, because experience shows that new errors creep in during implementation.

Migrated content is the second trouble spot

When old content is moved into a new system, errors appear that were not there before. Special characters and quotation marks break because the source and target systems use different encodings. Line breaks from the old layout end up in the middle of sentences. Bullet lists lose their structure and turn into one paragraph.

Damage like this does not show up in a spot check of the home page, because it is spread across the depth of the site. We therefore go through all migrated content, not only the newly written parts, and report encoding errors separately because they can usually be fixed in bulk and automatically.

Terms for relaunch projects

Billing runs through a free business account: proofreading from €1.90, editing from €4.90 per standard page of 1,800 characters. A relaunch quickly reaches several hundred standard pages, so the volume discount applies: from 250 pages seven per cent, from 500 pages nine per cent on proofreading.

We do not test technical function and we do not give legal advice on the legal notice or privacy policy. We report when recognisable components are missing, but we do not replace legal advice. We check English and German texts alike.

Further reading: business terms, editing for agencies and all text types.