Does having a blog on another server impact SEO
The blog is - blog.andwemet.com and is linked to the main website - we made the blog separately - we see a lot of SEO traffic on the blog but not on the homepage and were told to move the blog to - andwemet.com/blog - is this correct....we are finding it challenging to move the blog - so is there another solution around this. thank you in advance.
I believe so.
Some SEO experts say it doesn't matter but every serious company swaps and they even swap their knowledge base from doc.example.com to example.com/docs
It is one of the main reasons people sign up to https://versoly.com/ being able to edit landing pages and blog on one site without any maintenance (WordPress)
thank you so much, helpful inputs - our blog is made on Ghost and not Word Press
I believe you can use Nginx proxy.
What are you using for the main site?
we are using this but are not able to move all our resources like images, they are not displaying when we proxying using Nginx
Are you using any framework for React like CRA, Next, Gatsby etc? And how you integrating your images? Are you hosting them separately and just using the URLs or are you importing the files as resources for React?
thank you for responding - Our blog platform is also hosted on Digital Ocean & we use Ghost CMS (ghost.org) and self host it. It's an open source blogging platform written in Nodejs & use mysqldb
The problem we are facing is that the blogging platform is currently hosted on blogs.andwemet.com (A subdomain on another droplet) & we want it on andwemet.com/blogs (A suburl in the same droplet as main website)
The reason behind this is that since the blogging platform in on separate subdomain - our efforts on blogs are not increasing our SEO scores as google is treating the main website separate from the subdomin blog website
The solution can be to deploy the ghost cms on the same server as main website in a separate subfolder and using Nginx to setup proxies/ handle redirections.
Any guidance regarding how we can do that would be really helpful.
So the blog is hosted on a server using ghost CMS. it is stored in house on the server itself - no cdn or databse perse. However, what we have done is proxy the blog server on the main server at a sub-url. The frontend for ghost is made using handlebars and backend is written in Node
Having both on the same server would make this probably easier but it should work anyways.
The nginx proxy should run on the main server (which hosts andwemet.com) and should by default pass all traffic to the service that hosts andwemet.com.
Then you should add an wildcard exception for every route which starts with
/blogskind of like described here. But I guess this is kind of your setup already. (Make sure to not just redirect/blogsbut also/blogs/*!)A problem that could occur (and I guess that's kind of the problem with your images?) is that the blog server tries to load it's resources still from
blogs.andwemet.com. I'm not very familiar with your tech stack in this case, but it should be possible to change your "base url" of the blog to beandwemet.com/blogswhich should then load resources from a path likeandwemet.com/blog/cssand so on. Then I'd not allow any traffic fromblogs.andwemet.comas this would probably break the site.Kind of rough but in general this should be a solution to your problem.
We are on react.
You can use your Ghost as a headless CMS and show it on your website. (Check some articles on how to use ghost with React)
thank you for responding - So the blog is hosted on a server using ghost CMS. it is stored in house on the server itself - no cdn or databse perse. However, what we have done is proxy the blog server on the main server at a sub-url. The frontend for ghost is made using handlebars and backend is written in Node
So you have already found a solution that satisfies your needs?
While I don't have an answer, it make no sense to me. If I am Google, a search engine, I would know that people do both variants and that it means nothing. It means a lot of sense that traffic goes where the content it. In your case, that's the blog.
This comment was deleted 5 years ago