landing-page
ソーシャルメディアやウェブサイトなどの情報源から企業や個人の詳細なプロファイルを構築し、AIがマーケター視点で分析、ターゲットに合わせた魅力的なランディングページと画像を作成するSkill。
📜 元の英語説明(参考)
Research-driven landing page generator. Pulls data from social media, websites, Google Maps, YouTube, forums, and optionally a CV to build a complete profile of a company or person. Analyzes the data as a marketer to extract competitive advantages, value props, audience insights, and brand voice. Then generates a compelling landing page with AI-generated images tailored to the audience. Use this skill when the user says things like: 'create a landing page for...', 'build a website for this business', 'make a landing page from their social media', 'generate a page for this company', 'research and build a site for...', 'landing page for my client', 'portfolio page for...', 'personal brand page', or provides social media handles, a website URL, or a CV and wants a page built from it.
🇯🇵 日本人クリエイター向け解説
ソーシャルメディアやウェブサイトなどの情報源から企業や個人の詳細なプロファイルを構築し、AIがマーケター視点で分析、ターゲットに合わせた魅力的なランディングページと画像を作成するSkill。
※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o landing-page.zip https://jpskill.com/download/8632.zip && unzip -o landing-page.zip && rm landing-page.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/8632.zip -OutFile "$d\landing-page.zip"; Expand-Archive "$d\landing-page.zip" -DestinationPath $d -Force; ri "$d\landing-page.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
landing-page.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
landing-pageフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Skill本文(日本語訳)
※ 原文(英語/中国語)を Gemini で日本語化したものです。Claude 自身は原文を読みます。誤訳がある場合は原文をご確認ください。
ランディングページジェネレーター
対象者が誰であるかを、ソーシャルメディア、ウェブでの存在感、レビュー、そしてオプションで履歴書を通じて深く理解し、特定のオーディエンスに響くコピー、ビジュアル、デザインを作成することで、魅力的なランディングページを構築する、研究主導型の Skill です。
これは汎用的なページビルダーではありません。リサーチファーストのアプローチです。まず対象者を深く理解し、次にそのオーディエンスのためにデザインします。
ワークフローの概要
入力 (handles, URLs, CV)
→ リサーチ (Social Toolkit MCP + SearchAPI MCP)
→ 分析 (マーケター/SEOの視点)
→ デザインの方向性 (オーディエンス主導)
→ コピー生成 (声のトーンに合わせる)
→ 画像生成 (美的に合わせる)
→ ランディングページ (デプロイ準備完了)
ステップ 0: 入力を収集する
利用可能なものをできるだけ多くユーザーに尋ねてください。少なくとも、1つのソーシャルメディアのハンドルまたはウェブサイトの URL が必要です。
リクエストする構造化された入力:
| 入力 | 例 | 必須ですか? |
|---|---|---|
| Instagram handle | @kerikuamorelia |
少なくとも1つのソーシャルプロフィール |
| TikTok handle | @username |
オプション |
| Facebook page | Page Name |
オプション |
| YouTube channel | @channel または URL |
オプション |
| URL または会社名 | オプション | |
| Website URL | https://example.com |
オプション |
| Google Maps / Business name | K'ERI KUA Morelia |
オプション |
| CV / Resume | ファイルパスまたは貼り付けられたテキスト | オプション |
| Target audience hint | "young professionals in Mexico" | オプション |
| Language | es, en, pt, etc. | デフォルト: コンテンツから自動検出 |
また、以下も尋ねてください。
- これは誰のためですか? (自分自身、クライアント、友人、見つけたビジネス)
- 目標は何ですか? (クライアントを獲得する、コミュニティを構築する、製品を販売する、パーソナルブランド、ポートフォリオ)
ステップ 1: リサーチフェーズ
利用可能なすべてのソースから並行してデータを取得します。Social Toolkit MCP をプライマリとして、SearchAPI MCP をバックアップ/補完として使用します。
1A: ソーシャルメディアプロフィール
提供されたすべてのプロフィールを並行して取得します。
Social Toolkit MCP:
- FetchInstagramProfileTool → username (bio、フォロワー、投稿、キャプション、エンゲージメントを取得)
- FetchTiktokProfileTool → username (bio、フォロワー、動画、エンゲージメントを取得)
- FacebookBusinessPageInfoTool → page name (概要、いいね、投稿を取得)
- FetchYoutubeChannelTool → channel (説明、登録者、動画を取得)
- FetchYoutubeChannelVideosTool → channel (最近の動画タイトル、再生回数を取得)
各プロフィールから、以下を抽出します。
- Bio / 説明文
- フォロワー数とエンゲージメント率
- 過去10〜12件の投稿/動画とキャプション
- 頻繁に使用されるハッシュタグ
- 投稿頻度とコンテンツのテーマ
- ビジュアルスタイル (投稿の説明から — dark/light, colorful/muted, professional/casual)
- 言語と声のトーン
- ウェブサイトまたは他のプロフィールへのリンク
- 位置情報
1B: ウェブサイトのスクレイピング
ウェブサイトの URL が提供されている場合 (またはソーシャルメディアの bio に記載されている場合):
Social Toolkit MCP:
- FirecrawlMapTool → URL (サイト上のすべてのページを発見)
- FirecrawlScrapeTool → URL (メインページコンテンツをスクレイピング)
- FirecrawlScrapeTool → 主要なサブページ (about, services, contact)
抽出:
- タグライン / ヒーローテキスト
- 記載されているサービスまたは製品
- About セクション / 会社のストーリー
- テスティモニアル (存在する場合)
- 連絡先情報
- 既存のカラースキームとフォント
- SEO メタタグ (title, description)
- コールトゥアクションのパターン
1C: Google Maps & レビュー
ビジネス名または場所が提供されている場合:
SearchAPI MCP:
- google_maps_search → business name + location
- google_maps_place → search からの place_id (レビュー、評価、営業時間、写真を取得)
抽出:
- 評価とレビュー数
- ビジネスのカテゴリ/タイプ
- 住所、営業時間、電話番号
- GPS 座標 (
latitude,longitude) — 地図の埋め込みのために保存 - レビューのテーマ (顧客が賞賛すること、不満に思うこと)
- 人気の時間帯
- 支払い方法、アメニティ
- 写真の説明
people_also_search_for— これらをステップ 1G の潜在的な競合他社として保存
1D: ウェブ調査
追加のコンテキストを検索します。
Social Toolkit MCP:
- GoogleNewsSearchTool → business/person name (最近のプレス、言及)
- GoogleForumsSearchTool → business/person name (コミュニティのディスカッション、Reddit での言及)
- PerplexitySonarSearchTool → "who is [name] and what do they do" (合成された概要)
SearchAPI MCP (バックアップ):
- google_news_light → business/person name
1E: YouTube の詳細な調査
YouTube チャンネルが存在する場合:
Social Toolkit MCP:
- FetchYoutubeChannelVideosTool → channel (動画リストを取得)
- FetchYoutubeTranscriptTool → 再生回数の多い上位 2〜3 件の動画 (彼らが何について話しているかを理解)
- FetchYoutubeCommentsTool → トップ動画 (オーディエンスの反応を理解)
1F: CV / 履歴書の分析
CV が提供されている場合 (ファイルパスまたは貼り付けられたテキスト):
- Read ツールを使用してファイルを読み取ります
- 抽出: スキル、経験、教育、資格、実績、キャリアの物語
- 専門分野と経験年数を特定します
- 受賞歴、出版物、講演の機会に注意してください
1G: 競合他社 / 類似ビジネスの調査 (フォールバック)
以下の場合にこのステップをトリガーします。
- 対象者のウェブでの存在感が非常に少ない場合 (投稿が少ない、ウェブサイトがない、レビューが少ない)
- ソーシャルプロフィールがまばらであるか、最近作成されたものである場合
- 魅力的なページを構築するために、ステップ 1A〜1F で十分なデータが収集されなかった場合
目標: 上位にランク付けされている 2〜3 の類似ビジネスを見つけ、それらのウェブサイトを調査し、それらのパターンをインスピレーションとして使用します。ただし、出力はプロフェッショナルであり、対象者の実際のコンテキストに合わせて調整されている必要があります。
競合他社を見つける方法:
- Google Maps の検索結果 (ステップ 1C) から
people_also_search_forを使用します — これらが最も近い競合他社です - Google でビジネスカテゴリ + 場所を検索します。
Social Toolkit MCP: - PerplexitySonarSearchTool → "[city] で最高の [ビジネスタイプ]" または "[location] の近くの [ビジネスカテゴリ]" - GoogleForumsSearchTool → "[ビジネスタイプ] [city] のおすすめ" - 見つかった各競合他社について、そのウェブサイトをスクレイピングします。
Social Toolkit MCP: - FirecrawlScrapeTool → 競合他社のウェブサイト URL (ホームページを取得)
**Extra
(原文がここで切り詰められています)
📜 原文 SKILL.md(Claudeが読む英語/中国語)を展開
Landing Page Generator
A research-driven skill that builds compelling landing pages by first deeply understanding who the subject is — through social media, web presence, reviews, and optionally a CV — then crafting copy, visuals, and design that resonates with their specific audience.
This is NOT a generic page builder. It's a research-first approach: understand the subject deeply, then design for their audience.
Workflow Overview
Input (handles, URLs, CV)
→ Research (Social Toolkit + SearchAPI MCPs)
→ Analysis (marketer/SEO lens)
→ Design Direction (audience-driven)
→ Copy Generation (voice-matched)
→ Image Generation (aesthetic-matched)
→ Landing Page (deploy-ready)
Step 0: Gather Inputs
Ask the user for as many of these as available. At minimum, one social media handle or a website URL is required.
Structured inputs to request:
| Input | Example | Required? |
|---|---|---|
| Instagram handle | @kerikuamorelia |
At least one social profile |
| TikTok handle | @username |
Optional |
| Facebook page | Page Name |
Optional |
| YouTube channel | @channel or URL |
Optional |
| URL or company name | Optional | |
| Website URL | https://example.com |
Optional |
| Google Maps / Business name | K'ERI KUA Morelia |
Optional |
| CV / Resume | File path or pasted text | Optional |
| Target audience hint | "young professionals in Mexico" | Optional |
| Language | es, en, pt, etc. | Default: auto-detect from content |
Also ask:
- Who is this for? (themselves, a client, a friend, a business they found)
- What's the goal? (get clients, build community, sell products, personal brand, portfolio)
Step 1: Research Phase
Pull data from ALL available sources in parallel. Use Social Toolkit MCP as primary and SearchAPI MCP as backup/complement.
1A: Social Media Profiles
Fetch all provided profiles in parallel:
Social Toolkit MCP:
- FetchInstagramProfileTool → username (gets bio, followers, posts, captions, engagement)
- FetchTiktokProfileTool → username (gets bio, followers, videos, engagement)
- FacebookBusinessPageInfoTool → page name (gets about, likes, posts)
- FetchYoutubeChannelTool → channel (gets description, subscribers, videos)
- FetchYoutubeChannelVideosTool → channel (gets recent video titles, views)
From each profile, extract:
- Bio / description text
- Follower counts and engagement rates
- Last 10-12 posts/videos with captions
- Hashtags used frequently
- Posting frequency and content themes
- Visual style (from post descriptions — dark/light, colorful/muted, professional/casual)
- Language and tone of voice
- Links to website or other profiles
- Location information
1B: Website Scraping
If a website URL is provided (or found in social bios):
Social Toolkit MCP:
- FirecrawlMapTool → URL (discover all pages on the site)
- FirecrawlScrapeTool → URL (scrape main page content)
- FirecrawlScrapeTool → key subpages (about, services, contact)
Extract:
- Tagline / hero text
- Services or products listed
- About section / company story
- Testimonials if present
- Contact information
- Existing color scheme and fonts
- SEO meta tags (title, description)
- Call-to-action patterns
1C: Google Maps & Reviews
If a business name or location is provided:
SearchAPI MCP:
- google_maps_search → business name + location
- google_maps_place → place_id from search (gets reviews, rating, hours, photos)
Extract:
- Rating and review count
- Business category/type
- Address, hours, phone
- GPS coordinates (
latitude,longitude) — save these for the map embed - Review themes (what customers praise, what they complain about)
- Popular times
- Payment methods, amenities
- Photos description
people_also_search_for— save these as potential competitors for Step 1G
1D: Web Research
Search for additional context:
Social Toolkit MCP:
- GoogleNewsSearchTool → business/person name (recent press, mentions)
- GoogleForumsSearchTool → business/person name (community discussions, Reddit mentions)
- PerplexitySonarSearchTool → "who is [name] and what do they do" (synthesized overview)
SearchAPI MCP (backup):
- google_news_light → business/person name
1E: YouTube Deep Dive
If a YouTube channel exists:
Social Toolkit MCP:
- FetchYoutubeChannelVideosTool → channel (get video list)
- FetchYoutubeTranscriptTool → top 2-3 videos by views (understand what they talk about)
- FetchYoutubeCommentsTool → top video (understand audience reaction)
1F: CV / Resume Analysis
If a CV is provided (file path or pasted text):
- Read the file using the Read tool
- Extract: skills, experience, education, certifications, achievements, career narrative
- Identify expertise areas and years of experience
- Note any awards, publications, speaking engagements
1G: Competitor / Similar Business Research (Fallback)
Trigger this step when:
- The subject has very little web presence (few posts, no website, few reviews)
- The social profiles are sparse or recently created
- Not enough data was gathered in Steps 1A-1F to build a compelling page
Goal: Find 2-3 similar businesses that rank well, study their websites, and use their patterns as inspiration — while keeping the output professional and tailored to the subject's actual context.
How to find competitors:
- Use
people_also_search_forfrom the Google Maps results (Step 1C) — these are the closest competitors - Search Google for the business category + location:
Social Toolkit MCP: - PerplexitySonarSearchTool → "best [business type] in [city]" or "[business category] near [location]" - GoogleForumsSearchTool → "[business type] [city] recommendations" - For each competitor found, scrape their website:
Social Toolkit MCP: - FirecrawlScrapeTool → competitor website URL (get their homepage)
Extract from competitors:
- Page structure and section order (what sections do they include?)
- Services/offerings listed (use as inspiration for the subject's page)
- Tone of voice and copy patterns
- Color schemes and visual style
- CTAs and conversion patterns
- Trust signals they use (certifications, awards, "since 2005", etc.)
How to use competitor data:
- DO: Use the page structure, section patterns, and professional tone as a template
- DO: Adapt the mood and visual style to match what works in the industry
- DO: Include similar sections (e.g., if all competitors have a "Why Choose Us" section, include one)
- DON'T: Copy specific text or claims — everything must be about the actual subject
- DON'T: Use competitor branding, colors, or logos
- DON'T: Fabricate testimonials, awards, or stats the subject doesn't have
- DO: Be transparent with the user: "I didn't find much about [subject] online, so I studied similar businesses in the area to inform the design. Here's what I used as reference: [list competitors]"
When writing copy with limited data:
- Keep claims general but professional: "Quality service" instead of "Award-winning service"
- Focus on the basics that ARE known: location, hours, category, contact
- Use the aesthetic and tone of successful competitors as a guide
- Add placeholder sections the user can fill in: "[Your tagline here]", "Tell your story..."
- Make the page look established and professional even with minimal content — this IS the value
Step 2: Analysis Phase — Think Like a Marketer
After gathering all data, perform a structured analysis. Write this analysis out explicitly before designing — it informs every design decision.
2A: Subject Profile
Synthesize a clear picture:
- Who they are: One paragraph summary
- What they do: Core offering/service/product
- Where they operate: Geography, market, niche
- How long: Maturity/experience level
- Brand voice: Formal/casual, playful/serious, bold/understated, technical/accessible
- Content themes: Top 3-5 recurring topics across all platforms
- Visual identity: Colors, imagery style, and aesthetic patterns from existing content
2B: Audience Analysis
Based on followers, engagement, review language, and content type:
- Primary audience: Demographics, interests, pain points
- What they value: What makes them follow/engage/buy
- Language they use: Slang, formality level, emotional triggers
- Where they hang out: Which platforms are strongest
2C: Competitive Advantages
Identify from the data:
- Unique value prop: What do they offer that others don't?
- Social proof: Ratings, testimonials, follower count, engagement
- Authority signals: Years in business, certifications, press mentions, expertise
- Emotional hooks: Community, exclusivity, safety, luxury, accessibility, rebellion
- Content edge: What type of content performs best for them
2D: SEO & Conversion Insights
- Keywords: Terms from their content, hashtags, and audience language
- Search intent: What would someone Google to find them?
- Conversion goal: What action should the landing page drive?
- Trust barriers: What objections might a visitor have? How does the data address them?
Step 3: Design Direction
Based on the analysis, commit to a design direction. Don't ask the user to pick — propose one based on the data and let them override.
Aesthetic Selection
Choose based on brand voice + audience:
| If the data suggests... | Choose... |
|---|---|
| Luxury, exclusivity, high-end | Dark theme, serif fonts, gold accents, editorial layout |
| Friendly, accessible, community | Light/warm theme, rounded fonts, soft colors, open layout |
| Technical, professional, B2B | Clean minimal, monospace accents, structured grid, muted palette |
| Bold, rebellious, youth | High contrast, oversized type, asymmetric layout, neon accents |
| Natural, organic, wellness | Earth tones, organic shapes, textured backgrounds, botanical imagery |
| Playful, creative, artistic | Vibrant colors, custom illustrations, dynamic layout, personality |
Color Palette
Derive from:
- Their existing brand colors (from website/social)
- Their industry conventions
- Their audience preferences
- The emotional tone of their content
Typography
Select 2 fonts — a display font and a body font — that match the aesthetic. Never use Inter, Roboto, Arial, or system fonts. Use Google Fonts.
Content Structure
Based on conversion goal, structure the page:
For service businesses: Hero → Problem/Solution → Services → Social Proof → About → CTA
For personal brands / portfolios: Hero → About → Work/Projects → Testimonials → Contact
For communities / clubs: Hero → Experience → Pillars/Values → Events → Location → CTA
For products / e-commerce: Hero → Product Showcase → Features → Reviews → Pricing → CTA
For professionals (CV-based): Hero → Expertise → Experience Timeline → Skills → Publications/Talks → Contact
Step 4: Copy Generation
Write all copy in the subject's voice and the audience's language:
- Hero headline: Bold, specific, emotionally resonant. Not generic.
- Hero subheadline: Clarify what they do and for whom.
- Section headlines: Each tells a mini-story, not just labels.
- Body copy: Short paragraphs, conversational, benefit-driven.
- CTAs: Action-specific ("Solicitar Membresía", not "Click Here")
- Social proof snippets: Pull real quotes from reviews, format naturally.
- Meta tags: SEO-optimized title and description.
Language: Write in the same language the subject uses on their profiles. If mixed, default to the language most of their audience engages in.
Step 5: Image Generation
Generate 3-5 images that match the aesthetic direction using available image generation tools.
Check for infsh CLI availability (from the ai-image-generation skill):
which infsh
If available, generate images using FLUX or Grok models (avoid Seedream for potentially sensitive content):
infsh app run falai/flux-dev-lora --input '{
"prompt": "[aesthetic-matched prompt based on brand analysis]"
}'
Image set to generate:
| Image | Purpose | Aspect |
|---|---|---|
| Hero background | Main visual impact, sets the mood | 16:9 or full-width |
| About/Feature visual | Supports the story section | 3:4 or 1:1 |
| Service/Pillar images (2-3) | One per key offering | 1:1 or 16:9 |
| CTA background (optional) | Atmospheric, subtle | 16:9 |
Prompt engineering: Base each prompt on the analysis — use the brand's visual style, color palette, and industry context. Never generate generic stock-photo-style images.
If infsh is not available, check for the Social Toolkit HiggsfieldImageTool as an alternative. If no image generation is available, create the page with CSS-only atmospheric effects (gradients, noise textures, shapes) and note which images the user should add later.
Download all generated images to the project directory alongside the HTML/React files.
Step 6: Build the Landing Page
Output Format Selection
Present the user with options based on their situation:
Option A: Single HTML File (recommended for beginners)
- Zero dependencies, open in any browser
- Best for: clients who need it NOW, non-technical users, quick prototypes
- Inline CSS + JS, Google Fonts via CDN
- Images referenced as local files in same directory
- Deploy with Wrangler — include
wrangler.jsoncin the project folder:{ "name": "<project-name>", "compatibility_date": "2025-04-01", "assets": { "directory": "./" } }Then:
cd <project-folder> && wrangler deploy
Option B: Vite + React SPA (recommended for developers)
npm run build→ deploy withwrangler deploy- Component-based, easy to modify
- Best for: developers, projects that will grow, custom domains
- Follow the standalone React guidelines from the
frontend-designskill (includeswrangler.jsoncsetup)
Option C: Rails + Inertia Page (recommended for SaaS integration)
- Generates directly into a Rails project structure
- Inertia page component + controller + route
- Best for: when the landing page is part of a larger Rails app
- Only available when inside a Rails+Inertia project (auto-detected)
- Follow the Rails+Inertia guidelines from the
frontend-designskill
Option D: Deployable HTML + Asset Bundle (recommended for client handoff)
- Organized folder:
index.html+css/+images/+js/ - README with deployment instructions
- Best for: freelancers, agency work, client deliverables
- Include
wrangler.jsoncin the folder root:{ "name": "<project-name>", "compatibility_date": "2025-04-01", "assets": { "directory": "./" } }Deploy:
cd <project-folder> && wrangler deploy
Auto-selection logic (propose this, let user override):
- Inside a Rails+Inertia project → Option C
- User mentioned "client" or "freelance" → Option D
- User is technical / mentioned Vercel/Netlify/Cloudflare → Option B
- Default / beginner / "just make it work" → Option A
Design Execution
Regardless of format, apply ALL guidelines from the frontend-design skill:
- Distinctive typography (never generic)
- Bold color palette derived from the research
- Atmospheric backgrounds and textures
- Scroll animations and micro-interactions
- Mobile-responsive
- Fast loading (optimize images, minimal JS)
Map & Directions Integration
If Google Maps coordinates were obtained in Step 1C, include an interactive map section. Ask the user which option they prefer:
Option 1: Google Maps Embed (recommended — free, no API key)
<iframe
src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3000!2d{longitude}!3d{latitude}!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s{place_id}!2s{business_name}!5e0!3m2!1sen!4v1"
width="100%" height="400" style="border:0;" allowfullscreen="" loading="lazy">
</iframe>
Option 2: OpenStreetMap Embed (no Google dependency)
<iframe
src="https://www.openstreetmap.org/export/embed.html?bbox={lng-0.005},{lat-0.005},{lng+0.005},{lat+0.005}&layer=mapnik&marker={latitude},{longitude}"
width="100%" height="400" style="border:0;">
</iframe>
Option 3: Static Map Image (fastest load, no iframe)
- Generate a map screenshot or use a static map API
- Best for performance-critical pages
Option 4: No map (for online-only businesses, personal brands without a physical location)
"How to Get There" section — include alongside the map:
- Full formatted address
- A "Get Directions" button linking to Google Maps navigation:
<a href="https://www.google.com/maps/dir/?api=1&destination={latitude},{longitude}&destination_place_id={place_id}" target="_blank"> Get Directions </a> - Nearby landmarks or neighborhoods (if mentioned in reviews)
- Parking information (if found in Google Maps extensions)
- Public transit tips (if available from the data)
Auto-selection logic:
- Physical business with foot traffic (restaurant, store, club) → Option 1 + full "How to Get There"
- Professional office (agency, clinic, studio) → Option 1, minimal directions
- Online-only business → Option 4
- User requests minimal dependencies → Option 2
Page Must Include
Every generated landing page must have:
- [ ] SEO meta tags (title, description, OG image, canonical)
- [ ] Mobile viewport meta tag
- [ ] Semantic HTML structure
- [ ] At least one clear CTA above the fold
- [ ] Social proof section (ratings, followers, testimonials)
- [ ] Contact/location information (if available)
- [ ] Map embed with directions (if physical location — see Map & Directions section)
- [ ] Footer with legal/disclaimer text (if applicable)
- [ ] Google Fonts loaded
- [ ] All images with alt text
- [ ] Favicon link (if generated)
Step 7: Present the Result
After generating, provide:
- Research Summary: Key findings about the subject (2-3 bullet points)
- Design Rationale: Why you chose this aesthetic direction (1-2 sentences)
- The page: Open it in browser (
open index.html) or provide dev server instructions - What's included: List of files generated (HTML, images, CSS)
- Deployment instructions: Based on the format chosen
- Suggested improvements: Things that could be added with more data or budget (video, testimonials page, blog, etc.)
Behavior Notes
- Research thoroughly, don't rush to design. The quality of the landing page depends entirely on understanding the subject. Spend time in Steps 1-2.
- Be opinionated about design. Don't ask the user to pick colors or fonts — derive them from the research and propose confidently. The user will push back if they disagree.
- Write copy in context. Every headline and paragraph should feel like it was written BY someone who deeply understands the business, not by a generic AI.
- Use real data. Pull actual numbers (4.9 stars, 3,235 followers), real quotes from reviews, actual business hours. Never invent testimonials.
- Match the audience, not just the brand. A luxury brand targeting Gen Z needs a different page than one targeting executives, even with the same brand colors.
- Generate images that fit. Every AI-generated image should feel like it belongs to this specific business. No generic stock vibes.
- Handle multiple languages naturally. If the business operates in Spanish, write in Spanish. Don't translate — write natively.
- Respect disclaimers. If the business includes legal disclaimers in their content (e.g., cannabis clubs, financial services), include appropriate disclaimers in the landing page footer.
- Always show the research. Before presenting the design, share a brief summary of what you found. This builds trust and lets the user correct any misunderstandings before you build.