Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Keep the blog separate or incorporate into main domain?
-
So my organization currently has both a main site and on a separate domain and separate host a wordpress blog. (our own domain not a wordpress.com)
the content posted on this blog is local, community driven, and related to our business but it is not used in anyway as a "sales" tool. It's more for interaction purposes with members and employees.
This blog has a lot of content and is updated with new posts very often. (generate traffic from a pretty wide variety of searches some related some not) My plan has been to 301 the old domain and move the wordpress blog over to our root domain in a subdirectory such as oursite.com/blog.
Does anyone have tips for moving a blog over like this? I'm concerned about any link juice it has dropping off and since it does provide some links to our root site currently (since it's basically a separate site). Basically i'm wondering if it'll be worth the effort or if i should just keep it separate and focus on other content gen strategies.
-
great input and much appreciated.
Ideally i would like to have the blog moved over, but there is a lot of links/content to deal with. I'm working on developing several content gen strategies, and wanted to make the blog a part of that. Currently it's always been more a part of the social media efforts, but work has been done to better connect it to the main site and make sure it's branded to be one in the same.
Where i'm a little unclear is the tech efforts of doing this. I would assume as thomas mentioned it's a matter of creating the subfolder to house the wordpress install/content and setting up a 301 on the old domain, but the need to do each post individually is where my concern is.
-
Absolutely! This is probably a priority project in my eyes if you are serious about building this up and going in the right direction now.
Moving the BLOG to your domain.com will not only improve the relation to your site and content, but brand it as well. Having the BLOG on another domain (as it is now) might help you from a link building perspective (more than likely not helping very much) due to the fact Google would know you own that domain, and perhaps place less emphasis on the inbound links to the main site.
First - setup your site/domain to host the BLOG as you mentioned. www.domain.com/blog. There are a few reasons for this.
1. It will allow you to reap the rewards of the content you build (supporting your site/company/mission) and support the main domain, and it's
2. The content you build, share and move into the social sphere and space will allow for inbound links to be shared across the entire site/domain. (don't build it into a sub-domain like blog.domain.com as this is considered to be a completely separate domain and won't pass any link value and juice across the domain). sub-domains are considered to be domains by themselves in the eyes of a search engine like Google.
3. The content you build (and load daily to the BLOG) will keep search spiders coming back for more
4. Keeping the BOG content on the main domain, allows you to share the content of the BLOG to your web visitors who might be searching via BRAND or specific, helping associate the brand with the content marketing resource you are building. This in itself is a gold-mine, as it will also act as another source for long-tail traffic opportunity, but you'll have to do your due diligence on this from a research perspective to capitalize on the traffic.
5. Content marketing is going to be BIG (as it's already on the rise and exploding now). This will all fall under your efforts for the BLOG and should be focused on. The value here is that over time, Google will begin to apply TRUST and AUTHORITY factors to the content you write and submit - helping to support your brand as a quality resource of shared information for people.
Make sure to use rel=canonical from the old location URL's and point those over to the new URL's on the domain.com/blog listing. Also make sure to use rel=author for each of the articles on the new blog from a META position.
NOTE: Handling a migration such as this is very complex (especially if the BLOG is extremely large with thousands, or 10's of thousands of posts and articles). Even a few hundred can be TRICKY!
Not only do you have to setup the files (BLOG) on the new domain, but you will have to write and execute 301's for every single article on the old location/domain and point that over to the new one. Some CMS's like Drupal can assist with this if your programmers can handle writing the scripts. This is a very technical undertaking, so make sure to do your research. If it's a small resource, you can still follow the same protocols, but it will take much less time to complete.
I recently handled and oversaw a technical project like this months back that took quite a long time to do, troubleshoot as it had over 30K articles and 25K in image files over the past 6 years! It was a huge undertaking that went extremely well, but you have to be patient.
Hope this helps some! There's probably a little more I didn't mention as I'm late for a meeting with a client!, so if you have questions - let me know!
Rob
-
I've got a separate blog site. There are benefits to both scenarios. The reason I have chosen to keep them separate is so that I can post content from other bloggers and contributors and not worry about the content being officially endorsed by Bulwark.
If you do move it over to your main site, you can easily export the wordpress site and all it's content to a sub-folder and then do a 301 redirect rule from your old blog. It is probably ideal to have them all on one site so long as the company wants to take claim for all the content written there.
-
I would say it's worth the effort to give your main site a boost. IMO the more content you can get on your own site that's relevant, the more Google has to base it's evaluation off you. If your blog has alot of fresh content, that'll keep Google coming back for more!
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
We switched the domain from www.blog.domain.com to domain.com/blog.
We switched the domain from www.blog.domain.com to domain.com/blog. This was done with the purpose of gaining backlinks to our main website as well along with to our blog. This set us very low in organic traffic and not to mention, lost the backlinks. For anything, they are being redirected to 301 code. Kindly suggest changes to bring back all the traffic.
Technical SEO | | arun.negi0 -
Which Sitemap to keep - Http or https (or both)
Hi, Just finished upgrading my site to the ssl version (like so many other webmasters now that it may be a ranking factor). FIxed all links, CDN links are now secure, etc and 301 Redirected all pages from http to https. Changed property in Google Analytics from http to https and added https version in Webmaster Tools. So far, so good. Now the question is should I add the https version of the sitemap in the new HTTPS site in webmasters or retain the existing http one? Ideally switching over completely to https version by adding a new sitemap would make more sense as the http version of the sitemap would anyways now be re-directed to HTTPS. But the last thing i can is to get penalized for duplicate content. Could you please suggest as I am still a rookie in this department. If I should add the https sitemap version in the new site, should i delete the old http one or no harm retaining it.
Technical SEO | | ashishb010 -
Are .clinic domains effective?
We acquired a .clinic domain for a client, they are right now running under a .ca and I was just wondering if there were any cons to making the switch. On the flip side are there any pros? I've tried to search for the answer but couldn't seem to come across anything, thank you if you have any knowledge or could point me to a resource.
Technical SEO | | webignite0 -
Correct linking to the /index of a site and subfolders: what's the best practice? link to: domain.com/ or domain.com/index.html ?
Dear all, starting with my .htaccess file: RewriteEngine On
Technical SEO | | inlinear
RewriteCond %{HTTP_HOST} ^www.inlinear.com$ [NC]
RewriteRule ^(.*)$ http://inlinear.com/$1 [R=301,L] RewriteCond %{THE_REQUEST} ^./index.html
RewriteRule ^(.)index.html$ http://inlinear.com/ [R=301,L] 1. I redirect all URL-requests with www. to the non www-version...
2. all requests with "index.html" will be redirected to "domain.com/" My questions are: A) When linking from a page to my frontpage (home) the best practice is?: "http://domain.com/" the best and NOT: "http://domain.com/index.php" B) When linking to the index of a subfolder "http://domain.com/products/index.php" I should link also to: "http://domain.com/products/" and not put also the index.php..., right? C) When I define the canonical ULR, should I also define it just: "http://domain.com/products/" or in this case I should link to the definite file: "http://domain.com/products**/index.php**" Is A) B) the best practice? and C) ? Thanks for all replies! 🙂
Holger0 -
Umlaut in domain
Hi, My client wants to expand it's business to Germany and logically we need a domain name to match. We've found a great one and regsiterd several variants to it. However I just found out that in Germany it is possible (while here it's not) to register a domain with an umlaut. My question is: will google assign more value to: schädlinge.de than schadlinge.de when users search for schädlinge? If yes, how large will the difference be? (I will use an umlaut in the title etc) Kind regards,
Technical SEO | | media-surfer
Jason.0 -
Any way around buying hosting for an old domain to 301 redirect to a new domain?
Howdy. I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway! Basically DomainA.com is being retired, and DomainB.com is going to be launched. We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately. Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com? Thanks!
Technical SEO | | SamTurri0 -
Multiple Domains, Same IP address, redirecting to preferred domain (301) -site is still indexed under wrong domains
Due to acquisitions over time and the merging of many microsites into one major site, we currently have 20+ TLD's pointing to the same IP address as our "preferred domain:" for our consolidated website http://goo.gl/gH33w. They are all set up as 301 redirects on apache - including both the www and non www versions. When we launched this consolidated website, (April 2010) we accidentally left the settings of our site open to accept any of our domains on the same IP. This was later fixed but unfortunately Google indexed our site under multiple of these URL's (ignoring the redirects) using the same content from our main website but swapping out the domain. We added some additional redirects on apache to redirect these individual pages pages indexed under the wrong domain to the same page under our main domain http://goo.gl/gH33w. This seemed to help resolve the issue and moved hundreds of pages off the index. However, in December of 2010 we made significant changes in our external dns for our ip addresses and now since December, we see pages indexed under these redirecting domains on the rise again. If you do a search query of : site:laboratoryid.com you will see a few hundred examples of pages indexed under the wrong domain. When you click on the link, it does redirect to the same page but under the preferred domain. So the redirect is working and has been confirmed as 301. But for some reason Google continues to crawl our site and index under this incorrect domains. Why is this? Is there a setting we are missing? These domain level and page level redirects should be decreasing the pages being indexed under the wrong domain but it appears it is doing the reverse. All of these old domains currently point to our production IP address where are preferred domain is also pointing. Could this be the issue? None of the pages indexed today are from the old version of these sites. They only seem to be the new content from the new site but not under the preferred domain. Any insight would be much appreciated because we have tried many things without success to get this resolved.
Technical SEO | | sboelter0