원클릭으로 Manus에서 모든 스킬 실행

seo-competitor

스타4

포크0

업데이트2026년 7월 10일 22:22

SEO-optimized competitor comparison and alternatives pages: 'X vs Y' layouts, 'alternatives to X' pages, feature matrices, comparison schema markup, and conversion-aware structure. Use when the user says 'comparison page', 'vs page', 'versus page', 'alternatives page', 'compare us against', 'competitor comparison', or 'alternative to X'. For competitor backlink gaps use seo-backlinks; for competitor content strategy use seo-content.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Gekkos-tech

Gekkos-tech/agency-os

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

시장조사 분석가·마케팅 전문가비즈니스 및 금융 운영직·SOC 13-1161

파일 탐색기

2 개 파일

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

agency-workflow

Gekkos-tech/agency-os

The agency project router — orchestrates the full client-project lifecycle BRIEF → CONCEPT → DESIGN → BUILD → QA → LAUNCH plus the post-launch MAINTAIN loop, and tells Claude which specialist skill to load at each phase. Use this skill whenever a client web project starts or advances — trigger on "new project", "neues Projekt", "website for a client", "Website für Kunde/Kunden", "Kundenprojekt starten", "start a client project", "we won a pitch", "relaunch for", "where does the project stand", "wo steht das Projekt", or any request to plan, kick off, continue, or maintain a client website, landing page, or web app — even if the user only describes the client and goal ("a website for a café in Cologne"). This skill routes, enforces phase gates, and keeps docs/project-state.md current; the actual design/build/QA work happens in the specialist skills it delegates to.

2026-07-124

cms-integration

Gekkos-tech/agency-os

Choose and integrate the right CMS for a client website — decision tree (client editing needs, budget, hosting, stack) plus integration patterns for Payload, Sanity, Storyblok, Strapi, Decap, and headless WordPress, and a client-handover checklist. Use when the user asks "which CMS", "add a CMS", "the client wants to edit content themselves", "Kunde soll Inhalte selbst pflegen", "WordPress or something modern", "headless CMS", or when the BUILD phase reveals editable content requirements. Covers selection, modeling content from the design handoff, preview setup, and editor training. NOT for building the site's frontend (BUILD phase skills), NOT for content strategy or SEO content (seo-content), NOT for one-off static sites where nothing needs client editing — recommending "no CMS" is a valid outcome of this skill.

2026-07-124

impeccable

Gekkos-tech/agency-os

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks; GSAP/scroll animation implementation belongs to gsap-suite (motion-3d).

2026-07-124

ad-concepts

Gekkos-tech/agency-os

Generates advertising campaign concepts and creative routes. Use when the user asks for a "campaign for" / "Kampagne für" a product, "ad ideas", "campaign ideation", "creative concepts for ads", "hook ideas", or wants creative directions before production. Always delivers exactly 3 distinct campaign routes (working title, core claim, hook, visual idea, primary channel, persuasion framework) built on an audience-insight step and a framework toolbox (AIDA, PAS, JTBD, 4U, hook formulas). NOT for writing finished ad copy or headlines (use ad-copy), NOT for platform format specs or asset dimensions (use social-formats), NOT for landing page structure (use landingpage-cro).

2026-07-104

ad-copy

Gekkos-tech/agency-os

Writes performance ad and landing page copy in German and English. Use when the user asks for "ad copy", "Werbetext", "headlines for", "CTA ideas", "A/B variants", "copy for the campaign", or needs finished text for Meta/Google/LinkedIn ads, landing pages, or banners. Provides headline systems (benefit, curiosity, social-proof, urgency), a funnel-stage CTA library (DE+EN), an A/B/C variant protocol with per-variant hypotheses, a tonality matrix, German-specific rules (Du/Sie, compound words, character lengths), and compliance guardrails. NOT for campaign ideation or creative routes (use ad-concepts), NOT for long-form content strategy, blog posts, or SEO articles (use seo-content skills).

2026-07-104

landingpage-cro

Gekkos-tech/agency-os

Structures and audits landing pages for conversion — the bridge between design, SEO, and copy. Use when the user asks about "landing page structure", "CRO", "conversion optimization", "why isn't the page converting", "landingpage aufbauen", or needs a section-by-section page architecture, friction audit, message-match check, or A/B testing plan. Covers the conversion narrative sequence (hero → credibility → problem/solution → offer → proof → objections → risk reversal → CTA), DACH trust elements, mobile-first conversion rules, and a measurement plan. NOT for visual design systems, typography, or component styling (use design-foundation skills), NOT for SEO audits, rankings, or keyword research (use seo-marketing skills), NOT for writing the copy itself (use ad-copy).

2026-07-104

name	seo-competitor
description	SEO-optimized competitor comparison and alternatives pages: 'X vs Y' layouts, 'alternatives to X' pages, feature matrices, comparison schema markup, and conversion-aware structure. Use when the user says 'comparison page', 'vs page', 'versus page', 'alternatives page', 'compare us against', 'competitor comparison', or 'alternative to X'. For competitor backlink gaps use seo-backlinks; for competitor content strategy use seo-content.
user-invocable	true
argument-hint	[url or generate] [competitor]
license	MIT
metadata	{"author":"AgriciDaniel","version":"2.2.0","category":"seo"}

Competitor Comparison & Alternatives Pages

Create high-converting comparison and alternatives pages that target competitive intent keywords with accurate, structured content.

Page Types

1. "X vs Y" Comparison Pages

Direct head-to-head comparison between two products/services
Balanced feature-by-feature analysis
Clear verdict or recommendation with justification
Target keyword: [Product A] vs [Product B]

2. "Alternatives to X" Pages

List of alternatives to a specific product/service
Each alternative with brief summary, pros/cons, best-for use case
Target keyword: [Product] alternatives, best alternatives to [Product]

3. "Best [Category] Tools" Roundup Pages

Curated list of top tools/services in a category
Ranking criteria clearly stated
Target keyword: best [category] tools [year], top [category] software

4. Comparison Table Pages

Feature matrix with multiple products in columns
Sortable/filterable if interactive
Target keyword: [category] comparison, [category] comparison chart

Comparison Table Generation

Feature Matrix Layout

| Feature          | Your Product | Competitor A | Competitor B |
|------------------|:------------:|:------------:|:------------:|
| Feature 1        | ✅           | ✅           | ❌           |
| Feature 2        | ✅           | ⚠️ Partial   | ✅           |
| Feature 3        | ✅           | ❌           | ❌           |
| Pricing (from)   | $X/mo        | $Y/mo        | $Z/mo        |
| Free Tier        | ✅           | ❌           | ✅           |

Data Accuracy Requirements

All feature claims must be verifiable from public sources
Pricing must be current (include "as of [date]" note)
Update frequency: review quarterly or when competitors ship major changes
Link to source for each competitor data point where possible

Schema Markup Recommendations

Product Schema with AggregateRating

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "[Product Name]",
  "description": "[Product Description]",
  "brand": {
    "@type": "Brand",
    "name": "[Brand Name]"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "[Rating]",
    "reviewCount": "[Count]",
    "bestRating": "5",
    "worstRating": "1"
  }
}

SoftwareApplication (for software comparisons)

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "[Software Name]",
  "applicationCategory": "[Category]",
  "operatingSystem": "[OS]",
  "offers": {
    "@type": "Offer",
    "price": "[Price]",
    "priceCurrency": "USD"
  }
}

ItemList (for roundup pages)

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "name": "Best [Category] Tools [Year]",
  "itemListOrder": "https://schema.org/ItemListOrderDescending",
  "numberOfItems": "[Count]",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "[Product Name]",
      "url": "[Product URL]"
    }
  ]
}

Keyword Targeting

Comparison Intent Patterns

Pattern	Example	Search Volume Signal
`[A] vs [B]`	"Slack vs Teams"	High
`[A] alternative`	"Figma alternatives"	High
`[A] alternatives [year]`	"Notion alternatives 2026"	High
`best [category] tools`	"best project management tools"	High
`[A] vs [B] for [use case]`	"AWS vs Azure for startups"	Medium
`[A] review [year]`	"Monday.com review 2026"	Medium
`[A] vs [B] pricing`	"HubSpot vs Salesforce pricing"	Medium
`is [A] better than [B]`	"is Notion better than Confluence"	Medium

Title Tag Formulas

X vs Y: [A] vs [B]: [Key Differentiator] ([Year])
Alternatives: [N] Best [A] Alternatives in [Year] (Free & Paid)
Roundup: [N] Best [Category] Tools in [Year], Compared & Ranked

H1 Patterns

Match title tag intent
Include primary keyword naturally
Keep under 70 characters

Conversion-Optimized Layouts

CTA Placement

Above fold: Brief comparison summary with primary CTA
After comparison table: "Try [Your Product] free" CTA
Bottom of page: Final recommendation with CTA
Avoid aggressive CTAs in competitor description sections (reduces trust)

Social Proof Sections

Customer testimonials relevant to comparison criteria
G2/Capterra/TrustPilot ratings (with source links)
Case studies showing migration from competitor
"Switched from [Competitor]" stories

Pricing Highlights

Clear pricing comparison table
Highlight value advantages (not just lowest price)
Include hidden costs (setup fees, per-user pricing, overage charges)
Link to full pricing page

Trust Signals

"Last updated [date]" timestamp
Author with relevant expertise
Methodology disclosure (how comparisons were conducted)
Disclosure of own product affiliation

Fairness Guidelines

Accuracy: All competitor information must be verifiable from public sources
No defamation: Never make false or misleading claims about competitors
Cite sources: Link to competitor websites, review sites, or documentation
Timely updates: Review and update when competitors release major changes
Disclose affiliation: Clearly state which product is yours
Balanced presentation: Acknowledge competitor strengths honestly
Pricing accuracy: Include "as of [date]" disclaimers on all pricing data
Feature verification: Test competitor features where possible, cite documentation otherwise

Internal Linking

Link to your own product/service pages from comparison sections
Cross-link between related comparison pages (e.g., "A vs B" links to "A vs C")
Link to feature-specific pages when discussing individual features
Breadcrumb: Home > Comparisons > [This Page]
Related comparisons section at bottom of page
Link to case studies and testimonials mentioned in the comparison

Output

Comparison Page Template

COMPARISON-PAGE.md: Ready-to-implement page structure with sections
Feature matrix table
Content outline with word count targets (minimum 1,500 words)

Schema Markup

comparison-schema.json: Product/SoftwareApplication/ItemList JSON-LD

Keyword Strategy

Primary and secondary keywords
Related long-tail opportunities
Content gaps vs existing competitor pages

Recommendations

Content improvements for existing comparison pages
New comparison page opportunities
Schema markup additions
Conversion optimization suggestions

Error Handling

Scenario	Action
Competitor URL unreachable	Report which competitor URLs failed. Proceed with available data and note gaps in the comparison.
Insufficient competitor data (pricing, features unavailable)	Flag missing data points clearly. Use "Not publicly available" in comparison tables rather than guessing.
No product/service overlap found	Report that the products serve different markets. Suggest alternative competitors that share feature overlap, or pivot to a category roundup format.