I received an email the other day from a customer that’s been us nearly 15 years.
About a year or so ago, we served this customer by upgrading their website design and hosting as well as implementing SEO retainer services.
Most recently, in an effort to speed up and optimize website performance, we implemented the use of Cloudflare for the customer’s website hosted via Bluehost.
If you haven’t heard of or not using Cloudflare, then you are missing out on realizing greater website performance and increased boost search rankings.
The reason I mention Cloudflare is because this is where my mind immediately was drawn to when receiving the customer’s email about not being able to successfully File Transfer Protocol (FTP) to the web server. Continue reading
All was working well until I encountered a pesky 400 Bad Request error as I attempted to access GoDaddy’s Hosting Manager using Chrome.
It’s the top of another fast moving day. To get this day started off, I discovered an opportunity to save money on your next emoji domain purchase.
So, if you so desire to own a .TO emoji domain, then today’s offer could be just the opportunity to secure a single or combo emoji domain. Continue reading
Back to life and back to… wait for it… a blank WordPress website. 😱
That’s not how this song is suppose to go, per Soul II Soul. It’s suppose to be back to life, back to reality.
Nevertheless, this unfortunate, stark reality of a potential customer stating their website loaded a blank white screen came by way of a frantic call a few days ago.
What in the world could and would cause a WordPress website to load with HTTP 200 response, yet load a white screen?
Although there are many things that could cause a WordPress website white or blank screen to be loaded, I’m sharing with you the top 6 items to check. Continue reading
A few days ago, a customer contacted me about performing some WordPress work in regards to redirecting two additional WordPress websites to their primary website.
To perform the work and lessen the manual labor of redirecting all links by hand, I wrote a few lines of code in a .htaccess file.
I setup a quick test environment to ensure the .htaccess file was executing as it should. And it worked like a charm, redirecting all previous blog posts to their respective new url.
What should have been a routine change, rather an addition of code to the .htaccess file, turned out to be a wild goose chase to locate the .htaccess file. Continue reading
I received an email yesterday afternoon from GoDaddy that reminded me I have two websites that I’ve not transitioned to HTTPS.
In the last few years, there has been an uptick in the number of websites that have transitioned from HTTP to strictly HTTPS.
Of course, many website owners transitioned their websites to HTTPS from HTTP upon hearing Google would consider and likely bump website search rankings for those in full HTTPS compliance.
Nevertheless, the interesting thing about the GoDaddy email is that it is stoked with a bit of subliminal fear using a number of terms throughout the email multiple times. Continue reading