# Landing page intel Human Guide

## What This Is For
Extract GTM-relevant intelligence from any company's landing page by scraping its HTML source. It gives the agent a clearer input/output frame for conversion optimization: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Landing page intel agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for landing page intel.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Landing page intel guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- **Competitive intel**: See what tools competitors use, how they position, who their customers are
- **Prospect research**: Before a sales call, scan a prospect's site to understand their stack and maturity
- **Market mapping**: Scan multiple competitors to compare positioning, customer segments, and GTM motions
- **Customer discovery**: Extract competitor customer logos as potential prospects for your own product

## Decision Points And Nuance
The original skill emphasizes: Quick Start, What It Extracts, CLI Reference, GTM Use Cases, Cost.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | `--url` | *required* | Target website URL |
- Free. No API keys required. Uses only HTTP requests to fetch public HTML.

## Copy-And-Paste Prompt
```text
Use the Landing page intel human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gooseworks-ai/goose-skills skill entry for `landing-page-intel`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Landing Page Intel

Extract GTM-relevant intelligence from any company's landing page by scraping its HTML source.

## Quick Start

Only dependency is `pip install requests`. No API key needed.

```bash
# Basic scan of a single URL
python3 skills/landing-page-intel/scripts/scrape_landing_page.py \
  --url "https://example.com"

# Scan multiple pages of the same site
python3 skills/landing-page-intel/scripts/scrape_landing_page.py \
  --url "https://example.com" --pages "/,/pricing,/about"

# Output as summary table instead of JSON
python3 skills/landing-page-intel/scripts/scrape_landing_page.py \
  --url "https://example.com" --output summary

# Save full report to file
python3 skills/landing-page-intel/scripts/scrape_landing_page.py \
  --url "https://example.com" --output json > report.json
```

## What It Extracts

| Category | Details |
|----------|---------|
| **Tech Stack** | Analytics (GA4, Mixpanel, Amplitude, PostHog, Heap), marketing automation (HubSpot, Marketo, Pardot), chat widgets (Intercom, Drift, Crisp, Zendesk), A/B testing (Optimizely, VWO, LaunchDarkly), session recording (Hotjar, FullStory, LogRocket), CDPs (Segment, Clearbit, 6sense) |
| **Ad Pixels** | Meta Pixel, Google Ads, LinkedIn Insight Tag, TikTok pixel, Twitter pixel |
| **Customer Logos** | Image URLs from "trusted by" / logo carousel sections, grouped by directory |
| **SEO Metadata** | Title, meta description, Open Graph tags, Twitter Cards, canonical URL, structured data (JSON-LD), hreflang tags |
| **CTAs & Sales Motion** | All CTA button text and links — reveals PLG vs sales-led motion |
| **Social Proof** | Testimonials, customer counts, case study links, badge images |
| **Integrations** | Links to integration/partner pages, embedded third-party widgets |
| **Hidden Elements** | Content in `display:none`, `hidden`, or HTML comments that may reveal upcoming features |
| **Infrastructure** | CMS platform (Webflow, WordPress, Next.js, etc.), detected from HTML signatures |

## CLI Reference

| Flag | Default | Description |
|------|---------|-------------|
| `--url` | *required* | Target website URL |
| `--pages` | `/` | Comma-separated paths to scan (e.g., `/,/pricing,/about`) |
| `--output` | `json` | Output format: `json` or `summary` |
| `--timeout` | `15` | Request timeout in seconds |

## GTM Use Cases

- **Competitive intel**: See what tools competitors use, how they position, who their customers are
- **Prospect research**: Before a sales call, scan a prospect's site to understand their stack and maturity
- **Market mapping**: Scan multiple competitors to compare positioning, customer segments, and GTM motions
- **Customer discovery**: Extract competitor customer logos as potential prospects for your own product

## Cost

Free. No API keys required. Uses only HTTP requests to fetch public HTML.