SEO question regarding rails app on www.site.com hosted on Heroku and www.site.com/blog at another host

[Anward]

Hi, I have a rails app hosted on Heroku (www.site.com) and would much prefer to set up a Wordpress blog using a different host pointing to www.site.com/blog, as opposed to using a gem within the actual app.

Whats are peoples thoughts regarding there being any ranking implications for implementing the set up as noted in this post on Stackoverflow:

"What I would do is serve your Wordpress blog along side your Rails app (so you've got a PHP and a Rails server running), and just have your /blog route point to a controller that redirects to your Wordpress app. Add something like this to your routes.rb:

_`get '/blog', to:'blog#redirect'`_

and then have a redirect method in your BlogController that simply does this:

_`classBlogController<applicationcontrollerdef redirect="" redirect_to="" "url_of_wordpress_blog"endend<="" code=""></applicationcontrollerdef>`_

_Now you can point at yourdomain.com/blog and it will take you to the Wordpress site._

[Anward]

Hi Kane, thanks for that. After a fair bit of trawling the internet I eventually found the article below which provides a great way of doing what I wanted. For anyone else with an application built on rails (of which I'm sure there are quite a few!) then the following might make a lot of sense to those wishing to utilize the benefits of a Wordpress blog platform: https://medium.com/@parterburn/wordpress-inside-a-ruby-on-rails-app-c324fbf39ad8

[KaneJamison]

I don't understand how the Rails side of things work, but as long as the Wordpress URLs resolve to www.site.com/blog, and canonical tags reflect that, then you should be good.

For app companies where there won't be many links accumulated to the app itself, we often recommend running a complete Wordpress website at www.mysite.com, and running their actual app at app.mysite.com. This allows for easy content management by the marketing team, and marketing projects don't require lots of developer resources to get implemented. Not saying you should do this, but it can simplify things from a marketing & IT perspective. If there's a public facing version of the app, for example how Moz allows pages like https://moz.com/researchtools/ose/ to rank, then it can make more sense to run everything on a single subdomain.