SaaS Meta Tags Cheat Sheet - Title Tags, Meta Descriptions & Schema for Every Page Type
A reference for writing page titles, meta descriptions, and schema recommendations across homepages, services, industries, blogs, case studies, pricing, and contact pages.
Built for practical use
10 page-type patterns
A reference for writing page titles, meta descriptions, and schema recommendations across homepages, services, industries, blogs, case studies, pricing, and contact pages.
Open Graph guidance
A reference for writing page titles, meta descriptions, and schema recommendations across homepages, services, industries, blogs, case studies, pricing, and contact pages.
Keyword placement rules
A reference for writing page titles, meta descriptions, and schema recommendations across homepages, services, industries, blogs, case studies, pricing, and contact pages.
Schema reminders
A reference for writing page titles, meta descriptions, and schema recommendations across homepages, services, industries, blogs, case studies, pricing, and contact pages.
How to Use This Cheat Sheet
This is a copy-paste reference for writing title tags, meta descriptions, and JSON-LD schema for every page type in a SaaS website. Use the formulas as starting points, then adapt them to your product.
What you'll find:
- Character count rules for titles and meta descriptions
- Formulas for 10 common SaaS page types
- JSON-LD schema templates for each page type
- Open Graph and Twitter Card meta tags
- Keyword placement strategy
Draft Your Meta Tags
Choose a page type, draft the tags, and preview the structure before sending it to development.
Part 1: The Rules
Title Tag Rules
- Length: 50-60 characters (Google truncates around 580 pixels; 60 characters is a safe ceiling)
- Format:
Primary Keyword | Secondary Context | Brand - Keyword placement: Primary keyword appears in the first 30 characters
- Uniqueness: Every page has a unique title (no duplicates anywhere on the site)
- Tone: Descriptive, benefit-focused, not clickbait
- Avoid: ALL CAPS, excessive punctuation, brand at the start (unless brand is the query)
Meta Description Rules
- Length: 140-160 characters (Google truncates around 155-160)
- Format: Clear statement of what's on the page + value proposition + implicit CTA
- Keyword placement: Primary keyword naturally included (bolded in search results)
- Tone: Action-oriented, benefit-focused, specific
- Avoid: Quotes (escape them), special characters that break rendering
- Remember: Meta descriptions are NOT a direct ranking factor — but they impact click-through rate, which IS a ranking factor
Open Graph & Twitter Card Rules
- og:title: Can be longer than title tag (up to 95 characters) — optimize for social sharing
- og:description: 2-4 sentences (up to ~200 characters is safe)
- og:image: 1200×630px (Facebook/LinkedIn ideal), with text readable at thumbnail size
- twitter:card: "summary_large_image" for most SaaS pages
Part 2: Page-by-Page Templates
1. Homepage
Title tag formula: [Brand] — [What You Do in One Sentence]
Examples:
Stripe — Online Payment Processing for Internet BusinessesNotion — One Workspace. Every Team.Desisle — SaaS UI/UX Design Agency in Bengaluru
Meta description formula: [What you do]. [Primary value proposition]. [Who it's for]. [Soft CTA].
Example: Stripe is a payment infrastructure platform for the internet. Accept payments, send payouts, and automate financial processes. Trusted by millions of businesses worldwide.
JSON-LD schema:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Brand Name",
"url": "https://yourdomain.com",
"logo": "https://yourdomain.com/logo.png",
"description": "Brief description of what you do",
"sameAs": [
"https://twitter.com/yourbrand",
"https://linkedin.com/company/yourbrand",
"https://github.com/yourbrand"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-XXX-XXX-XXXX",
"contactType": "customer service",
"email": "hello@yourdomain.com"
},
"address": {
"@type": "PostalAddress",
"addressLocality": "City",
"addressRegion": "State",
"addressCountry": "Country"
}
}
2. Product / Feature Page
Title tag formula: [Feature Name]: [Primary Benefit] | [Brand]
Examples:
Automated Invoicing: Send Invoices in Seconds | StripeReal-Time Analytics: Track Performance Live | Mixpanel
Meta description formula: [What this feature does]. [Specific benefit with number if possible]. [Who uses it]. Learn more or [CTA].
Example: Automate your invoicing with Stripe. Create, send, and track invoices in under 30 seconds. Used by over 50,000 businesses to reduce payment delays by 40%.
JSON-LD schema (SoftwareApplication):
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "Feature Name",
"operatingSystem": "Web",
"applicationCategory": "BusinessApplication",
"offers": {
"@type": "Offer",
"price": "29.00",
"priceCurrency": "USD"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"ratingCount": "1254"
}
}
3. Pricing Page
Title tag formula: Pricing | [Brand] — [Plan Range or Key Feature]
Examples:
Pricing | Notion — Free, Plus, Business, EnterprisePricing Plans | Figma — Free for Individuals
Meta description formula: [Product] pricing. [Key value of pricing — e.g., "Start free"]. [Plan tiers listed briefly]. [CTA like "See plans"].
Example: Notion pricing. Start free forever. Upgrade to Plus ($10/mo), Business ($18/mo), or Enterprise. Transparent pricing with no hidden fees. See all plans.
JSON-LD schema (Product with offers):
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Brand Product Name",
"description": "Product description",
"offers": [
{
"@type": "Offer",
"name": "Starter",
"price": "29.00",
"priceCurrency": "USD",
"priceValidUntil": "2026-12-31"
},
{
"@type": "Offer",
"name": "Professional",
"price": "99.00",
"priceCurrency": "USD"
}
]
}
4. Blog Post / Article
Title tag formula: [Primary Keyword or Article Title] | [Brand Blog]
Or for SEO-focused articles: [Primary Keyword]: [Specific Benefit/Count] [Year]
Examples:
10 Best Project Management Tools in 2026 (Compared) | Asana BlogSaaS Onboarding: The 2026 Playbook for Activation
Meta description formula: [Problem or question]. [What this article covers]. [Specific value — lists, frameworks, data]. [Soft CTA like "Read the full guide"].
Example: Struggling with low activation rates? This 2026 onboarding playbook covers the aha moment framework, 12 patterns, and 8 anti-patterns used by top SaaS companies. Read now.
JSON-LD schema (Article):
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title Here",
"description": "Brief description of the article",
"image": "https://yourdomain.com/article-image.jpg",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://yourdomain.com/authors/author-name"
},
"publisher": {
"@type": "Organization",
"name": "Your Brand",
"logo": {
"@type": "ImageObject",
"url": "https://yourdomain.com/logo.png"
}
},
"datePublished": "2026-04-18",
"dateModified": "2026-04-18",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://yourdomain.com/blog/article-slug"
}
}
5. Case Study
Title tag formula: How [Customer] Achieved [Specific Outcome] with [Brand]
Examples:
How Acme Corp Reduced Churn 40% with MixpanelHow Stripe Helped Notion Process $10M Safely
Meta description formula: [Customer] faced [specific problem]. By using [product], they [specific outcome with numbers]. Read the full case study.
Example: Acme Corp was losing 15% of users monthly to churn. After implementing Mixpanel Journeys, they reduced churn by 40% in 6 months. Read the full case study.
JSON-LD schema (Article): Same as blog post, but can include additional properties:
{
"@type": "Article",
"articleSection": "Case Study",
"about": {
"@type": "Organization",
"name": "Customer Company Name"
}
}
6. Comparison Page ("Competitor Alternatives")
Title tag formula: [Competitor] Alternatives: [Number] Options to Consider in 2026
Or: [Brand] vs [Competitor]: Which Is Better? (2026 Comparison)
Examples:
Asana Alternatives: 8 Options to Consider in 2026Notion vs ClickUp: Which Is Better? (2026 Comparison)
Meta description formula: Looking for alternatives to [Competitor]? Compare [number] tools on features, pricing, and reviews. [Our product] stands out for [unique benefit]. See the full comparison.
Example: Looking for alternatives to Asana? Compare 8 top project management tools on features, pricing, and user reviews. Find the best fit for your team. Full comparison included.
7. About / Team Page
Title tag formula: About [Brand] — [Mission or Key Differentiator]
Examples:
About Stripe — Increasing the GDP of the InternetAbout Linear — The Issue Tracker You'll Enjoy Using
Meta description formula: [Brand] was founded in [year] to [mission]. [Key stats — team size, customers, locations]. Our mission is to [specific outcome].
Example: Stripe was founded in 2010 to increase the GDP of the internet. Today, millions of businesses worldwide use Stripe to process billions in online transactions.
JSON-LD schema (Organization + founders):
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Brand",
"foundingDate": "2020-01-15",
"founders": [
{
"@type": "Person",
"name": "Founder Name"
}
],
"numberOfEmployees": "11-50"
}
8. Contact / Support Page
Title tag formula: Contact [Brand] — [Response Time or Commitment]
Examples:
Contact Desisle — We Respond Within 24 HoursContact Sales | HubSpot
Meta description formula: Get in touch with [Brand]. [How to reach us — email, phone, form]. [Response expectation]. [Specific services available].
Example: Get in touch with Desisle. Email us at hello@desisle.com or use the contact form below. We respond within 24 hours on weekdays. Available for project inquiries and partnerships.
JSON-LD schema (ContactPage):
{
"@context": "https://schema.org",
"@type": "ContactPage",
"name": "Contact Us",
"mainEntity": {
"@type": "Organization",
"name": "Your Brand",
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "+91-XXX-XXX-XXXX",
"contactType": "customer service",
"email": "hello@desisle.com",
"availableLanguage": ["English", "Hindi"]
}
]
}
}
9. FAQ Page
Title tag formula: [Brand] FAQ | Common Questions About [Product/Service]
Examples:
Stripe FAQ | Common Questions About Online PaymentsFrequently Asked Questions | Linear
Meta description formula: Answers to the most common questions about [Brand]. Pricing, features, integrations, security, and more. Can't find an answer? Contact us.
Example: Answers to common questions about Stripe. Pricing, supported currencies, fees, integrations, and security. Can't find an answer? Contact our support team.
JSON-LD schema (FAQPage):
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is [your product]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The answer to the question..."
}
},
{
"@type": "Question",
"name": "How much does it cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Pricing details..."
}
}
]
}
Why FAQPage schema matters: Google may show your FAQ directly in search results (rich snippet), dramatically increasing your search visibility.
10. Landing Page (Campaign-Specific)
Title tag formula: [Specific Value Proposition for Campaign Audience] | [Brand]
Examples:
Free Project Management Tool for Startups | AsanaHubSpot CRM — Free Forever. No Credit Card.
Meta description formula: [Specific offer or value]. [Who it's for — matches ad targeting]. [Social proof or guarantee]. [CTA].
Example: Free project management tool built for startups. Manage unlimited tasks, invite your team, and track progress. No credit card required. Start free.
Part 3: Open Graph & Twitter Card Tags
Every page should include these tags:
<!-- Basic Meta -->
<title>Your page title here</title>
<meta name="description" content="Your meta description here">
<meta name="keywords" content="keyword1, keyword2, keyword3">
<!-- Canonical -->
<link rel="canonical" href="https://yourdomain.com/page-url">
<!-- Open Graph (Facebook, LinkedIn) -->
<meta property="og:type" content="website">
<meta property="og:url" content="https://yourdomain.com/page-url">
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Your page description (up to ~200 chars)">
<meta property="og:image" content="https://yourdomain.com/og-image.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:site_name" content="Your Brand">
<meta property="og:locale" content="en_US">
<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@yourhandle">
<meta name="twitter:creator" content="@authorhandle">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="Your page description">
<meta name="twitter:image" content="https://yourdomain.com/twitter-image.jpg">
<!-- Additional SEO -->
<meta name="robots" content="index, follow">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="author" content="Your Name or Brand">
<meta name="theme-color" content="#3B82F6"> Part 4: Keyword Placement Strategy
Primary keyword appears in:
- Title tag (in first 30 characters)
- H1 (exactly or close variation)
- URL slug
- First 100 words of content
- At least one H2
- Meta description
- Image alt text (where relevant)
Secondary keywords appear in:
- Other H2s and H3s
- Naturally throughout content
- Image alt text
- Internal link anchor text
Avoid keyword stuffing:
- Keyword density above 2-3% is a red flag
- Never sacrifice readability for keyword inclusion
- Use synonyms and related terms (LSI keywords)
Part 5: Common Meta Tag Mistakes
Mistake 1: Duplicate titles across pages
Every page needs a unique title. Use Screaming Frog to find duplicates.
Mistake 2: Meta description over 160 characters
Google truncates it. Readers see "..." instead of your value prop.
Mistake 3: No og:image (or low-quality image)
Social shares look broken without a proper preview image.
Mistake 4: og:image too small
Minimum: 1200×630px. Anything smaller looks pixelated on LinkedIn/Facebook.
Mistake 5: Brand at the beginning of every title
Users search for what they need, not your brand. "Your Brand | Feature" is inferior to "Feature | Your Brand" for discovery.
Mistake 6: Meta keywords tag (obsolete)
Google stopped using <meta name="keywords"> years ago. It's irrelevant.
Mistake 7: No canonical tag
Prevents duplicate content issues. Every page needs self-referencing canonical.
Mistake 8: Missing structured data (JSON-LD)
Rich snippets, featured snippets, and enhanced search listings require schema.
Part 6: Testing & Validation Tools
Title/meta preview:
- SERP Simulator by Mangools
- Moz Title Tag Preview
Schema validation:
- Google Rich Results Test (search.google.com/test/rich-results)
- Schema.org Validator
Social preview:
- Facebook Sharing Debugger (developers.facebook.com/tools/debug)
- Twitter Card Validator (cards-dev.twitter.com/validator)
- LinkedIn Post Inspector (linkedin.com/post-inspector)
Technical SEO:
- Screaming Frog SEO Spider
- Ahrefs Site Audit
- Google Search Console
Sources and References
- Google Search Central Documentation (developers.google.com/search)
- Schema.org Official Documentation
- Open Graph Protocol (ogp.me)
- Moz Title Tag Guide
- Ahrefs On-Page SEO Research
Created by Desisle — SaaS UI/UX Design Agency desisle.com | hello@desisle.com Free to use and share with attribution.
For a complete SEO audit of your site, contact us at hello@desisle.com.
Keep Building With These Next
The SaaS SEO Checklist - 60 Points From Technical to Content
A foundational SEO checklist that covers technical SEO, on-page optimization, content strategy, and link quality for SaaS teams.
Open SEO ChecklistLanding Page Conversion Checklist - 40 Elements That Drive Clicks
A conversion checklist for headline clarity, value proposition, social proof, CTA design, form optimization, trust signals, mobile experience, and speed.
Open Conversion ChecklistContent Marketing Calendar Template - 90-Day Editorial Plan for SaaS
A structured editorial calendar with topic clusters, keywords, search intent, funnel stage, publish dates, owners, and performance columns.
Open Content CalendarNeed This Applied to Your Product? We'll Turn It Into Execution.
These resource pages are meant to be used hands-on. If you want the audit, plan, or framework translated into live product work, we can do that with your team.