Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the genesis domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/darren/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":8162,"date":"2013-08-21T06:00:05","date_gmt":"2013-08-21T10:00:05","guid":{"rendered":"https:\/\/darrenslaughtercom.stage.site\/?p=8162"},"modified":"2013-08-21T06:00:05","modified_gmt":"2013-08-21T10:00:05","slug":"two-tools-every-contractor-website-should-have","status":"publish","type":"post","link":"https:\/\/darrenslaughter.com\/two-tools-every-contractor-website-should-have\/","title":{"rendered":"Two Tools Every Contractor Website Should Have"},"content":{"rendered":"

\"1199157221_4c9c6d67f5\"<\/a>Contractor websites<\/a> (and their designs) are no different from any other site on the interwebs. A lot of emphasis on where your site ranks in Google depends on visitor \u201cstickability\u201d<\/em>. This is a measure of how long visitors stay and how many of your pages they visit. The longer they stay and the more pages they look at, the better it is for you.<\/p>\n

Follow the bouncing ball<\/strong><\/p>\n

When people leave your website, this increases what Google calls your \u201cbounce rate\u201d. Don\u2019t confuse bounce rate with the \u201cexit rate\u201d, which gives a ranking to whichever page the visitor exits from.<\/p>\n

How the bounce rate is worked out can be incredibly complicated: e.g. \u201cBounce Rate = total number of visitors viewing a single page divided by total number of visits greater than or equal to the average variable page load speed\u201d. The take away here is that a high bounce rate is bad; a low bounce rate is good.<\/p>\n

Google Analytics & Webmaster Tools<\/strong><\/p>\n

To get an accurate picture of what\u2019s happening on your website \u2013 including your bounce rate \u2013 you need to install Google Analytics. This is a free service that will also tell you how many visitors you\u2019ve had on a given day, where they came from, how long they stayed, and a ton more useful information you really need to have.<\/p>\n

Some \u201cexperts\u201d claim that Google uses Analytics to spy on webmasters. This might possibly be true to a degree, but if you’ve got nothing to hide, what’s the problem?<\/p>\n

If your website has decent content and operates within Google\u2019s terms and conditions, then signing up can be a positive advantage. It gives you access to information Google already has anyway, and which you\u2019ll need in order to fully implement your SEO program.<\/p>\n

Curbing a High Bounce Rate<\/span><\/strong><\/p>\n

Once you start receiving data from Google Analytics you\u2019ll be able to see what your bounce rate is. Anything over 60% means you\u2019re in trouble; 40-60% is \u201cOK but needs working on\u201d; below 40% is manageable.<\/span><\/p>\n

So how do we lower a high bounce rate? The object of the exercise is to stop people leaving your site too quickly. The solution comes in two stages: capturing them when they arrive and keeping them informed and entertained once they are there. You need to ensure that your site:<\/span><\/p>\n