Skip to main content

4 Core Patterns for SEO

  1. Relevance
    • Your content is relevant to keywords
    • On-page optimization
    • In the past, could just repeat keywords
      • Today, content keywords should be related
    • Think TOPIC Not keywords
    • Divide web pages by topics not by keywords
    • Many pages same topic—google will get confused
    • Aggregate keywords to topics
    • Identify primary keyword within topic
    • Topic in
      • Url's
      • Title tag
        • title tag
      • Header tags
        • <h1>⁣ – Best description of the web page
        • <h2>⁣ – Synonyms to topic
        • <h3+>⁣ – You don't have to optimize
      • Keyword density copy from results 1 – 5
        • How many times your keyword appear vs your total words in your page
        • Use tool tools.seobook.com/general/keyword-density
      • LSI Latent Semantic indexing
        • Prove you are on that topic if you discuss java interview tips, I guesstimate problem coding works would be in your page
        • Do search on Google on below see related searches could give ideas to similar keywords
        • Use tool http://lsigraph.com
        • Don't just include all synonyms just some
      • Image filenames / Alt tags
        • Are primary keywords
      • Outbound links
        • You do want to help your customers, right?
      • Create multiple pages around the topic if this was your main topic, you must have multiple pages surrounding the topic
        • They should all backlink your main page
  2. Crawlability
    • sitemap, internal links, external links
  3. Engagement
    • Customers don't just come to your website and leave it to other websites
  4. Authority
    • Backlinks from authoritative sites

Comments

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: http://amzn.to/2pwEuFJ 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