Need better solution for 301s with Jekyll/S3 Site
-
Hey Mozzers,
So, this isn't the first time that I've come to the community with questions regarding my new site. Although running a site using static HTML-generated pages has been fantastic in the first few weeks as far as load times, it's been a nightmare in terms of a few other SEO-related concerns, namely redirects.
In the Q&A post above, Mat Shepherd pointed out a solution for adding 301s to an Amazon Webservices site using their "Redirection Rules" field on the "Configure Bucket for Website Hosting" page. However, I discovered soon after that I was limited to only 50 redirects using this method. Obviously, all things considered, this will not be enough.
At this point, I'm basically out of ideas. If anyone else out there has a website with a similar setup, (Jekyll platform hosted on Amazon S3,) that has overcome this problem with redirects, I'd really appreciate hearing from you.
Thanks in advance, everyone
-
As a follow-up to my own post...
After a ton of research today, I feel like I've come to a couple of resolutions that might be of interest to anyone who is considering possibly running a static site on S3 and reading this forum:
-
S3 probably isn't the place for your website if you're a Moz user. Although it's the only static website host that actually does provide a way to create 301s, it limits you to 50. Additionally, the process for creating 301s involves writing lengthy XML documents. Not fun
-
An additional thorn in the side of static sites is the SUPER oldschool web practice of instituting 302s to add trailing slashes. I.e.:
-
_http://www.examplesite.com/page_ 302s to _http://www.examplesite.com/page/_
So, at the end of the day, I would say it's probably best to avoid this kind of setup until some solutions for these kinds of issues come up. Not fun times.
-
-