mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
Four MIT collections ported — growthOS, openclaw-marketing-skills, Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45 commands, each naming its origin in its own frontmatter so the tree can be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names appeared in more than one collection and none of the copies were identical; the longest wins, which lands on the more developed text where they genuinely diverge. A fifth collection is deliberately absent. awesome-growth-hacking-skills carries NO licence, which leaves its author every right by default — and it is a list of links rather than a collection of skills, so there is nothing in it to port and no permission to port it with. It is cited as a directory to read. THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing vendor SDKs, running OAuth flows of their own, and ending with long-lived credentials in JSON files under .agents/ and ~/.growthos/ at mode 600. That is a secret on a disk with no rotation path, protected from other users and not from the agent — and one auth implementation per skill. Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect` is the one home for the flow and the platform skills defer to it by provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a tool and a curl cannot disagree. Two had nothing real behind them and now say so. There is no search_console provider, so that skill names what does answer the same questions (google_analytics, google_bigquery) and states that the remedy is a provider in hanzoai/cloud rather than a vendor SDK here. And getxapi-connect was a wrapper around a paid reseller of X's public data with the vendor's key in an env var; it is `listen` now, on our own x connector — a skill named after a vendor makes the vendor the capability and dies with it. The skills referenced paths that only existed inside the source repo, so the shared material they read is ported to reference/ and the paths rewritten. Three skills need the growthOS APPLICATION rather than its data; per the estate's own split an application belongs in hanzoai/ads, social, email or sms as a cloud plugin, so those three say what they need instead of carrying an import that resolves to nothing. Third-party product names are out of our prose and kept in the notices, which is where the licence requires them and the only place they belong. A skill's persona names a role, not somebody else's product. Co-authored-by: Hanzo Dev <[email protected]>
378 lines
23 KiB
HTML
378 lines
23 KiB
HTML
<!doctype html>
|
|
<html lang="en"><head>
|
|
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
|
|
<title>content-patterns</title>
|
|
<meta name="color-scheme" content="dark">
|
|
<style>
|
|
/* Committed to one visual world: a dark instrument panel. No light variant —
|
|
the dot field and the hairline rules only read on black, and a naive
|
|
inversion would wash both out. Every colour is painted explicitly so the page
|
|
never borrows a host background. */
|
|
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
|
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
|
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
|
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
|
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
|
|
|
|
:root{
|
|
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
|
|
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
|
|
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
|
|
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
|
|
--font-zen-pixel-square:'Zen Pixel Square',monospace;
|
|
--mono:var(--font-zen-mono);
|
|
--sans:var(--font-zen-sans);
|
|
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
|
|
--r:999px; --r-soft:14px;
|
|
}
|
|
*{box-sizing:border-box}
|
|
html{-webkit-text-size-adjust:100%}
|
|
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
|
|
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
|
|
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
|
|
|
|
/* The dot field. A halftone made of one repeating radial-gradient, faded out
|
|
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
|
|
/* No overflow clip here: the dot field is inset to the box already, and a clip
|
|
would cut off the copy-prompt menu. */
|
|
.hero{position:relative;border-bottom:1px solid var(--line)}
|
|
.hero::before{content:"";position:absolute;inset:0;
|
|
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
|
|
background-size:7px 7px;
|
|
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
|
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
|
pointer-events:none}
|
|
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
|
|
|
|
nav{border-bottom:1px solid var(--line)}
|
|
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
|
|
justify-content:space-between;align-items:center;gap:1rem}
|
|
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
|
|
text-transform:uppercase;color:var(--ink);text-decoration:none;
|
|
display:inline-flex;align-items:center;gap:.6rem}
|
|
.brand i{font-style:normal;color:var(--faint)}
|
|
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
|
|
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
|
|
text-transform:uppercase;color:var(--soft);text-decoration:none}
|
|
nav a.up:hover{color:var(--ink)}
|
|
|
|
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
|
|
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
|
|
h1 em{font-style:normal;color:var(--faint)}
|
|
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
|
|
|
|
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
|
|
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
|
|
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
|
|
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
|
|
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
|
|
line-height:1.2;font-weight:400}
|
|
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
|
|
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
|
|
.btn.solid:hover{background:#d8d8d4}
|
|
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
|
|
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
|
|
|
|
/* Copy-prompt selector. Each row copies the prompt for its own target. */
|
|
.copy{position:relative;display:inline-flex}
|
|
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
|
|
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
|
|
padding:.4rem;display:flex;flex-direction:column;
|
|
box-shadow:0 12px 32px rgba(0,0,0,.75)}
|
|
.menu[hidden]{display:none}
|
|
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
|
|
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
|
|
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
|
|
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
|
|
white-space:nowrap}
|
|
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
|
|
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
|
|
.mi:hover .mark{color:var(--ink)}
|
|
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
|
|
letter-spacing:.1em;text-transform:uppercase}
|
|
|
|
/* Works-with bar: one scrolling row, name and mark per agent. */
|
|
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
|
|
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
|
|
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
|
|
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
|
|
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
|
|
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
|
|
display:flex;align-items:center}
|
|
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
|
|
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
|
|
-webkit-overflow-scrolling:touch;
|
|
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
|
|
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
|
|
.bar::-webkit-scrollbar{display:none}
|
|
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
|
|
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
|
|
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
|
|
text-decoration:none;background:var(--ground)}
|
|
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
|
|
.agent .mark{width:.95rem;height:.95rem}
|
|
|
|
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
|
|
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
|
|
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
|
|
p{margin:0 0 1rem;max-width:70ch}
|
|
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
|
|
li{margin:.22rem 0}
|
|
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
|
|
text-decoration-color:var(--line-hi)}
|
|
a:hover{text-decoration-color:var(--ink)}
|
|
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
|
|
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
|
|
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
|
|
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
|
|
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
|
|
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
|
|
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
|
|
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
|
|
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
|
|
display:block;overflow-x:auto}
|
|
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
|
|
|
|
.curl{display:block;background:var(--panel);border:1px solid var(--line);
|
|
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
|
|
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
|
|
white-space:pre;line-height:1.9}
|
|
.curl b{color:var(--ink);font-weight:400}
|
|
.curl i{font-style:normal;color:var(--faint)}
|
|
|
|
/* index */
|
|
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
|
|
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
|
|
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
|
|
#q:focus{outline:none;border-color:var(--soft)}
|
|
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
|
|
text-transform:uppercase;margin:0 0 2rem}
|
|
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
|
|
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
|
|
padding-bottom:.45rem}
|
|
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
|
|
border-radius:var(--r-soft);text-decoration:none}
|
|
.row:hover{background:#0a0a0a}
|
|
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
|
|
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
|
|
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
|
|
color:var(--faint);font-size:.85rem}
|
|
footer a{color:var(--soft)}
|
|
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
|
|
margin:0 0 2rem;font-size:.85rem}
|
|
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
|
|
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
|
|
border-bottom:1px solid var(--line);padding-bottom:.4rem}
|
|
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
|
|
.fmap a:hover{text-decoration:underline}
|
|
.fmap div{color:var(--faint);line-height:1.5}
|
|
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
|
|
|
|
@media (max-width:640px){
|
|
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
|
|
.btns{gap:.5rem}
|
|
.btn{padding:.75rem 1.15rem;font-size:.68rem}
|
|
.copy,.copy .btn{width:100%;justify-content:center}
|
|
.menu{left:0;right:0;min-width:0}
|
|
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
|
|
.strip b{border-right:0;padding-right:0}
|
|
.bar{width:100%}
|
|
}
|
|
</style>
|
|
<link rel="alternate" type="text/markdown" href="/content-patterns.md">
|
|
|
|
<link rel="icon" href="/favicon.svg">
|
|
<link rel="canonical" href="https://hanzoskills.com/content-patterns">
|
|
</head>
|
|
<!-- Reading this with a machine? Every page here is also plain markdown.
|
|
This one: https://hanzoskills.com/content-patterns.md
|
|
Index: https://hanzoskills.com/llms.txt
|
|
Corpus: https://hanzoskills.com/all.md
|
|
Append .md to any path for the markdown twin. -->
|
|
<body>
|
|
<nav><div class="in">
|
|
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
|
|
<a class="up" href="/">All skills</a>
|
|
</div></nav>
|
|
|
|
<div class="wrap">
|
|
<h1>content-patterns</h1><p class="lede">Reusable content block patterns optimized for answer engines and AI citation.</p><h1>AEO and GEO Content Patterns</h1>
|
|
<p>Reusable content block patterns optimized for answer engines and AI citation.</p>
|
|
<hr>
|
|
<h2>Contents</h2>
|
|
<ul><li>Answer Engine Optimization (AEO) Patterns (Definition Block, Step-by-Step Block, Comparison Table Block, Pros and Cons Block, FAQ Block, Listicle Block)</li><li>Generative Engine Optimization (GEO) Patterns (Statistic Citation Block, Expert Quote Block, Authoritative Claim Block, Self-Contained Answer Block, Evidence Sandwich Block)</li><li>Domain-Specific GEO Tactics (Technology Content, Health/Medical Content, Financial Content, Legal Content, Business/Marketing Content)</li><li>Voice Search Optimization (Question Formats for Voice, Voice-Optimized Answer Structure)</li></ul>
|
|
<h2>Answer Engine Optimization (AEO) Patterns</h2>
|
|
<p>These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.</p>
|
|
<h3>Definition Block</h3>
|
|
<p>Use for "What is [X]?" queries.</p>
|
|
<pre><code class="lang-markdown">## What is [Term]?
|
|
|
|
[Term] is [concise 1-sentence definition]. [Expanded 1-2 sentence explanation with key characteristics]. [Brief context on why it matters or how it's used].</code></pre>
|
|
<p><strong>Example:</strong></p>
|
|
<pre><code class="lang-markdown">## What is Answer Engine Optimization?
|
|
|
|
Answer Engine Optimization (AEO) is the practice of structuring content so AI-powered systems can easily extract and present it as direct answers to user queries. Unlike traditional SEO that focuses on ranking in search results, AEO optimizes for featured snippets, AI Overviews, and voice assistant responses. This approach has become essential as over 60% of Google searches now end without a click.</code></pre>
|
|
<h3>Step-by-Step Block</h3>
|
|
<p>Use for "How to [X]" queries. Optimal for list snippets.</p>
|
|
<pre><code class="lang-markdown">## How to [Action/Goal]
|
|
|
|
[1-sentence overview of the process]
|
|
|
|
1. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
2. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
3. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
4. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
5. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
|
|
[Optional: Brief note on expected outcome or time estimate]</code></pre>
|
|
<p><strong>Example:</strong></p>
|
|
<pre><code class="lang-markdown">## How to Optimize Content for Featured Snippets
|
|
|
|
Earning featured snippets requires strategic formatting and direct answers to search queries.
|
|
|
|
1. **Identify snippet opportunities**: Use tools like Semrush or Ahrefs to find keywords where competitors have snippets you could capture.
|
|
2. **Match the snippet format**: Analyze whether the current snippet is a paragraph, list, or table, and format your content accordingly.
|
|
3. **Answer the question directly**: Provide a clear, concise answer (40-60 words for paragraph snippets) immediately after the question heading.
|
|
4. **Add supporting context**: Expand on your answer with examples, data, and expert insights in the following paragraphs.
|
|
5. **Use proper heading structure**: Place your target question as an H2 or H3, with the answer immediately following.
|
|
|
|
Most featured snippets appear within 2-4 weeks of publishing well-optimized content.</code></pre>
|
|
<h3>Comparison Table Block</h3>
|
|
<p>Use for "[X] vs [Y]" queries. Optimal for table snippets.</p>
|
|
<pre><code class="lang-markdown">## [Option A] vs [Option B]: [Brief Descriptor]
|
|
|
|
| Feature | [Option A] | [Option B] |
|
|
|---------|------------|------------|
|
|
| [Criteria 1] | [Value/Description] | [Value/Description] |
|
|
| [Criteria 2] | [Value/Description] | [Value/Description] |
|
|
| [Criteria 3] | [Value/Description] | [Value/Description] |
|
|
| [Criteria 4] | [Value/Description] | [Value/Description] |
|
|
| Best For | [Use case] | [Use case] |
|
|
|
|
**Bottom line**: [1-2 sentence recommendation based on different needs]</code></pre>
|
|
<h3>Pros and Cons Block</h3>
|
|
<p>Use for evaluation queries: "Is [X] worth it?", "Should I [X]?"</p>
|
|
<pre><code class="lang-markdown">## Advantages and Disadvantages of [Topic]
|
|
|
|
[1-sentence overview of the evaluation context]
|
|
|
|
### Pros
|
|
|
|
- **[Benefit category]**: [Specific explanation]
|
|
- **[Benefit category]**: [Specific explanation]
|
|
- **[Benefit category]**: [Specific explanation]
|
|
|
|
### Cons
|
|
|
|
- **[Drawback category]**: [Specific explanation]
|
|
- **[Drawback category]**: [Specific explanation]
|
|
- **[Drawback category]**: [Specific explanation]
|
|
|
|
**Verdict**: [1-2 sentence balanced conclusion with recommendation]</code></pre>
|
|
<h3>FAQ Block</h3>
|
|
<p>Use for topic pages with multiple common questions. Essential for FAQ schema.</p>
|
|
<pre><code class="lang-markdown">## Frequently Asked Questions
|
|
|
|
### [Question phrased exactly as users search]?
|
|
|
|
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
|
|
|
### [Question phrased exactly as users search]?
|
|
|
|
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
|
|
|
### [Question phrased exactly as users search]?
|
|
|
|
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].</code></pre>
|
|
<p><strong>Tips for FAQ questions:</strong></p>
|
|
<ul><li>Use natural question phrasing ("How do I..." not "How does one...")</li><li>Include question words: what, how, why, when, where, who, which</li><li>Match "People Also Ask" queries from search results</li><li>Keep answers between 50-100 words</li></ul>
|
|
<h3>Listicle Block</h3>
|
|
<p>Use for "Best [X]", "Top [X]", "[Number] ways to [X]" queries.</p>
|
|
<pre><code class="lang-markdown">## [Number] Best [Items] for [Goal/Purpose]
|
|
|
|
[1-2 sentence intro establishing context and selection criteria]
|
|
|
|
### 1. [Item Name]
|
|
|
|
[Why it's included in 2-3 sentences with specific benefits]
|
|
|
|
### 2. [Item Name]
|
|
|
|
[Why it's included in 2-3 sentences with specific benefits]
|
|
|
|
### 3. [Item Name]
|
|
|
|
[Why it's included in 2-3 sentences with specific benefits]</code></pre>
|
|
<hr>
|
|
<h2>Generative Engine Optimization (GEO) Patterns</h2>
|
|
<p>These patterns optimize content for citation by AI assistants like ChatGPT, Claude, Perplexity, and Gemini.</p>
|
|
<h3>Statistic Citation Block</h3>
|
|
<p>Statistics increase AI citation rates by 15-30%. Always include sources.</p>
|
|
<pre><code class="lang-markdown">[Claim statement]. According to [Source/Organization], [specific statistic with number and timeframe]. [Context for why this matters].</code></pre>
|
|
<p><strong>Example:</strong></p>
|
|
<pre><code class="lang-markdown">Mobile optimization is no longer optional for SEO success. According to Google's 2024 Core Web Vitals report, 70% of web traffic now comes from mobile devices, and pages failing mobile usability standards see 24% higher bounce rates. This makes mobile-first indexing a critical ranking factor.</code></pre>
|
|
<h3>Expert Quote Block</h3>
|
|
<p>Named expert attribution adds credibility and increases citation likelihood.</p>
|
|
<pre><code class="lang-markdown">"[Direct quote from expert]," says [Expert Name], [Title/Role] at [Organization]. [1 sentence of context or interpretation].</code></pre>
|
|
<p><strong>Example:</strong></p>
|
|
<pre><code class="lang-markdown">"The shift from keyword-driven search to intent-driven discovery represents the most significant change in SEO since mobile-first indexing," says Rand Fishkin, Co-founder of SparkToro. This perspective highlights why content strategies must evolve beyond traditional keyword optimization.</code></pre>
|
|
<h3>Authoritative Claim Block</h3>
|
|
<p>Structure claims for easy AI extraction with clear attribution.</p>
|
|
<pre><code class="lang-markdown">[Topic] [verb: is/has/requires/involves] [clear, specific claim]. [Source] [confirms/reports/found] that [supporting evidence]. This [explains/means/suggests] [implication or action].</code></pre>
|
|
<p><strong>Example:</strong></p>
|
|
<pre><code class="lang-markdown">E-E-A-T is the cornerstone of Google's content quality evaluation. Google's Search Quality Rater Guidelines confirm that trust is the most critical factor, stating that "untrustworthy pages have low E-E-A-T no matter how experienced, expert, or authoritative they may seem." This means content creators must prioritize transparency and accuracy above all other optimization tactics.</code></pre>
|
|
<h3>Self-Contained Answer Block</h3>
|
|
<p>Create quotable, standalone statements that AI can extract directly.</p>
|
|
<pre><code class="lang-markdown">**[Topic/Question]**: [Complete, self-contained answer that makes sense without additional context. Include specific details, numbers, or examples in 2-3 sentences.]</code></pre>
|
|
<p><strong>Example:</strong></p>
|
|
<pre><code class="lang-markdown">**Ideal blog post length for SEO**: The optimal length for SEO blog posts is 1,500-2,500 words for competitive topics. This range allows comprehensive topic coverage while maintaining reader engagement. HubSpot research shows long-form content earns 77% more backlinks than short articles, directly impacting search rankings.</code></pre>
|
|
<h3>Evidence Sandwich Block</h3>
|
|
<p>Structure claims with evidence for maximum credibility.</p>
|
|
<pre><code class="lang-markdown">[Opening claim statement].
|
|
|
|
Evidence supporting this includes:
|
|
- [Data point 1 with source]
|
|
- [Data point 2 with source]
|
|
- [Data point 3 with source]
|
|
|
|
[Concluding statement connecting evidence to actionable insight].</code></pre>
|
|
<hr>
|
|
<h2>Domain-Specific GEO Tactics</h2>
|
|
<p>Different content domains benefit from different authority signals.</p>
|
|
<h3>Technology Content</h3>
|
|
<ul><li>Emphasize technical precision and correct terminology</li><li>Include version numbers and dates for software/tools</li><li>Reference official documentation</li><li>Add code examples where relevant</li></ul>
|
|
<h3>Health/Medical Content</h3>
|
|
<ul><li>Cite peer-reviewed studies with publication details</li><li>Include expert credentials (MD, RN, etc.)</li><li>Note study limitations and context</li><li>Add "last reviewed" dates</li></ul>
|
|
<h3>Financial Content</h3>
|
|
<ul><li>Reference regulatory bodies (SEC, FTC, etc.)</li><li>Include specific numbers with timeframes</li><li>Note that information is educational, not advice</li><li>Cite recognized financial institutions</li></ul>
|
|
<h3>Legal Content</h3>
|
|
<ul><li>Cite specific laws, statutes, and regulations</li><li>Reference jurisdiction clearly</li><li>Include professional disclaimers</li><li>Note when professional consultation is advised</li></ul>
|
|
<h3>Business/Marketing Content</h3>
|
|
<ul><li>Include case studies with measurable results</li><li>Reference industry research and reports</li><li>Add percentage changes and timeframes</li><li>Quote recognized thought leaders</li></ul>
|
|
<hr>
|
|
<h2>Voice Search Optimization</h2>
|
|
<p>Voice queries are conversational and question-based. Optimize for these patterns:</p>
|
|
<h3>Question Formats for Voice</h3>
|
|
<ul><li>"What is..."</li><li>"How do I..."</li><li>"Where can I find..."</li><li>"Why does..."</li><li>"When should I..."</li><li>"Who is..."</li></ul>
|
|
<h3>Voice-Optimized Answer Structure</h3>
|
|
<ul><li>Lead with direct answer (under 30 words ideal)</li><li>Use natural, conversational language</li><li>Avoid jargon unless targeting expert audience</li><li>Include local context where relevant</li><li>Structure for single spoken response</li></ul>
|
|
<footer>
|
|
<div class="fmap">
|
|
<div><b>Build</b>
|
|
<a href="https://hanzo.app">hanzo.app</a> app builder
|
|
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
|
|
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
|
|
<div><b>Run</b>
|
|
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
|
|
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
|
|
<div><b>Account</b>
|
|
<a href="https://hanzo.id">hanzo.id</a> sign in
|
|
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
|
|
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
|
|
<div><b>Company</b>
|
|
<a href="https://hanzo.ai">hanzo.ai</a> canonical
|
|
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
|
|
</div>
|
|
<div class="fend"><a href="/content-patterns.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
|
|
</footer>
|
|
</div></body></html> |