Day: September 21, 2026

September 21, 2026

4GoodHosting, Linux Web Hosting, WordPress Hosting, WordPress hosting support

Reading Time: 7 minutes

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 are plenty of other motor vehicle seating options but bucket seats are the ideal mix of comfort and positioning as it relates to driving those types of cars. Web hosting needs to be speedy too if landing pages are to load quickly, and for fast web ho0sting in Canada it’s best to have something along the lines of what we offer here with the different types of web hosting here at 4GoodHosting. Linux website hosting in Canada is the default choice for most of us as a web hosting OS. The fit has everything to do with website architecture, and most sites that are serving as the online storefront for an eCommerce business are going to have Linux bones, as the saying goes. Windows architecture or a WordPress website may be a different story, and our managed WordPress hosting is especially popular with small business owners who have this kind of website for themselves. This isn’t a situation where the difference between iOS and Android comes down to personal preference for the most part, as what makes Linux the most popular choice for web servers is the fact that most websites function best with it being behind them. We know that most of our customers know next to nothing about how web hosting works, but they may know a few things about web hosting and designers. Especially if they enjoy putting together the site themselves, and making the decisions about layout and images. This may include people who got their start with doing this stuff by using our website builder, but most people who are proactive in their web design needs will have already been plenty proficient with designing and updating a website. These folks will be best served having their site on Linux servers too. So what we’ll do with this week’s blog entry here is look at why Linux is the standard choice as web hosting OS. Much of what we’ll say will...

September 21, 2026

Domain Related, Hosting Related, SEO Related

Reading Time: 29 minutes

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 it. Its ranking systems use Core Web Vitals, the three metrics for loading, responsiveness and visual stability. Other aspects of page experience, such as mobile layout or avoiding pop-ups, do not directly help a page rank higher, although they make a site more satisfying to use, which is aligned with what those systems reward. Google also says it will always show the most relevant result even when its page experience is poor. So if your page is the best answer to a search, a clunky mobile layout probably will not stop it ranking. And if it is not the best answer, a polished mobile layout will not rescue it. What mobile user experience does decide, very directly, is what happens after the click. It decides whether a visitor on a phone finds your phone number, finishes your quote form, books the appointment or completes the checkout. For most Canadian small businesses, that is where the money is. A page that ranks third and converts well on phones will usually earn more than a page that ranks first and loses half its mobile visitors at the form. This guide is about those fixes: the ones that are easiest to make and pay back fastest. Where a fix also affects rankings, it says so, and says how much. Indexing and the Core Web Vitals metrics themselves are covered in depth elsewhere on this blog, so they get a summary here and a link, not a repeat. What Google actually rewards on mobile, and what it doesn't It is worth being precise, because a lot of wasted effort comes from getting this wrong. Google indexes and ranks the mobile version of your pages. That process, mobile-first indexing, is complete across the web, and its practical requirements are content parity between mobile and desktop, crawlable resources and consistent structured data. If you need that side of things, our mobile-first indexing guide covers it fully. On ranking, Google's current page...

September 21, 2026

4GoodHosting, Domain Related, Hosting Related, SEO Related

Reading Time: 29 minutes

There is a particular kind of frustration that hits a business owner about three months after a landing page goes live. The page converts well. The paid traffic is working. Somebody suggests "we should get organic traffic to this too," and a check in Search Console returns one of two answers: the URL is not in the index at all, or it sits in a state called Crawled – currently not indexed, which reads like a technicality and is actually a verdict. The page was not unlucky. It was built that way. Almost everything that makes a landing page convert well makes it hard to index. Stripping the navigation removes distraction — and severs the page from the site's link graph. Keeping copy tight respects the visitor's attention — and produces a page with nothing to rank for. Running three headline variants improves conversion rate — and creates three near-identical URLs. Building the page in a dedicated tool ships it in an afternoon — and frequently publishes it on somebody else's domain. None of those are mistakes in isolation. Each is a deliberate, defensible conversion decision. Taken together they produce a page that no search engine has any reason to index, and the sixteen articles you will find on this topic mostly do not mention it, because they are describing a page that ranks and quietly assuming it is the same page that converts. This article is about the conflict. What actually stops landing pages indexing, which of those causes you can fix without hurting conversion, which require you to accept a genuine trade, and where the page should physically live — because that last decision turns out to govern more of the outcome than any on-page factor. It is written for Canadian businesses running lead-generation or product landing pages, and for the people who build them. One note on sources: Google's own SEO Starter Guide is the correct starting point for general on-page work and this article does not attempt to restate it. What that guide does not cover is landing pages specifically — the structural tension described above — which is the gap this piece occupies. The two...

September 21, 2026

Domain Related

Reading Time: 44 minutes

When this article first appeared on the 4GoodHosting blog at the end of 2019, it offered six quick tips: keep menus slim, use descriptive labels, be careful with dropdowns, put important items first and last, include search, and link to your blog. Most of that advice was reasonable for its time. Some of it was never quite right, and all of it treated navigation as a question of menu design. That is too narrow for a modern online store. Navigation on an e-commerce site does three jobs at once, for three very different audiences. It helps shoppers find the product they came for, or discover one they did not know they wanted. It tells search engines which pages matter and how they relate to each other, which shapes what gets crawled, indexed and ranked. And every link, filter and search box it exposes becomes a request your server has to answer, whether it comes from a customer, Googlebot or a scraper working through every filter combination you offer. A store whose navigation serves only one of those audiences will struggle. A beautiful mega menu that search engines cannot follow leaves products undiscovered. Filters that generate millions of crawlable URLs can bury your real product pages and load your server with traffic that never buys anything. A technically perfect structure that uses labels nobody searches for will not sell. This guide rebuilds the topic around all three jobs. It covers how to design a category structure, menus, filters, search and breadcrumbs that customers can use; how to make that structure clear to Google; and how to keep it from quietly overloading your hosting. The short version If you only have five minutes, these are the points that matter most. Design the category structure before the menu. The menu is only a view of your taxonomy. If the taxonomy uses the wrong words or the wrong groupings, no menu design will fix it. Use real links. Google finds products by following <a href> links from menus to categories to products. Navigation built from JavaScript click handlers, or products reachable only through search, may never be found. Treat filters as your biggest SEO...

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