Monthly Archives: June 2013

Using Call To Action (CTA) In WordPress

The HubSpot software is pretty good with using call to action messages when creating blog posts.  HubSpot users can create many different CTA messages, and they can be inserted into posts as they see fit.  Or a user can set it to where a set of CTA buttons are randomly inserted after a blog post.  It’s a nice system.

call to action

call to action

But what happens if you move your blog from HubSpot and on to WordPress?  Well, there are several options one could take to incorporate call to action buttons after moving from .

First, you could just enter them in an individual post.  This is by far the easiest route to take, but it has some drawbacks.  The main drawback being that if you have the same CTA button in several posts and want to change them all, you’ll have to edit each and every post manually.   Or you could do a database search and replace, but that method is usually beyond the abilities of most people.

Second, you could use a WordPress plugin geared for this purpose.  , and some may not suit your purposes at all.  For example, I’ve seen one WordPress CTA plugin that is configured to place your message in the sidebar via a widget.  That may be fine for some people, but most people tend to want to insert their CTA message at the bottom of their blog posts.

In addition to the many free WordPress CTA plugins, there are some premium call to action plugins that look very promising.  The looks like it would be a good fit for most people, and it’s reasonably priced at $50.

Lastly, you could code the ability to insert a call to action message in your blog posts directly into your WordPress theme.  This is a route I’ve taken in the past, and it has worked well.

wordpress call to action feature

WordPress call to action feature

What you see above is an example of how I’ve created a simple call to action system in a WordPress site in the past.  The site owner can enter in the CTA script or code in the box, and this is then automatically inserted after every blog post on the site.  The owner can also change this code at any time when they want to use a different button, image, or script.

I have expanded on this system to include the ability to override or delete the primary CTA code on a per post basis.  That way, the site owner isn’t stuck with the same action message on every post; they can have something different from the default, or display none at all.

This just goes to show that migrating from HubSpot to WordPress doesn’t mean you have to give up the ability to influence visitors to take specific actions on your site.  There will always be a way to continue your marketing on WordPress.

Redirects Can Make Or Break Your Migration

About 2 months ago I was approached to do a migration from HubSpot to WordPress.  I spoke with the prospective client’s agent several times over the course of a few days.  During this process, I did a pretty thorough examination of the HubSpot site to be migrated, including creating a list of all the URLs in his site that would need to be transferred to WordPress.  In the end, the client chose to go with a different provider to migrate their website.

Recently, I decided to follow up on this lost project.  I typed in the url of his website and saw that the website was now on WordPress and no longer on HubSpot.  Curiosity got the better of me, so I decided to investigate his site a little just to see how well of a migration this turned out to be.

I still had the list of URLs I created a while back, so I tried some of them out to see if the proper redirects were set in place.  Much to my shock, I kept getting the dreaded 404 page for so many of the old URLs I entered.

And to make matters worse, every link this former prospective client posted to his blog on Twitter kept bring me the, “Oops! That page can’t be found” message.  This is really, really not good. Broken backlinks are never a good thing

When migrating a website to WordPress, it is very important to ensure that the proper redirects are in place.  301 redirects make your visitors happy, keep search engines happy, and they maintain the value of any and all incoming links.

For example, let’s say you have a blog post with the url of something like http://yoursite.com/blog/bid/67283/my-super-blog-post.  Over time, let’s also say 20 other websites link to that blog post.  Those links help increase the ranking of that blog post associated with that URL.

If that blog post’s URL changes during a migration, and you don’t have the proper redirect in place, then all the value from those incoming links are gone.  Those links are pointing to an address that doesn’t exist anymore.  But with a 301 redirect in place, the value of those links are maintained, and all remains well and good in the world.

When a website receives a slew of 404 errors, especially to pages/posts that have incoming links, it hurts your website’s overall SEO.  The search rankings for your content will drop, and so will the search traffic that came with them.

Your blog is a highly effective tool to improving your business.  And if you migrate your blog from one platform to another, avoid the proverbial wooden stake to the heart by making sure every URL change is covered by proper 301 redirects.