thedaviddias/Front-End-Checklist / skills/meta-description
meta-description
VerifiedUse when auditing page metadata or generating descriptions for new pages. Applies to every page that should receive organic search traffic.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.0 KB |
| references/rule.md | markdown | 3.1 KB |
SKILL.md
View on GitHub---
name: meta-description
description: "Use when auditing page metadata or generating descriptions for new pages. Applies to every page that should receive organic search traffic."
metadata:
category: seo
priority: high
difficulty: beginner
estimatedTime: "10"
source: frontendchecklist.io
url: https://frontendchecklist.io/rules/seo/meta-description
---
# Write a meta description for each page
A compelling meta description acts as organic ad copy in search results—well-written descriptions improve click-through rates even though they are not a direct ranking signal.
## Quick Reference
- Every page should have a unique meta description between 120–160 characters
- Meta descriptions are not a ranking factor but strongly influence click-through rates
- Write descriptions as a call to action that summarises the page value
- Google may override your description with content from the page
## Check
Check the <head> for a <meta name='description'> tag. Verify it is present, unique, and between 120 and 160 characters. Flag pages where it is missing, duplicated, or outside the recommended length.
## Fix
Add or update the <meta name='description' content='...'> tag in <head>. Write a unique summary of 120–160 characters that accurately describes the page content and includes a natural call to action or value proposition.
## Explain
The meta description appears as the short paragraph below the title in search results. Although not a ranking factor, a compelling description improves click-through rate, which can indirectly benefit rankings.
## Code Review
Check the <head> for <meta name='description' content='...'> element. Verify: (1) the element exists, (2) content attribute is non-empty, (3) length is between 70 and 160 characters, (4) no HTML tags inside content, (5) the description is unique (not the same as other pages).
---
For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.
Rule page: https://frontendchecklist.io/rules/seo/meta-description
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |