Landing Page Roast

Get an AI critique of a landing page: an overall score, the headline, call to action, value proposition and trust signals, with issues and fixes.

Pay by wallet (x402) AI-generated landing-page-roast

Example

Input

{
  "url": "https://google.com"
}

Answer

{
  "url": "https://google.com",
  "issues": [
    "Primary CTA ('Google Search') lacks visual distinction/urgency",
    "Secondary CTAs ('I'm Feeling Lucky' variations) create decision friction",
    "New Gemini feature callout buried and not compelling for core search users",
    "No clear value proposition for first-time visitors",
    "Search bar could benefit from placeholder text or microcopy",
    "Limited mobile optimization cues visible"
  ],
  "summary": "Google's homepage maintains exceptional clarity through minimalist design and strong branding, achieving high CTA effectiveness. However, conversion could be optimized by reducing interface complexity and providing clearer value propositions for new users while maintaining the iconic simplicity that defines the brand.",
  "disclaimer": "AI-generated analysis. Results reflect automated assessment, not guaranteed conversion outcomes.",
  "cta_clarity": 88,
  "suggestions": [
    "Enhance primary CTA button styling (color contrast, size) to reduce cognitive load",
    "Consider A/B testing simplified interface with fewer 'I'm Feeling' options",
    "Make the Gemini Maps feature more prominent or remove if not core to conversion",
    "Add subtle placeholder text in search box (e.g., 'Search the web')",
    "Implement dynamic CTA based on user behavior/device type",
    "Test sign-in prominence for authenticated users vs. new visitors"
  ],
  "overall_score": 85,
  "trust_signals": [
    "Google branding (globally recognized)",
    "Privacy and Terms links in footer",
    "Search settings and advanced options",
    "Official Google account/sign-in",
    "AI transparency messaging (Gemini integration)",
    "Environmental commitment statement"
  ],
  "mobile_readiness": "good",
  "headline_effectiveness": 90,
  "value_proposition_score": 82
}

Inputs

Field	Type	Required	What it is
`url`	string	Yes	Landing page URL to analyze

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`issues`	array	Always (present in every successful answer)
`cta_clarity`	integer	Always (present in every successful answer)
`suggestions`	array	Always (present in every successful answer)
`overall_score`	integer	Always (present in every successful answer)
`trust_signals`	array	Always (present in every successful answer)
`headline_effectiveness`	integer	Always (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "landing-page-roast",
    "inputs": {
      "url": "https://google.com"
    },
    "max_price_cents": 50
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "landing-page-roast",
    "inputs": {
      "url": "https://google.com"
    },
    "max_price_cents": 50
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "landing-page-roast",
  inputs: {
    "url": "https://google.com"
  },
  max_price_cents: 50,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="landing-page-roast",
    inputs={
        "url": "https://google.com",
    },
    max_price_cents=50,
))

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/landing-page-roast?url=https%3A%2F%2Fgoogle.com'

Limitations

Brand tone is not assessed
AI-generated critique based on conversion best practices — subjective elements like brand tone are not assessed
What to do instead: Use the structural and CTA recommendations directly, but validate brand-voice feedback against your own style guide
Screenshots are limited to 4 MiB
Pages whose viewport screenshot exceeds 4 MiB are refused with a caller_input error. The call is not charged.

Bundled checks that include it

Competitive Intelligence Snapshot €1.54