Overview
SpiderLanding captures landing pages from URLs (typically Facebook/Google ad tracking links) and provides:- Screenshots: Above-fold and full-page captures
- HTML Bundles: Self-contained HTML with embedded assets
- AI Extraction: Marketing content analysis via Claude
- Redirect Tracking: Full chain from tracking URL to final page
Use Cases:
- Competitor ad research and landing page analysis
- Marketing funnel documentation
- A/B test monitoring
- Archiving campaign landing pages before they change
Quick Start
1. Submit a Landing Page Capture
2. Get Results
3. Access Your Files
Results include public URLs for:screenshot_fold_url- Above-fold screenshot (PNG)screenshot_full_url- Full-page screenshot (PNG)html_bundle_url- Self-contained HTML file
What You Get
1. Screenshots
Above-Fold Screenshot
Captures exactly what users see when the page loads (viewport only).File:
fold.png
Default Size: 1440x900pxFull-Page Screenshot
Captures the entire page height, including content below the fold.File:
full.png
Height: Varies by page2. HTML Bundle
The HTML bundle is a self-contained file with all assets embedded:- CSS stylesheets (inline)
- JavaScript files (inline)
- Images (base64 data URIs)
- Fonts (embedded)
File Sizes: Simple pages produce 5-50KB bundles. Complex marketing pages can be 10-50MB due to embedded images.
3. AI-Extracted Content
Whenextract_content is enabled, Claude AI analyzes the page and extracts:
4. Redirect Chain
Track the full journey from ad click to landing page:Configuration Options
Viewport Size
Customize the browser viewport for different device simulations:| Device | Width | Height |
|---|---|---|
| Desktop (default) | 1440 | 900 |
| Desktop HD | 1920 | 1080 |
| Laptop | 1366 | 768 |
| Tablet | 768 | 1024 |
Feature Toggles
Disable features you don’t need to speed up processing:Timeouts
Adjust timeouts for slow-loading pages:Common Patterns
Competitor Landing Page Research
Capture competitor landing pages for analysis:Facebook Ad Tracking URLs
Capture landing pages from Facebook ad tracking links:ad_id field lets you correlate captures with your ad tracking system.
Screenshots Only (Fast Mode)
When you only need visual documentation:Handling Popups
SpiderLanding automatically handles common overlays:- Cookie consent banners
- Newsletter signup popups
- Chat widgets
- Interstitial ads
If popup dismissal fails, the page is still captured - you’ll just see the popup in the screenshot.
Lazy Loading
Modern landing pages often lazy-load images and content. SpiderLanding:- Scrolls through the entire page
- Waits for network activity to settle
- Scrolls back to top
- Then captures
Storage
Files are stored in your SpiderMedia bucket:Error Handling
SpiderLanding uses graceful degradation:| Scenario | Behavior |
|---|---|
| Page never reaches “network idle” | Captures after timeout with whatever loaded |
| Popup dismissal fails | Continues capture (popup visible) |
| Screenshot fails | Other captures still attempted |
| HTML bundling fails | Returns null for html_bundle_url |
| AI extraction fails | Returns extracted: null |
errors array:
Performance
| Page Type | Expected Time |
|---|---|
| Simple static page | 3-5 seconds |
| Marketing landing page | 15-30 seconds |
| Complex SPA (React/Vue) | 30-60 seconds |
| Heavy page with timeout | 60-90 seconds |
- Page load time
- Number of assets to embed
- AI extraction (adds 2-5 seconds)
- Lazy loading scroll time
Best Practices
Disable unused features
Disable unused features
If you don’t need AI extraction, disable it to save 2-5 seconds per capture.
Use appropriate timeouts
Use appropriate timeouts
Most pages load in 30 seconds. Only increase timeout for known slow pages.
Store ad_id for correlation
Store ad_id for correlation
Always include
ad_id when capturing ad landing pages to correlate with your ad spend data.Check redirect chain
Check redirect chain
The redirect chain shows you tracking pixels and intermediate redirects - useful for understanding ad attribution.
