Google’s John Mueller Shares Tips For Streamlining Website Structure

Prior to making modifications to your site structure, you need to think about the effect it might have on search rankings and user experience.

Google Browse Supporter John Mueller just recently shared important suggestions on this topic in a Reddit thread.

With his suggestions, you can discover how to streamline your site structure without impacting its SEO.

Keep reading to read more about Mueller’s suggestions and how it can assist you attain your site simplification objectives.

Eliminating Subdirectories– Great Or Bad Concept?

A Reddit user inquired about simplifying their website structure by retiring/ fr and/ de subdirectories.

Rather, they would direct all European traffic to the/ eu subdirectory.

They ask if that’s a great or bad concept and inquire about its effect on SEO and rankings.

Mueller’s Suggestion

Mueller encourages not to retire the subdirectories and move whatever to/ eu, stating it’s a great deal of deal with absolutely nothing to get.

Rather, he recommends moving “/” (en-us) into a “/ us” folder, which permits more accurate separation of the parts. By doing this, “/” is all United States, “/ fr/ *” is all French, and so on.

Furthermore, he suggests including hreflang on all pages, not simply areas, to pages that get puzzled the most by incorrect nation visitors.

” My suggestion would be not to move/ de & &/ fr into/ eu/de or/ eu/fr. There’s no SEO benefit you ‘d receive from that, and site-moves like this are a great deal of work. If anything, I may think about moving “/” (en-us) into a “/ us” folder. That method you have clearer separation of the parts (“/ us/” is all United States, “/ fr/ *” is all French, and so on). It would make tracking a bit much easier, and make it much easier for online search engine to comprehend the areas (vs moving/ fr into/ eu/fr, which would make it even harder to comprehend areas).

Likewise, hreflang is on a per-page basis, so you would do it on all pages. You discussed it as being areas, and maybe you’re currently doing it appropriately, so this is simply for efficiency. If you’re refraining from doing it on all pages, I ‘d think about examining your statistics for pages that get puzzled the most (incorrect nation visitors), and a minimum of include it there. Possibilities are this is primarily your homepage, so if you’re just doing it there, you’re most likely getting a great deal of the worth of hreflang currently.”

The Value of X-Default

Mueller highlights the value of x-default, particularly when doing geo-IP redirects.

His suggestions is to make certain that the root homepage reroutes to the proper variation which it’s defined as the x-default for the set of homepages.

Without doing this, to Google, it can appear like the root homepage is a different page from the others.

Setting the root homepage as the x-default will prevent this problem and permit Google to see it as the default for particular nations.

” And … if you do any of this and immediately reroute “/” (simply the root homepage) to the proper variation, you need to make certain that it’s defined as the x-default for the set of homepages. Without doing that, to Google it can appear like “/” is a different page from the others.

( modify to elaborate just on that tail end …– this is particularly if you have/ us for United States, and do geo-IP redirects, which I usually do not suggest)

If for United States users, “/” (simply that page) reroutes to “/ us”, AND you have hreflang throughout/ us,/ fr with x-default appointed to/ us, what can occur is that Google sees “/” as being an English page, likewise acknowledges/ us,/ fr as different pages, and after that reveals both “/” and “/( among the others” in the search engine result. You can prevent this by setting “/” as the x-default (even if it reroutes). Then Google will see “/” as the default “/ us” for United States, “/ fr” for France.

This likewise implies that you can’t have “/ eu” as x-default (there can just be one #highlander #xdefault), however you can still utilize that by defining it as hreflang for a lot of your typical nations (you can define several nations per URL). So in the end you ‘d have “/” = x-default, “/ us” for United States, “/ fr” for France, “/ eu” for a lot of nations, and reroute from “/” to the very best variation.

All of this is just for the homepage, I would not do it for any of the other pages of the website due to the fact that it’s so intricate & & tough to handle, and due to the fact that the homepage is most likely the page that gets one of the most search impressions.”

More On Geo-Redirects

Concerning geo-redirects, Mueller encourages utilizing them just on the primary homepage of the site and not on any of the other pages.

This assists to streamline the procedure for users typing in the domain to discover the closest match to their area and permits them to quickly click a various nation to gain access to that variation of the site.

There are alternative choices to geo-redirects, such as dynamically altering the language of the homepage, however this method can include more intricacy to the site.

Another choice is to utilize a country-picker on the homepage, however this can adversely impact use, especially if there are numerous nations to select from.

In Summary

If you wish to streamline your site structure, it’s finest not to do it by moving subdirectories around.

In this case, a site owner wished to move/ de and/ fr into/ eu/de or/ eu/fr.

Rather, Mueller stated they must think about moving “/ *” (en-us) into a “/ us” folder, including hreflang on all pages, and defining the root homepage as the x-default for the set of homepages.


This will assist prevent confusion amongst online search engine and make it much easier for them to comprehend the site’s various areas.

Included Image: GoodStudio/Shutterstock

Source: Reddit

Leave a Reply

Your email address will not be published. Required fields are marked *

Schedule Call

👋🏻 Hi friend, how are you today?

Need help? contact us here... 👇