Forums Forums White Hat SEO How to avoid keyword stuffing in an article when you have to use the keyword to describe the topic?!

  • How to avoid keyword stuffing in an article when you have to use the keyword to describe the topic?!

    Posted by seohelper on July 20, 2020 at 5:21 pm

    So I just wrote a killer decked out SEO article however I run it through keyword density checker and it’s flagging me as KW stuffing… which I suspected may happen.

    The thing is I didn’t purposely stuff the keyword. The article is on how well (XYZ [keyword]) works and it’s hard to describe “XYZ Keyword” without using “XYZ Keyword”.

    So what’s the work around to this issue?

    Do I use similar terms to describe the same thing

    For example let’s just pick a topic, let’s say alternative medicine. Would you use “Natural Medicine” and “Complimentary Medicine” in place of Alternative Medicine to avoid KW stuffing?… Or is it better to say alternative medicine (AM) and just use the abbreviation AM from then on?

    Both of those seem lame when I just want to use what the thing is actually called to describe it.

    Or am I overthinking and I just need to write a good article that’s optimized and forget about every tiny detail?

    Gentii77 replied 5 years, 5 months ago 1 Member · 2 Replies
  • 2 Replies
  • Jeff-in-Bournemouth

    Guest
    July 20, 2020 at 6:03 pm

    If you are speaking to a friend, you don’t need to keep repeating the name of the thing you are discussing,.

    Because you both know what you are discussing.

    Write articles as if you are speaking to a friend.

  • Gentii77

    Guest
    July 20, 2020 at 9:13 pm

    If you want to rank higher for a given keyword you can use it naturally without sounding weird and you can also use LSI words ( Latent Semantic Indexing) that are words that are quite similar to the keyword you want to rank higher for example, if your keyword is cars you can use other words that are related for example engine, tires and so on.

    Hope I answered your question

Log in to reply.