majesticlabs-dev Paid Search
Boundary
Create a strategy, not a platform guarantee. Verify current product behavior and policies before giving platform-specific instructions. Do not invent benchmarks, competitor claims, or expected returns.
Required Inputs
- Business model, offer, audience, geography, and acquisition goal
- Budget, margin, conversion value, sales cycle, and risk tolerance
- Existing account, query, creative, landing-page, and conversion data
- Current official platform documentation and policy constraints
Workflow
- Verify current campaign types, match behavior, bidding, measurement, and policy rules.
- Audit conversion definitions, attribution, consent, and tag quality before optimizing bids.
- Segment campaigns by intent, economics, geography, and landing-page promise.
- Build keyword and negative-keyword hypotheses from real queries and buyer language.
- Choose exact, phrase, broad, or keywordless reach based on control, data, and automation readiness.
- Create evidence-safe ads and message-matched landing-page requirements.
- Choose bidding from data volume and business value, then define budget guardrails.
- Set search-term, creative, landing-page, and incrementality review cadence.
Output
- Verification date and platform assumptions
- Campaign and intent architecture
- Keyword, negative, audience, and creative plan
- Bidding, budget, tracking, and guardrails
- Experiment and optimization backlog
Quality Gate
- Official current docs support platform-specific claims.
- Primary conversions represent business value.
- Benchmarks are sourced, dated context only.
- Automation has measurement and spend safeguards.
Reference
Read current-platform-checks.md before implementation.