My first job in search engine optimisation was in 1997. So much has changed - SEO is more nuanced than ever before, with every character, every comma having an effect.
In addition to writing about SEO and speaking at various conferences, I enjoy actioning it myself too. There's nothing quite like sending a client a graph showing their organic traffic skyrocketing - without them having to increase their monthly spend.
The Spinoff are doing a special week dedicated to screens. It’s like Shark week but more digital. 🙂
They took me up on my offer to write an article about digital safety for kids. How much screen time is too much, how much it too little – etc.
In a previous life I worked in education and was involved in hours of discussion around digital safety for young people, different approaches, etc.
It’s great to be able to continue some of those conversations in this very different, Covid-19 era.
It can be hard to talk about, but we have to acknowledge that our children can be at risk when they’re spending time in digital spaces we’re not familiar with. Just as parents talk with their offspring and help them navigate difficult situations in the playground, we need to do the same with digital communication.
Peter Mahoney in the Spinoff
The pandemic really has changed everything with screen time. Kids expect (and need to) socialise – which leaves them doing that online in games we don’t play, interacting with people we don’t know.
Video calling has become totally the norm for hours at a time.
Just three years ago in 2019 a major survey in NZ found kids used screens around two hours a day. Current (last month’s) data puts that figure at just over five! And that’s not five total, that’s on top of what’s needed for schoolwork.
It’s a dangerous playground out there – but at the same time it’s best to teach kids how to navigate it all in the safest way we can provide.
Definitely don’t throw them to the digital wolves or keep them ‘locked in the house’.
Just like we help teach our children what to look out for in the physical world, how to interact in the physical world, and how to play their part in keeping them safe in it too – we can and should do the same thing in the digital world.
It happens. Your WordPress installation stops behaving as it should and just returns a white screen.
It can affect the whole site or just the Dashboard and login pages.
It’s not terrible to troubleshoot though, just try the following (in this order):
Rename your /wp-content/plugins folder to something else, like plugins1. In most cases the white screen is due to some plugin interacting poorly with your theme or another plugin. If doing this fixes the white screen issue, then you can change the folder name back and start to work out which plugin is being problematic.
Reinstall WordPress core from wordpress.org. This is the next most likely thing to fix your site. Just remember to not over-write your wp-config.php file under any circumstances, and leave the wp-content folder as it is too. If you need an older version of WordPress you can get any previous version here.
Very occasionally your theme might be playing up. Move the folder for all the themes except one of the WordPress default (like TwentyEighteen) and see if that improves things.
The white screen of death is definitely worrying when it crops up – but it’s not hard to resolve.
In my last post I mentioned the importance of forcing HTTPS if you’re using it on your website. (Which you absolutely should be.)
You don’t want visitors seeing the non-secure version of the site anyway, but from an SEO perspective Google doesn’t love it when they can see both either – they’ll interpret it as two different sites with the exact same content.
As long as your site is running on an Apache server (and most do) then you can edit the .htaccess file – this is the hidden file at the top level of your website that has specific instructions for how the server should load things.
To force HTTPS, just stick this at the top of it:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
And that’s it.
Or if you’re running a WordPress website you just want to stick this in that same file somewhere:
And just one more quick tip to make it even easier to force HTTPS on a WordPress site; as long as you use the normal permalink structure (domain/postname) then just replace the WordPress code in the .htaccess file with this:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# Rewrite HTTP to HTTPS
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*) https://%{SERVER_NAME}/$1 [R,L]
</IfModule>
# END WordPress
That will take care of the permalinks and forcing HTTPS.