跳到正文
cccskills
免费在 GitHub 公开

duplicate-description

Audit page descriptions used for search results, identify text reused across URLs, and write descriptions specific to each page. Review CMS settings and shared templates so each route outputs its own description in the final HTML.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use when auditing a site's meta tag uniqueness, generating page-specific meta descriptions, or reviewing CMS templates that inject the same description globally.

查看安装方法

适用场景

  • Auditing duplicate page descriptions across a site
  • Writing descriptions for individual articles
  • Reviewing shared SEO component settings
  • Checking site-wide description defaults in a CMS

包含的文件(2)

  • SKILL.md2.7 KB
  • references/rule.md4.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Avoid duplicate meta descriptions

When multiple pages share the same meta description, Google ignores them and generates its own snippet, often pulling unrelated text. Unique descriptions improve click-through rates from search results and help users quickly understand what a page offers.

Quick Reference

  • Each page must have a unique <meta name="description"> — never reuse the same text across multiple pages
  • Google may auto-generate snippets when descriptions are duplicated or missing, often producing worse results
  • Target 50–160 characters; craft descriptions that describe the specific page, not the site

Check

Scan the HTML of every page for <meta name="description" content="...">. Identify any description value that appears on more than one URL. Flag pages using the same description as another page, and flag pages where the description matches the site tagline or homepage description.

Fix

  1. List every page with a duplicate meta description.
  2. For each page, write a unique description that summarises that page's specific content (50–160 characters).
  3. In Next.js/React, pass a dynamic description prop through your SEO component instead of a static string.
  4. In WordPress/CMS, disable site-wide description fallback in your SEO plugin (Yoast, RankMath) and set per-post descriptions. Example of a unique description per page:
  • Homepage: "Front-End Checklist helps developers build faster, more accessible, and better-ranked websites."
  • Blog post: "Learn how canonical tags prevent duplicate-content penalties and consolidate PageRank across URL variants."

Explain

Duplicate meta descriptions tell Google the pages are interchangeable, diluting search visibility. Each page competes in search for different queries, so the description must match the page's unique intent and content to earn a relevant snippet and a higher click-through rate.

Code Review

Check that no two <meta name="description"> tags in the rendered HTML across different routes share identical content values. Confirm the description is set dynamically per route in the framework's head management (e.g., Next.js metadata export, Nuxt useHead).


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

Rule page: https://frontendchecklist.io/rules/seo/duplicate-description

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 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 的全部技能

报告此技能的问题