Ta kontakt med oss


Vilken ska du använda?


Which One Should You Use?

When it’s time to launch a new site, undergo a site migration or change your CMS, launch a new product, or make another major change, what overarching site structure to use is one of the most common questions.

Should we use or change over to a subdirectory, subdomain, or use a country code top-level domain (ccTLD) if we have international content?

And is one better than the other?

Google says there isn’t a difference.

This is definitely a topic that falls resoundingly in the “it all depends” box.

After all, when it comes to SEO, there are a lot of factors to consider.

Let’s break down the pros and cons of each option and help you decide which is best for your website.


First, let’s define subdomain, subdirectory, and a ccTLD.

Subdomain, Subdirectory And ccTLD Defined

A subdomain is a unique domain that is part of a larger domain.

For example, you could create a subdomain for your blog or another section of your site that sells products or if you need to differentiate content.

This would give you a URL that looks like this: blog.example.com or productname.subdomain.com.

Subdomains are often used to create separate website sections with distinct content.

A subdirectory is a folder on your website that contains separate pages or pieces of content.

For example, if you were managing the GAP, I would recommend a simple and SEO-friendly product subdirectory instead of the URL they have now, i.e., https://www.gap.com/browse/category.do?cid=6998&nav=expmore%3Amen%3Acategories%3Ajeans#pageId=0&department=75.

Subdirectories are often used to create separate website sections with distinct content.


A country code top-level domain (ccTLD) is a unique domain specific to a certain country.

For example, if you have a website for your business in Canada, you will need a ccTLD for the site, i.e., bestbuy.ca.

Pros And Cons Of Using A Subdomain

There are some benefits and drawbacks to using a subdomain when the overwhelming bulk of the content will be substantially unique from the root domain.

It comes down to what the publisher is trying to accomplish with that new content.

Will they make an effort to establish the necessary link equity?

Is the new content really that substantially unique from the primary content of the root domain?


  • Subdomains can help with organization.
  • By keeping your content on its own subdomain, it’s easy to keep track of the content and make sure it’s separate from the rest of your website.
  • Especially helpful if you have a large website with lots of distinct types of content.
  • Search engines view subdomains as separate websites, so a well-optimized subdomain has the potential to rank in search results.


  • More expensive than other options.
  • Additionally, some users find subdomains confusing. For example, if someone is looking for your business website and types in example.com, they may not realize that your blog is at blog.example.com. This can lead to confusion and lost traffic.

Also, since Google treats subdomains as separate sites if you create new content on a subdomain, it does not benefit from the authority being passed down because it is considered a brand-new separate website.

Pros And Cons Of Using A Subdirectory

There are several benefits and drawbacks to using a subdirectory for your site.



  • Usually more cost-effective to maintain than other options.
  • Some users find subdirectories easier to understand than subdomains. For example, if someone is looking for your business website and types in example.com, they will immediately see your blog at example.com/blog. It can help prevent confusion and lost traffic.
  • Authority is passed down from the root domain over to the subfolder, which can help with your search engine visibility.


  • Can be more difficult to set up than other options.
  • Subdirectories are not always seen as separate websites by search engines.

Pros And Cons Of Using A ccTLD

There are some benefits and drawbacks to using a ccTLD.


  • Can help set up your international website content.
  • Using a ccTLD is a strong signal that tells the search engines your content focuses on a specific country.


  • If you don’t have any international content or serve users around the globe, you do not need it.
  • Usually more expensive than other options.
  • Each ccTLD appears as a different website, so if you own multiple websites across the globe with different ccTLDs, you will have to optimize them all because they are all seen as separate entities.
  • Some countries require you to be a citizen or have some affiliation with the country to purchase the domain names with ccTLDs.

What Is Favored By Most SEO Experts?

SEO experts often favor subdirectories over subdomains because new URLs benefit from the root domain’s already established online authority and equity accumulated through external links.

By leveraging that authority of the root domain, subdirectories accumulate meaningful rankings and organic performance quicker than subdomains.

For that reason, many SEO professionals favor them, which frequently gets translated as “better.”

While it’s true Google recognizes subdomains as properties of the larger domain entity and can see the relationship between the two when done well and correctly, publishers will limit the linking between the two properties.

Therefore, the new subdomain then needs many external links pointed to it to become an established authority. That often takes substantial time and effort.

You might need a ccTLD if you have content in different countries and need to send a strong signal to Google and other search engines about your international content strategy.

While this can be expensive depending on the number of countries you manage, it may be worth looking into subdirectories or subdomains to direct users from different countries to the appropriate content.


Case Study

One of our clients in the financial space moved from a .com to a subdomain which we advised against.

When they moved, our client experienced decreased search engine visibility and traffic, but it was not too drastic.

After a year on a subdomain, they moved back to the main domain.

Once we set up the redirect and content migration strategy, our client experienced a 15% growth in traffic by moving back to the main domain with the authority, links, etc.


So, which is better for SEO: A subdomain, subdirectory, or ccTLD?

There is no easy answer.

It depends on your specific needs and goals. As we’ve seen, there are pros and cons to each option.

Fler resurser:


Utvald bild: metamorworks/Shutterstock


if( typ av sopp !== “odefinierad” && sopp === 'ja' ){
fbq('dataProcessingOptions', ['LDU'], 1, 1000);
fbq('dataProcessingOptions', []);

fbq('init', '1321385257908563');

fbq('track', 'PageView');

fbq('trackSingle', '1321385257908563', 'ViewContent', {
content_name: ‘subdomain-subdirectory-cctld-which-one-should-you-use’,
content_category: ‘seo web-development ‘




Yoast SEO 19.5 Update Causes Fatal Errors


Yoast SEO 19.5 Update Causes Fatal Errors

Publishers who updated to Yoast SEO 19.5 may have experienced more than they expected. Reports of fatal errors caused by the update soon began surfacing. Interestingly, the error appears confined to specific situations and not across the board.

Yoast SEO version 19.5

Yoast version 19.5 contains several changes that improve the user experience, fix a validation issue in the Article structured data, and address some minor bugs.

A standout improvement is the Front-end SEO inspector that provides an overview of posts and various SEO settings like meta tags and structured data.

Unfortunately, a bug also occurred in a specific situation that caused a fatal error.

A fatal error can occur when there is a conflict between two plugins.

Yoast Fatal Error

Eli Schwartz, sökmarknadsföring expert and author of the popular book Product Led SEO, tweeted about a fatal error.

It’s not uncommon for a random conflict between plugins to cause a problem. But this wasn’t all that random, as others confirmed that the same thing was happening to them.

The official Yoast SEO support page on WordPress.org also contained reports of fatal errors.

One user posted:

Fatal error: Uncaught YoastSEO_Vendor

“I woke up today and tried to access the dashboard of my website and I was met with a Fatal Error, I’m not able to access it through backend nor Login.
How can I solve this issue.”

Two others responded with the same problem, with one of them offering this comment:

“Same here. Can’t login in backend and both site and backend throw a fatal error.

Saw that Yoast has autoupdated today.


Moved both the free and the premium version from plugins directory to a temporary directory and now the site is back online.”

Someone else with the same setup of the free and premium version echoed that report, posting:

“Getting a fatal error after the update too. Also have the free version, premium version and News SEO.”

The official Yoast support person was apologetic, responding with this statement:

“We’re sorry that you’re experiencing a fatal error. Thanks for reporting.

We’re investigating and it seems to be a problem with the latest update of Yoast SEO while the newest Premium wasn’t released yet. This shouldn’t have happened.

We’re looking at getting this resolved as soon as we can by releasing a patch for free and also by releasing Yoast SEO Premium asap.

Either should fix the fatal error.

Yoast Responds

Joost de Valk, the founder of Yoast, offered this feedback to Search Engine Journal:

“A patch was created quickly by the team indeed and for most sites that resolved it entirely.

For some sites the auto update mechanism failed to run properly and therefore those sites didn’t automatically fix themselves.


We’ve been discussing this internally a lot, as we weren’t happy that this happened at all, and we weren’t happy with how we handled it. We’re all honestly really bummed by it and feel sorry for the sites we’ve broken.”

Yoast Identifies the Problem

The last commenter who noted how they had two versions of the Yoast plugin installed, the free and the premium versions, may have been a clue to what caused the fatal flaw because that situation was cited as the reason why the Fatal Error was happening.

Yoast responded quickly to the issues and issued a patch the very same day, version 19.5.1.

Enligt Yoast SEO WordPress Plugin changelog that documents what is in each update:

“19.5.1 – Bugfixes:

Fixes a bug where a fatal error would be thrown on the front-end when Yoast SEO 19.5 was used with an older version of Yoast SEO Premium.”

The Problem is Fixed with Version 19.5.1

Yoast 19.5.1 has fixed the problem.

One user posted this comment in the Yoast support forum:

“Update 19.5.1 has corrected the issue.”

However, because there are millions of users with millions of combinations of other plugins installed, it’s almost inevitable that very few edge cases may pop up with issues.


For example, in a post in the official Yoast support forum, one user describes updating from 19.4 directly to 19.5.1 and not having a satisfactory experience.

They shared:

“I went from 19.4 to 19.5.1 and it still broke my site. I don’t think .5.1 fixed the entire issue. I never updated to 19.5. Went straight from 19.4 to 19.5.1.
I have yoast, Yoast premium, and woo. all 3. First, one to try to update was regular yoast. All other plugins and WP on my site are current. Hope that helps to fix 19.5.1

Glad I never trust autoupdate, Not a fan of paying anyone to be a beta tester.

Yet this one still got me.”

It’s not unusual for edge cases to surface for any update, and this might be the case for Yoast 19.5.1.

The cause of the problem appears to be that Yoast published an update for the free version of Yoast (19.5) but did not simultaneously publish an update to the premium version, which then caused the two plugins to conflict, resulting in a fatal error.

Featured image by Shutterstock/Kues

window.addEventListener( 'load', function() { setTimeout(function(){ striggerEvent( 'load2' ); }, 500); });

window.addEventListener( 'load2', function() {

if( sopp != 'yes' && addtl_consent != '1~' ){

!function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(fönster,dokument,'script', 'https://connect.facebook.net/en_US/fbevents.js');

if( typ av sopp !== "odefinierad" && sopp === 'ja' ){ fbq('dataProcessingOptions', ['LDU'], 1, 1000); }else{ fbq('dataProcessingOptions', []); }

fbq('init', '1321385257908563');

fbq('track', 'PageView');

fbq('trackSingle', '1321385257908563', 'ViewContent', { content_name: 'yoast-seo-plugin-fatal-errors', content_category: 'news wp' }); } });



Fortsätt läsa

Prenumerera på vårt nyhetsbrev
Vi lovar att inte spamma dig. Avsluta prenumerationen när som helst.
Ogiltig e-postadress