Worked examples

Twelve practical meta tag setups you can copy and adapt

These examples are written for common page types we see most often: SaaS pages, local services, articles, ecommerce products, comparisons, documentation, home pages, events, nonprofits, marketplaces, and portfolios. Each example shows the reasoning behind the title, description, canonical, and social tags instead of only giving a finished snippet.

SaaS landing page

Project management software for small teams

Use a clear category term plus the audience and the main outcome. The description should explain what the product helps people do, not repeat every feature.

Open generator

Suggested inputs

Title tag
Project Management Software for Small Teams | Flowpilot
Meta description
Plan projects, assign work, and track deadlines in one place. Flowpilot helps small teams stay organized without enterprise complexity.
Canonical URL
https://example.com/project-management-software
OG title
Project Management Software for Small Teams | Flowpilot
OG description
A simple workspace for planning projects, tracking deadlines, and keeping small teams aligned.

Why this works

  • The primary category term is near the front of the title.
  • The title promises a specific audience fit instead of sounding generic.
  • The description explains the product outcome in plain language.
  • Social copy is short enough to be readable when shared.

Avoid these mistakes

  • Stuffing the title with every feature the product has.
  • Using a home page canonical on the landing page.
  • Writing a description that is only slogans and no concrete use case.
HTML snippet
<title>Project Management Software for Small Teams | Flowpilot</title>
<meta name="description" content="Plan projects, assign work, and track deadlines in one place. Flowpilot helps small teams stay organized without enterprise complexity.">
<link rel="canonical" href="https://example.com/project-management-software">
<meta property="og:title" content="Project Management Software for Small Teams | Flowpilot">
<meta property="og:description" content="A simple workspace for planning projects, tracking deadlines, and keeping small teams aligned.">
Local service page

Emergency plumber in Austin

Local pages should lead with the service and location. The description should set expectations about area served and response time rather than reading like a national template.

Open generator

Suggested inputs

Title tag
Emergency Plumber in Austin, TX | 24/7 Repairs | Hart Plumbing
Meta description
Need urgent plumbing help in Austin? Hart Plumbing handles burst pipes, leaks, and clogged drains with local 24/7 emergency response.
Canonical URL
https://example.com/austin-emergency-plumber
OG title
Emergency Plumber in Austin, TX | Hart Plumbing
OG description
Local 24/7 emergency plumbing for burst pipes, leaks, and drain issues in Austin.

Why this works

  • Service plus city appears immediately, which matches local search intent.
  • The description gives real service coverage rather than generic trust language.
  • The canonical points to the local landing page, not a broader services hub.

Avoid these mistakes

  • Reusing the same description across every city page.
  • Including cities the business does not actually serve.
  • Pointing every local page back to the homepage as canonical.
HTML snippet
<title>Emergency Plumber in Austin, TX | 24/7 Repairs | Hart Plumbing</title>
<meta name="description" content="Need urgent plumbing help in Austin? Hart Plumbing handles burst pipes, leaks, and clogged drains with local 24/7 emergency response.">
<link rel="canonical" href="https://example.com/austin-emergency-plumber">
<meta property="og:title" content="Emergency Plumber in Austin, TX | Hart Plumbing">
<meta property="og:description" content="Local 24/7 emergency plumbing for burst pipes, leaks, and drain issues in Austin.">
Blog article

Tutorial post with a practical promise

Article metadata should make the scope obvious. Good titles for posts describe the thing learned and hint at the angle or audience.

Open generator

Suggested inputs

Title tag
How to Write Meta Descriptions for Product Pages
Meta description
A step-by-step guide to writing product page meta descriptions that match search intent, avoid duplicate copy, and improve snippet quality.
Canonical URL
https://example.com/blog/meta-descriptions-product-pages
OG title
How to Write Meta Descriptions for Product Pages
OG description
A practical walkthrough with examples, rewrites, and a review checklist for ecommerce teams.

Why this works

  • The title clearly states the skill the article teaches.
  • The description previews what the reader will get from the piece.
  • The social description is written for clicks without becoming clickbait.

Avoid these mistakes

  • Using a vague title such as "Meta Description Tips".
  • Repeating the title with no extra value in the description.
  • Publishing the article under multiple paths and leaving canonicals inconsistent.
HTML snippet
<title>How to Write Meta Descriptions for Product Pages</title>
<meta name="description" content="A step-by-step guide to writing product page meta descriptions that match search intent, avoid duplicate copy, and improve snippet quality.">
<link rel="canonical" href="https://example.com/blog/meta-descriptions-product-pages">
<meta property="og:title" content="How to Write Meta Descriptions for Product Pages">
<meta property="og:description" content="A practical walkthrough with examples, rewrites, and a review checklist for ecommerce teams.">
Ecommerce product page

Product page with one clear differentiator

Product page metadata should combine the product name with the strongest buying detail such as material, size, audience, or shipping benefit. Do not paste the full spec sheet into the title.

Open generator

Suggested inputs

Title tag
Leather Laptop Sleeve 14 Inch | Padded Travel Case | Alder Goods
Meta description
Slim 14 inch leather laptop sleeve with padded lining and magnetic closure. Designed for daily carry and gift-ready shipping.
Canonical URL
https://example.com/products/leather-laptop-sleeve-14-inch
OG title
Leather Laptop Sleeve 14 Inch | Alder Goods
OG description
Slim leather sleeve with padded lining, magnetic closure, and gift-ready shipping.

Why this works

  • The title leads with the product and size, which filters the right click quickly.
  • The description mentions benefits shoppers care about instead of keyword stuffing.
  • Social tags keep the same product identity while using shorter phrasing.

Avoid these mistakes

  • Adding variant SKUs or every available size into the title.
  • Using the collection page canonical on every product page.
  • Writing descriptions that are only feature lists with no buying context.
HTML snippet
<title>Leather Laptop Sleeve 14 Inch | Padded Travel Case | Alder Goods</title>
<meta name="description" content="Slim 14 inch leather laptop sleeve with padded lining and magnetic closure. Designed for daily carry and gift-ready shipping.">
<link rel="canonical" href="https://example.com/products/leather-laptop-sleeve-14-inch">
<meta property="og:title" content="Leather Laptop Sleeve 14 Inch | Alder Goods">
<meta property="og:description" content="Slim leather sleeve with padded lining, magnetic closure, and gift-ready shipping.">
Comparison page

Two software products compared for a specific buyer

Comparison metadata should name the compared options and the decision angle. The page must actually compare criteria instead of acting as a disguised sales page.

Open generator

Suggested inputs

Title tag
Flowpilot vs Taskbase | Project Management Comparison for Agencies
Meta description
Compare Flowpilot and Taskbase on client approvals, workload planning, reporting, pricing structure, and agency handoff workflows.
Canonical URL
https://example.com/compare/flowpilot-vs-taskbase
OG title
Flowpilot vs Taskbase for Agencies
OG description
A practical comparison of agency project workflows, reporting, pricing, and client approval features.

Why this works

  • The title names both options and the audience.
  • The description lists concrete comparison criteria.
  • The canonical uses a stable comparison path instead of a campaign URL.

Avoid these mistakes

  • Writing a comparison page that only praises one option.
  • Using a vague title such as "Best Project Management Tool".
  • Changing the canonical based on whichever product is promoted.
HTML snippet
<title>Flowpilot vs Taskbase | Project Management Comparison for Agencies</title>
<meta name="description" content="Compare Flowpilot and Taskbase on client approvals, workload planning, reporting, pricing structure, and agency handoff workflows.">
<link rel="canonical" href="https://example.com/compare/flowpilot-vs-taskbase">
<meta property="og:title" content="Flowpilot vs Taskbase for Agencies">
<meta property="og:description" content="A practical comparison of agency project workflows, reporting, pricing, and client approval features.">
Documentation page

API documentation for a narrow implementation task

Documentation metadata should identify the exact task, product area, and technical audience. Avoid marketing copy that hides the implementation purpose.

Open generator

Suggested inputs

Title tag
Webhook Retry API | Delivery Rules and Error Codes | Flowpilot Docs
Meta description
Implement webhook retries with delivery timing, signature validation, retry limits, and error-code examples for Flowpilot integrations.
Canonical URL
https://example.com/docs/webhook-retries
OG title
Webhook Retry API Documentation
OG description
Delivery timing, signatures, retry limits, and error-code examples for webhook integrations.

Why this works

  • The title starts with the documented feature.
  • The description previews concrete implementation details.
  • The docs path is stable and canonicalized to the final documentation URL.

Avoid these mistakes

  • Using product marketing claims on developer documentation.
  • Omitting the product area when the docs site is large.
  • Letting versioned docs canonicalize to unrelated latest pages without a plan.
HTML snippet
<title>Webhook Retry API | Delivery Rules and Error Codes | Flowpilot Docs</title>
<meta name="description" content="Implement webhook retries with delivery timing, signature validation, retry limits, and error-code examples for Flowpilot integrations.">
<link rel="canonical" href="https://example.com/docs/webhook-retries">
<meta property="og:title" content="Webhook Retry API Documentation">
<meta property="og:description" content="Delivery timing, signatures, retry limits, and error-code examples for webhook integrations.">
Homepage

Homepage metadata for a clear business category

Homepage metadata should explain the site category and primary audience. It should not try to rank for every service, feature, and location the business has.

Open generator

Suggested inputs

Title tag
Flowpilot | Project Management Software for Client Service Teams
Meta description
Flowpilot helps agencies and client service teams plan projects, manage approvals, track deadlines, and report progress from one workspace.
Canonical URL
https://example.com/
OG title
Flowpilot Project Management Software
OG description
Plan client work, approvals, deadlines, and reporting in one workspace built for service teams.

Why this works

  • The title states category, brand, and audience.
  • The description explains the main workflow without listing every feature.
  • The homepage canonical is the clean root URL.

Avoid these mistakes

  • Using "Home" or only the brand name as the title.
  • Stuffing every feature and industry into the homepage title.
  • Using a slash and non-slash homepage inconsistently.
HTML snippet
<title>Flowpilot | Project Management Software for Client Service Teams</title>
<meta name="description" content="Flowpilot helps agencies and client service teams plan projects, manage approvals, track deadlines, and report progress from one workspace.">
<link rel="canonical" href="https://example.com/">
<meta property="og:title" content="Flowpilot Project Management Software">
<meta property="og:description" content="Plan client work, approvals, deadlines, and reporting in one workspace built for service teams.">
Event page

Event page with date, place, and audience

Event metadata should make the event identity, date, location, and audience obvious. The page should be updated or redirected after the event passes.

Open generator

Suggested inputs

Title tag
Austin Founder Finance Workshop | June 12, 2026 | LedgerNorth
Meta description
Join a one-day Austin workshop for startup founders covering cash-flow planning, bookkeeping systems, tax readiness, and investor reporting.
Canonical URL
https://example.com/events/austin-founder-finance-workshop-2026
OG title
Austin Founder Finance Workshop
OG description
A one-day finance operations workshop for startup founders in Austin on June 12, 2026.

Why this works

  • The title includes event topic, place, date, and host.
  • The description explains what attendees will learn.
  • The canonical URL includes a stable event slug and year.

Avoid these mistakes

  • Leaving old event pages indexable with no update.
  • Using vague titles such as "Upcoming Workshop".
  • Promising limited seats or outcomes without page evidence.
HTML snippet
<title>Austin Founder Finance Workshop | June 12, 2026 | LedgerNorth</title>
<meta name="description" content="Join a one-day Austin workshop for startup founders covering cash-flow planning, bookkeeping systems, tax readiness, and investor reporting.">
<link rel="canonical" href="https://example.com/events/austin-founder-finance-workshop-2026">
<meta property="og:title" content="Austin Founder Finance Workshop">
<meta property="og:description" content="A one-day finance operations workshop for startup founders in Austin on June 12, 2026.">
Nonprofit program page

Program page for a nonprofit service

Nonprofit metadata should explain the program, who it serves, and what action visitors can take. Avoid vague mission language when the page supports a concrete program.

Open generator

Suggested inputs

Title tag
Free Weekend Meal Program for Denver Students | BrightTable
Meta description
BrightTable provides weekend meal packs for Denver students through school pickup sites, volunteer packing shifts, and family support partners.
Canonical URL
https://example.com/programs/weekend-meals-denver-students
OG title
Weekend Meal Program for Denver Students
OG description
Meal packs, pickup sites, volunteer shifts, and partner support for Denver student families.

Why this works

  • The title names the program, audience, location, and organization.
  • The description explains services and participation paths.
  • The page can support donors, volunteers, and families without using one generic message.

Avoid these mistakes

  • Using only broad mission language in metadata.
  • Mixing donor, volunteer, and recipient intent without clarity.
  • Publishing program pages without eligibility or contact details.
HTML snippet
<title>Free Weekend Meal Program for Denver Students | BrightTable</title>
<meta name="description" content="BrightTable provides weekend meal packs for Denver students through school pickup sites, volunteer packing shifts, and family support partners.">
<link rel="canonical" href="https://example.com/programs/weekend-meals-denver-students">
<meta property="og:title" content="Weekend Meal Program for Denver Students">
<meta property="og:description" content="Meal packs, pickup sites, volunteer shifts, and partner support for Denver student families.">
Portfolio case study

Case study metadata with result and scope

Portfolio metadata should name the project type, client or industry when allowed, and the work performed. Do not invent results that the case study does not support.

Open generator

Suggested inputs

Title tag
B2B SaaS Website Redesign Case Study | Conversion UX | Northstar Studio
Meta description
See how Northstar Studio redesigned a B2B SaaS marketing site with clearer messaging, pricing paths, product pages, and analytics-ready forms.
Canonical URL
https://example.com/work/b2b-saas-website-redesign
OG title
B2B SaaS Website Redesign Case Study
OG description
Messaging, product pages, pricing paths, and conversion UX for a SaaS marketing site redesign.

Why this works

  • The title states project category and specialty.
  • The description previews the actual work rather than vague creativity.
  • The case study can earn qualified clicks from similar buyers.

Avoid these mistakes

  • Claiming revenue or conversion results not shown in the case study.
  • Using a title that only says "Case Study".
  • Hiding the project type until deep in the page.
HTML snippet
<title>B2B SaaS Website Redesign Case Study | Conversion UX | Northstar Studio</title>
<meta name="description" content="See how Northstar Studio redesigned a B2B SaaS marketing site with clearer messaging, pricing paths, product pages, and analytics-ready forms.">
<link rel="canonical" href="https://example.com/work/b2b-saas-website-redesign">
<meta property="og:title" content="B2B SaaS Website Redesign Case Study">
<meta property="og:description" content="Messaging, product pages, pricing paths, and conversion UX for a SaaS marketing site redesign.">
Marketplace category page

Marketplace category page with buyer filters

Marketplace metadata should describe the category and the selection logic. It should not index every filter unless the filtered page has durable demand and enough unique value.

Open generator

Suggested inputs

Title tag
Vintage Walnut Dining Tables | Verified Sellers | FurnishMarket
Meta description
Browse vintage walnut dining tables from verified sellers with dimensions, condition notes, delivery options, and saved search filters.
Canonical URL
https://example.com/marketplace/vintage-walnut-dining-tables
OG title
Vintage Walnut Dining Tables
OG description
Verified seller listings with dimensions, condition notes, delivery options, and saved filters.

Why this works

  • The title names the product category and trust signal.
  • The description explains useful buyer filters and listing details.
  • The canonical points to a durable category page rather than a temporary filter state.

Avoid these mistakes

  • Letting every sort order and filter state become indexable.
  • Using a description that only says "browse our marketplace".
  • Canonicalizing valuable category pages to the marketplace homepage.
HTML snippet
<title>Vintage Walnut Dining Tables | Verified Sellers | FurnishMarket</title>
<meta name="description" content="Browse vintage walnut dining tables from verified sellers with dimensions, condition notes, delivery options, and saved search filters.">
<link rel="canonical" href="https://example.com/marketplace/vintage-walnut-dining-tables">
<meta property="og:title" content="Vintage Walnut Dining Tables">
<meta property="og:description" content="Verified seller listings with dimensions, condition notes, delivery options, and saved filters.">
Resource download page

Download page for a practical template

Resource pages should describe what the visitor gets before asking for a download or signup. The metadata should preview the format and use case.

Open generator

Suggested inputs

Title tag
SEO Content Inventory Template | Free Spreadsheet Download
Meta description
Download a spreadsheet template for tracking URL purpose, title tags, canonical status, original value, internal links, and review dates.
Canonical URL
https://example.com/resources/seo-content-inventory-template
OG title
SEO Content Inventory Template
OG description
A spreadsheet for auditing URL purpose, metadata, canonicals, internal links, and review dates.

Why this works

  • The title names the resource and format.
  • The description lists the fields included in the template.
  • The page can support conversion without hiding the value.

Avoid these mistakes

  • Using a vague title such as "Free SEO Download".
  • Forcing a signup before explaining the resource.
  • Indexing many nearly identical download pages.
HTML snippet
<title>SEO Content Inventory Template | Free Spreadsheet Download</title>
<meta name="description" content="Download a spreadsheet template for tracking URL purpose, title tags, canonical status, original value, internal links, and review dates.">
<link rel="canonical" href="https://example.com/resources/seo-content-inventory-template">
<meta property="og:title" content="SEO Content Inventory Template">
<meta property="og:description" content="A spreadsheet for auditing URL purpose, metadata, canonicals, internal links, and review dates.">