Bug 29875 - Old german wiki page needs to get blocked from search engine crawlers
Summary: Old german wiki page needs to get blocked from search engine crawlers
Status: NEW
Alias: None
Product: Websites
Classification: Unclassified
Component: wiki.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-12 12:31 CET by sturmvogel
Modified: 2022-01-13 10:31 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description sturmvogel 2022-01-12 12:31:47 CET
Since some time the german Mageia wiki can be reached via
https://wiki.mageia.org/en/Hauptseite-de

But the old wiki page https://wiki.mageia.org/de/Hauptseite (and all sites
below) is/are still reachable and get crawled by all search engines. This
outdated and no longer maintained sites gets really high rankings in the
search results. Users are not aware that they are on a no longer maintained
site! Only the wiki main page has a short note that the wiki moved, but not
the sites below.

This lead to an actual problem with a german user who followed the
instructions from this old wiki because it was the first search result in his
search engine.

Who from our devs/sysadmins/maintainers/siteowners is able to put up a working
robots.txt to the old server adress? Or are there any other ways to prevent
that this wiki shows up in the search results any longer? Im aware that any
meassures won't show immediate results and that it needs time that this search
results disappear. But we should act NOW!
Comment 1 Filip Komar 2022-01-12 23:18:13 CET
Reassigning as this is beyond atelier access.

CC: (none) => filip.komar
Assignee: atelier-bugs => sysadmin-bugs

Comment 2 sturmvogel 2022-01-13 10:24:57 CET
I don't know if it is more feasible to delete everthing below https://wiki.mageia.org/de/ or if we still have any infrastructure  running an this subdomain.
Comment 3 sturmvogel 2022-01-13 10:31:25 CET
Correction: "directory" instead of "subdomain"

Note You need to log in before you can comment on or make changes to this bug.