Blog Menu G
Search
Categories
m
m
Archives
Tags
m
m
m
4gh blog post pic.webp
If your business is in Edmonton, the electricity running your office, your shop floor and, if your website is hosted locally, your web server comes from one of the more carbon-intensive grids in Canada. That is not a knock on Alberta. The province has cut the emissions intensity of its electricity sharply over the past two decades and finished moving off coal in June 2024, years ahead of its own 2030 deadline. But the grid that remains runs mostly on...
a3c1663c fef7 466e ab19 a6e755387db8 768x432

When this article first appeared on the 4GoodHosting blog in December 2015, the pool of unallocated IPv4 addresses for North America had run dry only three months earlier. IPv6 was described, here and almost everywhere else, as "the future of internet addressing." That framing has aged. IPv6 is no longer a future event that website owners need to wait for. It is the protocol that roughly half of the people reaching Google now arrive on, and it is already carrying traffic to and from a large share of websites whether their owners have noticed or not. Meanwhile, IPv4 has become something it never used to... Read More

chatgpt 28 768x432.webp

There’s a reason why bucket seats are the default choice for any performance roadster where the driver is going to be sitting low and driving stick shift with plenty of ponies under the hood. There... Read More

chatgpt image sep 22 2026 12 58 45 am 768x432

Most advice on this subject promises that making your website better on phones will push it up Google's rankings. That is partly true and mostly beside the point. Google's own documentation is unusually direct about... Read More

There is a particular kind of frustration that hits a business owner about three months after a landing page goes live. The... Read More
"Managed hosting" sounds like a simple product: you pay more, and someone else looks after your server. In practice it is one... Read More
It’s common knowledge that having good and regular blog content on your website is seen favourably by search engine algorithms, but what’s... Read More
A massage clinic on 124 Street loses a booking at 7:12 on a Tuesday evening. The client picked a therapist, picked a... Read More
Every hosting company sells uptime, and almost every hosting company sells it with a number: 99.9%, 99.99%, occasionally five nines. The number... Read More
There is a piece of email marketing advice that appears in almost every list-building guide on the internet, and in Canada it... Read More
chatgpt image sep 10 2026 11 37 41 pm 768x432
reading time Reading Time: 56 minutes

Not deprecating it. Not reducing its features. Removing it. Google emailed users to say Assistant is being discontinued on compatible Android phones and tablets, with Wear OS devices, headphones, and Android Auto following. The rollout runs over several weeks, and once a device switches, there is no going back. Gemini becomes the assistant experience on Android. Assistant launched in 2016; ten years later, the product that most "voice search optimization" advice was written about is being decommissioned while that advice sits unrevised on hundreds of agency blogs. This matters more than a product retirement usually would, because Google Assistant was not incidental to voice search SEO. It was the mechanism. The specific technical recommendations that circulated for the better part of a decade — mark up your content with speakable structured data, add FAQPage schema to win the spoken answer, optimise for the featured snippet Assistant reads aloud — were all recommendations about how one product retrieved and read one answer. Two of those three recommendations no longer apply to anyone. The third applies to a product that is being turned off. So this is a reasonable moment to rebuild the topic from the ground up. What follows is not a refresh of the standard voice search checklist. It is an attempt to establish what is actually true about spoken and conversational search in 2026, what a Canadian business can genuinely act on, what cannot be measured, and where the real constraints sit. Some of those constraints turn out to be in your hosting infrastructure rather than your content, which is not where most of this conversation usually goes. A warning about the rest of this article: it will contradict a great deal of what you have read on this subject. Where it does, the reasoning and the source are given so you can check. What "voice search" actually means in 2026 The phrase has always been sloppy, and the sloppiness is the root of most bad advice about it. Three genuinely different things get bundled under one label, and they behave differently enough that treating them as one topic guarantees you optimise for the wrong one. Path one: voice...

You may find this interesting too.
chatgpt 31 1 768x432.webp

There is a particular kind of conversation that happens when a small business gets breached. Somebody asks where the firewall was. And the honest answer, increasingly, is that there wasn't one, because there was nothing left for it to sit in front of. The business runs on a website it doesn't host, email it doesn't run, a payment processor it doesn't operate, and a laptop that connects to all of them from a kitchen table. There is no network edge. There is no inside. The thing everybody spent twenty years learning to defend simply isn't there any more. That is the shape of the problem, and it is why the security industry keeps announcing that the perimeter is dead. But the perimeter is not dead. It moved, it fragmented, and it multiplied. For a business whose most exposed asset is a public website, the new perimeter is small enough to write on a single page — which is precisely what makes it defensible, and precisely why so few businesses have done it. This guide is about drawing that page. Not a zero trust architecture programme. Not a reference model written for an organisation with a security team. An actual inventory of the things that, if someone else controlled them, would end your ability to operate — and what to do about each one. What the ‘perimeter’ used to mean, and what actually changed The traditional model was physical before it was digital. Your computers sat in your building. They talked to each other over cable you owned. Anything from outside had to pass through one controlled point, and you put your defences at that point. Castle and moat, as the metaphor goes, though the more accurate comparison is a factory with one gate and a security desk. It worked because two assumptions held. The first was that everything valuable sat inside a boundary you could draw. The second was that traffic crossing that boundary was rare enough and slow enough to inspect. Both assumptions have now failed, and they failed for ordinary commercial reasons rather than security ones. The three shifts that dissolved the boundary Software moved off your premises....

You may find this interesting too.
chatgpt 28 768x432.webp
reading time Reading Time: 50 minutes

Two things are worth establishing before any discussion of how to scrape a website. The first is legal, and it is the reason most guidance on this subject is unsafe reading for a Canadian business. Almost every web scraping article, tutorial and vendor page assumes American law. In the United States, fair use is an open-ended standard that courts apply case by case, and several recent decisions have gone in favour of large-scale data collection. Canada has no equivalent. Fair dealing under the Copyright Act is a closed list of specific purposes, and Canada has no text and data mining exception at all. The federal government has consulted on introducing one; it has not done so. A Canadian business scraping copyrighted material for a commercial purpose that does not fall within the enumerated categories is on considerably weaker ground than an American business doing the same thing, and no amount of "web scraping is legal" content written in California changes that. The second is about the word "better." A large part of the scraping industry defines better as harder to detect: rotate through residential IP addresses, spoof browser fingerprints, defeat the CAPTCHA, make your bot indistinguishable from a person. That is the business model of several of the tools you will find recommended, and this article does not cover it. Not out of squeamishness, but because it is a bad engineering strategy as well as a legally exposed one. It produces systems that are expensive, fragile, permanently one step from breaking, and dependent on infrastructure of dubious provenance. The better ways are duller and they work. Check whether the data is already available in a form you are welcome to take. Read the terms before you write the code. Identify yourself honestly. Make fewer requests. Cache what you already have. Fail gracefully. Store less than you could. These practices are more reliable, cheaper to maintain, and far less likely to end in a letter from someone's lawyer. This guide covers both, because for most readers here both apply. The first half is about collecting data from other people's sites. The second half is about the other side of the same...

You may find this interesting too.
chatgpt 22 768x432.webp
reading time Reading Time: 55 minutes

Black Friday falls on Friday 27 November this year, with Small Business Saturday on the 28th and Cyber Monday on the 30th. The six weeks that decide how that weekend goes for your website begin on 12 October — which, conveniently or otherwise, is Thanksgiving Monday. Realistically you start on the Tuesday. Most Black Friday advice for small businesses is about the offer. What to discount, when to email, how to segment the list, how to write a subject line that gets opened. That advice is useful and it is also everywhere. What gets far less attention is the thing all of it depends on. A promotion that works is, by definition, a promotion that sends more people to your website in a shorter window than at any other point in the year. The website is the part almost nobody stress-tests until it fails. And it usually does not fail in the way people expect. Sites rarely fall over on Black Friday. They get slow. Product pages still load, but the cart takes eleven seconds. Checkout times out on the third attempt and the customer gives up. Order confirmation emails arrive an hour late, so support spends the afternoon fielding "did my order go through" messages. Nothing registers as an outage, so your uptime monitor stays green and you never learn what it cost. You just have a disappointing weekend and no explanation for it. What follows is how to prepare your website for Black Friday, as distinct from how to prepare the promotion. This guide covers the other half of the job. Black Friday website preparation, in the sense that matters here, is the infrastructure and performance work that has to be finished before the marketing calendar takes over. Each of the six weeks below has one task, and the order matters, because the later weeks assume the earlier ones are done. Why this is the half that gets skipped Partly because it is less fun than designing a promotion, and partly because the consequences are invisible until they are not. But mostly because the numbers everyone quotes are the wrong numbers. The Canadian picture from last year is...

You may find this interesting too.
4gh blog post pic.webp

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...

You may find this interesting too.
chatgpt 27 1 768x432.webp

A proxy server is a computer that makes requests on behalf of something else. That is the whole idea, and everything else is detail. The reason proxies confuse people is not that the concept is difficult. It is that one word has been stretched to cover several genuinely different technologies that happen to share that one behaviour. The software filtering web traffic on an office network, the service sitting in front of a busy website distributing traffic across servers, the thing someone buys to scrape product prices, and the layer terminating encryption at the edge of a content network are all called proxies. They do not do similar jobs. Most explanations of proxy servers make this worse rather than better. They list types without explaining what distinguishes them, they repeat the claim that a proxy encrypts your traffic (which is usually false), and they treat proxies and VPNs as near-synonyms (which they are not). By the end you know more words and no more mechanics. This guide takes the opposite approach. It explains what a proxy actually does at the level of the request, distinguishes the two fundamental directions a proxy can face, works through the types properly, is specific about what happens to encrypted traffic, and is honest about what proxies can and cannot protect. It also covers the parts that matter for a Canadian business in particular, including where a proxy sits relative to your data and what that means for the privacy commitments you may have made to your clients. The definition, and the request path A proxy server is an intermediary that receives a network request, forwards it to its destination on the requester's behalf, receives the response, and passes that response back. The two endpoints communicate through it rather than directly with each other. Walk through what happens without one first. You type an address into your browser. Your device resolves the hostname to an IP address, opens a connection to that address, sends an HTTP request, and receives a response. The web server sees your IP address, because your device is the thing talking to it. Now insert a proxy. Your browser is configured...

You may find this interesting too.
chatgpt 23 768x432.webp
reading time Reading Time: 35 minutes

If you have spent an evening comparing website builders, you have probably noticed that almost everything written about them is published by a company that sells one. That does not make the advice wrong. It does mean one question rarely gets a straight answer: what happens to your website if you decide to leave? This article covers what a website builder is and how one actually works, which is the easy part. It also covers the parts that get skipped — what you own at the end of it, what a builder does to your search visibility, where your site physically lives, and the specific circumstances in which a builder is the wrong tool. Some of those answers argue against using one. What is a website builder? A website builder is software that lets you create and publish a website through a visual editor, instead of writing the code yourself. You start from a template, add your own text and images, arrange the layout by pointing and clicking, and publish. The builder generates the underlying HTML, CSS and JavaScript on your behalf. That is the whole concept. Everything else — templates, drag-and-drop, AI page generation, built-in stores — is a variation on it. It helps to be precise about what a builder replaces, because the term gets used loosely. A website builder replaces the act of writing front-end code. It does not replace design judgement, copywriting, product photography, or the decision about what your website is for. Those remain yours, and they are the parts that determine whether the site works. One more distinction worth making early, because it causes real confusion later: a website builder is a tool for making a site. Hosting is the service that keeps the site available on the internet. Some builders bundle the two so tightly that they look like one product. Others keep them separate. That difference turns out to matter a great deal, and it is the subject of the next two sections. How does a website builder work? A drag-and-drop website builder sits between you and the code, and it works in four stages. 1. The template establishes the structure You...

You may find this interesting too.
chatgpt 20 768x432.webp
reading time Reading Time: 6 minutes

You’re freer to be a little more indifferent to how your website is performing if you have one for more hobby or avocational purposes. It’s entirely different if you’ve got an eCommerce site and the generating revenue is dependent on that site. It will be where new customers discover you as a retailer or service provider online, and the purchases that you need them to be making will be done there. Every website is going to be nowhere to be found without web hosting, and not all hosting is equal. More often than not these eCommerce business managers will be looking to get the best Linux web hosting. This is because it’s the most ideal fit for the majority of websites, and really the only exceptions to that will be for WordPress websites or ones that are built with Windows architecture. Most sites have a framework that works best with Linux, and so that tends to the best web hosting OS to have propping up you site on the World Wide Web. Ensuring it’s there to be visited anytime and from anywhere, and also for as many visitors as possible at any time. There’s more that goes into having a website handle traffic spikes, but being on the right web host OS is a significant determining factor. With dedicated Linux hosting you’re going be even more defended against any type of site slowdowns or anything else that might lead potential customers to leave and never return. This type of web hosting comes with a higher price, but for many businesses it quickly becomes money well spent as part of their operating budget. The same will apply for managed WordPress hosting is you’re a smaller online business and you are getting by just fine with a WordPress website. You definitely get real value from these options if your website is central to the profitability of your business. So what we’ll do with this week’s entry is look at Linux hosting for eCommerce and go over the most primary feature and advantages that continue to lead people to see that this is the type of web hosting they need to be behind...

You may find this interesting too.
canadian cybersecurity data vault 768x432

Most server security guides are checklists, and checklists have a flaw that rarely gets mentioned. They record what you meant to do, not what is true on the machine today. A firewall rule added in March gets loosened during a late-night troubleshooting session in June and never tightened again. The automatic update job stops running after a package conflict, and nobody notices because nothing visibly breaks. A backup schedule runs faithfully for two years and has never once been restored. Every one of those servers would pass a checklist review. Every one of them is less secure than its owner believes. This guide asks a different question. Not "have you done the seven things?" but "could you prove, this afternoon, that each of them is still working?" That is what reliably secure means in practice: security you can verify on demand, rather than security you remember setting up. It's also the most useful answer to the question of how to secure a server for the long term. It's written for Canadian small and mid-sized businesses running websites, online stores, client portals and internal applications on rented infrastructure, whether that's a shared hosting account, a virtual private server or a dedicated machine. Each step covers what to do, why it matters, and the specific check that tells you it's working. It also covers two things generic guides tend to skip: who is actually responsible for each layer under different hosting arrangements, and what Canadian privacy law expects of you when something goes wrong. This piece stays at the level of the server itself. For the wider picture, including identity, third-party scripts and edge controls, see our guide to the broader security strategy for Canadian businesses. What a secure server actually is Any explanation of how to secure a server should start with what the goal looks like. A secure server is one where only the people and processes that need access have it, known weaknesses are closed within a defined time, data is protected in transit and at rest, abnormal activity gets noticed, and the business can return to a known-good state after a failure or compromise. Notice what that definition...

You may find this interesting too.
chatgpt image sep 7 2026 09 27 09 pm 768x432.webp

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...

You may find this interesting too.
On This Page G
Explore 4GOODHOSTING
Copyright © 2026 4GoodHosting. All Rights Reserved.
.CA by CIRA
+1 866 708 4678