SEO Title Tags vs. Meta Descriptions: What Each Does and Where to Set It

A title tag names a page. Its text appears in the browser tab and can serve as the headline for that page in search results. A meta description is a separate, short summary that may appear beneath the headline. If you need to tell those two fields apart in your CMS, ask what each one should do: identify the page, or describe what a visitor will find there. The page-title explanation from SEOTesting distinguishes their locations in the browser and search results.

Two fields for one page

For a hypothetical photography studio’s /services/ page, the document head could contain:

<head>
  <title>Portrait Photography Services | Example Studio</title>
  <meta name="description" content="Explore portrait photography sessions, locations, and booking details from Example Studio.">
</head>

The <title> element holds the page name. The description is a <meta> element whose name is description and whose content holds the summary. Both go in the document’s <head>, rather than in the visible page copy. The markup comparison at Gizmoop describes those locations and recommends one of each per page.

These values fit a services page: the title identifies the service and studio, while the description tells a visitor what details to expect. A booking page or a gallery would need values that describe that page instead. Reusing the same generic text across the site makes it harder for each field to do its job. There is no need to force the whole page into either field; the title is a name, and the description is a preview.

Where to edit them

If you maintain the HTML directly, edit the relevant page’s <head> and put the intended text in the two elements shown above. Check the published page, not just a local file or an unsaved editor view: the useful question is what the page source actually contains at its URL.

In a CMS, look for per-page fields labelled something like SEO title and SEO description or meta description. Enter the values for the page you are editing, then inspect its published source to see which HTML the CMS produced. Backend SEO fields are a common way to enter this information, as described in McKenzie’s explanation of title tags and descriptions; the labels and behavior still depend on the CMS.

In particular, do not assume that a field called page title and one called SEO title are interchangeable. Portfoliobox documents its own fallback: if its SEO-title field is empty, it uses the Page title as the SEO title. Check how your CMS handles an empty SEO-title field before relying on that behavior. A fallback may save an empty field from becoming a missing title, but it does not tell you whether the resulting title is the one you intended for search.

What a search result may show

The fields are inputs to search appearance, not fixed instructions for a search-result listing. The supplied description may be used as the snippet below a result’s headline, but Google may instead select other page text that better fits the user’s query, as discussed by RevenueZen. A result title can differ from the page’s title tag too; SEOTesting describes Google creating a different title when the supplied one does not accurately describe the page.

That distinction matters when diagnosing a mismatch. A different-looking result does not, by itself, show that your HTML edit failed. First establish what the published page contains. Then treat the text displayed in a particular search result as a separate observation, not as a direct view of the document head.

A short implementation check

1. Open the published /services/ page and inspect its page source. Find the <head> and confirm it contains the intended <title> and <meta name="description"> values, with one of each for that page.
2. Look at the browser tab and confirm it shows the intended title. Do not expect the meta description there; it is a separate field in the page source.
3. Repeat the source check on other important pages. Their titles and descriptions should accurately describe their own content, rather than repeating the services-page example.

Those checks establish what you published and what the browser shows. They cannot establish that a search engine will use the same words for every result or query.