Category: Web Hosting

September 21, 2026

4GoodHosting, Domain Related, Hosting Related, Web Hosting

Reading Time: 24 minutes

"Managed hosting" sounds like a simple product: you pay more, and someone else looks after your server. In practice it is one of the least consistently defined terms in the hosting industry. One provider's managed plan means it patches the operating system and nothing else. Another's means it updates your WordPress plugins, tests your backups and rescues you at 2 a.m. when a checkout breaks. Both use the same word. That is why most "pros and cons" lists are less useful than they look. They compare an idealised managed service with an idealised do-it-yourself server, and conclude that managed is easier but more expensive. That is true, and it does not help you decide. The better question is who does which job. Every website sits on a stack of layers: hardware, network, operating system, web server, PHP, database, control panel, application and content. Someone has to keep each layer secure, updated and working. Managed hosting moves some of those jobs to your provider. Which jobs move, and which stay with you, determines whether managed hosting is a bargain or an expensive misunderstanding. There is a timely example. PHP 8.2, still common on business websites, reaches the end of its security support on 31 December 2026, according to the PHP project. After that date it receives no further security fixes. On a fully managed plan, moving your site to a supported version is usually the provider's job, possibly with some testing on your side. On an unmanaged server, it is entirely yours, and if nobody does it, nobody does it. Multiply that by every component in the stack, and you have the real trade-off. This guide maps those responsibilities, then tests the pros and cons against them. It includes a cost comparison that counts your time, a Canadian angle most guides miss, and the questions to ask any provider before you sign. What "managed" actually means: a responsibility map The clearest way to understand managed hosting is to look at who is responsible for each layer under each type of hosting. The table below shows the typical pattern. Individual providers vary, which is exactly why you need to ask. Layer Shared...

September 13, 2026

4GoodHosting, Hosting Related, Web Hosting, WordPress, WordPress Hosting

Reading Time: 28 minutes

Every hosting company sells uptime, and almost every hosting company sells it with a number: 99.9%, 99.99%, occasionally five nines. The number is presented as the answer to a question, and it is worth being precise about what question it actually answers. It answers: how often did our server respond to a request? The question a business owner is actually asking is: how often was my website working? Those are not the same question, and the gap between them is where most real downtime lives. A WordPress site can return a clean HTTP 200 response with a white screen where the content should be. It can serve a homepage perfectly while the checkout throws a fatal error. It can load in two seconds for a visitor in Toronto and time out for a visitor in Halifax. It can look entirely healthy while the contact form has been silently failing to send for eleven days. Under every uptime SLA in the industry, all four of those sites were up. This article is about the difference. What actually takes WordPress sites offline — which is almost never a hardware failure — what a managed environment genuinely prevents, what it demonstrably cannot prevent no matter what the sales page says, and how to monitor your own site in a way that catches the failures the uptime number is blind to. It is written for Canadian business owners and the people who look after their sites: the ones who have been told managed WordPress hosting is more reliable, and want to know specifically what that buys and where the limits are. What an uptime SLA actually measures Start with the arithmetic, because most people have never done it. SLA figure Downtime allowed per month Per year 99.0% 7 hours 18 minutes 3 days 15 hours 99.5% 3 hours 39 minutes 1 day 19 hours 99.9% 43 minutes 8 hours 46 minutes 99.95% 21 minutes 54 seconds 4 hours 23 minutes 99.99% 4 minutes 19 seconds 52 minutes 36 seconds 99.999% 26 seconds 5 minutes 15 seconds Two things jump out. First, the difference between 99.9% and 99.99% is not a rounding detail — it...

September 9, 2026

4GoodHosting, Domain Related, Hosting Related, VPS Hosting, Web Hosting, WordPress, WordPress Hosting

Reading Time: 43 minutes

Most advice on building a retail brand is about how things look and feel. Colour palette, typography, store layout, shelf presence, packaging, the tone of the signage, the workshop where everybody agrees on three adjectives. It is a large and well-developed body of work, and for a physical shop it is largely correct — when the customer is standing in your space, the space is the brand. Then the customer is not standing in your space. They are on a phone, on a bus, at 9:40 on a Tuesday night, with your site half-loaded and a payment method you do not accept. Nothing about your colour palette is relevant to what happens next. This article is about that second situation, which is now where most of a retail brand's damage occurs. Not because design does not matter — it does — but because design is the part everyone already works on, and the failures that actually destroy trust are almost entirely invisible to the business until a customer tells them, or does not. Written for Canadian retail businesses running a website alongside, or instead of, a physical location. It covers what breaks, in rough order of how badly it damages you, and what the infrastructure underneath has to do to stop it. What ‘brand’ becomes once the store is a website The useful starting point is to be precise about what transfers from physical retail and what does not, because a great deal of retail branding advice is written as though the online version is the same exercise on a smaller screen. It is not, for one structural reason. In a shop, staff absorb the failures. Online, nothing does When something goes wrong in a physical store — an item is out of stock, the card terminal is slow, the queue is long, the price on the shelf does not match the till — a person intervenes. They apologise, they check the back, they offer an alternative, they honour the shelf price. The failure still happened, but it was absorbed, and the customer's memory of it is mediated by someone who was visibly trying. Online there is no one on...

September 6, 2026

4GoodHosting, Dedicated Hosting, SEO Related, Web Hosting

Reading Time: 32 minutes

A plumbing website has one job, and it is narrower than most web design advice assumes. It is not to showcase your brand or to explain your history. It is to make the phone ring when someone with water on their floor searches for help, and to make you the obvious choice when someone with a planned renovation is comparing three companies. Those are two different visitors with two different urgencies, and a site that serves one badly serves both badly. The emergency caller needs your number and your service area in under five seconds on a phone, possibly at two in the morning, possibly on a weak connection in a basement. The planned-work customer needs evidence you are licensed, insured, competent and reachable, and will read considerably more before deciding. This guide covers all three parts of getting that right: the design decisions, the local search work, and the hosting underneath it. We are a Canadian web hosting provider, so the hosting section is the part we handle daily, and we have tried to be specific about which hosting factors genuinely matter for a trades business and which are marketing. It is written for the plumbing business owner who is either building a first website, replacing one that generates nothing, or trying to work out why competitors appear above them in local results. Where something requires a specialist, it says so rather than pretending otherwise. Start here: your two customers behave completely differently Almost every mistake in plumbing website design comes from designing for one visitor and forgetting the other. Getting this distinction clear first makes the rest of the decisions obvious. Emergency customer Planned-work customer Situation Burst pipe, blocked drain, no hot water, flooding Bathroom renovation, fixture replacement, new build, inspection Search behaviour “emergency plumber near me”, “plumber open now”, often on a phone “bathroom plumbing cost”, “plumber [city] reviews”, often on desktop, over days Time on site Seconds. They want a phone number Minutes across several visits. They are comparing What convinces them You answer, you cover their area, you can come now Licensing, insurance, reviews, photos of real work, clear pricing approach What loses them A...

September 4, 2026

4GoodHosting, Domain Related, Hosting Related, Linux VPS Hosting, VPS Hosting, Web Hosting

Reading Time: 55 minutes

Canadian VPS hosting occupies an awkward middle ground. It costs several times what shared hosting does, it asks more of you technically, and the sales pages describing it are written almost entirely in specifications that mean nothing until you know which of them constrains your site. So this guide is organised around the decision rather than the product. The first question is whether you need a VPS at all, because a large share of businesses who buy one did not need to and a smaller share needed one two years before they bought. The second is managed or unmanaged, which is the choice people most often get wrong and the one with the largest hidden cost. Only then do specifications matter. It also covers what a VPS genuinely fixes and what it cannot touch, since the most common disappointment with a VPS upgrade is a site that is still slow afterwards. That outcome is predictable in advance, and predicting it correctly saves the money. The Canadian dimension is real but narrower than most hosting marketing suggests: latency for Canadian visitors and data residency are genuine considerations, and a Canadian IP address is not a search ranking advantage. Both are covered honestly below. What a VPS actually is A virtual private server is a partition of a physical machine with resources allocated to you specifically. You get a defined amount of CPU, memory and storage, your own operating system instance, and root or administrative access. Other customers share the same hardware, but not your allocation. That last distinction is the whole product. On shared hosting, your site's performance depends partly on what other accounts on the machine are doing, because CPU and memory are pooled. On a VPS, your allocation is yours whether the neighbours are busy or idle. You are buying predictability rather than raw speed. Type Resource model What you manage Typical fit Shared Pooled across many accounts Nothing below the control panel Brochure sites, low-traffic blogs, early-stage businesses VPS Allocated to you, on shared hardware Depends on managed or unmanaged Growing sites, ecommerce, uneven traffic, custom software needs Dedicated An entire physical machine Full stack, or the provider's...

September 3, 2026

4GoodHosting, Domain Related, SEO Related, Web Hosting

Reading Time: 30 minutes

Most guides to Google mobile-first indexing are written as though it were coming. They tell you to prepare, to audit, to make the transition. That framing is several years out of date: Google announced the completion of the mobile-first indexing migration in October 2023, in a Search Central post titled “Mobile-first indexing has landed”. There is nothing left to prepare for. Google crawls and indexes the web with its smartphone crawler, and the mobile version of your pages is the version that determines what gets indexed and how it ranks. That is simply the current state of Search, not an upcoming change. Which changes the useful question. It is no longer “is my site mobile-friendly?”, and Google reinforced that by retiring the tool that answered it. It is now something more specific and more consequential: does the mobile version of your page contain everything Google needs to index, and can a person on a mid-range phone on mobile data actually use it? Those are different questions with different answers, and most sites that pass the first fail the second. This guide covers what mobile-first indexing actually means, the widely repeated misconceptions about it, the tools Google has retired and what to use instead, and the failure mode that causes real ranking damage. Mobile SEO in 2026 is largely about content parity, and almost nothing about a binary friendliness verdict. What mobile-first indexing actually means Mobile-first indexing means Google uses the mobile version of your content for indexing and ranking. Googlebot crawls as a smartphone user agent, renders the page as a mobile browser would, and indexes what it finds there. The single practical consequence, from which nearly everything else follows: if content exists on your desktop layout but not on your mobile layout, Google may not see it at all. Not rank it lower. Not see it. A page whose mobile version hides half its content is, from Google's perspective, a page with half that content. Three misconceptions worth clearing up “There is a separate mobile index.” There is not. There is one index, built from the mobile version of pages. Your desktop rankings are determined by what Google found...

September 2, 2026

4GoodHosting, Hosting Related, SEO Related, Web Hosting

Reading Time: 37 minutes

Product page SEO is where most ecommerce search strategies quietly fail. Homepages get the design attention, category pages get the keyword research, blog posts get the content budget, and product pages, the only pages where someone actually buys something, inherit whatever the platform generates by default. That is an odd allocation, because product pages have a property no other page type shares: they attract traffic that has already decided to buy and is now deciding where. A visitor searching “waterproof hiking boots size 10” is further down the funnel than one searching “how to choose hiking boots”. Product pages catch the second query badly and the first query brilliantly, if they are built for it. This guide covers 21 things worth doing, organised in the order a real project should tackle them: foundation first, then on-page content, then images, then technical implementation, then performance and AI search. Each tip explains the mechanism rather than just the instruction, because in ecommerce product page SEO the instruction without the mechanism is what produces sites where every recommendation has been followed and nothing ranks. Two framing notes. First, you almost certainly should not optimise every product page, and a large part of product page optimization is deciding which pages deserve the work at all. Second, several widely repeated pieces of advice on SEO for product pages are now wrong, including some that appear in guides published this year. Those are flagged as they arise. Why product pages are the hardest pages to optimise Product pages fail in ways that other pages do not, and understanding the failure modes explains most of the tips that follow. They are generated at scale. A category page is hand-built; product pages are produced by a template filled from a database. Whatever is wrong with the template is wrong on ten thousand URLs simultaneously, which is why product page problems are almost always systemic rather than individual. They start as duplicate content. Most product pages launch with the manufacturer's description, which means the same paragraphs exist on every retailer selling that item. Google has no reason to index the fiftieth copy of a description it already has, which...

September 1, 2026

4GoodHosting, Hosting Related, Linux Web Hosting, Security, Security Related, VPS Hosting, Web Hosting

Reading Time: 36 minutes

Most hosting comparisons answer the wrong question. They line up two products, declare that one is cheap and one is powerful, and leave you to guess which description fits your site. The guessing is where the money gets wasted — either on a plan too small to hold your traffic, or on a server that costs five times more than you need and requires skills nobody on your team has. The useful question isn't which product is better. It's this: what is your site actually asking for right now, and what will it ask for in eighteen months? Answer that, and the choice between shared and VPS hosting stops being a judgment call and becomes an obvious one. This guide covers both sides honestly. It explains what shared hosting has genuinely become in the last few years, which is not what most articles still describe. It sets out the benefits of VPS hosting without pretending it's a free upgrade. It gives you the specific, measurable signals that tell you when you've outgrown a shared plan — not vague advice about "growing sites." And because your visitors, your customers, and in many cases your legal obligations are Canadian, it covers the part almost nobody writes about: where your data physically sits, and why that increasingly matters. Shared vs VPS hosting at a glance Before the detail, the short version. Shared hosting places many customer accounts on one physical server, each with a capped allocation of CPU, memory, processes, and disk I/O, all managed by the provider. You get a control panel and a website; you never touch the operating system. VPS hosting (Virtual Private Server) uses a hypervisor to divide one physical server into several independent virtual machines. Each one runs its own operating system, holds its own reserved slice of CPU and RAM, and can be configured down to the kernel by whoever holds root access. Shared hosting VPS web hosting Resource model Capped share of a pooled server Reserved allocation, guaranteed to you Operating system One OS shared by all accounts Your own OS instance Root access No Yes (on unmanaged and most managed plans) Who patches the server...

September 1, 2026

4GoodHosting, Hosting Related, VPS Hosting, Web Hosting

Reading Time: 26 minutes

Search for VPS hosting in Canada and you'll get a page of results that look nearly identical. Canadian flags, promises of low latency, a mention of strong privacy laws, a pricing table, a call to action. Read the fine print on those same pages and something else emerges. One is published by a company headquartered in California, billing in US dollars, with a currency disclaimer noting that exchange rates and bank fees will change what you actually pay. Another announced a Toronto location and then quietly froze it, a fact discoverable only in the blog comments where a staff member suggested New York or Chicago as alternatives. A third is a template with the country name swapped out — the same article exists on the same site as "VPS Hosting in Australia" and "VPS Hosting in India." None of that makes those companies bad hosts. It does mean "Canadian VPS hosting" is a claim rather than a specification, and the difference between the claim and the reality is where Canadian businesses get caught: a support queue that answers at 3 a.m. Eastern, an invoice that moves with the dollar, a data-residency question in a client questionnaire that suddenly has an awkward answer. This guide is about buying well. It assumes you've already worked out that you need a VPS rather than a shared plan. If you're still deciding that, our comparison of shared vs VPS hosting walks through the resource ceilings and upgrade triggers in detail. From here on, the question is narrower and more practical: among providers all claiming to offer Canadian VPS hosting, how do you tell which one actually does, and which one fits your business? VPS hosting, defined precisely A Virtual Private Server is one physical machine divided by a hypervisor into several independent virtual machines. Each one runs its own operating system, holds a reserved allocation of CPU cores, RAM, and disk, and is administered by whoever holds root access. Your instance is isolated from the other tenants on that hardware at the virtualisation layer. That's the whole concept. The reserved allocation is what distinguishes it from shared hosting, and the shared physical hardware is...