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
      • 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
        • 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


Popular posts from this blog

Functional Programming in Scala for Working Class OOP Java Programmers - Part 1

Introduction Have you ever been to a scala conf and told yourself "I have no idea what this guy talks about?" did you look nervously around and see all people smiling saying "yeah that's obvious " only to get you even more nervous? . If so this post is for you, otherwise just skip it, you already know fp in scala ;) This post is optimistic, although I'm going to say functional programming in scala is not easy, our target is to understand it, so bare with me. Let's face the truth functional programmin in scala is difficult if is difficult if you are just another working class programmer coming mainly from java background. If you came from haskell background then hell it's easy. If you come from heavy math background then hell yes it's easy. But if you are a standard working class java backend engineer with previous OOP design background then hell yeah it's difficult. Scala and Design Patterns An interesting point of view on scala, is

Alternatives to Using UUIDs

  Alternatives to Using UUIDs UUIDs are valuable for several reasons: Global Uniqueness : UUIDs are designed to be globally unique across systems, ensuring that no two identifiers collide unintentionally. This property is crucial for distributed systems, databases, and scenarios where data needs to be uniquely identified regardless of location or time. Standardization : UUIDs adhere to well-defined formats (such as UUIDv4) and are widely supported by various programming languages and platforms. This consistency simplifies interoperability and data exchange. High Collision Resistance : The probability of generating duplicate UUIDs is extremely low due to the combination of timestamp, random bits, and other factors. This collision resistance is essential for avoiding data corruption. However, there are situations where UUIDs may not be the optimal choice: Length and Readability : UUIDs are lengthy (typically 36 characters in their canonical form) and may not be human-readable. In URLs,

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