My wife started a food blog this weekend and decided to use the “Scrappy” WordPress theme by Caroline Moore. But like all WordPress themes, there are a few customizations that are usually made to personalize the theme, the first of which is removing “Powered by WordPress” in the footer.
The first thing to do to customize the Scrappy footer is make a copy of the footer.php file from the Scrappy theme and place it in your child theme folder. It is this file that we will modify in order to remove “Powered by WordPress” and the reference to the Scrappy theme name.
Comment out code within the “site-info” section of the footer
Within the footer code, there is a <div> section that references site-info:
<div><?phpdo_action('scrappy_credits');?><ahref="<?phpechoesc_url(__('http://wordpress.org/','scrappy'));?>"title="<?phpesc_attr_e('A Semantic Personal Publishing Platform','scrappy');?>"rel="generator"><?phpprintf(__('Proudly powered by %s','scrappy'),'WordPress');?></a><span> | </span><?phpprintf(__('Theme: %1$s by %2$s','scrappy'),'Scrappy','<a href="http://carolinemoore.net/" rel="designer">Caroline Moore</a>');?></div><!-- .site-info -->
What we want to do is comment out the code, starting at the first php reference and ending after the “Caroline Moore” line. We can do this using the <!- and ->codes. When the code is commented out correctly, it will look like the following:
<a href="<?phpechoesc_url(__('http://wordpress.org/','scrappy'));?>" title="<?phpesc_attr_e('A Semantic Personal Publishing Platform','scrappy');?>" rel="generator"><?phpprintf(__('Proudly powered by %s','scrappy'),'WordPress');?></a>
<span> | </span>
<?phpprintf(__('Theme: %1$s by %2$s','scrappy'),'Scrappy','<a href="http://carolinemoore.net/" rel="designer">Caroline Moore</a>');?> -->
Be sure to hit “Save” to your footer.php file after making the comment changes, and you’re all done: no more “Powered by WordPress”!
Original "Scrappy" footer - Powered by WordPress
Modified WordPress Scrappy footer (with slightly different pattern!)
Adding your own footer text
If you want to add your own footer text, like a copyright statement, you can add any HTML code you want within the same section of code where we just commented out code. For an example of how to add a copyright statement, see the bottom of my prior blog post about modifying the footer of the WordPress Twenty Eleven theme.
That’s it! One step closer to making the WordPress Scrappy theme your own.
If you’ve spent any time working in digital marketing or analytics, you’re already familiar with the power of A/B testing. A/B testing (and it’s more complicated brother multivariate testing) allows site owners to find out optimal combinations of site design and content for their visitors without having to directly ask/inconvenience the user. All it takes to improve a website is forming a hypothesis of something that could work better, creating multiple versions of a page (or other content), setting up the experiment…and the money flows in faster than you can count it. At least, that’s the hope!
Getting Started - Sign up
The first step to installing Optimizely is to sign up. A 30-day trial is provided, but you do need to put in a credit card to activate the free trial.
After doing so, when you click on the “Implementation” button, a pop-up shows you your customized “single line of code” to implement.
Installing Optimizely code snippet in WordPress Header
When you click on the ‘Implementation’ link, you’ll get code that looks like the following:
What we want to do is install this code in our WordPress header, pretty much after the first <head> tag. By placing the code as high as possible in the WordPress header, this gives Optimizely the ability to affect your website as soon as the page starts loading, and assures that your site visitors don’t notice anything happening before their eyes!
The only consideration you need to make when installing the code snippet is whether your site is already running jQuery or not. You can determine this by looking in the header of your WordPress site to see if there are any scripts that say something like jquery-xxxx.js. If you don’t see any jQuery references in the header, you don’t need to do anything: Optimizely already includes jQuery! If you already have jQuery installed, be sure to place the Optimizely code snippet after the WordPress jQuery reference. Then, go to the Optimizely website, click on the My Experiments" -> "View All Experiments" - > "Project Code" menu to change the jQuery settings to “Do not include”.
After you place the code snippet line in the header and hit save, that’s it! You’ll be able to start using Optimizely to create experiments.
Integrating Optimizely with Google Analytics
In order to track your Optimizely experiments within Google Analytics, no code changes need to be made. The only thing you need to do is make sure you have the asynchronous version of the Google Analytics code installed and a free custom variable slot. Then, within the Optimizely interface, you can choose which custom variable to write your data to and you’re done.
Of the hundreds of stock reports and capabilities present within Adobe (Omniture) SiteCatalyst, calculating year-over-year growth isn’t the easiest thing to do. And while conversion reports (eVars) have the “Compare Dates” functionality within the calendar menu, we can’t quickly plot the difference between two time periods within a dashboard. This is where the Omniture SiteCatalyst Target report comes in handy.
Setting up your “Goal”
Within the Omniture Knowledge Base KB2153, I think Omniture does a disservice by stating:
Targets are quantifiable goals that you can place within the SiteCatalyst interface and compare against reports.
While this is a true statement, I think one of the reasons that the Omniture SiteCatalyst Target report isn’t more widely used is that it doesn’t have to be a future “goal” per se, any set numbers can be used. When last year’s numbers are used, the report becomes a year-over-year comparison!
For this example, I’m going to be comparing page views year-over-year. Here’s what the page views summary by month looks like for 2011:
Omniture Page Views Report - 2011
Using this report to set a year-over-year target, we can see the early months are in the few thousands of page views, increasing to 12,000 -14,000 later in the year.
Assuming you are using Omniture SiteCatalyst v15, you set up a Target report under Favorites -> Targets -> Manage Targets, then choose Add New once you’re in the Targets menu. I’ll be setting up a monthly target for Page Views, so I’ll just type it in instead of using the file upload capability. For this example, we want to apply this target to “Entire Site” for the “Page Views” Metric. The date range will be all of 2012, with “Monthly” granularity. This will give you 12 boxes to type in the 2011 Page View results, and once we hit “Ok” to save, we’ll have our year-over-year report set up.
Getting the Year-over-Year graph within Omniture
Showing the results of our newly created Target report is as easy as going to Favorites -> Targets, then choosing the appropriate Target. By default, the report will show like a normal metric report, with a green overlay for your targets:
Default view of Omniture SiteCatalyst Target report
The above report shows that Page Views for January 2012 are well above our January 2011 “Target” and that February has already exceeded the goal as well…which is great since we’ve got 7 more days left in the month!
If we want to show the year-over-year delta, however, we can choose the “Variance” report option at the top of the graph. Doing so will show the following report:
By placing this report in a dashboard, we can quickly evaluate whether Page Views have grown by month year-over-year. It’s disappointing that the only graph option Adobe provides is the raw metric higher/lower than the target instead of a percentage difference view, but the percentage difference is calculated as part of the data table view that goes along with this report.
When talking about “growth” many businesses aren’t content with just year-over-year growth, usually aiming for 10%, 20%…10,000% growth. These are goals that work well to track within the Omniture SiteCatalyst Target report. But year-over-year growth can be worth monitoring too, and the Omniture SiteCatalyst Target report is a great way to do so.