SEOClerks

Clear
Sign In Join

Keyword Density & Keyword Stuffing goes hand in hand? - How do you calculate this?

  • hitmeasap Level X5
    • 5

    Write the reason you're deleting this FAQ

    Keyword Density & Keyword Stuffing goes hand in hand? - How do you calculate this?

    A few months ago ajlancer made a topic about "What is Keyword density and SEO?"

    In that topic, this is stated:

    The ideal amount of keywords is 5-7%, though in practice, you can have up to 7-8% which will not likely have negative SEO consequences.


    That being said, I recently made a discussion about keyword stuffing. And this topic is simply just a question about these two. It seems like both of these goes hand in hand.

    However, how would you be able to calculate your keyword density? - What's the easiest way of doing that?

    And if you have 1000 words of content, then you could literally have between 50-70 keyword mentions, and even up to 70-80 keyword mentions. Or am I wrong?

    Best Regards,
    hitmeasap

    #Seo #Ranking #Keyword #Keywords #Rank #Google #Pagerank #Pr SEO
    Share post:

    Comments

    Please login or sign up to leave a comment

    Join
    TommyCarey

    TommyCarey

    The easiest way to calculate the keyword density of an article is to figure out how many keywords show up per 100 words of the article. You can also do 1,000 like you mentioned above, but more people write up 300 to 500 word articles because it's easier for them.

    Basically keyword density is a percentage game. I like to keep my keyword density around 3% and I'll never go higher than 5%. There are some people out there that say you can go as high as 12% but that's just ridiculous and you should never believe them lol Keyword Density & Keyword Stuffing goes hand in hand? - How do you calculate this? The higher your keyword density, the more unreadable your article will become. It will just look like you wrote the article to simply keyword stuff it, and that's never a good thing.

    When you're writing an article for your website or a marketing campaign you should always focus on the reader and not how the search engines will evaluate your writings. If you focus on the readers, you'll probably stay within the keyword density limits that Google is looking for. Make the article readable and not only your traffic will love it, Google will too Keyword Density & Keyword Stuffing goes hand in hand? - How do you calculate this? Having a keyword density that is high will make your post or article unreadable and your visitors will think less of your website. If you somehow got your article indexed and it's bringing in traffic, that doesn't mean you're winning. You could get ranked, but if your article has a super high keyword density, your traffic will leave pretty quick. This will increase your bounce rate and over time your article will drop a lot in the SERPs.

    A good way to optimize an article is to aim for a 3% keyword density and if you happen to get to 5% that's ok. Set some guidelines for yourself so that you don't get hit with any kind of penalties like keyword stuffing Keyword Density & Keyword Stuffing goes hand in hand? - How do you calculate this?
    9 years ago

    Are you sure you want to delete this post?

    Lynne

    Lynne

    Thanks for giving the actual way for working it out Razzy, I was wondering about that but never really investigated it properly.

    I also prefer 1000 word articles, but when I first started blogging I struggled to get a 300 - 500 word post written. It is amazing how much easier it has become to write longer posts now that I have been blogging for a while.
    9 years ago

    Are you sure you want to delete this post?

    idealmike

    idealmike

    Hmmm do Keyword Density & Keyword Stuffing go hand in hand with each other? I think that Keyword Density & Keyword Stuffing are two different things. Although they are both about content keywords, and they are both kind of connected to each other in some ways.

    Keyword Density
    This is a measure of how many repeated words are within your content. Basically what Raz said, a % of times a keyword or phrase appears on a web page compared to the total number of words on the page. From an SEO perspective, your keyword density is looked at to determine how relevant that web page is to the searcher, searching for those keywords or keyword phrases. With the general idea that the more times that those words or keywords or phrases appear on that page, the more relevant that page is to the people searching for those words, keywords or phrases. And because people know this, it makes them do things like....

    Keyword Stuffing
    This is a black hat technique of using the same keyword repeatedly many many many many times. Many many many times it's used in the meta information, and many many many times it's used in the alt and title tag of images and also of course, many many many times, and used within the actual content itself, many many many many many many times. You see what I done there right? Keyword Density & Keyword Stuffing goes hand in hand? - How do you calculate this? I'm trying to rank this web page for the word "many" and or "many many" and or "many many many many". So I'm using it many times on the page to make Google think this web page is very related to and relevant for that word or phrase.

    But it's usually easy to tell when someone has done this. It's easy to spot in the content when they keep saying the keywords over and over again many times. And I think Google is better at knowing this now too. It must look at that content and say okay, so it has these words on it quite a lot of times so it must be quite relevant and related to those words, but let's look at the backlinks and age of this as well and see just how good it is in the eyes of the world. Basically just meaning that it comes down to your backlinks as well.

    I think people should keep their Keyword Density within their content the same as they would in a title. It's not good to use the same keywords more than twice in a title in my opinion and in the content maybe 2-3 times. 4-5 at a push but make sure you have long content.
    9 years ago

    Are you sure you want to delete this post?

    Lynne

    Lynne

    Andre I honestly never check my keyword density when I write for my blogs. I simply put my keywords in the prime places, like the url, the meta title, meta description, the first and last paragraph, in some headings and then I just write naturally for the rest of the article. I highlight and underline some key phrases and that's it.

    I find this works well for me. In fact I just answered your question about what you could blog about and the website of mine that has grown the most in SEO terms this year is the one I have spent the least effort on ranking. I write there because I love it. Of course I do target a keyword or two but I seriously just write.

    I think writing for your audience is as important as keyword research and writing for SEO, so put that as a priority too.
    9 years ago

    Are you sure you want to delete this post?

    Corzhens

    Corzhens

    I have come across a discussion on keyword density with lots of comments that were mostly pointing to a percentage like for a 100-word article for the content 2% to 5% of the keyword’s appearance is the optimum number. My take on the density is to read the article yourself and you will notice if the keyword is being redundant and if not then it is okay. Write for the reader and not for the search engines.
    7 years ago

    Are you sure you want to delete this post?

    Order Now
    Process Time: 0.7456169128418

    Possible Duplicate queries found!
    MatchCountSQLScript
    SELECT * FROM `questions` as q JOIN categories_faq as c ON q.catid=c.CATID WHERE (q.status=1 OR (q.status=2 AND userid='') ) AND q.quesid='20616'1SELECT q.*, c.seo as CatSEO, c.name as CatName, c.parentid FROM `questions` as q JOIN categories_faq as c ON q.catid=c.CATID WHERE (q.status=1 OR (q.status=2 AND userid='') ) AND q.quesid='20616'

    		/opt/clerks-staging/docroot/viewfaq.php 496 () ()

    SELECT * FROM seoclerks.members WHERE USERID='6160'1SELECT * FROM seoclerks.members WHERE USERID='6160'

    		/opt/clerks-staging/docroot/include/functions/includes/member.php 445 GetAllUserDetails() ()

    SELECT * FROM seoclerks.members WHERE USERID=61601SELECT googleplus_profile FROM seoclerks.members WHERE USERID=6160

    		/opt/clerks-staging/docroot/include/functions/main.php 16914 GetGooglePlusProfileFromId() ()

    SELECT * FROM ratings_faq as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=20616 LIMIT 51SELECT m.username FROM ratings_faq as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=20616 LIMIT 5

    		/opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() ()

    SELECT * FROM answers a, seoclerks.members b WHERE a.quesid='20616' AND a.userid=b.USERID and b.status='1' AND a.status=1 ORDER BY a.combined_votes DESC, a.date_answered asc1SELECT a.answer, a.USERID, a.upvotes, a.downvotes, a.ansid, a.parentid, a.combined_votes, a.date_answered, b.username, b.userlevel, b.profilepicture FROM answers a, seoclerks.members b WHERE a.quesid='20616' AND a.userid=b.USERID and b.status='1' AND a.status=1 ORDER BY a.combined_votes DESC, a.date_answered asc

    		/opt/clerks-staging/docroot/viewfaq.php 1245 () ()

    SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112233 LIMIT 51SELECT m.username FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112233 LIMIT 5

    		/opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() ()

    SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112685 LIMIT 51SELECT m.username FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112685 LIMIT 5

    		/opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() ()

    SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112284 LIMIT 51SELECT m.username FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112284 LIMIT 5

    		/opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() ()

    SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112234 LIMIT 51SELECT m.username FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=112234 LIMIT 5

    		/opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() ()

    SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=168927 LIMIT 51SELECT m.username FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=168927 LIMIT 5

    		/opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() ()

    UPDATE questions SET total_views = total_views + 1 WHERE quesid='20616'1UPDATE questions SET total_views = total_views + 1 WHERE quesid='20616'

    		/opt/clerks-staging/docroot/include/functions/main.php 1765 update_Faqviewcount() ()

    SELECT * FROM questions WHERE quesid!='20616' AND status='1' AND (question like '%Keyword Density & Keyword Stuffing hand hand? - calculate this?%' OR question like '%Keyword%' OR question like '%Density%' OR question like '%&%' OR question like '%Keyword%' OR question like '%Stuffing%' OR question like '%hand%' OR question like '%hand?%' OR question like '%calculate%' OR question like '%this?%') -- ORDER BY RAND() LIMIT 151SELECT quesid, question, seo, userid FROM questions WHERE quesid!='20616' AND status='1' AND (question like '%Keyword Density & Keyword Stuffing hand hand? - calculate this?%' OR question like '%Keyword%' OR question like '%Density%' OR question like '%&%' OR question like '%Keyword%' OR question like '%Stuffing%' OR question like '%hand%' OR question like '%hand?%' OR question like '%calculate%' OR question like '%this?%') -- ORDER BY RAND() LIMIT 15

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() ()

    SELECT * FROM seoclerks.members WHERE USERID='1323' limit 11SELECT profilepicture FROM seoclerks.members WHERE USERID='1323' limit 1

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture()

    SELECT * FROM seoclerks.members WHERE USERID='840' limit 11SELECT profilepicture FROM seoclerks.members WHERE USERID='840' limit 1

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture()

    SELECT * FROM seoclerks.members WHERE USERID='337' limit 11SELECT profilepicture FROM seoclerks.members WHERE USERID='337' limit 1

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture()

    SELECT * FROM seoclerks.members WHERE USERID='632' limit 11SELECT profilepicture FROM seoclerks.members WHERE USERID='632' limit 1

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture()

    SELECT * FROM seoclerks.members WHERE USERID='1364' limit 11SELECT profilepicture FROM seoclerks.members WHERE USERID='1364' limit 1

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture()

    SELECT * FROM members_ledger WHERE script='/opt/clerks-staging/docroot/viewfaq.php' AND querystring LIKE '%id=20616%' AND added>=UNIX_TIMESTAMP(NOW())-1200 GROUP BY USERID 1SELECT USERID, username FROM members_ledger WHERE script='/opt/clerks-staging/docroot/viewfaq.php' AND querystring LIKE '%id=20616%' AND added>=UNIX_TIMESTAMP(NOW())-1200 GROUP BY USERID

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() ()

    SELECT * FROM categories1SELECT * FROM categories

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() parseRedundantQueriesCache()

    select * from categories_software order by name asc1select * from categories_software order by name asc

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_GetSoftwareCategories()

    select * from categories_wanttobuy order by name asc1select * from categories_wanttobuy order by name asc

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_wantcategories()

    select * from categories_wanttotrade order by name asc1select * from categories_wanttotrade order by name asc

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_tradecategories()

    SELECT * FROM seoclerks.members WHERE USERID='19821.png'1SELECT profilepicture FROM seoclerks.members WHERE USERID='19821.png'

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage()

    SELECT * FROM seoclerks.members WHERE USERID='306632.jpg'1SELECT profilepicture FROM seoclerks.members WHERE USERID='306632.jpg'

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage()

    SELECT * FROM seoclerks.members WHERE USERID='272.jpg'1SELECT profilepicture FROM seoclerks.members WHERE USERID='272.jpg'

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage()

    SELECT * FROM seoclerks.members WHERE USERID='600657.jpg'1SELECT profilepicture FROM seoclerks.members WHERE USERID='600657.jpg'

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage()

    select * from categories_faq order by name asc1select * from categories_faq order by name asc

    		/opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_GetFaqCategories()

    Invalid SQL

    count(*)sql1error_msg

    Expensive SQL

    Tuning the following SQL could reduce the server load substantially
    LoadCountSQLMaxMin

    Suspicious SQL

    The following SQL have high average execution times
    Avg TimeCountSQLMaxMin