Most costly website mistakes are not unusual technical failures. They are ordinary planning and ownership gaps that remain unnoticed until launch: unclear objectives, late content, missing access, untested forms or an agreement that never defined what “finished” means.
1. Starting with a platform instead of a requirement
Choosing WordPress, Wix, Shopify or another platform before defining the business process can force the project into awkward workarounds. Record pages, functions, operators, data and maintenance needs first.
2. Treating the home page as the whole website
Visitors often enter through service, product, article or location pages. Plan complete routes from search or referral to evidence, decision and action.
3. Leaving content until the design is finished
Placeholder text hides real length, hierarchy and evidence requirements. Prepare representative copy before approving key templates.
4. Writing generic claims
“High quality”, “tailored solutions” and “excellent service” provide little evidence. Explain scope, process, limitations, qualifications and real examples instead.
5. Adding every requested feature to the first release
Each integration introduces configuration, testing and maintenance. Launch the smallest complete version that safely performs the primary task, then add features based on real need.
6. Failing to protect ownership
The business should control the domain and critical service accounts. Record hosting, DNS, email, analytics, Search Console, payment, booking and licence access.
7. Comparing quotations by price alone
One supplier may include content, migration and testing while another quotes only for templates. Compare deliverables, exclusions and recurring costs.
8. Ignoring ongoing cost
Budget for subscriptions, licences, maintenance, backups, content and support. A website that cannot be maintained is not a finished asset.
9. Forgetting the old URLs during a redesign
Changing or removing URLs without mapping and redirects can break bookmarks, links and search visibility. Inventory the old site before launch.
10. Assuming a successful form message means delivery
Test real submissions to the business mailbox, including spam handling and reply workflow. Repeat after DNS or email changes.
11. Testing only on the designer's computer
Check narrow mobile screens, keyboard navigation, common browsers, slow connections and realistic content. Test tasks, not only appearance.
12. Installing tools without an owner
Analytics, security plugins and monitoring are useful only when someone reviews and acts on them. Assign responsibility and a review rhythm.
13. Publishing pages only to target variations of a keyword
Near-identical pages with town or service names changed can confuse users and compete with one another. Create a separate page only when it provides distinct, useful information.
14. Optimising speed by changing random settings
Measure first. Large images, third-party scripts, server response and layout behaviour require different fixes. Change one controlled area and retest.
15. Launching without a rollback route
Take a current backup, record DNS values and define who can reverse the launch. A rollback plan is especially important for migrations and online transactions.
16. Treating legal text as a copied template
Privacy, cookies, consumer information and accessibility obligations depend on what the website and business actually do. Use accurate operational information and obtain appropriate advice where needed.
17. Hiding limitations
Clear service areas, availability, exclusions and response expectations prevent unsuitable enquiries and improve trust.
18. Declaring the project complete at launch
Monitor forms, transactions, indexing, redirects, errors and user feedback during the first days and weeks. Launch is a controlled transition, not the end of ownership.
Pre-launch prevention checklist
- The objective and primary action are defined.
- Pages and functions match real requirements.
- Content is approved and evidence-based.
- Accounts and renewals are documented.
- Recurring costs are affordable.
- Forms, bookings and payments have been tested.
- Important old URLs have a plan.
- Backups and rollback are ready.
- Maintenance and monitoring owners are named.
The next practical step is to review the current project against this checklist and fix ownership or launch risks before visual refinements.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.