You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have canonical tags on https://www.councilclimatescorecards.uk pages, pointing to their https://councilclimatescorecards.uk equivalents, which should mean that search engines don’t see the sites as duplicates.
But Isaac wondered whether, if it’s not too much bother, we should just set up a 301 redirect from every https://www.councilclimatescorecards.uk/* page to its https://councilclimatescorecards.uk/* equivalent?
(We seem to have non-www to www redirects set up for our other services—eg LIH, TWFY, FMS—so I guess councilclimatescorecards would be the same but in the opposite direction, sending people from www to non-www.)
The text was updated successfully, but these errors were encountered:
This is made more complex because councilclimatescorecards.uk and cape.mysociety.org are served from the same vhost. The redirect mechanism we use on other sites is present here in that it will redirect previous URLs (e.g caps.mysociety.org) but it redirects them to the default host name which is cape.mysociety.org.
I think for this to work we probably need to do something clever in the http.conf.
FWIW, this used to work when this was all hosted in a docker container.
We already have canonical tags on
https://www.councilclimatescorecards.uk
pages, pointing to theirhttps://councilclimatescorecards.uk
equivalents, which should mean that search engines don’t see the sites as duplicates.But Isaac wondered whether, if it’s not too much bother, we should just set up a 301 redirect from every
https://www.councilclimatescorecards.uk/*
page to itshttps://councilclimatescorecards.uk/*
equivalent?Is there any reason not to do this? /cc @struan @sagepe
(We seem to have non-www to www redirects set up for our other services—eg LIH, TWFY, FMS—so I guess councilclimatescorecards would be the same but in the opposite direction, sending people from www to non-www.)
The text was updated successfully, but these errors were encountered: