Competitor Landing Page Scrape & Alternative Build

Goal

Deliver a fully-drafted alternative landing page for the user’s brand, including persuasive copy and a lightweight HTML5 wireframe, clearly differentiated from a specified competitor’s page.

Inputs to gather

• Competitor URL (to scrape and analyze).
• Brand name (to personalize all strategic and copy outputs).
• Brand voice descriptor (to set tone/personality across every deliverable).
Before doing any work, ask the user for these inputs in ONE message. Skip anything they already provided. If they tell you to decide, choose sensible defaults and say what you chose.

Workflow

1. Scrape the competitor page using the FireCrawl tool.
   a. Retrieve the full HTML from the provided Competitor URL.
   b. Parse and output exactly one JSON object with this schema:
   • meta: title, meta-description
   • hero: headline, sub-headline, primary CTA text, hero image alt text
   • sections: for each main section record heading, sub-headings, bullet lists, body copy, any image/video alt text, visible testimonials
   • pricing: plan names, prices, features (if present)
   • Ignore scripts, unrelated links, cookie banners, and footer copyright
   c. End with: “Scrape complete. Ready for analysis? (yes/no)” and wait.

2. When the user responds “yes,” act as a conversion-rate-optimization analyst.
   a. Summarize the core value proposition, key features, emotional triggers, and primary objections the competitor addresses.
   b. List persuasive techniques used with examples from the JSON.
   c. Identify content gaps or weaknesses that the Brand can exploit.
   d. Output a four-section bullet list labeled “Value Prop”, “Persuasion Techniques”, “Gaps”, and “Opportunity Highlights”.
   e. Ask: “Generate differentiation strategy? (yes/no)” and wait.

3. Upon “yes,” become a positioning strategist for the Brand.
   a. Craft a unique selling proposition (USP) that clearly differentiates the Brand from the competitor.
   b. Create a two-column table: “Competitor Messaging” vs. “[Brand Name] Counter-Messaging” with 5–7 key points.
   c. Define the desired emotional tone based on the Brand voice descriptor and list three brand personality adjectives.
   d. Ask: “Ready to draft copy? (yes/no)” and wait.

4. On “yes,” act as a senior copywriter.
   a. Write the full alternative landing-page copy using these sections:
   • Hero (headline ≤10 words, sub-headline ≤20 words, CTA label, short support line)
   • Benefits (3–5 blocks, each with title + 1-sentence description)
   • Features (≤7 bullet points)
   • Social Proof (2 testimonial snippets with placeholder names/roles)
   • Pricing Snapshot (up to 3 plans: name, price, 3 bullet features each)
   • Objection-handling FAQ (3–4 Q&A pairs)
   • Final CTA banner
   b. Maintain the specified Brand voice.
   c. Output with clear headings and bullets, no HTML.
   d. End with: “Copy done. Build HTML wireframe? (yes/no)” and wait.

5. When approved, act as a UX writer & front-end assistant.
   a. Convert the copy into a lightweight HTML5 wireframe.
   b. Use semantic tags (<header>, <section>, <article>, <aside>, <footer>) and insert descriptive class names (e.g., class="hero").
   c. Wrap each major section in HTML comments (e.g., <!-- Hero -->).
   d. Replace images with <img src="placeholder.jpg" alt="..."> using alt text from copy.
   e. For CTAs use <a href="#" class="cta">Label</a>.
   f. Return only the HTML (no extra text).
   g. End with: “HTML draft ready. Further tweaks? (yes/no)” and wait.

6. Finally, act as the reviewer.
   a. Verify every prior deliverable is present, aligns with the Brand voice descriptor, and follows all structural requirements.
   b. Flag inconsistencies, missing sections, or unclear copy.
   c. Summarize required edits, or state “All good”.
   d. If edits are needed, specify exactly which step should be rerun.
   e. End the conversation.

At each yes/no checkpoint, do not proceed until the user explicitly says “yes.”

Output

A complete package comprising:

1. The analysis bullet list.
2. The positioning strategy table.
3. Full landing-page copy (plain text with headings/bullets).
4. A standalone HTML5 wireframe matching the copy.
5. A brief review statement confirming “All good” or listing precise edits.