On a 50-page site, you can write every title and meta description by hand. On a site with 20,000 products, 3,000 categories and a blog, nobody does. Titles and descriptions come from templates, and a single template decision affects thousands of results at once.
That is good news when the template is right and a quiet problem when it is not. It becomes a loud problem after a migration, when a new platform ships with new defaults and nobody checks them.
How Google uses titles and descriptions
Two facts shape everything else.
Titles are a strong input, not a guarantee. Google generates the clickable title in results, called the title link, from several sources: the <title> element, the main visible heading, h1 and other headings, og:title, prominent text on the page, anchor text and WebSite structured data (Google Search Central). Your <title> is the main lever, but Google can choose another source when the title does not describe the page well.
Meta descriptions are optional input for snippets. Google says it primarily uses the content on the page to generate snippets, and sometimes uses the meta description when it gives a more accurate summary. A good description can still shape what users read, so it is worth doing well, but it does not control the snippet.
Why Google rewrites titles, and what that says about templates
Google lists the common issues that lead to rewritten title links. Almost all of them are template problems:
| Issue described by Google | How it usually appears at scale |
|---|---|
| Half-empty titles | A variable is empty: “| Brand” on products without a name field |
| Obsolete titles | A hardcoded year in a template that nobody updated |
| Inaccurate titles | Category template reused on filtered pages that show different products |
| Micro-boilerplate | Hundreds of titles that differ by one word, or not at all |
| No clear main title | Several headings with the same visual weight |
| Language mismatch | Titles in English on pages whose content is in German |
If you see many rewritten titles in a section, look at the template behind it before editing individual pages.
Designing title templates
A good title template combines the page’s distinctive information with a short brand suffix. Google recommends titles that are descriptive and concise, unique per page, without keyword stuffing, with the site name added concisely at the start or end, separated by a delimiter.
Some practical patterns:
- Product page:
{Product name} {key attribute} | {Brand}, for example “Oak dining table 180 cm, extendable | Maison Lumen”. - Category page:
{Category} {qualifier} | {Brand}, for example “Outdoor lighting for terraces | Maison Lumen”. - Article:
{Specific headline}, with the brand suffix optional when the headline is already long.
On length: Google sets no limit on the title element, but truncates title links to fit the device width. Rather than enforcing a strict character count, put the distinctive words first so truncation removes the brand, not the product.
Plan fallbacks for missing fields. If {key attribute} is empty, the template should drop it cleanly instead of leaving a dangling separator.
Designing description templates
For large sites, Google explicitly says that programmatic generation of descriptions can be appropriate and is encouraged, while warning that identical or similar descriptions on every page are not helpful.
A useful description template pulls in facts specific to each page: price range, number of items in a category, materials, location, author, date. For example:
“48 extendable dining tables in oak, walnut and ash, from 2 to 12 seats. Free returns within 30 days.”
Each value comes from the database, so every category gets a different, accurate description. There is no length limit either, but the snippet is truncated to fit the device, so lead with the most useful facts.
What to check during and after a migration
Migrations are where titles and descriptions get lost: a new CMS, a new theme, a renamed field, a plugin that is not reinstalled. Google’s guidance on site moves recommends mapping every old URL to its new URL, using server-side permanent redirects, checking canonical tags and robots meta rules, and expecting temporary ranking fluctuation during the move. Titles and descriptions belong in the same checklist.
Before launch
- Export the current titles, descriptions and H1 for all indexable URLs.
- Map each old URL to its new URL, and carry the metadata across in the same file.
- On staging, render a sample of every template and compare titles with the export.
- Check language: each localized template should output titles in the page’s language.
On launch day
- Crawl the new site and compare titles, descriptions and H1 against the mapped export.
- Look for empty values, default CMS titles (“Untitled”, “Product”, “Home”), and the same title on many URLs.
- Confirm that no staging
noindexremains and that canonicals point to the new URLs, as Google’s site move guide advises.
In the following weeks
- Track clicks and impressions per section in Search Console. Google notes that traffic should move from the old URLs to the new ones and that rankings may fluctuate temporarily.
- Compare CTR for key pages with their pre-migration level at similar positions. A drop at stable positions points to the result itself: title, description or how Google rewrote them.
- Search a few key queries manually to see the title links Google actually shows.
A short checklist for metadata at scale
- Every indexable template outputs a unique
<title> - Empty variables are handled with clean fallbacks
- No hardcoded years or outdated claims in templates
- Brand suffix is short and consistent
- Descriptions use page-specific data, not one sentence for all
- Title, H1 and content agree on what the page is
- Titles match the language of the page
- Metadata is compared before and after any migration
How SearchFirefly helps
SearchFirefly’s technical analysis flags missing, duplicated and empty titles and descriptions, grouped by theme and severity with the pages affected, so template problems surface as a pattern rather than thousands of rows. Read alongside Search Console clicks, impressions and positions, it shows whether a migration changed how your pages appear, and each recommendation states the exact fix with a check after release.