-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pylint dot org - Add a notice in README to clarify that this website is defunct #8934
Comments
Aren't we're going to offer them free SEO (more visibility) if we do that ? |
Maybe we can find a way to allude to the existence of the dead domain without mentioning its exact address. |
Strangely there's a link to the repo with the source code for the website that surprisingly had commit not so long ago: https://forge.extranet.logilab.fr/open-source/pylint.org/-/commits/branch/default/. But anyway, if someone is already on the official doc/github they're don't need the info that the other website is not controlled by pylint. And if they are on the other website then we can't do anything, I don't think adding noise to the already convoluted readme would be a good thing. Maybe we can add something in the FAQ:
Btw i'm going to edit the original question for SEO. |
Just wanted to bump this thread: I feel it could be helpful to specify in the readme or elsewhere that |
It's because it is, it's one of the criteria (word is in the url, preferably alone) google used for years and maybe is still using. But there's not much we can do about it (apart from adding this in the FAQ as you said), feel free to open a PR for that @d33bs :) |
Currently, DuckDuckGo still reports
pylint dot org
at the top of the search result. Many tutorials, etc. also point to that domain. Per #7384 , it is impossible to recover the domain. But I think it is needed to add a notice in README to clarify that:Nor does pylint sell Japanese pills.pylint.readthedocs.io
(Yes, it's on the top of the GitHub page but it's worth reiterating)The text was updated successfully, but these errors were encountered: