# 30-Day Commercial Launch Plan

## Launch objective

Establish SearchSignal as the clearest agent-native SEO platform, convert technical curiosity into free token creation, and measure activation through the first successful agent call.

## North-star activation event

**A new account creates a token, connects a client, and completes one successful SearchSignal tool call for a real project.**

Signup alone is not activation.

## Week 1: production readiness

### Product

- Remove the temporary login bypass and test direct-route authorization.
- Verify Free and Pro entitlements against production billing.
- Test token creation, rotation, and revocation.
- Test MCP setup in Cursor, Claude, Windsurf, and VS Code.
- Test Bearer HTTP from a generic client and the ChatGPT workflow.
- Confirm package and API URLs.

### Website

- Deploy all commercial, feature, integration, solution, and resource pages together.
- Verify canonical host, redirects, 404 behavior, and noindex on private routes.
- Run the validator and production Lighthouse checks.
- Submit the sitemap in Search Console.
- Connect analytics and conversion events.

### Proof

- Record a 45–75 second screen capture: create token → connect Cursor → ask for latest audit → receive prioritized work queue.
- Capture five real product screenshots.
- Publish a versioned tool catalog.

## Week 2: category launch

### Owned launch

- Homepage announcement
- Product-led launch article: “Why SEO data belongs inside the agent”
- Email to current users or waitlist
- Founder post with the actual workflow video
- Documentation and integration-page launch

### Community distribution

Use communities where the workflow is relevant, not broad “AI” groups:

- MCP developer discussions
- Cursor, Claude, Windsurf, and VS Code communities where promotion is permitted
- Technical SEO communities
- Indie founder and SaaS growth groups
- Agency-operations communities

Lead with a working demonstration and architecture explanation, not “we launched an AI SEO tool.”

## Week 3: paid validation

### Search campaign 1: category and integration

Ad groups:

- SEO MCP server
- MCP SEO tools
- SEO tools for Cursor
- Claude SEO tools
- AI SEO API
- SEO API for agents

Landing pages should match the exact intent. Do not send every term to the homepage.

### Search campaign 2: high-intent feature

Ad groups:

- AI technical SEO audit
- SEO audit API
- keyword research API for AI
- competitor gap API
- rank tracking API for agents

Begin with exact and phrase match. Add negatives aggressively. Optimize toward activated token, not click-through rate.

### Retargeting

Audience:

- Visited pricing, connect, docs, or an integration page
- Did not create a token

Creative:

- “One token. Your entire AI stack.”
- 20-second setup demonstration
- Free plan proof

## Week 4: conversion refinement

Review the funnel by source and page:

1. Landing-page view
2. Primary CTA click
3. Signup started
4. Signup completed
5. Project created
6. Token created
7. Config copied
8. First successful call
9. Second active day
10. Pro upgrade

Run no more than two major conversion tests at once.

Recommended first tests:

- “Start free — get your token” versus “Connect your AI free”
- Agent-console hero versus product-dashboard hero
- Free-plan proof directly under CTA versus lower on page
- Client-specific CTA on integration pages versus generic signup CTA

## Launch assets

Included in this package:

- Open Graph images for home, platform, integrations, pricing, docs, resources, solutions, and guides
- Social avatar and banner
- New logo and favicon system
- Search, social, and retargeting copy
- Press boilerplate
- Analytics event map
- Keyword and content plan

Still needed from production:

- Real screen recording
- Real authenticated screenshots
- Customer permission for any logos or quotes
- Verified customer outcome data
- Support and legal contacts
- Final billing and cancellation language

## Launch decision rules

- Do not scale paid traffic until token activation is measured correctly.
- Do not use fake testimonials to fill visual space.
- Do not publish a comparison page that misrepresents another product.
- Do not claim autonomous implementation unless the connected delivery system and permissions actually support it.
- Pause any keyword group that produces signup volume but no successful first call.
- Prioritize pages and channels that produce activated developers or teams, not vanity traffic.
