How to Write SEO Titles and Meta Descriptions with Examples
Write accurate, distinct page titles and useful meta descriptions, then check the published HTML and social sharing metadata.
By New Delhi Website Technologies · Practical SEO learning series
Start with a website you own or are authorised to edit. Examples are teaching exercises; search rankings and traffic results are not guaranteed.
What you will learn
A useful title tells a potential visitor what the page offers. A useful description summarises the answer clearly enough to help that visitor decide whether to open it. Neither should be a container for every keyword the business wants to rank for. In this lesson you will turn a vague title and description into a pair that accurately represents one page. You will also learn why the text entered into HTML may differ from the title link or snippet displayed for a particular search.
1. Give each page a distinct promise
Start with the visible subject of the page and its audience. A guide about contact-form validation needs a different promise from a company contact page. Write a one-sentence summary before drafting the title. Then compare nearby pages to make sure you are not giving several different URLs the same label. Shared branding can remain consistent, but the meaningful topic should be easy to identify. If you cannot describe what distinguishes a page, investigate whether its contents should be improved or combined with another page before writing more metadata.
2. Write the title around the actual topic
Use wording that would make sense in a browser tab, search result or shared link. Put the important topic where readers can recognise it quickly. Add a useful qualifier when the page genuinely supports it, such as “for beginners,” “with code examples” or a real service location. Avoid unverified superlatives and repeated synonyms. There is no universal character count that guarantees a complete display on every device. Judge the title for clarity and relevance, then check that it still works if its branding or ending is visually shortened.
3. Write the description as a useful summary
Explain what the reader can learn or do, including a specific benefit supported by the page. For a tutorial, mention the task and type of example. For a service page, explain scope and the next step without making unsupported claims. Keep the description readable instead of listing comma-separated phrases. Use the actual page content as the source. A description that promises a free tool, a price or a downloadable file should only do so when that feature is genuinely available and clearly explained on the destination page.
4. Understand what search engines can change
The HTML title is an important input, but Google may generate a different title link using other page signals. Search snippets can also come from visible text instead of the meta description, depending on the query. This does not automatically mean that the tag is broken. Compare the displayed wording with the page promise and check for inconsistent headings or boilerplate. Treat search presentation as a set of signals you can improve, not a fixed advertisement whose exact wording is guaranteed to appear every time.
5. Implement one clean version in the head
Use a single title element and one description meta element in the document head. If your platform generates them automatically, edit the responsible template or page settings instead of adding another competing block. Escape quotation marks and special characters correctly. Keep Open Graph and social-description fields aligned with the page, while recognising that different platforms can cache previews. Verify the final published source after the build or upload. A correct local file is not enough when a CMS, build step or shared layout overwrites its metadata.
6. Measure changes with suitable comparisons
Record the previous text, new text, reason and publication date. When data is available, compare the same page and relevant queries over a sensible period. Look at impressions and position alongside click-through rate, because changes in where and how a page appears affect CTR. Do not declare success from one extra click or a different mix of queries. If the title becomes more accurate but performance remains limited, investigate intent, content and competition. Metadata is one part of the overall page experience, not a replacement for an answer worth visiting.
Example to inspect and adapt
Read the explanation before using this example. Replace example URLs with your own intended public URLs; do not combine conflicting indexing instructions on one page.
<title>HTML Contact Form Validation: Labels and Examples</title>
<meta name="description" content="Build an HTML contact form with accessible labels and browser validation. Learn what still needs a secure server for message delivery.">Worked example
Before: “Home | Best Website, SEO, Ecommerce, Delhi, Noida.” After, for a specific guide: “HTML Contact Form Validation: Labels and Examples.” Example description: “Build an HTML contact form with accessible labels and browser validation. Learn what still needs a secure server before messages can be delivered.” The revised pair is useful because it matches the guide and explains a real limitation.
Your practical exercise
- Write a one-sentence promise for three existing pages.
- Draft a distinct title and description for each without repeating lists of keywords.
- Confirm only one title and description exist in the published head.
- Keep a dated log before comparing page-level search performance.
Save the page URL, the observed problem, your proposed change, the publication date and the check you performed. Record real report data separately from examples or expectations.
Frequently asked questions
Does Google always show my meta description?
No. Google can select other page text to create a snippet relevant to the query.
Will adding a meta keywords tag improve Google rankings?
Google does not use that tag for indexing or ranking. Focus on relevant page content and accurate supported metadata.
Continue learning on this website
Explore our original practical guides below. Each page includes explanations, examples and checks you can apply to your own project.