Running Connect Dorset has taught me something that surprises a lot of business owners: most website problems are not caused by one big disaster. They come from lots of small unknowns that quietly stack up over time.
A website can look brilliant and still be slow. It can be fast and still fail to convert. It can rank for a few terms and still miss the searches that actually lead to enquiries. And for ecommerce, it can take payments perfectly… right up until a plugin update collides with a theme tweak and checkout becomes a mystery box.
So here is an approach I use with clients and on our own systems: treat your website like it should come with an operating manual. Not a technical tome, but a clear, living set of decisions, checks and routines that keep everything working together.
This post lays out what that “manual” looks like, in a way you can use whether you are on WordPress, Shopify, or a bespoke build.
Why an “operating manual” beats chasing quick fixes
Quick fixes are tempting because they feel productive. The issue is that websites are connected systems:
- Design decisions affect performance (heavy fonts, oversized images, too many scripts).
- Hosting affects SEO (core web vitals, crawl reliability, downtime).
- Security affects conversions (browser warnings, trust signals, payment confidence).
- Content affects support load (unclear pages create more calls, emails and abandoned baskets).
An operating manual gives you a stable baseline: you know what “good” looks like for your site, and you can spot drift before it becomes disruption.
Page 1: Define the job your website must do (in one sentence)
If you only do one thing, do this. Write a single sentence that describes the primary job of your site.
Examples:
- “Generate qualified enquiries for loft conversions in Bournemouth and Poole.”
- “Turn local searches into phone calls and bookings for a Dorset-based clinic.”
- “Sell a focused range of products with repeat purchases and email sign-ups.”
This sentence becomes your filter. If a feature, design pattern, or plugin does not serve that job, it needs a strong reason to exist.
Page 2: Your “non-negotiables” checklist (speed, security, resilience)
These are the three pillars I always anchor to.
1) Speed that stays fast
Speed is not a one-off project, it is a condition you maintain.
Keep an eye on:
- Image handling: modern formats (WebP/AVIF), correct sizing, lazy loading where appropriate.
- Script creep: chat widgets, tracking pixels, sliders, animation libraries.
- Mobile performance: your site does not “have” mobile users, it is built primarily for them.
Practical target: a homepage that loads quickly on 4G, not just on office Wi-Fi.
2) Security that is layered, not hopeful
Security is not only SSL. SSL is essential, but it is just one part of the picture.
A sensible baseline includes:
- Strong logins (unique passwords, MFA where possible)
- Regular updates (core, plugins, themes, apps)
- WAF or equivalent protection
- Backups that are tested, not just “enabled”
- Least privilege access (only the people who need admin access should have it)
3) Resilience that prevents panic
Resilience is your ability to take a hit and keep operating.
Key questions:
- If your site goes down, who gets alerted and how quickly?
- How fast can you restore a clean version?
- Are you relying on one person who “knows the passwords”?
If you cannot answer those confidently, you do not have resilience yet, you have hope.
Page 3: The “change log” rule (how to stop breaking your own website)
One of the simplest improvements I have seen is keeping a change log. It can be a Google Doc.
Every time anything changes, note:
- What changed (plugin update, app installed, copy edited, theme tweak)
- Who did it
- When it happened
- Why it happened
- What was tested afterwards
This is not bureaucracy. It is how you avoid the classic situation where something breaks and nobody knows what triggered it.
If you want a quick template, get in touch and I will share the one we use: /#contact
Page 4: A realistic testing routine (you do not need to test everything, just the right things)
Before and after any change, test the “money paths”. These vary by business, but typically include:
For lead generation sites
- Contact form submits successfully and emails arrive
- Phone number tap-to-call works on mobile
- Location pages are accurate and indexable
- Enquiry confirmation message is clear and reassuring
For booking-based businesses
- Availability loads quickly
- Booking flow completes without confusion
- Confirmation email and reminders send correctly
- Cancellation or rescheduling works as expected
For ecommerce (Shopify or WooCommerce)
- Add to basket
- Apply discount code (if you use them)
- Checkout completes (card, Apple Pay, PayPal as applicable)
- Order confirmation and fulfilment emails send
- Key pages are not blocked by cookie banners or pop-ups
Testing is not glamorous, but it is where revenue is protected.
Page 5: The SEO section most websites are missing (search intent mapping)
Many businesses do “SEO” by adding a few keywords and hoping. A better approach is to map your pages to search intent, meaning what the person is actually trying to do.
A clean intent map often includes:
- Do: “book”, “buy”, “price”, “availability”, “near me”
- Know: guides, FAQs, comparisons, “how long does… take”
- Trust: reviews, case studies, accreditations, guarantees, returns
- Local proof: service areas, directions, local projects, local delivery or coverage
When you map intent properly, you reduce thin pages and stop competing with yourself in Google.
Page 6: Content governance (how to keep your site consistent when multiple people edit it)
If your site has grown over time, you may already have:
- multiple versions of the same message
- conflicting prices or service descriptions
- outdated FAQs
- broken internal links
A simple governance plan solves this:
- Decide who owns each section of the site (services, blog, products, policies)
- Create a short style guide (tone, spelling, headings, calls to action)
- Set review dates for high-impact pages (every 3 to 6 months)
Consistency is not only about branding. It is about trust, accessibility, and conversions.
Page 7: Hosting as a business decision, not a technical one
Hosting is often treated like a commodity, but it is tied to:
- uptime (lost leads and sales when you are down)
- performance (speed affects rankings and conversions)
- support quality (how quickly issues get resolved)
- security posture (patching, monitoring, isolation, backups)
Good hosting reduces the number of emergencies you experience. That is the real return.
A 30-day “operating manual” starter plan (lightweight, but effective)
If you want to turn this into action without making it a full-time job, here is a sensible first month:
Week 1: Baseline
- Write the website job statement
- Record current performance metrics (mobile speed, key conversions)
- List integrations (forms, booking, email marketing, payments)
Week 2: Secure and back up
- Confirm SSL, updates and access levels
- Check backups and perform a test restore plan (even a partial test is better than none)
Week 3: Money-path testing
- Document the 3 to 5 most important user journeys
- Test them on mobile and desktop
- Fix anything that blocks completion
Week 4: SEO and content tidy
- Map key pages to intent
- Remove or merge duplicate pages
- Update titles, internal links and calls to action where needed
At the end of 30 days, you have the foundation of an operating manual and far fewer unknowns.
If you want help turning your site into a “known system”
At Connect Dorset, I focus on making websites dependable: hosting that holds up under pressure, designs that convert, platforms that are maintainable, and SEO work that matches real customer behaviour.
If you want me to take a look at your current setup or help you build a simple operating manual for your site, you can reach me here: /#contact