Landing Page Teardown

Get an expert analysis of any landing page with specific recommendations for improvement.

Conversion optimizationCompetitive analysisWebsite auditsMessaging review

The Challenge

Landing pages are critical for conversion, but it's hard to evaluate your own objectively. And analyzing competitors' pages takes time. This prompt gives you a structured teardown with specific, actionable recommendations.

What This Prompt Does

Find Key Pages

Locate homepage, pricing, and feature pages

Analyze Content

Evaluate messaging, CTAs, and structure

Identify Issues

Find conversion blockers and UX problems

Prioritize Fixes

Get quick wins and major opportunities

The Prompt

The Prompt

Task

Use @google_searchName it "google_search" and call it with @google_search to find a company's key landing pages, then use @Cotera Site Scraper/Scrape WebsiteName it "Cotera Site Scraper/Scrape Website" and call it with @Cotera Site Scraper/Scrape Website to analyze them for conversion issues, messaging clarity, and UX problems.

Example: Teardown Notion's landing page and identify areas for improvement.

Input

The user will provide a company name or specific URL.

Example: "Analyze Figma's landing page" or "Teardown https://example.com/pricing"

Context

What to Search For

Find these pages:

  • Homepage
  • Main product/feature pages
  • Pricing page
  • Key landing pages (search "[company] + specific feature")

Analyze for:

  • Messaging clarity: Is it immediately clear what they do?
  • Value proposition: Is the benefit obvious?
  • CTA effectiveness: Are calls-to-action clear and compelling?
  • Social proof: Do they have testimonials, logos, case studies?
  • Page structure: Is information hierarchy logical?
  • Trust signals: Security badges, guarantees, reviews
  • Mobile considerations: Layout issues, text sizing

Search Strategy

  1. Google the company to find their main domain
  2. Scrape the homepage first
  3. Scrape 2-3 additional key pages (pricing, features, etc.)
  4. Analyze each page against best practices
  5. Compile findings with specific recommendations

What Counts as a Valid Result

  • Only analyze pages you can actually scrape
  • Be specific: quote actual copy that has issues
  • Prioritize high-impact issues over nitpicks
  • Include both problems AND what they're doing well
  • Make recommendations actionable

Output

Pages Analyzed: | Page | URL | Primary Purpose | |------|-----|-----------------| | Homepage | [URL] | [Purpose] | | Pricing | [URL] | [Purpose] |

Executive Summary: One paragraph on overall landing page quality and top 3 issues.

Homepage Analysis:

What Works:

  • [Strength 1]: [Why it's effective]
  • [Strength 2]: [Why it's effective]

Issues Found:

  1. [Issue Category] — Severity: High/Medium/Low

    • Problem: [Specific issue with quote from page]
    • Recommendation: [Actionable fix]
  2. [Issue Category] — Severity: High/Medium/Low

    • Problem: [Specific issue with quote from page]
    • Recommendation: [Actionable fix]

Pricing Page Analysis: (Same format)

Overall Recommendations:

Quick Wins (Easy to implement, high impact):

  1. [Recommendation]
  2. [Recommendation]

Major Opportunities (Larger effort, significant impact):

  1. [Recommendation]
  2. [Recommendation]

Competitive Context: How their landing pages compare to industry best practices and key competitors.

Example Usage

Try asking:

  • "Teardown Notion's landing page"
  • "Analyze the homepage for Linear.app"
  • "Find issues with our competitor's pricing page"