Welcome to the Q&A Forum

So our company has new page that has just implemented (let say  "page x" --> not a landing page) and we want to see how many visitors that through  "page x " convert into the goal (let say "page y"). If I just make the goal destination like "/page y" the goal number that appear is ALL the visitors who reach "page y" (through or not through "page x"), so how I set the goal setting to only show the visitors who reach "page y" through "page x" ? Thank you

Currently we have a website in english but over time we will roll out parts of the whole site in different languages for different countries which will also result in country specific English versions of the website.

The goal is that Google shows the country specific version of a page in a native language or English if available or falls back to the default English version of the same page otherwise.

I listed below how we plan to use hreflang and canonical link tags to achieve this and was hoping to get some feedback from the Moz community if this will work as expected.

(1) A page (www.mysite.com/page1) exists only in English as default. Users should be able to find it in every country unless there is an English version specifically for this country. We would use the following tags:

(2) A page exists in English (www.mysite.com/id/en/page2) and Bahasa (www.mysite.com/id/id/page2) for a specific country (Indonesia in this case). Users in Indonesia searching in English should find the country specific English page. Indonesians searching in Bahasa should find the Bahasa version of that page. We would use the following tags on the English version:

and therefor the following tags on the Bahasa version:

In this case there wouldn't be a default English version available for the page.

(3) If a page exists in English global, English for Indonesians and Bahasa for Indonesians we would use:

on www.mysite.com/id/en/page3

on www.mysite.com/id/id/page3

on www.mysite.com/page3

If www.mysite.com/id/en/page3 and www.mysite.com/page3 are very similar we would risk google picking the page they want to rank for an english keyword searched in Indonesia, correct?

(4) If a page in (1) and (2) can be reached with a different URL, we would only use a canonical and don't specify any hreflang tags e.g.:

www.mysite.com/en/other-url-to-page1

or
www.mysite.com/id/en/other-url-to-page2-english-indonesia

(5) If a page that exists as global English page becomes available in English for a specific country as e.g. www.mysite.com/uk/en/page1 we would use the following tags:

and also add one more hreflang to www.mysite.com/page1:

The assumption here is that Google would rank the localized page instead of the global page after crawling our site again. But since this will be a new page, are we going to lose traffic because www.mysite.com/uk/en/page1 won't rank as well in the beginning (e.g. no offsite optimization)?

But if I end up creating a big number of these landing pages, it would appear to be some sort of content farm, correct? Even if it makes it more convenient for a user to book a service of our clients.

I have a number of clients offering a number of services on our platform. Currently we have only client profiles online but were thinking now to create landing pages for each client and each service based on long tail keyword patterns we saw emerge.
This would increase the number of landing pages by 10x but since those long tail keyword landing pages are fairly similar for each client+service combination we were wondering what issues we could run into with this approach.
Can our domain get penalized if we do this or would possible duplicate pages just not rank? Or is this all with in the rules?

One of my pages has two Google maps on it. This leads to a fairly high keyword density for words like "data", "map data" etc. Since one of the maps is basically at the bottom of the page I thought of loading it "on scroll" as soon as its container becomes visible (before loading the map div should be empty). Will the map then still be craweld by google (can they execute the JS in a way that the map is loaded anyways?) or would this help to reduce the keywords introduced by the maps?