Users searching on Google are getting search results for different versions of UCP/DTR, which causes them to waste time running commands that don't make sense for their particular version.
A possible solution is to display a banner with the version, but we also need to ensure Google will always send you to the latest docs
Below is the feedback of a user
feedback 1
One struggle I had is that I would install different version(s) of DTR based on the SEO results the Google provided (i.e. 2.2, 2.1 or latest). I was not paying attention to the commands I would enter. I had DTR joins not working, as I had multiple tabs open with different version of DTR in each tab. The DTR join would be different in each tab. E.G - Top link in Google is https://docs.docker.com/datacenter/dtr/2.1/guides/install/ , Second Link is https://docs.docker.com/datacenter/dtr/2.2/guides/admin/install/ , Third link is https://docs.docker.com/datacenter/dtr/2.2/reference/cli/install/ . Once I determined I was installing a range of DTR versions, I stopped and installed 2.1 as the go forward and saved the correct syntax. This helped in terms of the overall installation, and troubleshooting the 443 issue.
feedback 2
A lot many times they would have links that would direct them to some place and that place would have instructions for an older build or an older release
Users searching on Google are getting search results for different versions of UCP/DTR, which causes them to waste time running commands that don't make sense for their particular version.
A possible solution is to display a banner with the version, but we also need to ensure Google will always send you to the latest docs
Below is the feedback of a user
feedback 1
One struggle I had is that I would install different version(s) of DTR based on the SEO results the Google provided (i.e. 2.2, 2.1 or latest). I was not paying attention to the commands I would enter. I had DTR joins not working, as I had multiple tabs open with different version of DTR in each tab. The DTR join would be different in each tab. E.G - Top link in Google is https://docs.docker.com/datacenter/dtr/2.1/guides/install/ , Second Link is https://docs.docker.com/datacenter/dtr/2.2/guides/admin/install/ , Third link is https://docs.docker.com/datacenter/dtr/2.2/reference/cli/install/ . Once I determined I was installing a range of DTR versions, I stopped and installed 2.1 as the go forward and saved the correct syntax. This helped in terms of the overall installation, and troubleshooting the 443 issue.
feedback 2
A lot many times they would have links that would direct them to some place and that place would have instructions for an older build or an older release