Skip to main content

The Core of SEO

This is a summary from book “3 Months to No.1: The “No-Nonsense” SEO Playbook for Getting Your Website Found on Google” /

The core of SEO. Basically, all we do with SEO is that we optimize for keywords.  When we optimize for a keyword, we mean one or multiple search terms, that the customers would search for. This is where the battle happens, and it's a zero-sum game. Meaning if you want to beat someone from being at the first place on Google, a search results, you would need to remove in from there. 

In SEO, we optimize for 3 types of keywords:

1. Information

2. Commercial

3. Brand.

With informational customers are just searching for information while in commercial customers are actually looking to solve a problem they have fixed a door in their house, in branded keywords customers are looking for a specific brand.

We want to:

1. Find keywords in one of first 3 categories.

2. Rule out keywords that we wouldn't have the budget to fight for.

Estimate what happens if you are number 1

Then, once you have found the relevant keywords you want to estimate what would happen if you are now number 1 on Google, how much money you would make for this we have tools that would assist us, one of these tools is named SEMRush.

To look for good keywords we can just brainstorm for keywords put yourself in the shoes of the customer and ask yourself what would you search for, don't try to be too clever, aim for regular customers with most traffic?  For keyword suggestion and ideas, you can also use Uber suggest tool.

The next step after you have found candidate keywords is the bottom line, how much money would you make if you get to first position in google with these keywords, you want to first find keywords that would actually make you money and only then put months in optimizing them?

For that purpose, again we use SEMRush tool with this way you have a glance into the currently first position in google first ranked website, and then you can calculate how much money you would make if you get to this first position.


Popular posts from this blog

Dev OnCall Patterns

Introduction Being On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering b

SQL Window functions (OVER, PARTITION_BY, ...)

Introduction When you run an SQL Query you select rows, but what if you want to have a summary per multiple rows, for example you want to get the top basketball for each country, in this case we don't only group by country, but we want also to get the top player for each of the country.  This means we want to group by country and then select the first player.  In standard SQL we do this with joining with same table, but we could also use partition by and windowing functions. For each row the window function is computed across the rows that fall into the same partition as the current row.  Window functions are permitted only in the  SELECT  list and the  ORDER BY  clause of the query They are forbidden elsewhere, such as in  GROUP BY ,  HAVING  and  WHERE  clauses. This is because they logically execute after the processing of those clauses Over, Partition By So in order to do a window we need this input: - How do we want to group the data which windows do we want to have? so  def c

Ry's Git Tutorial BOOK Review

Ry's Git Tutorial BOOK Review There are many good books about git but  Ry's Git Tutorial stands out as an amazing git tutorial book  I will describe below why: I want to stress out although I'm going to list below what this books talks about that is not the reason you should read this book.   The reason you should read this book is that it's crystal clear about git! it's just an amazing book, it's fun to read, and I truly get to understand git. It very clear, Ry's manages to bring us closer to git by making things really clear. Ry's makes an outstanding effort to bring us from knowing nothing about git to being an expert. The book starts with the real basics like Initializing the repository on an example website, staging files, exploring the repository. Then he moves on to  undoing changes  and he scans various ways you can undo your changes: viewing old revisions, tagging release, undo commit stages etc. Branches