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.
Review the instructions the agent will receive before you install.
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.
<meta name="description"> — never reuse the same text across multiple pagesScan 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.
description prop through your SEO component instead of a static string.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.
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
No reviews yet. Tell others what you thought.
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.
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.
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.
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 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.
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.
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.