I had a quick look over your site in response to being asked for info on https://bugzilla.mozilla.org/show_bug.cgi?id=865381 and noticed that there are MANY ways to access your site. http://openbadges.org http://www.openbadges.org https://openbadges.org/ https://www.openbadges.org/ This isn't going to help SEO very much, and it could get a bit confusing in regard to which URLs are promoted and what Google finds. Would recommend choosing one canonical URL (I suggest http://openbadges.org - having this as http only will make it easier to embed external content on it) and having the other 3 redirect to that (either on the load balancer or apache, even in the .htaccess file). At this point you can lock down your site URL in the wpconfig.php and also your templates, and no fixed content errors anymore!
Well, this is half done, https now redirects to http, though the beta site https://beta.openbadges.org/ uses https which may mean the main site will too. IMHO, given that mozilla.net, mozilla.org, twitter.com, newrelic.com and google-analytics (the only requests to other content i can see) all offer https (some ONLY offer https) the site should just move to https only.
I'd be happy to get this site redirected to https. Andrew and I can set up some time to work together to make the openbadges.org site https compatible once again.
Right. beta.openbadges.org is actually not a beta of 'openbadges.org' at all, but rather the backpack, which now exists at backpack.openbadges.org. So beta.openbadges.org should probably not even be there any more, but whatever. Regardless, they should be on https, as they're dealing with external user data. openbadges.org is a slightly different story, and might need further discussion from the people who actually put content on it. I have a feeling this is something that we're going to have to bring Chris in on to decide how we're going to deal with it - I don't know how much longer the openbadges.org property is going to be under Mozilla's remit.
Flags: needinfo?(andrew) → needinfo?(chris)
You need to log in before you can comment on or make changes to this bug.