Skip to content

thedaviddias/Front-End-Checklist / skills/title-unique

title-unique

Verified

Use when applies to all HTML pages. Use when auditing a site crawl report or investigating why multiple pages compete for the same keyword in search results.

Keep page titles unique

Duplicate titles prevent Google from determining which page is the authoritative result for a given query, splitting ranking signals and reducing total organic visibility.

Quick Reference

  • Every page must have a <title> tag with content unique across the entire site
  • Duplicate titles cause search engines to arbitrarily choose which page to show for a query
  • Use page-specific keywords in the title: [Page Topic] | [Brand] pattern
  • Google rewrites titles that are too generic, too long (>60 chars), or keyword-stuffed

Check

Crawl all pages and extract <title> tag content. Group pages by identical title text and flag duplicates. Also flag pages with no title, empty titles, or titles matching the CMS default (e.g., 'Home', 'Page', 'Untitled').

Fix

Give each page a descriptive, unique title incorporating the page's primary keyword: [Specific Topic] – [Site Name]. For blog posts: use the post title. For products: use product name + key differentiator. For category pages: use the category name + context.

Explain

Explain how duplicate titles affect crawl budget, indexing prioritization, and keyword ranking; and why Google rewrites titles it considers misleading or non-descriptive.

Code Review

Review metadata generation, rendered HTML, structured data, and response headers related to Keep page titles unique. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.


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

Rule page: https://frontendchecklist.io/rules/seo/title-unique

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: 470kUpdated Claude CodeCodexVerifiedInstall
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: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall