←Back to insights

A practical checklist before launching a website

The final review should follow a visitor from the first page through navigation to a successfully submitted enquiry.

3D checklist and launch element for a website release
Contents14 sections

In brief

  • Test complete form and checkout journeys, including received notifications.
  • Keep staging restrictions separate from public indexing settings.
  • Prepare backups, rollback steps and post-deployment checks.

A website is not ready simply because its homepage looks good on the developer's computer. It is ready when a new visitor can understand the offer, navigate and complete the action they came for.

Check content and real interactions

Verify headings, prices, contact details and legal pages. Remove demo material only after identifying it and obtaining approval. Send a test enquiry through every form and check both storage and the recipient's inbox. For stores, test stock, tax, delivery, payment and order messages without unauthorised real transactions. Buttons should make the next step obvious.

Review mobile use, accessibility and speed

Use narrow screens, keyboard navigation and increased text size. Check focus visibility, field labels and error messages. Menus, cookie banners and floating actions must not cover useful content. Deliver the main image at an appropriate size and respect reduced-motion preferences for decorative animation. A phone simulator alone cannot prove that physical devices work correctly.

Check SEO and control the release

Review HTTP responses, canonical URLs, sitemaps and indexing directives for important pages. Keep staging protected without accidentally carrying noindex into production. Measure important actions without sending personal data to Analytics. Back up files and database, define rollback steps and repeat checks after domain propagation and cache clearing.

Separate content approval from technical verification

A technically correct website can still contain an inaccurate price, an unlicensed photograph or a discontinued service. Someone representing the business must confirm the information before launch. Technical testing cannot establish the commercial truth of every statement. Keep a page-approval list and name the responsible person, especially when several stakeholders supplied material and nobody has yet reviewed the complete public result as one coherent offer.

Look for demonstration copy, provisional contact details and incomplete fields. Review both languages rather than the homepage alone. A policy with missing identity details remains unfinished and needs real information. Do not invent figures or commitments merely to avoid empty space in a design. Clarifying the content before publication is safer than repairing an expectation created for customers by a polished but inaccurate page.

Complete each important journey end to end

On a service site, open the form from several entry points, complete it and follow the outcome. Check storage and notification rather than stopping when the button changes appearance. Test errors too: missing information, invalid formatting and expired anti-spam verification. People should be able to correct a response without losing everything already entered or guessing which condition prevented submission.

For shops, include variations, stock, basket, shipping, coupons and payment under authorised test conditions. For bookings or integrations, confirm the destination and final state. Avoid unnecessary real notifications to customers. Staging is useful, but some checks need controlled repetition after publication because email, domain or hosting settings differ from the demonstration environment. A successful test on one installation is not automatic proof of another installation's external-service configuration.

Review mobile states that arise in real use

  • Open navigation, scroll long pages and complete forms with the keyboard visible.
  • Change orientation and use cards with long titles.
  • Floating controls should not obscure important actions, and sliders should not capture normal vertical movement.
  • Where 3D elements exist, verify that navigation remains natural, including on less powerful devices when available.

A static screenshot cannot demonstrate every one of those interactions.

Review focus, contrast and enlarged text. Test the WordPress toolbar separately for signed-in administrators. Do not alter an unaffected public experience merely to solve an authenticated overlap. Record the browsers and devices actually used. Mobile-size simulation is useful evidence, but should be described accurately rather than presented as physical testing on every iOS or Android model. A precise verification boundary helps the owner understand what still requires live-device confirmation.

Inspect public access and indexing signals

After moving from testing to production, verify that important pages are intentionally accessible and indexable. Inspect robots metadata, server headers, sitemap and canonical declarations. A forgotten staging setting can block a visually correct website. Conversely, private pages, form responses and drafts should not become public merely to make every generated address appear available or indexable. Public accessibility must follow the content's intended role.

Test invalid addresses and out-of-range pagination. Missing content should return an appropriate 404 without a blanket homepage redirect. Review internal links and media. For Romanian and English, check the actual delivered language and equivalent-page relationships. The presence of a language switch does not prove that it preserves context or reaches a genuine translation. Acceptance should follow the result of the control, not merely its visual presence in the header.

Prepare administration and recovery

The owner needs to know how ordinary information is edited and who handles problems. Demonstrate a real change and verify its public result. Confirm access to source, hosting and services according to responsibilities. Avoid making the entire project dependent on one collaborator's personal account without a handover route. Credentials should not appear in public documents or be bundled into a distributable theme archive.

Retain a usable recovery copy and procedure. For sites receiving new records, explain how information created after launch survives a rollback. Losing enquiries or orders is not a neutral repair. Assign responsibility for observation during the first live days. Launch is not complete simply because the domain displays the new page. Essential functions need confirmation in the environment where customers will actually use them, with remaining limitations explicitly recorded.

Use acceptance evidence rather than a general impression

Classify checks as passed, not applicable or requiring production verification. For open issues, identify impact and ownership. Do not hide limitations behind a general claim that everything is optimised. A site can be ready with planned improvements if those are clearly distinguished from blockers and the owner understands the accepted scope. Transparent evidence supports a better decision than an undifferentiated approval based on attractive screenshots.

After publication, revisit caching, mail and measurement configuration. Submit the appropriate sitemap and observe reports without promising immediate indexation. Keep change and test history for the next update. A good release process does not guarantee that no fault will ever occur. It reduces surprises, protects records and helps identify the next investigation quickly when something behaves unexpectedly. Launch quality includes the ability to respond coherently after the initial release.

A dress rehearsal based on an ordinary visit

Before launch, simulate a visit starting somewhere other than the homepage. A customer may arrive directly at an article, service page or product shared in a message. Check whether they understand where they are and how to continue. Open navigation, change language, read essential information and attempt the main action. Use an unauthenticated session without previously saved browser data.

This exposes first-visit banners, empty fields and conditions that no longer appear in the session used to build the website. A successful rehearsal follows the visitor's task rather than the order in which the pages were designed.

Repeat the journey on a phone with an ordinary connection, not only a fast desktop computer. A form can be easy with a mouse yet awkward when the keyboard covers half the screen. A quotation dialog must allow scrolling and closing without losing the visitor's place. Try an invalid address, an omitted field and a double press on submit.

Feedback should explain the next step without claiming inbox delivery when the system confirms only that a response was stored. These are normal user conditions, not exceptional edge cases that can safely be postponed until complaints arrive.

Handing over access and responsibility after publication

Include notification services and their intended recipients in the handover. A technically valid configuration can still target a mailbox that no longer exists. Test an identifiable message and inspect the sending system's response. If inbox delivery was not confirmed, keep it unverified. Where submissions are stored in administration, demonstrate how the owner finds them and who checks for notification failures.

Launching should not make the company dependent on one person's private account. Establish ownership of the domain, hosting, analytics and email services. The owner needs to know where these systems are and how access can be recovered. This does not require technical privileges for every daily task. It requires clear ownership and a recovery route. Give collaborators individual accounts with appropriate permissions.

A shared account makes changes difficult to attribute and prevents withdrawing one person's access without disrupting everyone else. Access arrangements should remain understandable when a team member or supplier changes.

Make the handover practical using real website content. The owner should be able to change text, replace an image and save a draft without touching code. Explain preview versus publication, including translations. Record which tasks belong to ordinary administration and which require discussion with a developer. State who renews an expiring licence or service. These administrative details prevent genuine outages.

A properly handed-over website remains manageable after the excitement of launch day, when small and urgent edits begin. A brief rehearsal performed by the owner is more convincing than a demonstration where the developer performs every action on their behalf.

Short, focused checks during the first days

After switching the domain, download a document and an image used by public pages. Check their names, contents and source rather than only whether the links open. An outdated PDF can return successfully while containing an obsolete offer. Look for staging-domain references in navigation, buttons and automatic messages too.

Confirm the release without authentication. If an administrator sees the change but visitors receive older material, investigate caching for the affected route. Retain the time and tested address. Those details help the hosting administrator locate the stale response without unnecessarily resetting the website's entire configuration. A public-domain check should therefore include the actual materials a customer can download, not just a screenshot of the homepage.

Observe errors and real enquiries without immediately changing everything unfamiliar. A request can be absent from analytics because of consent choices or blocking software rather than a broken form. Compare available evidence and distinguish reproducible defects from incomplete measurement. For a confirmed issue, retain the time, URL and reproduction steps. Agree a short post-launch review period and one person to consolidate observations.

This enables controlled corrections instead of overlapping repair attempts that obscure causes and outcomes. Keep any remaining provider or physical-device checks explicit so the owner knows what launch evidence does and does not establish.

A practical example

Suppose local tests pass but notification email fails after publication because of hosting configuration. A controlled live enquiry exposes the issue before the owner assumes missing messages mean missing demand. Stored responses can be reviewed and notification retried after repair. This hypothetical case shows why local verification and production verification need explicit separation. An SMTP failure is not automatically a form-code defect, and a visual success message does not by itself establish receipt in the recipient's inbox.

Read also: What WordPress maintenance actually protects

Explore the website and technical optimisation services.

Sources and further reading

Information reviewed on 16 October 2026.

↑ Back to contents

Share
←Back to insights
Message me on WhatsApp