URL language naming convention for non-English websites - url

I am developing a website for a French audience. There seem to be an incompatibility between independent best practices :
Naming frontend urls in the audience's language for SEO and audience's confort. Ex: www.site.com/bonjour
Naming API urls in English as it is the default language for development. Ex: www.site.com/api/hello
Naming frontend urls and API urls in the same language to avoid mistakes. Either (www.site.com/bonjour and www.site.com/api/bonjour) or (www.site.com/hello and www.site.com/api/hello)
What is generally considered best practice ? What can be a good criteria to decide ?
Frontend urls in French, API urls in French
Frontend urls in French, API urls in English
Frontend urls in English, API urls in English

Related

redirect a subfolder from heroku to dedicated WordPress hosting

I have a simple site on heroku using Harp (not married to harp, just used something that can serve up static HTML.
We need to add a blog in a subfolder domain.com/blog instead of blog.domain.com for SEO reasons. Is there a way on Heroku to redirect just a subfolder?
I don't want to host, manage or deal with WordPress in any fashion. I'd like to avoid running any other blogging software. My preference is just to leverage the hosting solutions without losing SEO scores.
You'd have to do the redirect in Harp, but unfortunately Harp doesn't support server-side redirects. You can do a client-side redirect, though.

How do I create 301 redirect from WordPress (hosted on wsynth) to a Rails app hosted on Heroku?

I have a website (example.com) that is a WordPress site hosted on WSYNTH.
I am redesigning the site, same domain (example.com) in ROR hosted on Heroku.
I have been told that for SEO purposes, once I point my domain to the ROR app on Heroku, all the old pages from the Wordpress site will go dark. (Makes sense.) But this would be very bad for SEO, since example.com will now have many URLs associated with it (created from the WP site) that are no longer valid.
I've heard that a 301 Redirect for those WordPress URLs will take care of this SEO issue. But how and where should I do this? Should I be installing a plugin in WordPress that will automate the redirects to the pages I want to send them to in the ROR/Heroku app?)
Also, is it possible to keep some of those old WordPress URLs live?
DNS
The 301 redirect is not the issue - you can use Wordpress itself to redirect to specific pages (using the simple 301 redirects plugin), or a better way will be to redirect your domain (with your DNS) to your Rails app, and then use the routes to handle any stray pages
The world of "SEO" is highly overrated - Google is just a system which
follows links. If it cannot find a page, it removes it from its
rankings; if it can find the page, it judges its on & off-site
optimization to determine its relevance.
This means the only thing you need to concern yourself with is ensuring you don't have any "holes" in your URLs. The redirections essentially mean you will tell Google to follow a link to the new page
--
Redirections
The first thing you need to do is ensure you have the new pages you wish to show on your site. Preferrably, you'll want to make as many of them as identical to your previous URLS as you can.
Secondly, you can introduce redirects in your Rails routing system to give Google real pages when it visits the links for your Wordpress site:
#config/routes.rb
get '/your-old-post-name', to: redirect('/your-new-post-name')
This will mean you will have to create redirections for every wordpress post in your new Rails app - but should give Google the knowledge that those pages have changed, to which it will update

Rails/Heroku RESTful locale best practice?

What do you consider the best practice to handle locales and internationalization in a Rails app on Heroku in a RESTful way? What is your bit of code that gateways the user according to their locale? Is a subdomain solution (http://de.myapp.com, http://en.myapp.com, …) possible without the wildcard subdomain add-on on Heroku?
I don't believe there is anything to stop you using http://de.myapp.com, http://en.myapp.com and friends on Heroku.
Rather than using wildcard domains, what you'd have to do is:
Manually configure your DNS domain to provide 'true' DNS names for each locale.
Add each domain manually using the (free) Custom Domain plugin.
Obviously this is a bit more work than using wildcard domains, but should be fine unless you've got a lot of locales to manage.
You have different options to set the locale, e.g. you could as well go with myapp.com/en/... .
See RailsGuides for more information. There is no need to mess with domains unless you absolutely want to :)

Open site using default Browser Language Preference,developed in SharePoint 2007

We are developing multilingual site using SharePoint 2007. Now the requirement from client is whenerevr user access the site, the Site should be open in his browser using users browser Language Preference. Our current site is in English and Spanish. If users language preference is Spanish then Spanish site should be display to the user.
Thanks in Advance
You need to develop a redirector module which will read the browser settings on the redirect.aspx page (Example) and then redirect to the appropriate language site based on thei site.
See here for the example:
http://panvega.wordpress.com/2008/05/15/variationrootlandig-redirect-to-another-variation-site/

How to host different applications without subdomains in Heroku?

I would like to have different applications under the same domain using Heroku.
Because of the name of the domain, I would like to access the applications using folders (mydomain.com/app) instead of using subdomains (app.mydomain.com), is this possible? Thanks
There is no type of URL re-writing you have access over thats going to do that for you. You could create a "stub" Siantra-based app that allows you to define those types of URLs, but it would have to effectively redirect you to the subdomain version.
I'd have to play devil's advocate and ask why you'd want to have things namespaced as /app instead of using subdomains. Subdomains offer much more flexibility and are a lot less brittle than essentially having to url-rewrite all the time based on the first "slash" element.
You can't do this with heroku - it assumes the directory structure of the Rails application.

Resources