Skip to content
cccskills
FreePublished on GitHubEnglish overview

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.

OriginalShow the original description

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.

Run score Not tested

See how to install

Good for

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

Overview

What it does

keyword-stuffing checks web pages for unnatural keyword repetition and helps rewrite it into natural prose. It examines body text, titles, headings, meta descriptions, and image alt text, then reports the five most frequent terms and their density percentages. Keyword lists without context and phrases embedded in hidden elements are also included in the review.

When it helps

Use it to check whether an article written with SEO in mind repeats the same words too often. It also helps edit repetitive passages in AI-generated writing and check whether image alt text actually describes the image. You can review the page's text alongside its titles and metadata.

Example requests

  • “Show the most frequent terms and their density in this article, then fix unnatural repetition.”
  • “Review the title, meta description, and image alt text.”
  • “Rewrite this AI-generated body text so it reads naturally without relying on the same keywords.”

Notes

The source uses thresholds such as keyword density above 3% as review signals. Context and readability are checked alongside the numbers. Hidden-text investigations examine computed CSS styles in browser DevTools, and readability checks also cover Flesch Reading Ease.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodRemoval is limited to keyword content in hidden elements, with instructions to inspect it using DevTools.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt calls for DevTools and Flesch Reading Ease, but does not specify a tool for calculating readability.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (2)

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

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

404-page

FreeSummary

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-Checklist74.6KUpdated Oct 6, 2026

about-page

FreeSummary

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-Checklist74.6KUpdated Oct 6, 2026

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-Checklist74.6KUpdated Oct 6, 2026

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-Checklist74.6KUpdated Oct 6, 2026

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-Checklist74.6KUpdated Oct 6, 2026

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-Checklist74.6KUpdated Oct 6, 2026

See all skills by thedaviddias

Report a problem with this skill