01
Step-by-step
- 01
Summarize the page
Describe the answer, product, service, or process visible on the page.
- 02
Match intent
Use language that reflects the reader's task.
- 03
Explain value
State what the person can learn, compare, calculate, download, or accomplish.
- 04
Avoid unsupported claims
Do not add guarantees or benefits the page does not support.
- 05
Treat it as a suggestion
Search systems may generate a different snippet for a particular query.
02
Verification
- The visible page matches the intended topic and audience.
- The page can be crawled, rendered, and indexed when intended.
- Claims, examples, code, and links have been checked.
- The page has a measurable next action or outcome.
- A future reviewer can understand what changed and why.
03
Before you change the website
- Define the purpose and expected result of meta descriptions.
- Capture the current state using audience task, search intent, factual support, page purpose, structure, examples, links, calls to action, and maintenance ownership.
- Identify the source template, component, plugin, content owner, and release path that controls the output.
- Prepare a test case, approval path, backup or rollback method, and post-release verification plan.
04
Quality-control checks for meta descriptions
- Review the page against its intended task, validate claims and links, and measure whether users reach the next useful action.
- Check representative page types and edge cases instead of confirming only the example used during implementation.
- Confirm the change did not create optimizing wording before defining the page purpose and evidence.
- Record the implementation date, owner, release reference, evidence, and next review trigger.
Next useful action
Turn meta descriptions into an accountable record.
A tested implementation of meta descriptions with deployment notes, rollback context, and retained verification.