---
name: write-proper-title-tags-and-meta-descriptions
description: "Write clear page titles and search summaries. Make each one match the page it describes."
category: Digital Plumbing
stage: —
definitive_article: /digital-plumbing
status: needs-work
---

# Write Proper Title Tags and Meta Descriptions

Search results help people choose which page to open. This guide helps a site owner write clear titles and short page summaries. Start with the pages you want found and the question each one answers.

**The path:** Page intent → Clear title → Useful summary → Served check.

**Use this when:** new pages need metadata or existing intended-search pages have missing, misleading or unnecessarily duplicated metadata.

## Inputs
- The full in-scope intended-search page list, current titles/descriptions and canonical URL decisions.
- Each page’s actual purpose, reader and supported content, using the [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief and owned SEO Tree.
- Access to the actual CMS, SEO plugin or template that controls the served title and description. Rank Math is not a prerequisite when another source already owns these fields.

## First-run prompt

> Review every page in the supplied scope and write truthful, useful metadata for its actual purpose. Treat length as a readability target, not a Google hard limit. Save through the owning source and compare the public result, keeping search-engine display choices separate.

## Steps
1. Inventory the intended indexable URLs and their served title and meta-description values. Separate missing or copied boilerplate from legitimate related pages, redirects and deliberate noindex content. State the page count so a sample is not mistaken for the full inventory.
2. Read each page and assign its distinct reader question or purpose in the SEO Tree. Related pages can share vocabulary without being duplicates; do not force a different keyword merely to make a spreadsheet unique.
3. Write a concise descriptive title that matches the page. Use the natural topic phrase where it helps and the brand where useful. The source’s roughly 60-character target is a house brevity aid, not a Google maximum or a reason to cut the meaning.
4. Write a clear meta description that summarizes the actual content and useful reason to visit. The roughly 160-character target is also a house aid. Avoid fake proof, unsupported promises or awkward repeated keywords.
5. For personal stories and evidence claims, preserve the source’s actual voice and relationship limits. Do not turn a co-appearance into an endorsement in a short title, or add a trophy-name list to attract clicks. Keep necessary material disclosures.
6. Save the fields in the real owning plugin or template without duplicating sources. Confirm that the existing template, builder or language variant does not override the specific page metadata.
7. Read every changed public URL and compare its title and description to the intended values. Check escaping, meaningful text, obvious duplicates and page-source ownership. Use a snippet preview as an approximation, not proof of a fixed Google display width.
8. If actual search results are observed, record query, date and shown text separately. Google can choose a different title link or snippet from page content. Save the page-to-purpose map and remaining issues; do not promise zero truncation across all queries and devices.

## Definition of done (QA checklist)

- [ ] All in-scope intended-search pages have a recorded metadata decision and coverage result.
- [ ] Titles and descriptions accurately describe their page and useful reader purpose.
- [ ] House length guidance improves clarity without false Google-limit or keyword-stuffing rules.
- [ ] Served fields match the intended source and no misleading duplicate boilerplate remains.
- [ ] Search observations are dated and distinguished from authored fields or previews.

## Example(s)

**Fictional teaching example.** A repair page’s old title is “Home | Best Service.” The lesson title becomes “Roof leak checks | Oak Repair,” and its summary says what a visitor can learn before asking for a check. A separate page explains emergency steps, so it keeps related roof wording but serves a different question. The useful result is two truthful page purposes with matching served fields, not a claim that Google must display them verbatim.

## Handoff and Content Factory context

Give the page-to-purpose map to the content/search owner. Use [ensure robots meta not blocking indexing](https://local-service-spotlight.github.io/task-library/?task=ensure-robots-meta-not-blocking-indexing#task-ensure-robots-meta-not-blocking-indexing) for an eligibility issue or [create xml sitemap and reference in robots txt](https://local-service-spotlight.github.io/task-library/?task=create-xml-sitemap-and-reference-in-robots-txt#task-create-xml-sitemap-and-reference-in-robots-txt) for missing discovery coverage.

This setup supports the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. This check does not automatically execute all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run when a page is created or its meaning changes. Existing content reviews can check drift; no automatic keyword rotation or rewriting is needed on a timer.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Gate
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 3 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Record only the property IDs, access and checks required by this task in the client register. Pass the verified result to the task that needs it.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/digital-plumbing
- Exact task: [Write Proper Title Tags and Meta Descriptions](https://local-service-spotlight.github.io/task-library/?task=write-proper-title-tags-and-meta-descriptions#task-write-proper-title-tags-and-meta-descriptions)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Digital Plumbing training](https://blitzmetrics.com/digital-plumbing/)
- [SEO Tree](https://blitzmetrics.com/seo-tree/)
- [Google title links](https://developers.google.com/search/docs/appearance/title-link)
- [Google snippets](https://developers.google.com/search/docs/appearance/snippet)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Real page content and the owning metadata source must be supplied. No search-ranking or click-through improvement is claimed from the teaching draft.