Write for recognition
Name the specific page, not merely the organisation. A visitor comparing several tabs should be able to distinguish a product page from pricing, support or an article.
Put the information that differentiates the page early. A brand name can follow when it adds trust or context. There is no universal character count that creates rankings; display space varies by device, query and characters used.
Keep every important page distinct
Repeated titles make separate URLs look interchangeable. Templates should combine page-specific information with a consistent brand pattern, while allowing exceptional pages to use language that fits their purpose.
A title should agree with the visible primary heading without having to copy it word for word. A dramatic mismatch can disappoint visitors even when the markup is technically valid.
Implement the document title
Plain HTML uses one title element inside head. In Next.js App Router, prefer the Metadata API so titles participate in layouts and templates.
<!-- HTML -->
<title>Delivery information — Northwind Cycles</title>
// Next.js App Router
export const metadata = {
title: "Delivery information",
};Review it in context
Check the rendered source, not only a CMS field. Confirm that client code, a layout template or an SEO plugin has not replaced the value, and inspect important pages for accidental duplication.