International SEO: Choosing a gTLD (with subdomains or subdirectories) vs ccTLD

Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email

So, we grew up. The time came to start thinking beyond a single site’s structure that was only aimed at one market audience. (Locals in Australia).

We really do love our .design domain name (porkbun is currently giving away free .design domains the their first year of domain registration, after that it’s about AUD $55 year to run, pretty cheap depending on how you value your money and how many other domains you’re safeguarding from domain trolls/squatters, e.g. Your .com, and other domain combinations). It’s what makes us partly unique. If you search Google for the term “Web Designer Sydney” (or anywhere really) you will see nearly every site have either a .com or (or their respective ccTLD in whatever country). Most of these sites were tacky looking in design too. It made me lose a lot of faith in .com and based sites. Hence we sought after a fresh TLD to stand out in search engine result pages (SERPs) on Google and Bing etc.

We recently made an assumption that perhaps a would add greater trust to our website, but with no way to quickly test this apart from running some A/B tests in Cloudflare or Google Optimize (We had a look and didn’t like what we saw), there’s really no way yet to test what we want. Coupled with how Google doesn’t really like duplicate content scattered across multiple domains, makes this an even more difficult situation to be in.

Subscribe To Our Newsletter

Get updates and learn from the best

More To Explore

Do You Want To Boost Your Business?

drop us a line and keep in touch

Fatal error: Uncaught wfWAFStorageFileException: Unable to verify temporary file contents for atomic writing. in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:52 Stack trace: #0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(659): wfWAFStorageFile::atomicFilePutContents('/opt/bitnami/ap...', '<?php exit('Acc...') #1 [internal function]: wfWAFStorageFile->saveConfig('livewaf') #2 {main} thrown in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 52