Solving my SEO

I recently decided that I needed to put some focus into SEO techniques that are currently lacking on CodeTuple. During development SEO was something it was largely ignoring for the most part. I wanted to get a functional site up and running at the start. Now that I have all the basics in place for CodeTuple it was time put some focus into tightening up SEO. There are many services online that analyze your site and return back a wealth of information good and bad. I choose to use a service called to help me identify what may be missing and to steer me in the right direction in improving CodeTuple’s SEO.

Running an audit on CodeTuple with I found some interesting areas I need to focus in on. Overall I thought that CodeTuple rated pretty well, and that with a few hours spent on enhancing performance I could really improve CodeTuple. I was given an overall view of the failed and passed checks.


15 failed checks that need to be tended to. Now while I do claim to be a full-stack developer with moderate experience in SEO I must honestly state that it has been quite some time since I have been developing sites with SEO in mind. These days most popular blogging and CMS platforms take care of it all behind the scenes. One simple wordpress plugin and its all taken care of! Looks like there are some things I am about to learn.

Breakdown of the 15 failed checks:

  • Keyword Usage (Common keywords are not appearing in meta-tags to help identify the topic of the webpage)
  • <h1> Headings (Pages do not contain standard H1 headings which help tell the search engine the important topics on the page)
  • <h2> Headings (Pages do not contain standard H1 headings which help tell the search engine the important topics on the page)
  • Image Alt (Of 188 images on a wepage none of them contain and ‘alt’ attribute)
  • JS Error (One JavaScript error found)
  • Social Media Check (Website is not connected via API’s provided from Facebook, Google+, Twitter, Pinterest)
  • Page Objects (Page has more than 20 http requests which can slow down the page while loading)
  • CSS Minification (Some of the websites CSS files are not minified)
  • URL Canonicalization ( and should resolve to the same URL)
  • IP Canonicalization (Site’s IP does not redirect to your site’s domain name.)
  • HTTPS Test (Website is not using https)
  • Libwww-perl Access Test (Server appears to allow access from User-agent Libwww-perl.)
  • Microdata Schema (Webpage doesn’t use HTML Microdata specifications in order to markup structured data.)
  • SPF records (DNS server is not using an SPF record.)

So looks like i have some work on my hands. If i am honest most of these i would not have picked up on myself. Possibly the H1, H2 headings and the JS Error via the chrome console. Overall I am relatively please with my progress so far. I am certainly please with services like

Full report download:

Let’s see how i get on!


Continue Reading