🌐 Pagecord now uses subdomains
When I originally built Pagecord, I went with a /blogname format for URLs because I liked how this looked on social media sites (twitter.com/username etc). I also want to allow Pagecord users to easily follow other Pagecord blogs like you do on social media.
Turns out, Pagecord isn't social media and this wasn't a very good idea. At least in its current incarnation.
The /blogname approach meant each blog has a unique URL but not a unique domain. This is totally fine... until it's not. If you want to set up custom analytics for your blog (a feature I'd like to add), for example, you typically need to do this on a unique domain. If I implemented this feature I'd only be able to offer it to people using custom domains, which is a low percentage. The same goes for setting up robots.txt – this would only work for custom domains.
Not good enough!
This changes from today. Now every Pagecord blog has a unique subdomain. Your blog username (i.e. the /blogname) is essentially the subdomain. By way of example, this Pagecord blog used to be found at https://pagecord.com/blog but now it's found at https://blog.pagecord.com.
The old paths will continue to work using 301 redirects. The first ever Pagecord post was https://pagecord.com/blog/hello-world-5f5e111. If you click on that you'll see it automatically redirect to https://blog.pagecord.com/hello-world-5f5e111. As Google crawls your site, it will figure this all out and quietly update its index without affecting your search ranking.
Hopefully this makes sense and you like your new domain. As ever, if you spot anything awry, drop me an email by replying to this post (see link below) and I'll get it fixed up.
Turns out, Pagecord isn't social media and this wasn't a very good idea. At least in its current incarnation.
The /blogname approach meant each blog has a unique URL but not a unique domain. This is totally fine... until it's not. If you want to set up custom analytics for your blog (a feature I'd like to add), for example, you typically need to do this on a unique domain. If I implemented this feature I'd only be able to offer it to people using custom domains, which is a low percentage. The same goes for setting up robots.txt – this would only work for custom domains.
Not good enough!
This changes from today. Now every Pagecord blog has a unique subdomain. Your blog username (i.e. the /blogname) is essentially the subdomain. By way of example, this Pagecord blog used to be found at https://pagecord.com/blog but now it's found at https://blog.pagecord.com.
The old paths will continue to work using 301 redirects. The first ever Pagecord post was https://pagecord.com/blog/hello-world-5f5e111. If you click on that you'll see it automatically redirect to https://blog.pagecord.com/hello-world-5f5e111. As Google crawls your site, it will figure this all out and quietly update its index without affecting your search ranking.
Hopefully this makes sense and you like your new domain. As ever, if you spot anything awry, drop me an email by replying to this post (see link below) and I'll get it fixed up.