PLANNING & MAINTENANCE · 3 MIN READ

Before Website Launch: Check the Journeys, Not Just the Screens

Review a website launch through forms, navigation, mobile use, accessibility, indexing settings, and operational ownership before sending visitors to it.

A launch review should establish that visitors can understand the offer and complete the important tasks. A collection of attractive screenshots cannot show whether a form arrives, a menu works with a keyboard, or the public site is still marked as a test environment.

Organise acceptance around journeys and ownership.

01

Follow the main visitor paths

Start from likely entry pages, not only the homepage. Find a service, read its scope, and complete the intended next step. Check whether headings, links, and buttons make that route understandable.

For a hypothetical engineering business, a visitor arriving on a technical article should be able to find the related service without searching through an unrelated menu. Confirm that the destination exists and matches the link text.

02

Submit a controlled enquiry

Test required fields, invalid input, a successful submission, and the confirmation shown to the visitor. Verify the stored record or intended destination and any notification separately.

Record who receives enquiries and who investigates a delivery problem. Avoid declaring the form complete simply because its button changes colour or an email function returns success.

Use non-sensitive test information and keep it distinguishable from genuine customer requests.

03

Review mobile and accessible use

Check narrow layouts, readable text, visible controls, keyboard access, and form labels. W3C's Easy Checks provides a useful preliminary review of these areas while explicitly not replacing a comprehensive accessibility evaluation.

Inspect real content, including long headings and validation messages. A layout tested only with short placeholder text can fail when the business adds its actual information.

04

Check discovery settings

Verify page titles, descriptive headings, internal links, canonical destinations, and the intended indexing configuration. Google's SEO Starter Guide explains these as ways to help users and search engines understand content, not as a guarantee of placement.

If a staging site was intentionally excluded from indexing, review that setting for the production release. Keep unpublished drafts separate rather than accidentally including them in navigation or a sitemap.

05

Confirm operating ownership

Check domain and hosting access, certificates, backups, scheduled processes, and the contact route for incidents. Define who can approve launch and what would postpone it.

Keep a short list of known issues with an owner and decision for each. “We will fix it later” should not be the implicit answer to an essential task that does not work.

The release record should identify what was tested, on which environment, and what remains outside scope. That gives the business a concrete basis for launch and a useful starting point for maintenance afterward.

06

Discuss the implementation

Explore website redesign and website maintenance.

KEEP EXPLORING

Sources & further reading

Official documentation for the topics discussed. Check implementation details against the versions and services used by your project.

WRITTEN BY MARKO ARNAUTOVIC

Practical thinking.
Hands-on engineering.

I build AI automation, web platforms, and mobile applications for businesses. These notes share the decisions behind that work.

Meet the engineer behind ArnautCode

PUT THE IDEAS TO WORK

Need help with
the implementation?

Explore the approach and scope for website redesign.

Explore the service
Chat on WhatsApp