OOmnistu

Blog / SEO & Technical

SEO & Technical

Title tags and meta descriptions: write them for the actual page

Write clear titles and useful descriptions for the actual page, understand Google's possible rewrites and avoid rigid character-count myths.

OOmnistu
Reviewed 2026-11-16 · 4 min read

A title tag names a page in its HTML. A meta description gives a short summary. Both can help explain the page to a potential reader, but neither gives you exact control over the title and snippet Google displays for every search.

Google can build a title link from several sources, including the title element, visible main heading and link text. It primarily creates snippets from page content, sometimes using the meta description when that better describes the page. Different queries can produce different snippets.

The practical goal is therefore consistency: a useful page, a clear main heading, an accurate title and a summary that all make the same promise.

Start with the reader's question

Before writing metadata, finish this sentence: "This page helps someone understand or do ___."

For an article about securing SQL queries, "SQL injection prevention: parameters and allow-lists" is more informative than "Security tips you must know." A post explaining sitemap setup should not promise a guaranteed ranking increase merely because it discusses search engines.

A title should make a specific claim about the page's contents. If the article is an introductory explanation, do not label it a benchmark, a case study or an implementation test unless that work actually exists.

This is our editorial test, not a formula that guarantees clicks.

Title tag, visible heading and search title are different

Element Where it comes from What to check
HTML title The page's title element Specific, concise and accurate
Main visible heading The article or page design A clear, prominent statement of the topic
Google's title link Automatically generated by Google Whether it represents the page for the query

The title tag and main heading do not have to be identical word for word. They should not contradict one another. A heading offering a beginner explanation and a title promising an advanced performance test create an avoidable mismatch.

Google recommends making the main title visually distinctive. Two equally prominent headings can make it less clear which one names the page. That is a layout issue as well as a metadata issue.

There is no universal character limit to obey

Google says there is no fixed length limit for a title element or meta description, but displayed titles and snippets may be truncated to fit the device width.

Use preview tools as editing aids, not as proof of exactly what every search result will show. A title that technically fits a chosen character count can still be vague or repetitive. A slightly longer title may be clearer, but its important words should not depend on the reader seeing the very end.

Avoid stuffing several versions of the same keyword into one title. "App development, application development, mobile app developers" is not a helpful substitute for explaining which question the page answers.

Write a description that adds information

A good description is a short, page-specific summary. It should help the reader decide whether the page is relevant, not repeat the title with extra adjectives.

Original illustrative examples:

Page Weak description More useful description
Sitemap guide Best sitemap SEO guide and sitemap tips Learn which URLs belong in a blog sitemap, how to exclude drafts, and why submission does not guarantee indexing.
SQL injection article Everything about database security Understand parameter binding, fixed sort-field allow-lists and the difference between injection prevention and authorization.
Database indexes article Make your database much faster Review PostgreSQL query plans, multicolumn index choices and the operational risks of adding an index to a live table.

These examples promise explanations, not results the page cannot substantiate. They are not tested click-through-rate winners.

For large database-driven sites, Google allows programmatic descriptions when they remain human-readable and varied. That does not make one generic description suitable for every article. A template needs useful page-specific data and an editorial check.

Why Google may show different text

Google's title-link guide lists issues such as inaccurate or obsolete titles, repeated boilerplate, unclear main headings and language mismatches. If you update a dated page, update the title when the content warrants it rather than simply adding the current year to old advice.

Use the same language and writing system as the main content. A Hindi article should not depend on an unrelated English title to describe it.

After changes, Google needs to recrawl and reprocess the page. The documentation says this may take days to weeks. Repeatedly changing metadata before there is time to observe it can make the results harder to interpret.

A different snippet is not automatically a fault. It may be a closer match to the reader's query than the supplied description.

A review process for a growing blog

Our suggested workflow is:

  1. Assign one main reader question to each article.
  2. Check the completed body actually answers it.
  3. Write a distinct title and a one-sentence summary.
  4. Compare the title, main heading and description for conflicting promises.
  5. Inspect the generated page so metadata is not missing or duplicated by the template.
  6. When search data exists, review relevant queries and displayed results before changing the wording.

Do not treat metadata as a replacement for the article. Clear descriptions cannot repair unsupported claims, a thin answer or a broken page. They should accurately represent the work already present.

By Omnistu. Reviewed against Google Search Central guidance on 16 November 2026. No ranking, traffic or click-through-rate gain is claimed.

Sources

Previous
Google's SEO Starter Guide in plain terms: what to do and what to skip