anymorph 0.2.2 → 0.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -0
- package/dist/index.js +26 -6
- package/dist/skillpacks/geo/skills/brand-owned-diagnosis/SKILL.md +54 -0
- package/dist/skillpacks/geo/skills/brand-owned-diagnosis/agents/openai.yaml +4 -0
- package/dist/skillpacks/geo/skills/brand-owned-diagnosis/references/diagnosis-contract.md +96 -0
- package/dist/skillpacks/geo/skills/brand-owned-diagnosis/references/workflow.md +191 -0
- package/dist/skillpacks/geo/skills/geo-generating-actions/SKILL.md +43 -0
- package/dist/skillpacks/geo/skills/geo-generating-actions/agents/openai.yaml +4 -0
- package/dist/skillpacks/geo/skills/geo-generating-actions/references/orchestrator.workflow.md +274 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/SKILL.md +50 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/agents/openai.yaml +4 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/references/external-authority-diagnosis.md +66 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/references/foundation-diagnosis.md +86 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/references/memory-contract.md +15 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/references/semantic-clusters-diagnosis.md +58 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/references/strategy-map-contract.md +26 -0
- package/dist/skillpacks/geo/skills/geo-initializing-strategy/references/visibility-diagnosis.md +50 -0
- package/dist/skillpacks/geo/skills/geo-pages-diagnosis/SKILL.md +51 -0
- package/dist/skillpacks/geo/skills/geo-pages-diagnosis/agents/openai.yaml +4 -0
- package/dist/skillpacks/geo/skills/geo-pages-diagnosis/references/diagnosis-contract.md +106 -0
- package/dist/skillpacks/geo/skills/geo-pages-diagnosis/references/workflow.md +219 -0
- package/dist/skillpacks/geo/skills/geo-writer/SKILL.md +234 -0
- package/dist/skillpacks/geo/skills/geo-writer/agents/openai.yaml +4 -0
- package/dist/skillpacks/geo/skills/geo-writer/references/content-writer-contract.md +316 -0
- package/dist/skillpacks/geo/skills/geo-writer/references/direct-sql.md +187 -0
- package/dist/skillpacks/geo/skills/geo-writer/references/seo-geo-insights.md +269 -0
- package/dist/skillpacks/geo/skills/social-execution-planning/SKILL.md +53 -0
- package/dist/skillpacks/geo/skills/social-execution-planning/agents/openai.yaml +5 -0
- package/dist/skillpacks/geo/skills/social-execution-planning/references/execution-contract.md +68 -0
- package/dist/skillpacks/geo/skills/social-execution-planning/references/platform-playbooks.md +59 -0
- package/dist/skillpacks/geo/skills/social-execution-planning/references/reddit-rules.md +69 -0
- package/dist/skillpacks/geo/skills/third-party-diagnosis/SKILL.md +54 -0
- package/dist/skillpacks/geo/skills/third-party-diagnosis/agents/openai.yaml +4 -0
- package/dist/skillpacks/geo/skills/third-party-diagnosis/references/diagnosis-contract.md +111 -0
- package/dist/skillpacks/geo/skills/third-party-diagnosis/references/workflow.md +174 -0
- package/package.json +1 -1
|
@@ -0,0 +1,269 @@
|
|
|
1
|
+
# SEO/GEO Insight Reference
|
|
2
|
+
|
|
3
|
+
Canonical source distilled from:
|
|
4
|
+
|
|
5
|
+
- `/Users/tachyon/brain/01-Projects/Content/SEO GEO insight/SEO GEO 실행 원칙.md`
|
|
6
|
+
- `/Users/tachyon/brain/01-Projects/Content/SEO GEO insight/SEO GEO 콘텐츠 원칙.md`
|
|
7
|
+
|
|
8
|
+
This reference is the operating law for `geo-writer`. Apply it before drafting, briefing, or calling page generation.
|
|
9
|
+
|
|
10
|
+
## Core Thesis
|
|
11
|
+
|
|
12
|
+
SEO/GEO는 검색어를 노리는 일이 아니라 **발견되고, 이해되고, 신뢰되고, 선택되는 답변 자산을 운영하는 일**이다.
|
|
13
|
+
|
|
14
|
+
SEO 콘텐츠는 검색 결과에서 선택될 페이지여야 한다. GEO 콘텐츠는 AI 답변 안에 합성될 근거여야 한다. 공통 기준은 `intent`, `answer`, `evidence`, `entity`, `trust`, `conversion`을 모두 갖추는 것이다.
|
|
15
|
+
|
|
16
|
+
| Dimension | SEO | GEO |
|
|
17
|
+
| --- | --- | --- |
|
|
18
|
+
| Competition surface | 검색 결과 화면 | AI 답변 내부 |
|
|
19
|
+
| Core unit | keyword, URL, SERP | prompt, entity, source, answer |
|
|
20
|
+
| Success signal | ranking, CTR, click, conversion | mention, citation, framing, AI share of voice |
|
|
21
|
+
| Main asset | 검색 의도에 맞는 페이지 | AI가 인용 가능한 근거 자산 |
|
|
22
|
+
| Execution goal | 검색 결과에서 선택될 페이지 만들기 | AI 답변 안에 들어갈 신뢰 source 만들기 |
|
|
23
|
+
|
|
24
|
+
SEO는 `page selection` 문제다. 검색엔진이 특정 문제를 가진 사람에게 페이지를 발견, 이해, 신뢰, 선택하게 만드는 것이다.
|
|
25
|
+
|
|
26
|
+
GEO는 `answer inclusion` 문제다. AI가 답변을 합성할 때 브랜드, 콘텐츠, 데이터, 관점을 신뢰 가능한 근거로 선택하고 올바른 맥락으로 재서술하게 만드는 것이다.
|
|
27
|
+
|
|
28
|
+
## Execution Layers
|
|
29
|
+
|
|
30
|
+
| Layer | SEO job | GEO job |
|
|
31
|
+
| --- | --- | --- |
|
|
32
|
+
| Accessibility | Googlebot/Bingbot이 crawl/index 가능하게 한다 | OAI-SearchBot, PerplexityBot, Bingbot, Googlebot 접근 정책을 점검한다 |
|
|
33
|
+
| Discovery | sitemap, internal links, external links로 URL 발견성을 확보한다 | IndexNow, crawler allow, source feed, third-party surface를 관리한다 |
|
|
34
|
+
| Understanding | title, heading, schema, canonical, topic cluster를 정리한다 | entity, brand, product, category, competitor 관계를 일관되게 정의한다 |
|
|
35
|
+
| Content | search intent를 만족하는 페이지를 만든다 | AI가 답변에 바로 쓸 수 있는 answer block과 evidence block을 만든다 |
|
|
36
|
+
| Trust | author, source, date, methodology, backlinks를 확보한다 | 독자적 데이터, benchmark, 고객 사례, 외부 검증 source를 확보한다 |
|
|
37
|
+
| Selection | SERP에서 클릭받을 title/meta/format을 최적화한다 | 답변 내 mention, citation, framing, response position을 최적화한다 |
|
|
38
|
+
| Measurement | impressions, clicks, CTR, position, conversion을 본다 | prompt coverage, citation share, AI share of voice, framing accuracy를 본다 |
|
|
39
|
+
|
|
40
|
+
Important content must be accessible as HTML/text. If crawlers cannot read it, SEO/GEO cannot select it as a candidate.
|
|
41
|
+
|
|
42
|
+
## Common Operating Principles
|
|
43
|
+
|
|
44
|
+
| Principle | Why it matters | Measurement |
|
|
45
|
+
| --- | --- | --- |
|
|
46
|
+
| Open crawler access | 접근 불가하면 후보에 못 들어간다 | indexed pages, crawl errors, crawler logs |
|
|
47
|
+
| Link important URLs internally and in sitemaps | 발견되지 않는 페이지는 평가되지 않는다 | discovered/indexed URL ratio |
|
|
48
|
+
| Clean canonical and duplicates | 대표 URL 신호 분산은 신뢰를 약화한다 | canonical status, duplicate warnings |
|
|
49
|
+
| One URL, one primary intent | 의도가 섞이면 선택 확률이 낮아진다 | query-page match, engagement |
|
|
50
|
+
| Add unique POV, data, or experience | generic content has no citation value | backlinks, citations, branded mentions |
|
|
51
|
+
| Attach evidence to claims | users and AI trust evidence over assertions | citation frequency, source quality |
|
|
52
|
+
| Make trust signals visible | who/how/why/source/method matter | author/source/methodology coverage |
|
|
53
|
+
| Preserve page experience | slow or obstructive pages reduce satisfaction | Core Web Vitals, UX metrics |
|
|
54
|
+
| Avoid spam optimization | keyword stuffing, schemes, scaled AI content create long-term risk | manual actions, ranking drops |
|
|
55
|
+
|
|
56
|
+
## SEO-Specific Principles
|
|
57
|
+
|
|
58
|
+
| Principle | Rule |
|
|
59
|
+
| --- | --- |
|
|
60
|
+
| Search intent first | keyword보다 실제 의도와 검색 결과의 기대 형식을 분석한다 |
|
|
61
|
+
| SERP format fit | guide, list, comparison, product page, calculator 등 현재 SERP가 원하는 형식에 맞춘다 |
|
|
62
|
+
| Bottom-funnel priority | B2B에서는 alternatives, vs, pricing, integration page를 우선 만든다 |
|
|
63
|
+
| Internal authority flow | hub/spoke 구조와 anchor text로 중요한 페이지에 발견성과 권위를 전달한다 |
|
|
64
|
+
| Link-worthy asset | 외부에서 인용할 만한 원본 데이터, 도구, 표, 분석을 만든다 |
|
|
65
|
+
|
|
66
|
+
## GEO-Specific Principles
|
|
67
|
+
|
|
68
|
+
| Principle | Rule |
|
|
69
|
+
| --- | --- |
|
|
70
|
+
| Prompt set first | keyword가 아니라 ICP가 AI에게 던질 target prompt set을 정의한다 |
|
|
71
|
+
| Answer block | heading 직후 direct answer를 둔다 |
|
|
72
|
+
| Fan-out coverage | 원 질문에서 파생되는 하위 질문까지 커버한다 |
|
|
73
|
+
| Entity consistency | 브랜드, 제품, 카테고리, 경쟁사 대비 포지션을 일관되게 정의한다 |
|
|
74
|
+
| Third-party corroboration | first-party 주장과 외부 검증 source가 충돌하지 않게 한다 |
|
|
75
|
+
| Framing control | AI가 브랜드를 어떤 맥락으로 설명하는지 추적하고 교정한다 |
|
|
76
|
+
| AI visibility measurement | GSC만 보지 말고 prompt coverage, citation share, AI share of voice를 별도로 본다 |
|
|
77
|
+
| Influence tracking | click/referral뿐 아니라 AI 답변이 구매 판단에 미치는 영향도 본다 |
|
|
78
|
+
|
|
79
|
+
GEO 콘텐츠는 AI가 문단 하나, 표 하나, 정의 하나만 떼어가도 의미가 유지되어야 한다.
|
|
80
|
+
|
|
81
|
+
## Content Quality Criteria
|
|
82
|
+
|
|
83
|
+
| Criterion | Standard |
|
|
84
|
+
| --- | --- |
|
|
85
|
+
| Intent-first | 검색어가 아니라 buyer의 실제 질문과 prompt intent에 맞아야 한다 |
|
|
86
|
+
| Answer-first | 핵심 답을 초반에 바로 줘야 한다 |
|
|
87
|
+
| Evidence-dense | 주장마다 근거, 숫자, 사례, 출처가 있어야 한다 |
|
|
88
|
+
| Non-commodity | 누구나 쓸 수 있는 일반론이 아니어야 한다 |
|
|
89
|
+
| Entity-clear | 브랜드, 제품, 카테고리, 경쟁사, 사용 사례가 명확해야 한다 |
|
|
90
|
+
| Focused | 한 페이지는 한 primary topic/intent에 집중해야 한다 |
|
|
91
|
+
| Complete | 사용자가 다시 검색하지 않아도 될 만큼 충분해야 한다 |
|
|
92
|
+
| Citable | 문장, 표, 정의, 데이터가 인용 가능한 단위여야 한다 |
|
|
93
|
+
| Trustworthy | 누가, 왜, 어떻게 만들었는지가 보여야 한다 |
|
|
94
|
+
| Fresh | 바뀌는 정보는 실제 최신 상태여야 한다 |
|
|
95
|
+
| Crawlable | 중요한 내용은 HTML/text로 접근 가능해야 한다 |
|
|
96
|
+
| Differentiated | 경험, 데이터, 고객 사례, 관점이 들어가야 한다 |
|
|
97
|
+
| Conversion-aware | 읽은 뒤 다음 행동이 자연스러워야 한다 |
|
|
98
|
+
|
|
99
|
+
## Recommended Page Structure
|
|
100
|
+
|
|
101
|
+
| Position | Must include | Standard |
|
|
102
|
+
| --- | --- | --- |
|
|
103
|
+
| Title | topic, intent, audience | 누가 왜 읽어야 하는지 즉시 보여야 한다 |
|
|
104
|
+
| Intro | 2-3 sentence direct answer | 결론을 숨기지 않는다 |
|
|
105
|
+
| Definition | standalone concept explanation | AI가 정의 문장으로 가져갈 수 있어야 한다 |
|
|
106
|
+
| Context | why the problem matters | 변화와 배경을 설명한다 |
|
|
107
|
+
| Framework | criteria, taxonomy, decision model | 독자가 생각을 정리할 수 있어야 한다 |
|
|
108
|
+
| Evidence | numbers, examples, sources, methodology | 주장을 검증 가능하게 만든다 |
|
|
109
|
+
| Comparison | alternatives and differences | buyer shortlist와 AI comparison에 들어가기 쉽다 |
|
|
110
|
+
| Practical steps | ordered action path | 읽고 바로 행동할 수 있어야 한다 |
|
|
111
|
+
| Caveats | limits, exceptions, non-fit cases | 과장 없이 신뢰를 높인다 |
|
|
112
|
+
| CTA | next action | demo, template, audit, docs 등 자연스러운 전환 |
|
|
113
|
+
|
|
114
|
+
First screen gives the answer, body builds evidence, ending creates the next action.
|
|
115
|
+
|
|
116
|
+
## SEO Content Checklist
|
|
117
|
+
|
|
118
|
+
| Item | Requirement |
|
|
119
|
+
| --- | --- |
|
|
120
|
+
| Search intent | informational, commercial, transactional, navigational 중 어디를 노리는지 분명해야 한다 |
|
|
121
|
+
| SERP fit | 현재 SERP가 원하는 형식과 맞아야 한다 |
|
|
122
|
+
| Keyword coverage | primary keyword뿐 아니라 related query와 sub-intent를 자연스럽게 포함한다 |
|
|
123
|
+
| Internal linking | hub/spoke 구조로 관련 페이지와 연결한다 |
|
|
124
|
+
| Title/meta | 검색 결과에서 클릭할 이유가 분명해야 한다 |
|
|
125
|
+
| Topic authority | 한 글이 아니라 topic cluster로 권위를 만든다 |
|
|
126
|
+
| Backlink-worthiness | 외부에서 링크할 원본 데이터, 도구, 표, 분석이 있어야 한다 |
|
|
127
|
+
| Conversion path | 정보 소비 후 다음 단계가 명확해야 한다 |
|
|
128
|
+
|
|
129
|
+
## GEO Content Checklist
|
|
130
|
+
|
|
131
|
+
| Item | Requirement |
|
|
132
|
+
| --- | --- |
|
|
133
|
+
| Prompt fit | 사용자가 AI에게 물을 법한 자연어 질문에 답한다 |
|
|
134
|
+
| Answer block | 각 주요 heading 아래에 바로 인용 가능한 답변을 둔다 |
|
|
135
|
+
| Entity consistency | 브랜드명, 제품명, 카테고리, 경쟁사 대비 포지션이 일관된다 |
|
|
136
|
+
| Evidence block | AI가 근거로 삼을 수 있는 숫자, 출처, 사례, quote가 있다 |
|
|
137
|
+
| Comparison-ready | shortlist/recommendation 답변에 쓸 기준별 비교가 있다 |
|
|
138
|
+
| Third-party alignment | 외부 정보와 모순되지 않는다 |
|
|
139
|
+
| Sourceability | 문단, 표, FAQ, definition이 독립적으로 의미를 가진다 |
|
|
140
|
+
| Framing control | 제품이 무엇이고, 누구에게 맞고, 누구에게 안 맞는지 명확하다 |
|
|
141
|
+
| Citation likelihood | original data, benchmark, expert POV처럼 인용할 이유가 있다 |
|
|
142
|
+
|
|
143
|
+
## Content Type Standards
|
|
144
|
+
|
|
145
|
+
| Type | SEO purpose | GEO purpose | Must include |
|
|
146
|
+
| --- | --- | --- | --- |
|
|
147
|
+
| What is | category understanding | AI base definition | short definition, scope, misconceptions, examples |
|
|
148
|
+
| Guide | long-tail traffic | how-to answer source | steps, checklist, practical examples |
|
|
149
|
+
| Comparison | commercial intent | shortlist/recommendation entry | criteria table, pros/cons, fit/non-fit |
|
|
150
|
+
| Alternatives | competitor demand | vendor recommendation entry | audience-based recommendations, differentiation, migration points |
|
|
151
|
+
| Benchmark | links/authority | citation source | data, methodology, sample, date |
|
|
152
|
+
| Case study | proof | trust evidence | before/after, metric, context, limits |
|
|
153
|
+
| Glossary | topic coverage | entity definition | clear definition, related concept links |
|
|
154
|
+
| Docs/API | technical buyer support | implementation answer source | exact specs, examples, error handling |
|
|
155
|
+
| Pricing/ROI | purchase decision | cost/value answer source | price logic, formula, assumptions |
|
|
156
|
+
| Template/Tool | backlink asset | practical recommendation source | usable output, examples, explanation |
|
|
157
|
+
|
|
158
|
+
## B2B SaaS Priority Assets
|
|
159
|
+
|
|
160
|
+
| Priority | Asset | Purpose |
|
|
161
|
+
| --- | --- | --- |
|
|
162
|
+
| 1 | category benchmark/report/original data | citation and authority |
|
|
163
|
+
| 2 | competitor alternatives | high-intent buyer shortlist |
|
|
164
|
+
| 3 | product comparison | comparison criteria for AI and buyers |
|
|
165
|
+
| 4 | use-case implementation guide | proof of practical problem solving |
|
|
166
|
+
| 5 | integration/migration guide | reduce adoption friction |
|
|
167
|
+
| 6 | ROI/pricing calculator | quantify purchase decision |
|
|
168
|
+
| 7 | customer story/teardown/before-after | proof and trust |
|
|
169
|
+
| 8 | technical docs/API examples | technical evaluator and AI agent support |
|
|
170
|
+
| 9 | third-party reviews/profiles/listicles | external corroboration |
|
|
171
|
+
|
|
172
|
+
## Paragraph Rules
|
|
173
|
+
|
|
174
|
+
Every paragraph must pass these rules:
|
|
175
|
+
|
|
176
|
+
| Rule | Standard |
|
|
177
|
+
| --- | --- |
|
|
178
|
+
| Independence | 문단 하나만 떼어도 의미가 유지된다 |
|
|
179
|
+
| Directness | 질문에 대한 답이 첫 문장에 있다 |
|
|
180
|
+
| Specificity | 추상 명사보다 구체적 기준, 숫자, 예시가 있다 |
|
|
181
|
+
| Verifiability | 핵심 주장에는 source, methodology, date 중 하나 이상이 붙는다 |
|
|
182
|
+
| Differentiation | 누구나 아는 말이 아니라 고유한 관점이나 경험이 있다 |
|
|
183
|
+
| Connectivity | 다음에 읽을 관련 페이지로 자연스럽게 이어진다 |
|
|
184
|
+
|
|
185
|
+
## Table Rules
|
|
186
|
+
|
|
187
|
+
Use a table only when it helps decisions or extraction.
|
|
188
|
+
|
|
189
|
+
| Rule | Standard |
|
|
190
|
+
| --- | --- |
|
|
191
|
+
| Clear criteria | rows/columns directly help buyer decision |
|
|
192
|
+
| Standalone citation | 표만 봐도 핵심 판단이 가능하다 |
|
|
193
|
+
| No cherry-picking | 우리 제품에 유리한 기준만 만들지 않는다 |
|
|
194
|
+
| Freshness | pricing, feature, ranking, benchmark에는 업데이트 날짜가 있다 |
|
|
195
|
+
| Simple structure | AI가 항목을 추출하기 쉽다 |
|
|
196
|
+
|
|
197
|
+
## Operating Loop
|
|
198
|
+
|
|
199
|
+
| Step | Question | Output |
|
|
200
|
+
| --- | --- | --- |
|
|
201
|
+
| 1. Define prompts | ICP가 AI에게 어떤 buying/research 질문을 던지는가? | target prompt set |
|
|
202
|
+
| 2. Measure visibility | 그 질문에서 우리와 경쟁사는 어떻게 언급되는가? | AI visibility baseline |
|
|
203
|
+
| 3. Analyze sources | 답변은 어떤 first-party/third-party source를 근거로 삼는가? | source map |
|
|
204
|
+
| 4. Find gaps | 어떤 fan-out 질문, entity, proof, third-party source가 비어 있는가? | gap backlog |
|
|
205
|
+
| 5. Build assets | 어떤 페이지, 데이터, 비교, 외부 검증을 만들어야 하는가? | content brief |
|
|
206
|
+
| 6. Re-measure | mention, citation, framing, referral, pipeline이 개선됐는가? | visibility report |
|
|
207
|
+
|
|
208
|
+
## Measurement Framework
|
|
209
|
+
|
|
210
|
+
| Goal | Metric | Meaning |
|
|
211
|
+
| --- | --- | --- |
|
|
212
|
+
| SEO traffic | impressions, clicks, CTR, position | 검색 결과에서 발견되고 클릭되는 정도 |
|
|
213
|
+
| SEO quality | engagement, conversion, pipeline | traffic이 비즈니스 가치로 이어지는 정도 |
|
|
214
|
+
| GEO visibility | prompt coverage | 목표 prompt 중 브랜드가 등장하는 비율 |
|
|
215
|
+
| GEO authority | citation share | AI 답변 source/citation에 포함되는 비율 |
|
|
216
|
+
| GEO positioning | framing accuracy | AI가 브랜드를 정확한 카테고리와 맥락으로 설명하는지 |
|
|
217
|
+
| Competitive position | AI share of voice | 경쟁사 대비 답변 내 언급 점유율 |
|
|
218
|
+
| Business impact | influenced pipeline | AI visibility가 pipeline에 영향을 준 정도 |
|
|
219
|
+
|
|
220
|
+
## Anti-Patterns and Myths
|
|
221
|
+
|
|
222
|
+
| Bad belief or pattern | Reality |
|
|
223
|
+
| --- | --- |
|
|
224
|
+
| 글자 수가 길수록 좋다 | word count magic은 없다. 의도 충족이 중요하다 |
|
|
225
|
+
| keyword를 많이 넣으면 된다 | keyword stuffing은 spam이다 |
|
|
226
|
+
| SEO 1등이면 AI 답변에도 나온다 | AI citation은 fan-out과 source selection 때문에 organic rank와 부분적으로만 겹친다 |
|
|
227
|
+
| `llms.txt`가 GEO 필수다 | Google은 AI search 노출에 특별 파일이 필요 없다고 설명한다 |
|
|
228
|
+
| schema를 많이 넣으면 AI가 인용한다 | schema는 이해를 돕지만 보장하지 않는다. visible content와 정확성이 우선이다 |
|
|
229
|
+
| fake mention을 만들면 된다 | inauthentic mention과 AI manipulation은 장기 리스크다 |
|
|
230
|
+
| GEO는 SEO를 대체한다 | GEO는 SEO 위에 synthesis, citation, framing layer가 추가된 것이다 |
|
|
231
|
+
| 검색어만 바꾼 복붙 페이지 | doorway/scaled content 리스크 |
|
|
232
|
+
| AI로 대량 생성한 일반론 | non-commodity value가 없다 |
|
|
233
|
+
| 출처 없는 통계 | 신뢰와 citation 가능성이 낮다 |
|
|
234
|
+
| 과장된 title | 클릭 후 만족도와 신뢰가 낮아진다 |
|
|
235
|
+
| 제품 억지 끼워넣기 | 문제 해결보다 홍보로 보인다 |
|
|
236
|
+
| 오래된 날짜만 갱신 | freshness 조작으로 보일 수 있다 |
|
|
237
|
+
| 경쟁사 왜곡 | AI와 사용자가 cross-check할 때 신뢰를 잃는다 |
|
|
238
|
+
| 숨겨진 crawler-only text | cloaking/spam 리스크 |
|
|
239
|
+
| schema와 visible content 불일치 | rich result/GEO 신뢰 모두 훼손 |
|
|
240
|
+
| 너무 넓은 mega post | intent와 citation 단위가 흐려진다 |
|
|
241
|
+
|
|
242
|
+
## Minimum Acceptance Checklist
|
|
243
|
+
|
|
244
|
+
Reject or repair the brief/content unless every answer is "yes":
|
|
245
|
+
|
|
246
|
+
- 이 페이지가 답하는 primary question이 하나로 말해지는가?
|
|
247
|
+
- 첫 5초 안에 핵심 답이 보이는가?
|
|
248
|
+
- 사용자가 다시 검색하지 않아도 되는가?
|
|
249
|
+
- 다른 글에는 없는 관점, 데이터, 경험이 있는가?
|
|
250
|
+
- AI가 문장 하나를 떼어가도 의미가 유지되는가?
|
|
251
|
+
- 주장에 근거가 붙어 있는가?
|
|
252
|
+
- 브랜드, 제품, 카테고리, 경쟁사명이 일관되는가?
|
|
253
|
+
- 관련 하위 질문으로 내부 링크가 이어지는가?
|
|
254
|
+
- 최신 날짜와 실제 업데이트 내용이 맞는가?
|
|
255
|
+
- 다음 행동이 명확한가?
|
|
256
|
+
|
|
257
|
+
## Formulas
|
|
258
|
+
|
|
259
|
+
| Goal | Formula |
|
|
260
|
+
| --- | --- |
|
|
261
|
+
| SEO traffic | `Search intent x Useful answer x Technical accessibility x Authority` |
|
|
262
|
+
| GEO visibility | `Prompt fit x Entity clarity x Evidence density x Third-party corroboration x Citation-ready structure` |
|
|
263
|
+
| B2B pipeline | `High-intent topic x Trust proof x Clear differentiation x Conversion path` |
|
|
264
|
+
|
|
265
|
+
## Closing Standard
|
|
266
|
+
|
|
267
|
+
이 페이지가 사람에게는 결정을 돕고, AI에게는 신뢰 가능한 근거가 되는가?
|
|
268
|
+
|
|
269
|
+
이 질문에 `예`라고 답할 수 없는 콘텐츠는 SEO/GEO 자산이 아니다.
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: social-execution-planning
|
|
3
|
+
description: Use when turning a selected third-party GEO Earn action into a concrete human execution plan for Reddit, YouTube, TikTok, Instagram, or LinkedIn, including social enrichment, rule checks, drafts, execution steps, and success signals.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Social Execution Planning
|
|
7
|
+
|
|
8
|
+
Use this skill after a `third_party` GEO action has already been selected.
|
|
9
|
+
|
|
10
|
+
This skill does not diagnose whether an Earn action should exist. It enriches one approved third-party action into an executable social plan for a human operator.
|
|
11
|
+
|
|
12
|
+
## Scope
|
|
13
|
+
|
|
14
|
+
Plan execution for:
|
|
15
|
+
|
|
16
|
+
- Reddit posts or comment replies.
|
|
17
|
+
- YouTube creator outreach.
|
|
18
|
+
- TikTok creator briefs.
|
|
19
|
+
- Instagram Reel or carousel briefs.
|
|
20
|
+
- LinkedIn posts, comments, or outreach.
|
|
21
|
+
|
|
22
|
+
Do not recommend automated posting, fake engagement, vote/comment coordination, review manipulation, undisclosed paid promotion, spam, or impersonation.
|
|
23
|
+
|
|
24
|
+
## Workflow
|
|
25
|
+
|
|
26
|
+
Read these references before producing a plan:
|
|
27
|
+
|
|
28
|
+
- `references/execution-contract.md` for the exact output contract.
|
|
29
|
+
- `references/reddit-rules.md` for Reddit rule checks and draft format.
|
|
30
|
+
- `references/platform-playbooks.md` for platform-specific planning guidance.
|
|
31
|
+
|
|
32
|
+
1. Start from the provided `third_party` action, policy snapshot, and backend execution context.
|
|
33
|
+
2. Prefer backend-provided cited threads, URLs, creator profiles, and candidate surfaces before broad discovery.
|
|
34
|
+
3. Use `firecrawl_search` for search and discovery.
|
|
35
|
+
4. Use `social_analyze` for Reddit, YouTube, TikTok, Instagram, and LinkedIn URLs.
|
|
36
|
+
5. Select one best execution surface when evidence is sufficient.
|
|
37
|
+
6. Produce a dashboard-ready plan with surfaces, draft, execution steps, and success signal.
|
|
38
|
+
7. If evidence is thin or platform rules block execution, return a conservative plan with open questions or a do-not-post path.
|
|
39
|
+
|
|
40
|
+
## Output Contract
|
|
41
|
+
|
|
42
|
+
Return a third-party view model:
|
|
43
|
+
|
|
44
|
+
- `assetType`: always `third_party`.
|
|
45
|
+
- `surfaces`: exact publish, reply, creator, or discovery surfaces.
|
|
46
|
+
- `draft.format`: concrete content type.
|
|
47
|
+
- `draft.angle`: audience-facing angle.
|
|
48
|
+
- `draft.body`: concise execution brief or copy-paste-ready Reddit block.
|
|
49
|
+
- `draft.tone`: human operator tone.
|
|
50
|
+
- `executionSteps`: 2-5 ordered manual steps.
|
|
51
|
+
- `successSignal`: observable measurement signal and time window.
|
|
52
|
+
|
|
53
|
+
Keep the output executable by a human operator.
|
|
@@ -0,0 +1,68 @@
|
|
|
1
|
+
# Social Execution Contract
|
|
2
|
+
|
|
3
|
+
Use this contract when enriching one selected `assetType="third_party"` GEO action for social execution.
|
|
4
|
+
|
|
5
|
+
## Inputs
|
|
6
|
+
|
|
7
|
+
- `workspaceId`
|
|
8
|
+
- optional `runId`
|
|
9
|
+
- one `GeoStrategyAction`
|
|
10
|
+
- optional policy snapshot
|
|
11
|
+
- optional backend execution context
|
|
12
|
+
|
|
13
|
+
The action is already selected. Do not re-run third-party diagnosis.
|
|
14
|
+
|
|
15
|
+
## Tools
|
|
16
|
+
|
|
17
|
+
Use:
|
|
18
|
+
|
|
19
|
+
1. `firecrawl_search` for search and discovery.
|
|
20
|
+
2. `social_analyze` for Reddit, YouTube, TikTok, Instagram, and LinkedIn URLs.
|
|
21
|
+
|
|
22
|
+
Do not use social scraping as a substitute for platform rule checks when Reddit posting or replying is proposed.
|
|
23
|
+
|
|
24
|
+
## Output
|
|
25
|
+
|
|
26
|
+
Return JSON with:
|
|
27
|
+
|
|
28
|
+
```json
|
|
29
|
+
{
|
|
30
|
+
"assetType": "third_party",
|
|
31
|
+
"surfaces": [
|
|
32
|
+
{
|
|
33
|
+
"name": "string",
|
|
34
|
+
"url": "string | null",
|
|
35
|
+
"searchQueries": ["string"]
|
|
36
|
+
}
|
|
37
|
+
],
|
|
38
|
+
"draft": {
|
|
39
|
+
"format": "string",
|
|
40
|
+
"angle": "string",
|
|
41
|
+
"body": "string | null",
|
|
42
|
+
"tone": "string | null"
|
|
43
|
+
},
|
|
44
|
+
"executionSteps": ["string"],
|
|
45
|
+
"successSignal": "string | null"
|
|
46
|
+
}
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Requirements
|
|
50
|
+
|
|
51
|
+
- `surfaces` must include at least one exact surface or a rerunnable discovery surface.
|
|
52
|
+
- `executionSteps` must contain 2-5 ordered manual steps.
|
|
53
|
+
- `successSignal` must describe an observable signal and time window when possible.
|
|
54
|
+
- Do not invent platform rules, creator contacts, metrics, brand claims, or user experiences.
|
|
55
|
+
- If evidence is thin, lower confidence in the draft body and list open questions.
|
|
56
|
+
|
|
57
|
+
## Safety Boundaries
|
|
58
|
+
|
|
59
|
+
Never recommend:
|
|
60
|
+
|
|
61
|
+
- automated posting.
|
|
62
|
+
- fake engagement.
|
|
63
|
+
- vote/comment brigading.
|
|
64
|
+
- review manipulation.
|
|
65
|
+
- undisclosed paid promotion.
|
|
66
|
+
- spam.
|
|
67
|
+
- hiding AI assistance to evade moderation.
|
|
68
|
+
- impersonation or fabricated personal experience.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
# Social Platform Playbooks
|
|
2
|
+
|
|
3
|
+
## YouTube
|
|
4
|
+
|
|
5
|
+
Use for creator outreach, comparison reviews, explainers, or product mention opportunities.
|
|
6
|
+
|
|
7
|
+
Plan should include:
|
|
8
|
+
|
|
9
|
+
- target creator or channel URL when known.
|
|
10
|
+
- why audience fit is credible.
|
|
11
|
+
- outreach angle.
|
|
12
|
+
- no content approval requirement unless explicitly allowed by policy.
|
|
13
|
+
- success signal such as creator mention, review, or citation movement.
|
|
14
|
+
|
|
15
|
+
## TikTok
|
|
16
|
+
|
|
17
|
+
Use for short-form creator briefs and trend-compatible education.
|
|
18
|
+
|
|
19
|
+
Plan should include:
|
|
20
|
+
|
|
21
|
+
- creator/profile or rerunnable discovery query.
|
|
22
|
+
- video angle.
|
|
23
|
+
- claim constraints.
|
|
24
|
+
- disclosure needs.
|
|
25
|
+
- observable signal such as creator post, engagement quality, or AI answer citation movement.
|
|
26
|
+
|
|
27
|
+
## Instagram
|
|
28
|
+
|
|
29
|
+
Use for Reel, carousel, creator outreach, or owned profile improvement.
|
|
30
|
+
|
|
31
|
+
Plan should include:
|
|
32
|
+
|
|
33
|
+
- profile or creator surface.
|
|
34
|
+
- visual/story angle.
|
|
35
|
+
- caption or creator brief.
|
|
36
|
+
- disclosure needs.
|
|
37
|
+
- measurement window.
|
|
38
|
+
|
|
39
|
+
## LinkedIn
|
|
40
|
+
|
|
41
|
+
Use for professional commentary, founder/operator post, or relevant thread comment.
|
|
42
|
+
|
|
43
|
+
Plan should include:
|
|
44
|
+
|
|
45
|
+
- target post, company profile, person profile, or discovery query.
|
|
46
|
+
- business-facing angle.
|
|
47
|
+
- draft or outreach brief.
|
|
48
|
+
- evidence and claims used.
|
|
49
|
+
- success signal such as indexed post, relevant replies, or AI answer citation movement.
|
|
50
|
+
|
|
51
|
+
## General No-Action Cases
|
|
52
|
+
|
|
53
|
+
Prefer a conservative plan or open questions when:
|
|
54
|
+
|
|
55
|
+
- no exact surface can be found.
|
|
56
|
+
- audience fit is speculative.
|
|
57
|
+
- platform rules block participation.
|
|
58
|
+
- verified claims are insufficient.
|
|
59
|
+
- the action would require fake personal experience or undisclosed promotion.
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
# Reddit Execution Rules
|
|
2
|
+
|
|
3
|
+
For Reddit actions, choose one:
|
|
4
|
+
|
|
5
|
+
- `comment_reply`: answer a specific existing high-signal thread.
|
|
6
|
+
- `new_post`: create a useful-first post for a specific subreddit.
|
|
7
|
+
- `ask_mods_first`: request moderator approval before posting.
|
|
8
|
+
- `do_not_post`: rules or context make participation unsafe.
|
|
9
|
+
|
|
10
|
+
## Discovery
|
|
11
|
+
|
|
12
|
+
Use `firecrawl_search` to find candidate threads or subreddits.
|
|
13
|
+
|
|
14
|
+
Prefer backend-provided `redditCitationContext` threads when present.
|
|
15
|
+
|
|
16
|
+
Analyze the selected Reddit URL with `social_analyze` before drafting.
|
|
17
|
+
|
|
18
|
+
## Rule Check
|
|
19
|
+
|
|
20
|
+
Before drafting, inspect the selected subreddit rules when available.
|
|
21
|
+
|
|
22
|
+
Summarize this block in `draft.body`:
|
|
23
|
+
|
|
24
|
+
```text
|
|
25
|
+
ruleCheck:
|
|
26
|
+
sourceUrl: https://www.reddit.com/r/example/about/rules
|
|
27
|
+
relevantRules:
|
|
28
|
+
- Rule name: why it matters
|
|
29
|
+
verdict: allowed | ask_mods_first | do_not_post
|
|
30
|
+
reason: One sentence tied to the rules.
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
Use `do_not_post` when rules prohibit business participation, self-promotion, AI-generated content, surveys, undisclosed promotion, or brand representatives.
|
|
34
|
+
|
|
35
|
+
Use `ask_mods_first` when moderator approval is required or ambiguity is material.
|
|
36
|
+
|
|
37
|
+
## Reddit Plan Body
|
|
38
|
+
|
|
39
|
+
For Reddit, include a copy-paste-ready block:
|
|
40
|
+
|
|
41
|
+
```text
|
|
42
|
+
redditPlan:
|
|
43
|
+
mode: comment_reply | new_post | ask_mods_first | do_not_post
|
|
44
|
+
subreddit: r/example
|
|
45
|
+
targetThreadUrl: https://www.reddit.com/r/example/comments/...
|
|
46
|
+
postTitle: Short non-promotional title for new_post only
|
|
47
|
+
commentDraft: |
|
|
48
|
+
Copy-paste-ready Reddit comment for allowed comment_reply only.
|
|
49
|
+
postBody: |
|
|
50
|
+
Copy-paste-ready Reddit post body for allowed new_post only.
|
|
51
|
+
modmailDraft: |
|
|
52
|
+
Permission request for ask_mods_first only.
|
|
53
|
+
disclosureLine: Required affiliation line, or "Not needed: no brand/product mention."
|
|
54
|
+
claimsUsed:
|
|
55
|
+
- Verified claim from the action or analyzed thread
|
|
56
|
+
doNotPostIf:
|
|
57
|
+
- Subreddit rules prohibit brand participation
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
## Drafting Rules
|
|
61
|
+
|
|
62
|
+
- Be useful first.
|
|
63
|
+
- Answer the community's question.
|
|
64
|
+
- Cite only verified facts from the input or analyzed thread.
|
|
65
|
+
- Avoid promotional language.
|
|
66
|
+
- Disclose brand/operator affiliation when recommending the brand, linking to it, or speaking from official capacity.
|
|
67
|
+
- Do not volunteer AI assistance unless rules or operator policy require it.
|
|
68
|
+
- Do not directly name the brand unless the thread, question, or objective makes it materially relevant.
|
|
69
|
+
- Do not draft first-person lived experience, testimonials, location claims, or user identities unless verified facts explicitly provide them.
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: third-party-diagnosis
|
|
3
|
+
description: Use when diagnosing third-party citation surfaces, external authority gaps, competitor presence on external sources, profile/listing opportunities, reviews, or social sentiment risks.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Third-Party Diagnosis
|
|
7
|
+
|
|
8
|
+
Use this skill for directly callable Earn / third-party diagnosis.
|
|
9
|
+
|
|
10
|
+
The output is a compact diagnosis plus action candidates for `assetType="third_party"`.
|
|
11
|
+
|
|
12
|
+
## Scope
|
|
13
|
+
|
|
14
|
+
Diagnose:
|
|
15
|
+
|
|
16
|
+
- Cited third-party domains.
|
|
17
|
+
- Competitor presence on external sources.
|
|
18
|
+
- Tenant-owned third-party profiles.
|
|
19
|
+
- Submission, listing, review, and inclusion opportunities.
|
|
20
|
+
- External sentiment risk on social or community surfaces.
|
|
21
|
+
|
|
22
|
+
Do not recommend third-party work just because a domain is frequently cited. Prefer no action when the path is speculative.
|
|
23
|
+
|
|
24
|
+
## Workflow
|
|
25
|
+
|
|
26
|
+
Read these references before producing proposals:
|
|
27
|
+
|
|
28
|
+
- `references/workflow.md` for the full third-party product workflow, actionability boundaries, candidate types, evidence gates, social handling, and no-action cases.
|
|
29
|
+
- `references/diagnosis-contract.md` for the exact runtime diagnosis contract and artifact submission shape.
|
|
30
|
+
|
|
31
|
+
1. Read shared run context and the third-party candidate slice.
|
|
32
|
+
2. Use `get_citation_intelligence` before lower-level citation calls.
|
|
33
|
+
3. Use `list_geo_strategy_candidates` for actionable domain slices.
|
|
34
|
+
4. Use `get_geo_intent_diagnostic` when intent-level citation behavior matters.
|
|
35
|
+
5. Use `social_analyze` for YouTube, Reddit, TikTok, Instagram, or LinkedIn URLs.
|
|
36
|
+
6. Use `web_scrape` only for specific non-social pages where feasibility or profile quality must be checked.
|
|
37
|
+
7. Use `web_search` only to find an official submission/profile path or verify actionability.
|
|
38
|
+
|
|
39
|
+
## Output Contract
|
|
40
|
+
|
|
41
|
+
Each proposal should include:
|
|
42
|
+
|
|
43
|
+
- exact third-party source domain.
|
|
44
|
+
- exact publish surface URL when known.
|
|
45
|
+
- content format and content angle.
|
|
46
|
+
- 2-4 concrete execution steps.
|
|
47
|
+
- expected outcome.
|
|
48
|
+
- root cause, priority, confidence, risks, and evidence.
|
|
49
|
+
|
|
50
|
+
Allowed no-action outcomes:
|
|
51
|
+
|
|
52
|
+
- external path is not actionable.
|
|
53
|
+
- citation signal exists but no credible submission/profile/update path exists.
|
|
54
|
+
- owned or generated page coverage is the clearer bottleneck.
|