search

yarnpkg / website

Yarn package manager website
https://classic.yarnpkg.com
431 stars 974 forks source link

Get rid of yarn v1 for good! #1202

Open landsman opened 1 year ago

landsman commented 1 year ago

Guys, I really hate this day-to-day scenario when Google returns links to https://classic.yarnpkg.com/* as the first result. It's so annoying!

Could you please disable indexing for this website and, for God's sake, get rid of it permanently? 🙏

Please promote the latest version and place the history as a secondary option, somehow hidden below, like every other tool and service.

Is there any way I can help? 🙏

For context to others:

Related: https://github.com/yarnpkg/yarn/issues/8973

landsman commented 1 year ago

A few examples:

Screenshot 2023-08-03 at 15 38 58

Screenshot 2023-08-03 at 15 39 34

Screenshot 2023-08-03 at 15 39 54

It's time...

arcanis commented 1 year ago

Yes, I think removing the index is fine. We're actually wrapping up the new website, so we can do that once it's deployed (a couple of weeks).

tspearconquest commented 1 year ago

I'd also like to take a second to point out that the node docker image still pulls yarn 1.22.19. If anyone here has a connection with the team who manages the docker library where that image is built from, can you please ask them to update the images to use a supported yarn version?

Daniel15 commented 1 year ago

Doesn't this mean that the old site has better SEO than the new site? 🤔

get rid of it permanently?

If we want to remove the old site, all the old URLs should 301 (permanent redirect) to the correct page on the new site, for all languages the old site supported, such that none of the URLs indexed in Google become 404 errors.

There's still a bunch of people using Yarn v1 though, so maybe we do still need the content. Perhaps it can be integrated into the new site (e.g. a version dropdown or something)?

I'd also like to take a second to point out that the node docker image still pulls yarn 1.22.19.

As far as I can remember, Yarn v2 and newer are not designed to be installed globally in the same way that Yarn v1 was, which is why the Docker image, Debian package, etc are all still using Yarn v1. You can still have Yarn v1 installed globally but use Yarn v2/v3/... on a per-project basis.

landsman commented 1 year ago

@Daniel15 the goal is to index only latest version. Then you can provide dropdown with redirect to archived website with no-index flag for robots.

all the old URLs should 301 (permanent redirect) to the correct page on the new site

yeah I would redirect all of them to latest website, index (where will be notice about archive) => Google will remove them from SERP as duplicate.