Skip to main content

Be Careful When Republishing Blog Contents

One of the features of blogs, which a lot of blog owners seem to take for granted, is the maintaining of the posts and structure of the blog.

With a static website, you design the URL structure, and you publish the pages in the website to the URLs as you wish. If you link the various pages to each other, this requires that you keep a glossary, of the URL of each page.

The larger your website gets, the more painful a task this becomes. Make a mistake with one URL, and you have a broken link. Search engines don't like broken links - so if you want your website to be featured in search result pages, you want to minimize broken links.

One of the advantages of publishing a website, using a blogging platform, is the blogging infrastucture.

You provide the title of a post, and the URL is created and cataloged for you. With a Blogger blog, you can use the "Edit Posts" menu as a catalog of posts, and their URLs.

Blogger controls post URLs - and prevents duplicate URLs from being developed.

The downside here is that Blogger controls the URLs of the posts.

If you republish posts - maybe after you export then import them, or delete then readd them, or even change the Archiving option for the blog, you will end up with changed URLs. This was a challenge seen by a few blog owners this year, as they migrated their Blogger blogs from external hosting (FTP publishing) to Google hosting (custom domain publishing).

Republishing a blog to a new URL will lead to broken links.

If your blog is indexed by the search engines, and you republish the blog, you're going to end up with broken links in the search engines, caused by changed URLs.

Your prospective readers will click on an interesting SERP entry, and get a "Not Found". This won't encourage them to keep reading your blog, the search engines will drop the reputation, and you'll get less new readers.

Different content hosts will use different URL formats, for the posts.

This will also be a problem if you move hosting of your blog to another service.

Even if you can transfer a (non BlogSpot published) custom domain to another blogging platform, there will be differences in how the URLs are cataloged and generated, for each blogging service. No matter what you do, you will end up with broken links, and decreased search engine reputation.

If you move blog hosting, this won't cause major damage to the search engine reputation - at least as badly as renaming the URL of the blog. The search engines will continue to index the blog under the existing URL.

A blog is successfully renamed, with broken links minimised.

The success of moving blog hosting requires a minimised amount of broken links.

If you contemplate relocating or republishing the blog, look at the URL structure of the blog right now, at the possible changes, and at the possible effects from the changes. Make your decisions objectively.


Teri K said…
Can you please tell me what exactly counts as replenishing blog contents? Does any change I make -- like fixing a typo? Does changing my sidebar have anything to do with it? Or is it just when I remove a post and then re-add it?
Thanks again for your always great help. Without you I would have given up blogging long ago.
So, you're saying there is no way to prevent this problem aside from making no changes ever in your blog hosting or setup? If one wanted to change blog hosting would one have to start fresh and maybe notify all followers that this is what is happening?
Nitecruzr said…

As long as you don't change the base URL of the blog, the search engines won't be reindexing it from the bottom up - so it won't be like renaming the blog. You won't start out with Page Rank 0.0000000.

But you're going to have differences in the URL structure overall - and yes, this will cause broken links. You just have to be aware of the challenges, before you cause your problems.
Nitecruzr said…

Here I am referring to any change to the blog that causes a change in the post URLs. Fixing a typo, or changing the sidebar, won't cause any change to the post URLs.

However, if you remove and re add a post - yes, this will cause a URL change.
Admin1 said…
very useful info! I havent ever been to this blog before but, am so glad I came across it. I even had 2 questions answered just from a few readings! :) thanks!
Mary Brueske said…
Great site.....loved the post. Almost attempted this very idea but I'm reconsidering thanks to your blog. Appreciated!

Popular posts from this blog

What's The URL Of My Blog?

We see the plea for help, periodicallyI need the URL of my blog, so I can give it to my friends. Help!Who's buried in Grant's Tomb, after all?No Chuck, be polite.OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Leave Comments Here

Like any blogger, I appreciate polite comments, when they are relevant to the blog, and posted to the relevant article in the right blog. If you want to ask me a question thats relevant to blogging, but you can't find the right post to start with (I haven't written about everything blogger related, yet, nor the way things are going I don't expect to either), ask your questions here, or leave an entry in my guestbook.

As noted above, please note my commenting policy. If you post a comment to this post, I will probably treat it as a "Contact Me" post. If you have an issue that's relevant to any technical issue in the blog, please leave a comment on the specific post, not here. This post is for general comments, and for non posted contact to me.

If the form below does not work for you, check your third party cookies setting!

For actual technical issues, note that peer support in Blogger Help Forum: Something Is Broken, or Nitecruzr Dot Net - Blogging is, almos…

What Is "" vs. ""?

With Google Domains registered custom domains becoming more normal, we are seeing one odd attention to detail, expressed as confusion in Blogger Help Forum: Learn More About Blogger.My website uses "" - am I supposed to use "", instead?It's good to be attentive to detail, particularly with custom domain publishing. This is one detail that may not require immediate attention, however.