본문으로 건너뛰기
cccskills
무료GitHub에 공개

keyword-stuffing

Audit web pages for excessive keyword repetition in body text, titles, metadata, and image descriptions. Report frequent terms and their density, identify hidden keyword text, and help rewrite repetitive passages into natural language focused on readers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

  • Checking articles for excessive keyword repetition
  • Editing repetitive AI-generated content
  • Reviewing titles, meta descriptions, and image alt text
  • Finding hidden text containing keywords

포함된 파일(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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

404-page

무료

Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a helpful custom 404 page
  • Adding search and navigation for broken links
  • Checking missing pages that return HTTP 200
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a website’s About page
  • Creating a page about the organization and its mission
  • Checking how operator information appears in rendered output
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Review accessibility coverage for shared components
  • Add accessibility checks to page flow tests
  • Run accessibility tests in CI
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility across the sign-in process
  • Checking verification code paste and autofill
  • Inspecting password reset and account recovery
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing form error announcements
  • Checking success message display duration
  • Auditing live update notifications
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing tables for screen reader accessibility
  • Checking header relationships in tables with merged cells
  • Reviewing table patterns in a design system
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

thedaviddias의 스킬 모두 보기

이 스킬의 문제 신고