本文へ移動
cccskills
無料GitHub で公開

keyword-stuffing

Use when auditing content pages for over-optimisation, reviewing AI-generated content that may repeat target phrases excessively, or checking meta tags and alt text for unnatural keyword accumulation.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.5 KB
  • references/rule.md4.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Avoid keyword stuffing

Google's spam detection algorithms penalise pages that unnaturally repeat keywords to manipulate rankings. Keyword-stuffed pages are demoted in search results or removed from the index entirely. Natural, reader-focused writing with topical variation outperforms keyword-dense content.

Quick Reference

  • Keyword density above ~2–3% for any single term is a signal of keyword stuffing — write for readers, not keyword counters
  • Repeating keywords unnaturally in titles, headers, alt text, or meta descriptions triggers Google's spam filters
  • Google's algorithms (Panda, SpamBrain) penalise pages with manipulative keyword density; natural language variation is rewarded

Check

Analyse the page's main content body, <title>, <meta name='description'>, heading elements (H1–H6), and <img alt> attributes. Flag: (1) Any single keyword or phrase appearing more than 3× in the title tag. (2) Any keyword with a density above 3% of total word count. (3) Lists of keywords with no context (e.g., 'cheap flights, affordable flights, discount flights, best flight deals'). (4) Alt text that is a comma-separated list of keywords instead of a description. (5) Hidden text (white text on white background, or display:none containing keywords).

Fix

  1. Rewrite keyword-dense passages using natural language variation:
    • Instead of repeating "SEO best practices" 8 times, use: "search engine optimisation", "ranking strategies", "organic search tips", "on-page SEO"
  2. Remove keyword lists from meta descriptions — write a single natural sentence.
  3. Fix keyword-stuffed alt text: replace "cheap flights london paris affordable flights" with "Passenger cabin view on London to Paris flight"
  4. If AI-generated content was used, review for repetitive phrasing and rewrite with varied terminology.
  5. Check for hidden text using browser DevTools CSS computed styles — remove any keyword content in hidden elements.
  6. Test the page's readability with the Flesch Reading Ease score — awkward keyword insertion lowers readability scores.

Explain

Google's Panda algorithm (now core to its main ranking system) and SpamBrain spam detection specifically target content with unnatural keyword density. Pages that appear to manipulate keyword frequency are demoted or removed from results. Google's documentation explicitly cites 'stuffing keywords into your content' as a violation of its quality guidelines. Natural writing that covers a topic comprehensively, using synonyms and related terms, outperforms keyword-dense content.

Code Review

Extract text content from the page body (strip HTML tags). Tokenise into words. Compute frequency of each unique word and common phrases (bigrams, trigrams). Flag any word/phrase appearing more than 3% of total word count. Also check <title>, <meta name='description'>, and alt attributes for repeated keywords. Report top 5 most frequent terms and their density percentages.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/keyword-stuffing

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

404-page

無料

Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.

日本語の概要は準備中です。原文の説明を表示しています。

thedaviddias/Front-End-Checklist7.4万2026年10月6日 更新

Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.

日本語の概要は準備中です。原文の説明を表示しています。

thedaviddias/Front-End-Checklist7.4万2026年10月6日 更新

Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.

日本語の概要は準備中です。原文の説明を表示しています。

thedaviddias/Front-End-Checklist7.4万2026年10月6日 更新

Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.

日本語の概要は準備中です。原文の説明を表示しています。

thedaviddias/Front-End-Checklist7.4万2026年10月6日 更新

Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.

日本語の概要は準備中です。原文の説明を表示しています。

thedaviddias/Front-End-Checklist7.4万2026年10月6日 更新

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

日本語の概要は準備中です。原文の説明を表示しています。

thedaviddias/Front-End-Checklist7.4万2026年10月6日 更新

thedaviddias のスキルをすべて見る

このスキルの問題を報告する