Hi Gianluca,

I also have a translation for Latin American Spanish, what is the best way to target that? Do I need a site for each country? Or should I just call it "es" and use the same site for each country that I need to target?

Yes, I was actually going through the Moz guide to international seo and hreflang is mentioned.

https://moz.com/blog/guide-to-international-seo

Yes, I'm using Wordpress but I decided to go with Multisite. I didn't really like any of the plugins out there that handle translations. I'll look into the rewrite rule, thanks!

Hi Gianluca,

Thanks for your response. The main version of our site is actually English, that is the language that currently resides in the root.

-Brandon

Sorry, didn't mean to refer to that link as a guide more of a reference.

So using /pt-br/ is fine, what really matter is letting Google know the language/location through search console and other measures what language/location the page are targeting.

I'm not following what you mean in the last sentence: Unless you use some type of CMS, then you can just use RewriteRule or something to only display needed URL.

I'm wondering if there are any guides out there that list how subfolders should be structured for Internationalization? The first language/location that I'm targeting is Portuguese in Brazil so should my folder structure be:

www.example.com/br/pt/

or

www.example.com/pt-br/

I did find the guide below but was wondering if there was perhaps anything from Google?

http://www.lingoes.net/en/translator/langcode.htm

You can tell Google what URL parameters to ignore in Google Search Console. It's under Crawl > URL Parameters > Configure URL Parameters. Google does advise to use caution when changing how Google bot handles the parameters.

Thank you Paul,

This is exactly what I needed. I've been trying to push us in this direction but it's sometimes hard to break old habits. We might even be able to save a bit of money going this route.

Thank again for the input!

-Brandon

If I were to start creating individual pages for things such as webinars or other resources for our visitors to consume would I be running the risk keyword cannibalization? The webinars cover topics around our products and services so my fear is that the content might compete with our product and service pages.

I noticed here at moz that each webinar does not have it's own page and just links to the registration page (https://moz.com/webinars).

So it sounds like you create an archive for the previous years event? Moving the previous years highlights to another page so it can still be accessed?

The url on our registration site changes but we redirect the main landing page to that url temporary. I think ideally the content for the event should be on the main domain and just utilize the third part event site to manage the registrations.

Seems like there are so many ways to do this.

Every year our company has a user conference with between 300 - 400 attendees. I've just begun giving the event more of a presence on our website. I'm wondering, what is the best way to handle highlights from previous years? Would it be to create an archive (e.g. www.companyname.com/eventname/2015) while constantly updating the main landing page to promote the current event? We also use an event website (cvent) to handle our registrations. So once we have an agenda for the current years event I do a temporary redirect from the main landing page to the registration website. I don't really like this practice and I feel like it might be better to keep all of the info on the main domain. Wondering if anybody has any opinions or feedback on that process as well.

Just looking for best practices or what others have done and have had success with.

Every year our company has a user conference with between 300 - 400 attendees. I've just begun giving the event more of a presence on our website. I'm wondering, what is the best way to handle highlights from previous years? Would it be to create an archive (e.g. www.companyname.com/eventname/2015) while constantly updating the main landing page to promote the current event? We also use an event website (cvent) to handle our registrations. So once we have an agenda for the current years event I do a temporary redirect from the main landing page to the registration website. I don't really like this practice and I feel like it might be better to keep all of the info on the main domain. Wondering if anybody has any opinions or feedback on that process as well.

Just looking for best practices or what others have done and have had success with.

So it sounds like you create an archive for the previous years event? Moving the previous years highlights to another page so it can still be accessed?

The url on our registration site changes but we redirect the main landing page to that url temporary. I think ideally the content for the event should be on the main domain and just utilize the third part event site to manage the registrations.

Seems like there are so many ways to do this.