SKILL.md · jhustle44/jcr-guide-pro

Code Commits Issues Pulls Cloud Agent CI/CD

main

copilot/add-firebase copilot/change-app-name-to-jcrguru copilot/create-zip-file copilot/create-zip-file-again copilot/merge-any-updates main master

md 378 lines 15.6 KB

Rendered Raw

1	---
2	name: geo
3	description: Optimize content for AI-generated answers in ChatGPT, Perplexity, and Google AI Overviews.
4	---
5
6	# Generative Engine Optimization (GEO)
7
8	Optimize web content so it gets cited, quoted, and surfaced by AI engines (ChatGPT, Google AI Overviews/SGE, Perplexity, Bing Copilot, Claude, and others). GEO differs from traditional SEO because AI engines don't rank pages — they synthesize answers from sources. The goal is to become one of those sources.
9
10	## When to Use
11
12	- User asks to optimize content for AI search or AI engines
13	- User wants to audit or rewrite existing pages/posts for GEO readiness
14
15	- User wants to create new content designed to appear in AI-generated answers
16	- User wants a GEO content strategy or roadmap for their brand/blog
17
18	- User mentions GEO, generative engine optimization, or AI visibility
19	- User asks how to get cited by ChatGPT, Perplexity, Google AI Overviews, etc.
20
21	## Research Foundation
22
23	Key research finding (Princeton/IIT Delhi, KDD 2024): The most impactful GEO signals are statistics (+33.9% visibility), expert quotes (+32%), fluent writing (+30%), and authoritative citations (+30.3%). These numbers should guide prioritization — when time is limited, adding statistics and expert quotes yields the highest return.
24
25	## How AI Engines Select Sources
26
27	AI engines decide what to cite based on several signals. Every recommendation in this skill traces back to one of them:
28
29	1. Direct answerability — Content that directly answers a question in a clear, self-contained way is more likely to be extracted. AI engines prefer content that doesn't require inference to understand.
30	2. Authority signals — Cited statistics, named sources, references to studies, and expert attribution increase trust. AI engines weight sourced claims higher than unsourced opinions.
31
32	3. Structured clarity — Well-organized content with clear headings, lists, and logical flow is easier for models to parse and quote. 74% of AI citations come from structured lists and comparison formats.
33	4. Topical depth — Content that covers a topic comprehensively with specifics (numbers, examples, comparisons) is preferred over shallow overviews.
34
35	5. Freshness and accuracy — Up-to-date content with current data points wins over stale pages. Contradicting widely-known facts gets filtered out.
36	6. Technical accessibility — Proper schema markup, fast load times, and clean HTML help crawlers index content correctly.
37
38	7. Community signals — Reddit, LinkedIn, Quora, and forum mentions are crawled by AI engines. Content that generates authentic discussion in these communities gets additional visibility.
39
40	## Three Modes
41
42	### Mode 1: Audit & Rewrite Existing Content
43
44	When the user provides existing content (URL, blog post, article, page) to evaluate or improve.
45
46	#### Process
47
48	1. Collect the content — Get the URL or raw content from the user. If it's a URL, fetch and extract the main content body.
49	2. Identify the core query — What search or AI prompt is this content answering? What would someone type into ChatGPT to find this?
50
51	3. Evaluate against the GEO scorecard (see `scorecard.md` for the full checklist).
52	4. Apply the rewrite checklist if the user wants improvements (not just an audit):
53
54	- Add a direct answer block in the first 40-60 words — open with the key phrase ("X is..." or "The best Y for Z is..."). This is the single highest-impact change.
55	- Inject statistics — at least one concrete data point per major section. Flag where data is needed if none is available.
56
57	- Add or strengthen named expert quotes — direct attribution to a real person or study.
58	- Add source citations inline — link to research, .gov, .edu, or recognized publications.
59
60	- Rewrite H2/H3 headings as questions or clear topical answers ("How does X work?" not "Overview").
61	- Add or expand a FAQ section — 5-10 questions in real user language at the end.
62
63	- Improve information density — named entities, stats, and specific claims per paragraph (not vague generalities).
64	- Clearly name the brand/author early in the post and in the byline.
65
66	- Trim marketing fluff — remove filler phrases that add length without adding facts ("In today's fast-paced world...", "It's important to note...").
67	- Add Article JSON-LD schema (see `technical-checklist.md`) if the user manages their own site.
68
69	1. Produce the audit report using the format below.
70
71	#### Audit Report Format
72
73	```markdown
74
75	# GEO Audit Report: [Page Title or URL]
76
77	## Overall GEO Readiness: [Score]/100
78
79	## Summary
80
81	[2-3 sentence overview of the page's GEO strengths and weaknesses]
82
83	## Scores by Category
84
85	\| Category \| Score \| Status \|
86
87	\|----------\|-------\|--------\|
88
89	\| Direct Answerability \| X/20 \| [needs work / good / strong] \|
90
91	\| Authority & Citations \| X/20 \| [needs work / good / strong] \|
92
93	\| Structure & Formatting \| X/20 \| [needs work / good / strong] \|
94
95	\| Topical Depth \| X/20 \| [needs work / good / strong] \|
96
97	\| Technical Optimization \| X/20 \| [needs work / good / strong] \|
98
99	## Detailed Findings
100
101	### Direct Answerability
102
103	[What's working, what's missing, specific examples from the content]
104
105	### Authority & Citations
106
107	[Assessment of sourcing, statistics, expert quotes, credibility signals]
108
109	### Structure & Formatting
110
111	[Heading hierarchy, use of lists, paragraph length, scanability]
112
113	### Topical Depth
114
115	[Coverage completeness, specificity, comparisons, examples provided]
116
117	### Technical Optimization
118
119	[Schema markup, meta data, page speed considerations, HTML cleanliness]
120
121	## Priority Recommendations
122
123	1. [Highest-impact change with specific instructions]
124	2. [Second priority]
125
126	3. [Third priority]
127
128	...
129
130	## Rewritten Sections (if requested)
131
132	[Full rewritten content, followed by a "GEO changes made" summary]
133
134	```
135
136	#### Delivering the Report as PDF
137
138	After writing the audit report as a markdown file, convert it to PDF and present it to the user.
139
140	1. Write the audit report to a `.md` file (e.g., `.local/geo-audit-[site-name].md`).
141	2. Convert the markdown to a styled PDF (use available workspace tools or libraries such as `pdfkit`).
142	3. Present the PDF to the user using the file presentation tool.
143
144	### Mode 2: Create GEO-Optimized Content
145
146	When the user wants to write new content from scratch.
147
148	#### Pre-Writing — Confirm These First (ask if not provided)
149
150	- Target query / topic — What question is this content answering?
151	- Target audience — Who is reading this?
152
153	- Content type — Blog post, product page, FAQ, documentation, landing page, comparison page?
154	- Brand voice/tone — Formal, conversational, technical?
155
156	- Approximate length — Default: 1,200-2,000 words for blog posts/articles.
157
158	#### GEO-Native Blog Post Structure
159
160	```text
161
162	[TITLE — phrased as a question or definitive answer]
163
164	e.g. "What Is X? The Complete Guide" or "How to Do Y in 2026"
165
166	[BYLINE — Author name + credentials/title]
167
168	[DATE — always include publish date]
169
170	[DIRECT ANSWER BLOCK — 40-60 words]
171
172	Immediately answers the post's core question. No preamble.
173
174	Starts with the key phrase: "X is..." or "The best way to Y is..."
175
176	[KEY STATISTICS — 2-3 bullet data points]
177
178	Fast-load authority signals AI engines extract immediately.
179
180	[H2: Why Does X Matter? / What Is X?]
181
182	Dense, factual prose. Named sources. Specific claims.
183
184	[H2: How Does X Work? — or next logical question]
185
186	Same pattern. Include at least one expert quote or study citation.
187
188	[H2: Ranked List or Comparison Table]
189
190	"Top 5 ways to..." or "X vs Y" — structured lists are highly citable.
191
192	[H2: Common Questions About X]
193
194	5-10 FAQ entries in real user language.
195
196	Q: [exact phrasing someone would type into ChatGPT]
197
198	A: [self-contained 2-3 sentence answer — extractable on its own]
199
200	[SOURCES / REFERENCES]
201
202	Numbered list of all cited sources with URLs.
203
204	```
205
206	For other content types (product pages, documentation, landing pages, comparison pages), read `content-patterns.md` for type-specific templates.
207
208	#### Creation Process
209
210	1. Research the query landscape — Identify the questions users and AI engines ask about this topic. Think about what an AI engine would need to construct a complete answer.
211	2. Plan the content structure — Use the blog post template above or the appropriate pattern from `content-patterns.md`.
212
213	3. Write with GEO principles applied throughout (see Writing Rules below).
214	4. Add technical optimization — Schema markup recommendations, meta descriptions, etc.
215
216	### Mode 3: GEO Content Strategy
217
218	When the user wants a strategic GEO roadmap for their blog, brand, or website.
219
220	#### Process (2)
221
222	##### Step 1: Define the entity
223
224	- What is the brand/person/product being optimized?
225	- What are the 3-5 core topics they want to be cited for?
226
227	- Who are the target audiences?
228
229	###### Step 2: Identify target prompts
230
231	Generate 15-25 specific prompts the target audience would type into ChatGPT, Perplexity, or Google AI Overviews — these are the GEO equivalent of keywords. Focus on:
232
233	- Informational: "What is the best [topic] for [use case]?"
234	- How-to: "How do I [task related to the niche]?"
235
236	- Comparative: "X vs Y: which is better for Z?"
237	- Definitional: "What is [core concept]?"
238
239	###### Step 3: Content gap analysis
240
241	For each target prompt, assess:
242
243	- Does existing content answer it directly?
244	- What content format would AI engines prefer? (FAQ, article, comparison, listicle)
245
246	- What authority signals are missing?
247
248	###### Step 4: Prioritized content plan
249
250	Produce a prioritized list of content pieces to create or optimize, ranked by:
251
252	- Citation potential — How likely is an AI engine to pull from this format?
253	- Competitive gap — Is this topic underserved by competitors?
254
255	- Business impact — Does citation here drive leads, revenue, or brand awareness?
256
257	###### Step 5: Platform-specific tactics
258
259	Read `platform-notes.md` for engine-specific recommendations.
260
261	###### Step 6: Measurement framework
262
263	Recommend the user track:
264
265	- Mention rate — % of target prompts that return the brand name (test manually or via tools like Profound, Otterly.ai)
266	- Citation rate — % that include a clickable URL to their domain
267
268	- Citation position — First mention vs. buried in the response
269	- Review cadence — Monthly minimum; weekly for active campaigns
270
271	## Writing Rules
272
273	These apply across all modes — as requirements when creating, as recommendations when auditing:
274
275	### Answer-First Structure
276
277	Place the direct answer in the first 40-60 words of the relevant section. AI engines extract opening statements more frequently than buried conclusions. Don't build up to the answer — lead with it, then support it. This is the single highest-impact optimization.
278
279	### Quotable Statements
280
281	Write sentences that work as standalone quotes. AI engines pull individual sentences or short paragraphs. Each key claim should be a self-contained, factual statement that makes sense without surrounding context.
282
283	- Good: "The average cost of a kitchen renovation in 2025 ranges from $15,000 to $45,000, depending on scope, materials, and geographic location."
284	- Bad: "When thinking about costs, there are many factors to consider, and it really depends on what you're looking for."
285
286	### Facts Over Opinions
287
288	Every claim gets a source. Include specific numbers, percentages, study names, expert names, and publication references. Unsourced claims are treated as opinions by AI engines. Even when writing original analysis, anchor claims to verifiable data points. Flag where data is needed if it's unavailable — don't leave unsourced assertions.
289
290	### Use Structured Formats
291
292	- Definition blocks — "X is [clear definition]" format for definitional queries
293	- Step-by-step lists — Numbered steps for how-to queries
294
295	- Comparison tables — Side-by-side comparisons for "vs" or "best" queries
296	- FAQ sections — Question-and-answer pairs using actual user questions
297
298	- Pros/cons lists — For evaluation queries
299
300	### Heading Hierarchy as Query Map
301
302	Each H2/H3 should mirror a natural question someone would ask. AI engines use headings to locate relevant sections. "How Much Does X Cost?" is better than "Pricing Information" because it matches the query pattern.
303
304	### Comprehensive Coverage
305
306	Cover the topic from multiple angles. AI engines prefer sources that address the full scope of a query — including related questions, edge cases, and common follow-ups. Thin content that only partially answers a question gets passed over for more complete sources.
307
308	### Freshness Signals
309
310	Include dates, version numbers, "as of [year]" references, and "updated on" indicators. AI engines prefer current information and will note when content appears outdated. Especially critical for Perplexity (real-time crawling) and Google AI Overviews.
311
312	### Entity Clarity
313
314	Name things explicitly. Instead of "the platform" or "the tool," use the actual name every time. AI engines match entities by name — pronouns and vague references break that matching. The brand/author/company should be unambiguously named and described.
315
316	### No Filler
317
318	Trim phrases that add length without adding facts. Remove: "In today's fast-paced world...", "It's important to note...", "As we all know...", "When it comes to...". Every sentence should contain a fact, a specific claim, or a direct answer.
319
320	### Paragraph Discipline
321
322	Keep paragraphs to 3-5 sentences maximum. Dense walls of text get skipped by both AI engines and human readers.
323
324	## Universal Principles
325
326	- GEO and SEO compound. Content that ranks well on Google is more likely to be in AI training data. Optimize for both.
327	- Community signals count. Reddit, LinkedIn, Quora, and forum mentions are crawled by AI engines. Encourage authentic discussion around your content.
328
329	- Write for humans first. AI clarity follows from human clarity — if it reads well to a person, it parses well for an AI engine.
330
331	## Content Patterns by Type
332
333	Read `content-patterns.md` for detailed templates and examples for each content type:
334
335	- Blog posts and articles
336	- Product and service pages
337
338	- FAQ and knowledge base pages
339	- Technical documentation
340
341	- Landing pages
342	- Comparison and review pages
343
344	## Technical Optimization Checklist
345
346	Read `technical-checklist.md` for:
347
348	- Schema markup (JSON-LD) recommendations by content type
349	- Meta description optimization for AI extraction
350
351	- HTML semantics best practices
352	- Page performance considerations
353
354	- Sitemap and crawlability
355
356	## Platform-Specific Considerations
357
358	Different AI engines have different behaviors. Read `platform-notes.md` for engine-specific guidance:
359
360	- ChatGPT/OpenAI — Browsing plugin and training data considerations
361	- Google AI Overviews — Integration with traditional search signals
362
363	- Perplexity — Real-time crawling and citation patterns
364	- Bing Copilot — Bing index reliance and citation style
365
366	## Common Mistakes
367
368	- Keyword stuffing — AI engines parse semantics, not keyword density. Unnatural repetition hurts readability without improving AI visibility.
369	- Thin content — Short pages that only scratch the surface lose to comprehensive competitors. Depth wins.
370
371	- Missing attribution — Claims without sources are treated as opinions. Always cite.
372	- Poor structure — Wall-of-text content is hard for AI to parse and quote. Use headings, lists, and short paragraphs.
373
374	- Ignoring related queries — Answering only the primary question misses opportunities. Cover the "People Also Ask" and follow-up questions.
375	- Outdated information — AI engines deprioritize stale content. Keep data points and references current.
376
377	- Burying the answer — Leading with background or preamble instead of the direct answer. The answer belongs in the first 40-60 words.
378	- Vague language — Generic statements ("many experts agree", "studies show") without naming the experts or studies. AI engines can't cite what isn't specific.