Series of posts over the next few months to say what I’ve found works and what doesn’t in SEO. So this is installment 1 in Top SEO Tools I Use.
So this is somewhat of a product endorsement piece but its also worth sharing with others what you’ve found useful and hopefully they’ll let you know what they have found useful. So Tools I use and even a few I don’t and why.
No the first tool has NOTHING to do with keywords but more importantly everything to do with deciding what your keywords are … if you think my life revolves around keywords you really need to catch up. Backlinks and anchor text are the hardest things to control and often the most impactful. Consider….back in the 2000s Miserable Failure was backlinked to George W Bush’s White House biography page by so many websites that he ranked number one on Google for Miserable Failure. Now I guarantee his site had NO SEO or optimization for Miserable Failure but he held that spot until a counter wave of links went to Jimmy Carter. Then Google manually shut the term war off. Its backlinks that make or break a sites ranking.
You can optimize all day long on content choices and keywords but if the rest of the world doesn’t think you are that in their links neither will Google. So the product is essential. It trends your links and competitors and its just $25 a month. Here are screenshots I have taken from time to time to include in reports to clients.
Notice the colored circles at the top break down the links and provide you with metric like CF TF and DA. Below that image you can see link by link and the strength of each link as well as no follow or follow status.
Below are more links since the site added more features. Under the status column the G shows if its indexed by Google with green as good and indexed, yellow as not indexed but not out right banned and finally red … the worst link and honestly its like being caught hanging out with the wrong crowd. Google even allows you to “disavow” the red Gs.
Image above trends you backlinks, your traffic and your keywords. This graph is also why I dont mind nofollow links and I believe they do affect ranking. Notice the tower of purple nofollow domains that linked to us when I released a news story. The orange keyword position swings up from 90 to 50 as the new position.
Lets start off skipping the title and saying what this is actually about. Ranking on Google search for a clients site. First off the site itself is just 2 months old, studies suggest it should take about 3 to 6 months to rank well. The site languished in the 30s … or page 3 for the first month but now its presenting a commanding ranking. Of the 283 keywords I track the site ranks in 211. Page 1 rankings now reach 19 on Google, 37 on Bing and 38 on Yahoo….UPDATE…I was looking at last weekends numbers. 27 on Google, 54 on Bing and 63 on Yahoo for page one results.
SEO isn’t marketing. Onpage SEO may be, but what does a marketing course teach us about the Offpage SEO which is backlink and server performance related? Top ranking sites need both and I’d argue that Offpage SEO is more important. Granted neither of the two halves will rank a site as the top result alone, but too often people focus on Onpage SEO and neglect the technical side of ranking.
Of course the top 3 positions of search results are the next step for the site I’ve mentioned above and feeling confident in content and Onpage SEO I’ve focused recently on the server side of things. Towards that goal I am testing a WordPress High Availability deployment.
This coupled with Cloudflare DNS and CDN is I think going to produce a server environment that’s obscene. For those who aren’t familiar with a CDN network here is a handy image explaining it.
I’ll update everyone on the effect of the sites rankings. The first kick in rankings which in the line graphs is where the trend really caught upward direction happened when I moved the site off of a shared hosting server to its own LAMP stack server. Essentially now I am dividing the stack across auto-scaling servers.
Here’s a the getting started guide as provided by Google.
This document aims to provide the information necessary to maintain and perform administrative tasks on your WordPress High Availability deployment from the Google Cloud Launcher
This solution leverages a few GCP features, which require certain APIs to be enabled in your project in order for Deployment Manager to successfully deploy these resources. The following APIs should be enabled before you deploy the solution:
The solution architecture is made up of 5 main components:
Below you can see an architecture diagram of how the components relate to each other.
There are two custom services running on the deployed machines that are essential for the solution to function properly. These services are gcs-sync (running on WordPress instances – both Admin and Content) and cloudsql-proxy (running on the SQL Proxy instances).
The gcs-sync service runs a script /opt/c2d/downloads/gcs-sync that, depending on the role the VM is assigned (Content or Admin), will check in with the GCS bucket tied to the deployment and determine if content needs to be pushed to or pulled from GCS. If you need to interact with the service, you can do so via systemctl. For example:
systemctl stop gcs-sync
will kill the script checking GCS, and the node will not receive any updates that come from the Administrator Node. Conversely, if the service needs to be started you can do so with the following command:
systemctl start gcs-sync
The cloudsql-proxy service makes use of the Cloud SQL Proxy binary so you can connect to your Cloud SQL instance without having to whitelist IP addresses, which can change when instances are deleted and recreated in a Managed Instance Group. The Cloud SQL binary is located at /opt/c2d/downloads/cloud_sql_proxy and the script that executes the binary is located at /opt/c2d/downloads/cloudsql-proxy. Like the service that runs gcs-sync, it can be interacted with using systemctl. Stopping the service can be done with:
systemctl stop cloudsql-proxy
At this point your instance will not be able to communicate with the Cloud SQL instance, and the application will not function. If you needed to manually start the service for any reason you can do so with the following command:
systemctl start cloudsql-proxy