There is a separate issue #11 for taking old.plone.org offline, but it is also still publicly accessible for search engines to crawl. This is bad for SEO.
I didn't check if the robots.txt has been fixed accordingly when we moved to the new Plone 6 based website in december '22.
Should we add basic auth restriction? This needs to be added locally on wicked and is a temporary measure until wicked is archived and deleted from linode
There is a separate issue #11 for taking old.plone.org offline, but it is also still publicly accessible for search engines to crawl. This is bad for SEO.
I didn't check if the robots.txt has been fixed accordingly when we moved to the new Plone 6 based website in december '22.
Should we add basic auth restriction? This needs to be added locally on wicked and is a temporary measure until wicked is archived and deleted from linode