Title and Meta Description Templates for Large Sites

Short answer: On a site with thousands of pages, titles and descriptions come from templates that combine fields such as the product name, category, location and brand. A good template uses fields that make each page different, handles missing or very long values, keeps the main words near the start and is tested on real data before it goes live. Write the most important pages by hand, and check regularly for duplicates, empty values and awkward results.

Nobody writes ten thousand titles one by one. Online shops, directories, listing sites and large publishers rely on templates, and these decide how a huge part of the site appears in search. A weak template creates thousands of near-identical titles, strange phrases or truncated text. A careful one saves time and produces clear, specific titles that search engines can use. This guide explains how to build and maintain templates safely. For writing a single good title, see the guide to writing title tags.

What a template is

A template is a pattern with variables, for example the page name, a descriptive word, the category and the site name, in a fixed order. The system fills the variables from the database for each page. Descriptions work the same way, with a short sentence that includes a few fields. Because the pattern repeats, every mistake in it repeats too, which is why testing matters more than for single pages.

Different page types need different templates. A product page, a category page, a location page, an article and a tag archive each serve a different intent, so they should not share one pattern. Start by listing your page types and the search intent behind each, as in the guide to product pages and the guide to category pages.

Choose variables that make pages different

The purpose of a template is to produce unique, accurate titles. Pick fields that differ between pages and that people search for: the product name and the type, the brand, a key attribute such as size or colour, the city and the service, the author or the date for articles. Avoid fields that are the same on all pages, since they only add length. The brand name at the end is fine, but it should not use space that specific words need.

Be careful with variables that can contain unwanted text: internal codes, long lists of tags, words in capital letters or text with symbols. Clean them before they reach the title, or choose another field. Duplicates often arise when several items share the same name, in which case add a distinguishing attribute, as described in the guide to duplicate title tags.

Order and length

Put the most important words first, because titles can be cut in display and the start is read first. Keep titles within a length that usually displays fully, typically around 50 to 60 characters, though the real limit is based on pixel width and varies, as explained in the guide on how Google rewrites titles. Descriptions are usually kept around 120 to 160 characters. These are guides, not rules, and non-Latin scripts behave differently.

Build the template so that the least important part can be dropped when the title is too long. For example, if the full pattern is name, type, city and brand, drop the brand first, then shorten the type. Do not simply cut text at a fixed number of characters, because it may break a word or remove the key term. A rule that tries several versions in order, from the fullest to the shortest, works better.

Fallbacks for missing data

Real databases have empty fields. If the template expects a colour or a city and the value is missing, the title may contain double spaces, dangling dashes or the word null. Define a fallback for every optional field: a shorter version of the pattern that does not need it. Test with the worst cases: the longest names, the shortest names, missing values, special characters and other languages.

For descriptions, a fallback can be a short generic sentence for the page type, but use it sparingly. If most of your pages fall back to the same sentence, you have a duplication problem again. In that case, improve the data or write something better for those pages, as in the guide to boilerplate text.

Descriptions that help the click

A description should describe the page in a way that helps the person decide, and it can include a benefit, a fact such as the price range, availability or delivery information, and a clear call to action where suitable. Use real data from the page, not promises that the page does not support. Search engines often write their own snippet, but a good description still gives them better material and may be used for many queries, as explained in the guide to meta descriptions and the guide to how Google picks snippet text.

Do not stuff keywords. A template that repeats the product name five times looks spammy and reads poorly. One natural mention is enough.

Avoid thin, programmatic patterns

Templates for titles are not the same as templates for pages. If the pages themselves are near copies, even good titles will not solve the problem. Generating pages for every combination of city and service, without unique value, is the risk described in the guide to programmatic SEO and thin pages. Decide first which pages deserve to exist, then write their titles.

Also avoid year numbers that become outdated, unless you can update them automatically and mean it. See the guide to years in title tags.

Languages and special cases

On multilingual sites, do not use the same pattern word for word in every language. Word order, grammar and length differ, and the translation of a template may produce unnatural phrases. Provide a template for each language and test it with real data, as discussed in the guide to translating titles and descriptions. Remember that variables from the database, such as product names, may be in another language.

Special cases such as paginated lists, filtered pages and search results need their own rules. Often the page number can be added at the end of the title, and filtered pages that should not be indexed do not need a polished title at all.

Test, monitor and improve

Before launch, generate titles for a sample of several hundred real pages, including the odd ones, and read them. Run a check for length, duplicates, empty values and unwanted characters. After launch, crawl the site regularly and track the same checks, since data changes over time. Review the performance in Search Console by page type, and look for patterns such as pages with many impressions and a low click rate.

Use experiments carefully. Change the template for a group of pages and compare it with a similar group over several weeks, as described in the guide to SEO testing. Keep a log of template changes, so that you can explain later why traffic moved. Finally, review the pages that matter most by hand with the methods in the guide to scoring every page.

Who owns the templates

On large sites, templates are often changed by developers, plugin updates or agencies without anyone checking the effect on search. Assign an owner for each page type, write down the current pattern and the reason for it, and require a review before any change goes live. A small change, such as a new separator or a different order of words, can alter thousands of titles in a single release, and a mistake may remain unnoticed for weeks.

Keep a simple document with examples of the output for each page type, including the shortest and longest cases. When a new field or page type is added, extend the document and the tests. This also helps new team members and agencies to understand the rules, and it gives you a clear starting point if rankings or click rates change after a release.

Here is a short example. An online shop used a template of the product code, the product name and the shop name. Many titles were long and began with an internal code that no one searched for. The team changed the pattern to the product name, the type and a key attribute, then the brand, with rules to drop the brand and then the attribute if the text was too long. They wrote the titles of their fifty best sellers by hand. Click rates for the template pages improved and the report of duplicate titles fell sharply.

A second example is a directory with a page for each town. Its titles were identical except for the town name. The team added the number of listed businesses and the main category to the pattern, which made each title more informative and unique.

Site SEO AI Audit crawls your site and reports duplicate and missing titles and descriptions, length problems, headings, thin and duplicate content, broken links and structured data, so you can check how your templates turn out on real pages. It does not write the templates for you. The first audit of up to 200 pages is free, and larger sites can see the pricing page.

The bottom line

Use templates with distinct variables, sensible fallbacks and regular checks, and write your most important pages by hand.

FAQ

Are templated titles bad for SEO?

No. Templates are normal on large sites. They are a problem only when they produce duplicates, awkward text or empty values.

How long should a template title be?

Aim for roughly 50 to 60 characters, with the key words first, and design a shorter fallback version for long names.

Should every page have a unique description?

Ideally yes, built from real page data. For minor pages, a good generic description is acceptable if it is used sparingly.

Which pages should I write by hand?

Your home page, main categories, best-selling products, top articles and any page with high value or traffic.

How do I find broken template output?

Crawl the site and filter for duplicates, empty values, odd characters and titles that are too long or too short.