@miranda0808/maya-claude 0.1.0
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 +30 -0
- package/bin/maya-claude.js +36 -0
- package/package.json +19 -0
- package/payload/.agents/skills/ab-test-setup/SKILL.md +266 -0
- package/payload/.agents/skills/ab-test-setup/evals/evals.json +105 -0
- package/payload/.agents/skills/ab-test-setup/references/sample-size-guide.md +263 -0
- package/payload/.agents/skills/ab-test-setup/references/test-templates.md +277 -0
- package/payload/.agents/skills/ad-creative/SKILL.md +362 -0
- package/payload/.agents/skills/ad-creative/evals/evals.json +90 -0
- package/payload/.agents/skills/ad-creative/references/generative-tools.md +637 -0
- package/payload/.agents/skills/ad-creative/references/platform-specs.md +213 -0
- package/payload/.agents/skills/ai-seo/SKILL.md +398 -0
- package/payload/.agents/skills/ai-seo/evals/evals.json +90 -0
- package/payload/.agents/skills/ai-seo/references/content-patterns.md +285 -0
- package/payload/.agents/skills/ai-seo/references/platform-ranking-factors.md +152 -0
- package/payload/.agents/skills/analytics-tracking/SKILL.md +309 -0
- package/payload/.agents/skills/analytics-tracking/evals/evals.json +90 -0
- package/payload/.agents/skills/analytics-tracking/references/event-library.md +260 -0
- package/payload/.agents/skills/analytics-tracking/references/ga4-implementation.md +300 -0
- package/payload/.agents/skills/analytics-tracking/references/gtm-implementation.md +390 -0
- package/payload/.agents/skills/churn-prevention/SKILL.md +424 -0
- package/payload/.agents/skills/churn-prevention/evals/evals.json +93 -0
- package/payload/.agents/skills/churn-prevention/references/cancel-flow-patterns.md +316 -0
- package/payload/.agents/skills/churn-prevention/references/dunning-playbook.md +408 -0
- package/payload/.agents/skills/cold-email/SKILL.md +158 -0
- package/payload/.agents/skills/cold-email/evals/evals.json +94 -0
- package/payload/.agents/skills/cold-email/references/benchmarks.md +83 -0
- package/payload/.agents/skills/cold-email/references/follow-up-sequences.md +81 -0
- package/payload/.agents/skills/cold-email/references/frameworks.md +90 -0
- package/payload/.agents/skills/cold-email/references/personalization.md +79 -0
- package/payload/.agents/skills/cold-email/references/subject-lines.md +53 -0
- package/payload/.agents/skills/competitor-alternatives/SKILL.md +256 -0
- package/payload/.agents/skills/competitor-alternatives/evals/evals.json +93 -0
- package/payload/.agents/skills/competitor-alternatives/references/content-architecture.md +271 -0
- package/payload/.agents/skills/competitor-alternatives/references/templates.md +223 -0
- package/payload/.agents/skills/content-strategy/SKILL.md +359 -0
- package/payload/.agents/skills/content-strategy/evals/evals.json +90 -0
- package/payload/.agents/skills/copy-editing/SKILL.md +447 -0
- package/payload/.agents/skills/copy-editing/evals/evals.json +89 -0
- package/payload/.agents/skills/copy-editing/references/plain-english-alternatives.md +394 -0
- package/payload/.agents/skills/copywriting/SKILL.md +252 -0
- package/payload/.agents/skills/copywriting/evals/evals.json +111 -0
- package/payload/.agents/skills/copywriting/references/copy-frameworks.md +344 -0
- package/payload/.agents/skills/copywriting/references/natural-transitions.md +272 -0
- package/payload/.agents/skills/email-sequence/SKILL.md +309 -0
- package/payload/.agents/skills/email-sequence/evals/evals.json +93 -0
- package/payload/.agents/skills/email-sequence/references/copy-guidelines.md +113 -0
- package/payload/.agents/skills/email-sequence/references/email-types.md +515 -0
- package/payload/.agents/skills/email-sequence/references/sequence-templates.md +168 -0
- package/payload/.agents/skills/form-cro/SKILL.md +429 -0
- package/payload/.agents/skills/form-cro/evals/evals.json +90 -0
- package/payload/.agents/skills/free-tool-strategy/SKILL.md +178 -0
- package/payload/.agents/skills/free-tool-strategy/evals/evals.json +90 -0
- package/payload/.agents/skills/free-tool-strategy/references/tool-types.md +217 -0
- package/payload/.agents/skills/launch-strategy/SKILL.md +353 -0
- package/payload/.agents/skills/launch-strategy/evals/evals.json +91 -0
- package/payload/.agents/skills/marketing-ideas/SKILL.md +167 -0
- package/payload/.agents/skills/marketing-ideas/evals/evals.json +90 -0
- package/payload/.agents/skills/marketing-ideas/references/ideas-by-category.md +366 -0
- package/payload/.agents/skills/marketing-psychology/SKILL.md +455 -0
- package/payload/.agents/skills/marketing-psychology/evals/evals.json +88 -0
- package/payload/.agents/skills/onboarding-cro/SKILL.md +220 -0
- package/payload/.agents/skills/onboarding-cro/evals/evals.json +92 -0
- package/payload/.agents/skills/onboarding-cro/references/experiments.md +258 -0
- package/payload/.agents/skills/page-cro/SKILL.md +182 -0
- package/payload/.agents/skills/page-cro/evals/evals.json +111 -0
- package/payload/.agents/skills/page-cro/references/experiments.md +248 -0
- package/payload/.agents/skills/paid-ads/SKILL.md +315 -0
- package/payload/.agents/skills/paid-ads/evals/evals.json +90 -0
- package/payload/.agents/skills/paid-ads/references/ad-copy-templates.md +207 -0
- package/payload/.agents/skills/paid-ads/references/audience-targeting.md +243 -0
- package/payload/.agents/skills/paid-ads/references/platform-setup-checklists.md +277 -0
- package/payload/.agents/skills/paywall-upgrade-cro/SKILL.md +227 -0
- package/payload/.agents/skills/paywall-upgrade-cro/evals/evals.json +93 -0
- package/payload/.agents/skills/paywall-upgrade-cro/references/experiments.md +164 -0
- package/payload/.agents/skills/popup-cro/SKILL.md +453 -0
- package/payload/.agents/skills/popup-cro/evals/evals.json +94 -0
- package/payload/.agents/skills/pricing-strategy/SKILL.md +231 -0
- package/payload/.agents/skills/pricing-strategy/evals/evals.json +90 -0
- package/payload/.agents/skills/pricing-strategy/references/research-methods.md +152 -0
- package/payload/.agents/skills/pricing-strategy/references/tier-structure.md +232 -0
- package/payload/.agents/skills/product-marketing-context/SKILL.md +27 -0
- package/payload/.agents/skills/product-marketing-context/evals/evals.json +40 -0
- package/payload/.agents/skills/programmatic-seo/SKILL.md +238 -0
- package/payload/.agents/skills/programmatic-seo/evals/evals.json +94 -0
- package/payload/.agents/skills/programmatic-seo/references/playbooks.md +308 -0
- package/payload/.agents/skills/referral-program/SKILL.md +255 -0
- package/payload/.agents/skills/referral-program/evals/evals.json +89 -0
- package/payload/.agents/skills/referral-program/references/affiliate-programs.md +164 -0
- package/payload/.agents/skills/referral-program/references/program-examples.md +143 -0
- package/payload/.agents/skills/revops/SKILL.md +343 -0
- package/payload/.agents/skills/revops/evals/evals.json +91 -0
- package/payload/.agents/skills/revops/references/automation-playbooks.md +290 -0
- package/payload/.agents/skills/revops/references/lifecycle-definitions.md +278 -0
- package/payload/.agents/skills/revops/references/routing-rules.md +203 -0
- package/payload/.agents/skills/revops/references/scoring-models.md +247 -0
- package/payload/.agents/skills/sales-enablement/SKILL.md +349 -0
- package/payload/.agents/skills/sales-enablement/evals/evals.json +91 -0
- package/payload/.agents/skills/sales-enablement/references/deck-frameworks.md +263 -0
- package/payload/.agents/skills/sales-enablement/references/demo-scripts.md +355 -0
- package/payload/.agents/skills/sales-enablement/references/objection-library.md +270 -0
- package/payload/.agents/skills/sales-enablement/references/one-pager-templates.md +208 -0
- package/payload/.agents/skills/schema-markup/SKILL.md +179 -0
- package/payload/.agents/skills/schema-markup/evals/evals.json +87 -0
- package/payload/.agents/skills/schema-markup/references/schema-examples.md +398 -0
- package/payload/.agents/skills/seo-audit/SKILL.md +412 -0
- package/payload/.agents/skills/seo-audit/evals/evals.json +136 -0
- package/payload/.agents/skills/seo-audit/references/ai-writing-detection.md +200 -0
- package/payload/.agents/skills/signup-flow-cro/SKILL.md +359 -0
- package/payload/.agents/skills/signup-flow-cro/evals/evals.json +88 -0
- package/payload/.agents/skills/site-architecture/SKILL.md +357 -0
- package/payload/.agents/skills/site-architecture/evals/evals.json +88 -0
- package/payload/.agents/skills/site-architecture/references/mermaid-templates.md +216 -0
- package/payload/.agents/skills/site-architecture/references/navigation-patterns.md +305 -0
- package/payload/.agents/skills/site-architecture/references/site-type-templates.md +293 -0
- package/payload/.agents/skills/social-content/SKILL.md +278 -0
- package/payload/.agents/skills/social-content/evals/evals.json +92 -0
- package/payload/.agents/skills/social-content/references/platforms.md +170 -0
- package/payload/.agents/skills/social-content/references/post-templates.md +177 -0
- package/payload/.agents/skills/social-content/references/reverse-engineering.md +195 -0
- package/payload/.maya/executor.md +79 -0
- package/payload/.maya/meta-api-agent.md +48 -0
- package/payload/.maya/modes/consult.md +63 -0
- package/payload/.maya/modes/task.md +97 -0
- package/payload/.maya/planner.md +69 -0
- package/payload/.maya/researcher.md +51 -0
- package/payload/.maya/templates/plan.md +77 -0
- package/payload/.maya/templates/state.md +87 -0
- package/payload/.maya/templates/task-packet.md +75 -0
- package/payload/MAYA-CATALOG.md +115 -0
- package/payload/MAYA-DEPENDENCIES.md +58 -0
- package/payload/MAYA.md +151 -0
- package/payload/campaigns/README.md +14 -0
- package/payload/commands/maya-consult.md +28 -0
- package/payload/commands/maya-task.md +38 -0
- package/payload/commands/product.md +55 -0
- package/payload/research/README.md +14 -0
- package/payload/templates/README.md +15 -0
- package/payload/templates/plan.md +77 -0
- package/payload/templates/state.md +87 -0
- package/payload/templates/task-packet.md +75 -0
- package/payload/tools/REGISTRY.md +368 -0
- package/payload/tools/clis/README.md +187 -0
- package/payload/tools/clis/activecampaign.js +435 -0
- package/payload/tools/clis/adobe-analytics.js +161 -0
- package/payload/tools/clis/ahrefs.js +192 -0
- package/payload/tools/clis/amplitude.js +182 -0
- package/payload/tools/clis/apollo.js +142 -0
- package/payload/tools/clis/beehiiv.js +245 -0
- package/payload/tools/clis/brevo.js +368 -0
- package/payload/tools/clis/buffer.js +260 -0
- package/payload/tools/clis/calendly.js +253 -0
- package/payload/tools/clis/clearbit.js +163 -0
- package/payload/tools/clis/customer-io.js +205 -0
- package/payload/tools/clis/dataforseo.js +257 -0
- package/payload/tools/clis/demio.js +149 -0
- package/payload/tools/clis/dub.js +158 -0
- package/payload/tools/clis/g2.js +186 -0
- package/payload/tools/clis/ga4.js +194 -0
- package/payload/tools/clis/google-ads.js +189 -0
- package/payload/tools/clis/google-search-console.js +166 -0
- package/payload/tools/clis/hotjar.js +167 -0
- package/payload/tools/clis/hunter.js +249 -0
- package/payload/tools/clis/instantly.js +270 -0
- package/payload/tools/clis/intercom.js +399 -0
- package/payload/tools/clis/keywords-everywhere.js +185 -0
- package/payload/tools/clis/kit.js +232 -0
- package/payload/tools/clis/klaviyo.js +348 -0
- package/payload/tools/clis/lemlist.js +221 -0
- package/payload/tools/clis/linkedin-ads.js +185 -0
- package/payload/tools/clis/livestorm.js +292 -0
- package/payload/tools/clis/mailchimp.js +220 -0
- package/payload/tools/clis/mention-me.js +161 -0
- package/payload/tools/clis/meta-ads.js +181 -0
- package/payload/tools/clis/mixpanel.js +248 -0
- package/payload/tools/clis/onesignal.js +241 -0
- package/payload/tools/clis/optimizely.js +233 -0
- package/payload/tools/clis/paddle.js +385 -0
- package/payload/tools/clis/partnerstack.js +382 -0
- package/payload/tools/clis/plausible.js +249 -0
- package/payload/tools/clis/postmark.js +375 -0
- package/payload/tools/clis/resend.js +370 -0
- package/payload/tools/clis/rewardful.js +160 -0
- package/payload/tools/clis/savvycal.js +223 -0
- package/payload/tools/clis/segment.js +192 -0
- package/payload/tools/clis/semrush.js +207 -0
- package/payload/tools/clis/sendgrid.js +211 -0
- package/payload/tools/clis/snov.js +237 -0
- package/payload/tools/clis/tiktok-ads.js +190 -0
- package/payload/tools/clis/tolt.js +153 -0
- package/payload/tools/clis/trustpilot.js +276 -0
- package/payload/tools/clis/typeform.js +269 -0
- package/payload/tools/clis/wistia.js +256 -0
- package/payload/tools/clis/zapier.js +160 -0
- package/payload/tools/integrations/activecampaign.md +337 -0
- package/payload/tools/integrations/adobe-analytics.md +156 -0
- package/payload/tools/integrations/ahrefs.md +142 -0
- package/payload/tools/integrations/amplitude.md +135 -0
- package/payload/tools/integrations/apollo.md +148 -0
- package/payload/tools/integrations/beehiiv.md +157 -0
- package/payload/tools/integrations/brevo.md +268 -0
- package/payload/tools/integrations/buffer.md +138 -0
- package/payload/tools/integrations/calendly.md +161 -0
- package/payload/tools/integrations/clearbit.md +142 -0
- package/payload/tools/integrations/customer-io.md +187 -0
- package/payload/tools/integrations/dataforseo.md +165 -0
- package/payload/tools/integrations/demio.md +182 -0
- package/payload/tools/integrations/dub-co.md +160 -0
- package/payload/tools/integrations/g2.md +179 -0
- package/payload/tools/integrations/ga4.md +126 -0
- package/payload/tools/integrations/google-ads.md +159 -0
- package/payload/tools/integrations/google-search-console.md +147 -0
- package/payload/tools/integrations/hotjar.md +147 -0
- package/payload/tools/integrations/hubspot.md +178 -0
- package/payload/tools/integrations/hunter.md +90 -0
- package/payload/tools/integrations/instantly.md +104 -0
- package/payload/tools/integrations/intercom.md +292 -0
- package/payload/tools/integrations/keywords-everywhere.md +207 -0
- package/payload/tools/integrations/kit.md +167 -0
- package/payload/tools/integrations/klaviyo.md +228 -0
- package/payload/tools/integrations/lemlist.md +110 -0
- package/payload/tools/integrations/linkedin-ads.md +164 -0
- package/payload/tools/integrations/livestorm.md +313 -0
- package/payload/tools/integrations/mailchimp.md +150 -0
- package/payload/tools/integrations/mention-me.md +160 -0
- package/payload/tools/integrations/meta-ads.md +147 -0
- package/payload/tools/integrations/mixpanel.md +137 -0
- package/payload/tools/integrations/onesignal.md +229 -0
- package/payload/tools/integrations/optimizely.md +171 -0
- package/payload/tools/integrations/paddle.md +212 -0
- package/payload/tools/integrations/partnerstack.md +222 -0
- package/payload/tools/integrations/plausible.md +177 -0
- package/payload/tools/integrations/posthog.md +151 -0
- package/payload/tools/integrations/postmark.md +234 -0
- package/payload/tools/integrations/resend.md +168 -0
- package/payload/tools/integrations/rewardful.md +147 -0
- package/payload/tools/integrations/salesforce.md +150 -0
- package/payload/tools/integrations/savvycal.md +181 -0
- package/payload/tools/integrations/segment.md +159 -0
- package/payload/tools/integrations/semrush.md +121 -0
- package/payload/tools/integrations/sendgrid.md +161 -0
- package/payload/tools/integrations/shopify.md +176 -0
- package/payload/tools/integrations/snov.md +94 -0
- package/payload/tools/integrations/stripe.md +148 -0
- package/payload/tools/integrations/tiktok-ads.md +161 -0
- package/payload/tools/integrations/tolt.md +144 -0
- package/payload/tools/integrations/trustpilot.md +191 -0
- package/payload/tools/integrations/typeform.md +190 -0
- package/payload/tools/integrations/webflow.md +198 -0
- package/payload/tools/integrations/wistia.md +164 -0
- package/payload/tools/integrations/wordpress.md +175 -0
- package/payload/tools/integrations/zapier.md +150 -0
- package/payload/tools/meta/README.md +55 -0
- package/payload/tools/meta/meta-cache-schema.md +65 -0
- package/payload/tools/meta/meta-fetch.ps1 +324 -0
- package/payload/tools/meta/meta-fetch.test.ps1 +38 -0
- package/vendor/shared-installer/manifests/claude-files.json +13 -0
- package/vendor/shared-installer/manifests/codex-files.json +13 -0
- package/vendor/shared-installer/manifests/common-files.json +13 -0
- package/vendor/shared-installer/package.json +15 -0
- package/vendor/shared-installer/src/bootstrap.js +12 -0
- package/vendor/shared-installer/src/cli-options.js +53 -0
- package/vendor/shared-installer/src/fs.js +105 -0
- package/vendor/shared-installer/src/index.js +44 -0
- package/vendor/shared-installer/src/install.js +157 -0
- package/vendor/shared-installer/src/manifest.js +52 -0
- package/vendor/shared-installer/templates/claude/.claude/skills/.gitkeep +1 -0
- package/vendor/shared-installer/templates/claude/CLAUDE.md +27 -0
- package/vendor/shared-installer/templates/codex/.agent/skills/.gitkeep +1 -0
- package/vendor/shared-installer/templates/codex/AGENTS.md +27 -0
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
{
|
|
2
|
+
"skill_name": "ai-seo",
|
|
3
|
+
"evals": [
|
|
4
|
+
{
|
|
5
|
+
"id": 1,
|
|
6
|
+
"prompt": "How do I make sure our SaaS product shows up in AI search results? We're a project management tool and we keep getting left out of ChatGPT and Perplexity recommendations when people ask about project management software.",
|
|
7
|
+
"expected_output": "Should use approved TASK-PACKET.md inputs first in Maya task workflows, and read PRODUCT.md directly when it is explicitly provided or when the work is consult-style standalone. Should apply the three pillars framework: Structure (make content extractable), Authority (make content citable), Presence (be where AI looks). Should run through the AI Visibility Audit checklist across platforms (Google AI Overviews, ChatGPT, Perplexity, etc.). Should check content extractability (clear definitions, structured comparisons, statistics). Should reference Princeton GEO research findings (citations improve visibility +40%, statistics +37%). Should check AI bot access in robots.txt. Should provide a prioritized action plan.",
|
|
8
|
+
"assertions": [
|
|
9
|
+
"Uses approved TASK-PACKET.md inputs or PRODUCT.md context first",
|
|
10
|
+
"Applies three pillars framework (Structure, Authority, Presence)",
|
|
11
|
+
"Runs AI Visibility Audit across platforms",
|
|
12
|
+
"Checks content extractability",
|
|
13
|
+
"References Princeton GEO research findings",
|
|
14
|
+
"Checks AI bot access in robots.txt",
|
|
15
|
+
"Provides prioritized action plan"
|
|
16
|
+
],
|
|
17
|
+
"files": []
|
|
18
|
+
},
|
|
19
|
+
{
|
|
20
|
+
"id": 2,
|
|
21
|
+
"prompt": "Should we block AI crawlers like GPTBot and PerplexityBot in our robots.txt? We're worried about content theft.",
|
|
22
|
+
"expected_output": "Should address the AI bot access question directly. Should explain the tradeoff: blocking AI bots prevents training on your content but also prevents AI platforms from citing and recommending you. Should reference the specific bots and their purposes (GPTBot, Google-Extended, PerplexityBot, ClaudeBot, etc.). Should provide the recommended robots.txt configuration. Should explain that blocking may hurt AI visibility more than it protects content. Should provide a nuanced recommendation based on business goals.",
|
|
23
|
+
"assertions": [
|
|
24
|
+
"Addresses the blocking tradeoff directly",
|
|
25
|
+
"Explains impact on AI visibility vs content protection",
|
|
26
|
+
"Lists specific AI bot user agents",
|
|
27
|
+
"Provides recommended robots.txt configuration",
|
|
28
|
+
"Gives nuanced recommendation based on business goals",
|
|
29
|
+
"Explains what each bot does"
|
|
30
|
+
],
|
|
31
|
+
"files": []
|
|
32
|
+
},
|
|
33
|
+
{
|
|
34
|
+
"id": 3,
|
|
35
|
+
"prompt": "What kind of content gets cited most by AI systems? We want to create content specifically optimized for AI search.",
|
|
36
|
+
"expected_output": "Should reference the content types that get cited most, including comparisons (~33% of AI citations), definitive guides (~15%), and other high-citation content types. Should explain why these formats work (they provide the structured, extractable, authoritative information AI systems need). Should provide specific recommendations for creating AI-optimized content: clear definitions, structured data, original statistics, comparison tables, expert quotes. Should reference the Princeton GEO research on what increases citation probability.",
|
|
37
|
+
"assertions": [
|
|
38
|
+
"References specific content types with citation rates",
|
|
39
|
+
"Mentions comparisons as highest-cited format",
|
|
40
|
+
"Explains why these formats work for AI",
|
|
41
|
+
"Provides specific content creation recommendations",
|
|
42
|
+
"References Princeton GEO research",
|
|
43
|
+
"Mentions structured data, statistics, and clear definitions"
|
|
44
|
+
],
|
|
45
|
+
"files": []
|
|
46
|
+
},
|
|
47
|
+
{
|
|
48
|
+
"id": 4,
|
|
49
|
+
"prompt": "we noticed our competitors are showing up in google AI overviews but we're not. what do we need to change?",
|
|
50
|
+
"expected_output": "Should trigger on casual phrasing. Should focus specifically on Google AI Overviews visibility. Should explain how AI Overviews selects sources (authoritative, well-structured, directly answers queries). Should run through the Structure pillar checklist: content extractability, heading hierarchy, answer-first format, structured data. Should check Authority signals: domain authority, citations, E-E-A-T. Should recommend specific content structure changes. Should suggest monitoring approach.",
|
|
51
|
+
"assertions": [
|
|
52
|
+
"Triggers on casual phrasing",
|
|
53
|
+
"Focuses on Google AI Overviews specifically",
|
|
54
|
+
"Explains how AI Overviews selects sources",
|
|
55
|
+
"Checks Structure pillar (extractability, headings, answer-first)",
|
|
56
|
+
"Checks Authority signals",
|
|
57
|
+
"Recommends specific content structure changes",
|
|
58
|
+
"Suggests monitoring approach"
|
|
59
|
+
],
|
|
60
|
+
"files": []
|
|
61
|
+
},
|
|
62
|
+
{
|
|
63
|
+
"id": 5,
|
|
64
|
+
"prompt": "Can you audit our website for AI search readiness? We want to know how visible we are across ChatGPT, Perplexity, Google AI Overviews, and other AI platforms.",
|
|
65
|
+
"expected_output": "Should run the full AI Visibility Audit. Should check each platform in the landscape (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot). Should evaluate all three pillars: Structure (content extractability, JSON-LD, clear definitions), Authority (citations, backlinks, E-E-A-T signals), Presence (AI bot access, platform-specific factors). Should provide findings organized by pillar. Should provide a prioritized action plan with specific fixes.",
|
|
66
|
+
"assertions": [
|
|
67
|
+
"Runs full AI Visibility Audit",
|
|
68
|
+
"Checks multiple AI platforms",
|
|
69
|
+
"Evaluates all three pillars (Structure, Authority, Presence)",
|
|
70
|
+
"Checks content extractability",
|
|
71
|
+
"Checks AI bot access",
|
|
72
|
+
"Provides findings organized by pillar",
|
|
73
|
+
"Provides prioritized action plan"
|
|
74
|
+
],
|
|
75
|
+
"files": []
|
|
76
|
+
},
|
|
77
|
+
{
|
|
78
|
+
"id": 6,
|
|
79
|
+
"prompt": "Our organic search traffic has dropped 30% this quarter. Can you do a full SEO audit to figure out what's going on?",
|
|
80
|
+
"expected_output": "Should recognize this is a traditional SEO audit request, not specifically an AI SEO task. Should defer to or cross-reference the seo-audit skill, which handles comprehensive traditional SEO audits including crawlability, technical foundations, on-page optimization, and content quality. May mention AI search as one factor to investigate but should make clear that seo-audit is the primary skill for this task.",
|
|
81
|
+
"assertions": [
|
|
82
|
+
"Recognizes this as a traditional SEO audit request",
|
|
83
|
+
"References or defers to seo-audit skill",
|
|
84
|
+
"Does not attempt a full traditional SEO audit using AI SEO patterns",
|
|
85
|
+
"May mention AI search as one factor to consider"
|
|
86
|
+
],
|
|
87
|
+
"files": []
|
|
88
|
+
}
|
|
89
|
+
]
|
|
90
|
+
}
|
|
@@ -0,0 +1,285 @@
|
|
|
1
|
+
# AEO and GEO Content Patterns
|
|
2
|
+
|
|
3
|
+
Reusable content block patterns optimized for answer engines and AI citation.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Contents
|
|
8
|
+
- Answer Engine Optimization (AEO) Patterns (Definition Block, Step-by-Step Block, Comparison Table Block, Pros and Cons Block, FAQ Block, Listicle Block)
|
|
9
|
+
- Generative Engine Optimization (GEO) Patterns (Statistic Citation Block, Expert Quote Block, Authoritative Claim Block, Self-Contained Answer Block, Evidence Sandwich Block)
|
|
10
|
+
- Domain-Specific GEO Tactics (Technology Content, Health/Medical Content, Financial Content, Legal Content, Business/Marketing Content)
|
|
11
|
+
- Voice Search Optimization (Question Formats for Voice, Voice-Optimized Answer Structure)
|
|
12
|
+
|
|
13
|
+
## Answer Engine Optimization (AEO) Patterns
|
|
14
|
+
|
|
15
|
+
These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.
|
|
16
|
+
|
|
17
|
+
### Definition Block
|
|
18
|
+
|
|
19
|
+
Use for "What is [X]?" queries.
|
|
20
|
+
|
|
21
|
+
```markdown
|
|
22
|
+
## What is [Term]?
|
|
23
|
+
|
|
24
|
+
[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].
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
**Example:**
|
|
28
|
+
```markdown
|
|
29
|
+
## What is Answer Engine Optimization?
|
|
30
|
+
|
|
31
|
+
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.
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
### Step-by-Step Block
|
|
35
|
+
|
|
36
|
+
Use for "How to [X]" queries. Optimal for list snippets.
|
|
37
|
+
|
|
38
|
+
```markdown
|
|
39
|
+
## How to [Action/Goal]
|
|
40
|
+
|
|
41
|
+
[1-sentence overview of the process]
|
|
42
|
+
|
|
43
|
+
1. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
44
|
+
2. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
45
|
+
3. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
46
|
+
4. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
47
|
+
5. **[Step Name]**: [Clear action description in 1-2 sentences]
|
|
48
|
+
|
|
49
|
+
[Optional: Brief note on expected outcome or time estimate]
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
**Example:**
|
|
53
|
+
```markdown
|
|
54
|
+
## How to Optimize Content for Featured Snippets
|
|
55
|
+
|
|
56
|
+
Earning featured snippets requires strategic formatting and direct answers to search queries.
|
|
57
|
+
|
|
58
|
+
1. **Identify snippet opportunities**: Use tools like Semrush or Ahrefs to find keywords where competitors have snippets you could capture.
|
|
59
|
+
2. **Match the snippet format**: Analyze whether the current snippet is a paragraph, list, or table, and format your content accordingly.
|
|
60
|
+
3. **Answer the question directly**: Provide a clear, concise answer (40-60 words for paragraph snippets) immediately after the question heading.
|
|
61
|
+
4. **Add supporting context**: Expand on your answer with examples, data, and expert insights in the following paragraphs.
|
|
62
|
+
5. **Use proper heading structure**: Place your target question as an H2 or H3, with the answer immediately following.
|
|
63
|
+
|
|
64
|
+
Most featured snippets appear within 2-4 weeks of publishing well-optimized content.
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### Comparison Table Block
|
|
68
|
+
|
|
69
|
+
Use for "[X] vs [Y]" queries. Optimal for table snippets.
|
|
70
|
+
|
|
71
|
+
```markdown
|
|
72
|
+
## [Option A] vs [Option B]: [Brief Descriptor]
|
|
73
|
+
|
|
74
|
+
| Feature | [Option A] | [Option B] |
|
|
75
|
+
|---------|------------|------------|
|
|
76
|
+
| [Criteria 1] | [Value/Description] | [Value/Description] |
|
|
77
|
+
| [Criteria 2] | [Value/Description] | [Value/Description] |
|
|
78
|
+
| [Criteria 3] | [Value/Description] | [Value/Description] |
|
|
79
|
+
| [Criteria 4] | [Value/Description] | [Value/Description] |
|
|
80
|
+
| Best For | [Use case] | [Use case] |
|
|
81
|
+
|
|
82
|
+
**Bottom line**: [1-2 sentence recommendation based on different needs]
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
### Pros and Cons Block
|
|
86
|
+
|
|
87
|
+
Use for evaluation queries: "Is [X] worth it?", "Should I [X]?"
|
|
88
|
+
|
|
89
|
+
```markdown
|
|
90
|
+
## Advantages and Disadvantages of [Topic]
|
|
91
|
+
|
|
92
|
+
[1-sentence overview of the evaluation context]
|
|
93
|
+
|
|
94
|
+
### Pros
|
|
95
|
+
|
|
96
|
+
- **[Benefit category]**: [Specific explanation]
|
|
97
|
+
- **[Benefit category]**: [Specific explanation]
|
|
98
|
+
- **[Benefit category]**: [Specific explanation]
|
|
99
|
+
|
|
100
|
+
### Cons
|
|
101
|
+
|
|
102
|
+
- **[Drawback category]**: [Specific explanation]
|
|
103
|
+
- **[Drawback category]**: [Specific explanation]
|
|
104
|
+
- **[Drawback category]**: [Specific explanation]
|
|
105
|
+
|
|
106
|
+
**Verdict**: [1-2 sentence balanced conclusion with recommendation]
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
### FAQ Block
|
|
110
|
+
|
|
111
|
+
Use for topic pages with multiple common questions. Essential for FAQ schema.
|
|
112
|
+
|
|
113
|
+
```markdown
|
|
114
|
+
## Frequently Asked Questions
|
|
115
|
+
|
|
116
|
+
### [Question phrased exactly as users search]?
|
|
117
|
+
|
|
118
|
+
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
|
119
|
+
|
|
120
|
+
### [Question phrased exactly as users search]?
|
|
121
|
+
|
|
122
|
+
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
|
123
|
+
|
|
124
|
+
### [Question phrased exactly as users search]?
|
|
125
|
+
|
|
126
|
+
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
**Tips for FAQ questions:**
|
|
130
|
+
- Use natural question phrasing ("How do I..." not "How does one...")
|
|
131
|
+
- Include question words: what, how, why, when, where, who, which
|
|
132
|
+
- Match "People Also Ask" queries from search results
|
|
133
|
+
- Keep answers between 50-100 words
|
|
134
|
+
|
|
135
|
+
### Listicle Block
|
|
136
|
+
|
|
137
|
+
Use for "Best [X]", "Top [X]", "[Number] ways to [X]" queries.
|
|
138
|
+
|
|
139
|
+
```markdown
|
|
140
|
+
## [Number] Best [Items] for [Goal/Purpose]
|
|
141
|
+
|
|
142
|
+
[1-2 sentence intro establishing context and selection criteria]
|
|
143
|
+
|
|
144
|
+
### 1. [Item Name]
|
|
145
|
+
|
|
146
|
+
[Why it's included in 2-3 sentences with specific benefits]
|
|
147
|
+
|
|
148
|
+
### 2. [Item Name]
|
|
149
|
+
|
|
150
|
+
[Why it's included in 2-3 sentences with specific benefits]
|
|
151
|
+
|
|
152
|
+
### 3. [Item Name]
|
|
153
|
+
|
|
154
|
+
[Why it's included in 2-3 sentences with specific benefits]
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
---
|
|
158
|
+
|
|
159
|
+
## Generative Engine Optimization (GEO) Patterns
|
|
160
|
+
|
|
161
|
+
These patterns optimize content for citation by AI assistants like ChatGPT, Claude, Perplexity, and Gemini.
|
|
162
|
+
|
|
163
|
+
### Statistic Citation Block
|
|
164
|
+
|
|
165
|
+
Statistics increase AI citation rates by 15-30%. Always include sources.
|
|
166
|
+
|
|
167
|
+
```markdown
|
|
168
|
+
[Claim statement]. According to [Source/Organization], [specific statistic with number and timeframe]. [Context for why this matters].
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
**Example:**
|
|
172
|
+
```markdown
|
|
173
|
+
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.
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
### Expert Quote Block
|
|
177
|
+
|
|
178
|
+
Named expert attribution adds credibility and increases citation likelihood.
|
|
179
|
+
|
|
180
|
+
```markdown
|
|
181
|
+
"[Direct quote from expert]," says [Expert Name], [Title/Role] at [Organization]. [1 sentence of context or interpretation].
|
|
182
|
+
```
|
|
183
|
+
|
|
184
|
+
**Example:**
|
|
185
|
+
```markdown
|
|
186
|
+
"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.
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
### Authoritative Claim Block
|
|
190
|
+
|
|
191
|
+
Structure claims for easy AI extraction with clear attribution.
|
|
192
|
+
|
|
193
|
+
```markdown
|
|
194
|
+
[Topic] [verb: is/has/requires/involves] [clear, specific claim]. [Source] [confirms/reports/found] that [supporting evidence]. This [explains/means/suggests] [implication or action].
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
**Example:**
|
|
198
|
+
```markdown
|
|
199
|
+
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.
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
### Self-Contained Answer Block
|
|
203
|
+
|
|
204
|
+
Create quotable, standalone statements that AI can extract directly.
|
|
205
|
+
|
|
206
|
+
```markdown
|
|
207
|
+
**[Topic/Question]**: [Complete, self-contained answer that makes sense without additional context. Include specific details, numbers, or examples in 2-3 sentences.]
|
|
208
|
+
```
|
|
209
|
+
|
|
210
|
+
**Example:**
|
|
211
|
+
```markdown
|
|
212
|
+
**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.
|
|
213
|
+
```
|
|
214
|
+
|
|
215
|
+
### Evidence Sandwich Block
|
|
216
|
+
|
|
217
|
+
Structure claims with evidence for maximum credibility.
|
|
218
|
+
|
|
219
|
+
```markdown
|
|
220
|
+
[Opening claim statement].
|
|
221
|
+
|
|
222
|
+
Evidence supporting this includes:
|
|
223
|
+
- [Data point 1 with source]
|
|
224
|
+
- [Data point 2 with source]
|
|
225
|
+
- [Data point 3 with source]
|
|
226
|
+
|
|
227
|
+
[Concluding statement connecting evidence to actionable insight].
|
|
228
|
+
```
|
|
229
|
+
|
|
230
|
+
---
|
|
231
|
+
|
|
232
|
+
## Domain-Specific GEO Tactics
|
|
233
|
+
|
|
234
|
+
Different content domains benefit from different authority signals.
|
|
235
|
+
|
|
236
|
+
### Technology Content
|
|
237
|
+
- Emphasize technical precision and correct terminology
|
|
238
|
+
- Include version numbers and dates for software/tools
|
|
239
|
+
- Reference official documentation
|
|
240
|
+
- Add code examples where relevant
|
|
241
|
+
|
|
242
|
+
### Health/Medical Content
|
|
243
|
+
- Cite peer-reviewed studies with publication details
|
|
244
|
+
- Include expert credentials (MD, RN, etc.)
|
|
245
|
+
- Note study limitations and context
|
|
246
|
+
- Add "last reviewed" dates
|
|
247
|
+
|
|
248
|
+
### Financial Content
|
|
249
|
+
- Reference regulatory bodies (SEC, FTC, etc.)
|
|
250
|
+
- Include specific numbers with timeframes
|
|
251
|
+
- Note that information is educational, not advice
|
|
252
|
+
- Cite recognized financial institutions
|
|
253
|
+
|
|
254
|
+
### Legal Content
|
|
255
|
+
- Cite specific laws, statutes, and regulations
|
|
256
|
+
- Reference jurisdiction clearly
|
|
257
|
+
- Include professional disclaimers
|
|
258
|
+
- Note when professional consultation is advised
|
|
259
|
+
|
|
260
|
+
### Business/Marketing Content
|
|
261
|
+
- Include case studies with measurable results
|
|
262
|
+
- Reference industry research and reports
|
|
263
|
+
- Add percentage changes and timeframes
|
|
264
|
+
- Quote recognized thought leaders
|
|
265
|
+
|
|
266
|
+
---
|
|
267
|
+
|
|
268
|
+
## Voice Search Optimization
|
|
269
|
+
|
|
270
|
+
Voice queries are conversational and question-based. Optimize for these patterns:
|
|
271
|
+
|
|
272
|
+
### Question Formats for Voice
|
|
273
|
+
- "What is..."
|
|
274
|
+
- "How do I..."
|
|
275
|
+
- "Where can I find..."
|
|
276
|
+
- "Why does..."
|
|
277
|
+
- "When should I..."
|
|
278
|
+
- "Who is..."
|
|
279
|
+
|
|
280
|
+
### Voice-Optimized Answer Structure
|
|
281
|
+
- Lead with direct answer (under 30 words ideal)
|
|
282
|
+
- Use natural, conversational language
|
|
283
|
+
- Avoid jargon unless targeting expert audience
|
|
284
|
+
- Include local context where relevant
|
|
285
|
+
- Structure for single spoken response
|
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
# How Each AI Platform Picks Sources
|
|
2
|
+
|
|
3
|
+
Each AI search platform has its own search index, ranking logic, and content preferences. This guide covers what matters for getting cited on each one.
|
|
4
|
+
|
|
5
|
+
Sources cited throughout: Princeton GEO study (KDD 2024), SE Ranking domain authority study, ZipTie content-answer fit analysis.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## The Fundamentals
|
|
10
|
+
|
|
11
|
+
Every AI platform shares three baseline requirements:
|
|
12
|
+
|
|
13
|
+
1. **Your content must be in their index** — Each platform uses a different search backend (Google, Bing, Brave, or their own). If you're not indexed, you can't be cited.
|
|
14
|
+
2. **Your content must be crawlable** — AI bots need access via robots.txt. Block the bot, lose the citation.
|
|
15
|
+
3. **Your content must be extractable** — AI systems pull passages, not pages. Clear structure and self-contained paragraphs win.
|
|
16
|
+
|
|
17
|
+
Beyond these basics, each platform weights different signals. Here's what matters and where.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## Google AI Overviews
|
|
22
|
+
|
|
23
|
+
Google AI Overviews pull from Google's own index and lean heavily on E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness). They appear in roughly 45% of Google searches.
|
|
24
|
+
|
|
25
|
+
**What makes Google AI Overviews different:** They already have your traditional SEO signals — backlinks, page authority, topical relevance. The additional AI layer adds a preference for content with cited sources and structured data. Research shows that including authoritative citations in your content correlates with a 132% visibility boost, and writing with an authoritative (not salesy) tone adds another 89%.
|
|
26
|
+
|
|
27
|
+
**Importantly, AI Overviews don't just recycle the traditional Top 10.** Only about 15% of AI Overview sources overlap with conventional organic results. Pages that wouldn't crack page 1 in traditional search can still get cited if they have strong structured data and clear, extractable answers.
|
|
28
|
+
|
|
29
|
+
**What to focus on:**
|
|
30
|
+
- Schema markup is the single biggest lever — Article, FAQPage, HowTo, and Product schemas give AI Overviews structured context to work with (30-40% visibility boost)
|
|
31
|
+
- Build topical authority through content clusters with strong internal linking
|
|
32
|
+
- Include named, sourced citations in your content (not just claims)
|
|
33
|
+
- Author bios with real credentials matter — E-E-A-T is weighted heavily
|
|
34
|
+
- Get into Google's Knowledge Graph where possible (an accurate Wikipedia entry helps)
|
|
35
|
+
- Target "how to" and "what is" query patterns — these trigger AI Overviews most often
|
|
36
|
+
|
|
37
|
+
---
|
|
38
|
+
|
|
39
|
+
## ChatGPT
|
|
40
|
+
|
|
41
|
+
ChatGPT's web search draws from a Bing-based index. It combines this with its training knowledge to generate answers, then cites the web sources it relied on.
|
|
42
|
+
|
|
43
|
+
**What makes ChatGPT different:** Domain authority matters more here than on other AI platforms. An SE Ranking analysis of 129,000 domains found that authority and credibility signals account for roughly 40% of what determines citation, with content quality at about 35% and platform trust at 25%. Sites with very high referring domain counts (350K+) average 8.4 citations per response, while sites with slightly lower trust scores (91-96 vs 97-100) drop from 8.4 to 6 citations.
|
|
44
|
+
|
|
45
|
+
**Freshness is a major differentiator.** Content updated within the last 30 days gets cited about 3.2x more often than older content. ChatGPT clearly favors recent information.
|
|
46
|
+
|
|
47
|
+
**The most important signal is content-answer fit** — a ZipTie analysis of 400,000 pages found that how well your content's style and structure matches ChatGPT's own response format accounts for about 55% of citation likelihood. This is far more important than domain authority (12%) or on-page structure (14%) alone. Write the way ChatGPT would answer the question, and you're more likely to be the source it cites.
|
|
48
|
+
|
|
49
|
+
**Where ChatGPT looks beyond your site:** Wikipedia accounts for 7.8% of all ChatGPT citations, Reddit for 1.8%, and Forbes for 1.1%. Brand official sites are cited frequently but third-party mentions carry significant weight.
|
|
50
|
+
|
|
51
|
+
**What to focus on:**
|
|
52
|
+
- Invest in backlinks and domain authority — it's the strongest baseline signal
|
|
53
|
+
- Update competitive content at least monthly
|
|
54
|
+
- Structure your content the way ChatGPT structures its answers (conversational, direct, well-organized)
|
|
55
|
+
- Include verifiable statistics with named sources
|
|
56
|
+
- Clean heading hierarchy (H1 > H2 > H3) with descriptive headings
|
|
57
|
+
|
|
58
|
+
---
|
|
59
|
+
|
|
60
|
+
## Perplexity
|
|
61
|
+
|
|
62
|
+
Perplexity always cites its sources with clickable links, making it the most transparent AI search platform. It combines its own index with Google's and runs results through multiple reranking passes — initial relevance retrieval, then traditional ranking factor scoring, then ML-based quality evaluation that can discard entire result sets if they don't meet quality thresholds.
|
|
63
|
+
|
|
64
|
+
**What makes Perplexity different:** It's the most "research-oriented" AI search engine, and its citation behavior reflects that. Perplexity maintains curated lists of authoritative domains (Amazon, GitHub, major academic sites) that get inherent ranking boosts. It uses a time-decay algorithm that evaluates new content quickly, giving fresh publishers a real shot at citation.
|
|
65
|
+
|
|
66
|
+
**Perplexity has unique content preferences:**
|
|
67
|
+
- **FAQ Schema (JSON-LD)** — Pages with FAQ structured data get cited noticeably more often
|
|
68
|
+
- **PDF documents** — Publicly accessible PDFs (whitepapers, research reports) are prioritized. If you have authoritative PDF content gated behind a form, consider making a version public.
|
|
69
|
+
- **Publishing velocity** — How frequently you publish matters more than keyword targeting
|
|
70
|
+
- **Self-contained paragraphs** — Perplexity prefers atomic, semantically complete paragraphs it can extract cleanly
|
|
71
|
+
|
|
72
|
+
**What to focus on:**
|
|
73
|
+
- Allow PerplexityBot in robots.txt
|
|
74
|
+
- Implement FAQPage schema on any page with Q&A content
|
|
75
|
+
- Host PDF resources publicly (whitepapers, guides, reports)
|
|
76
|
+
- Add Article schema with publication and modification timestamps
|
|
77
|
+
- Write in clear, self-contained paragraphs that work as standalone answers
|
|
78
|
+
- Build deep topical authority in your specific niche
|
|
79
|
+
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
## Microsoft Copilot
|
|
83
|
+
|
|
84
|
+
Copilot is embedded across Microsoft's ecosystem — Edge, Windows, Microsoft 365, and Bing Search. It relies entirely on Bing's index, so if Bing hasn't indexed your content, Copilot can't cite it.
|
|
85
|
+
|
|
86
|
+
**What makes Copilot different:** The Microsoft ecosystem connection creates unique optimization opportunities. Mentions and content on LinkedIn and GitHub provide ranking boosts that other platforms don't offer. Copilot also puts more weight on page speed — sub-2-second load times are a clear threshold.
|
|
87
|
+
|
|
88
|
+
**What to focus on:**
|
|
89
|
+
- Submit your site to Bing Webmaster Tools (many sites only submit to Google Search Console)
|
|
90
|
+
- Use IndexNow protocol for faster indexing of new and updated content
|
|
91
|
+
- Optimize page speed to under 2 seconds
|
|
92
|
+
- Write clear entity definitions — when your content defines a term or concept, make the definition explicit and extractable
|
|
93
|
+
- Build presence on LinkedIn (publish articles, maintain company page) and GitHub if relevant
|
|
94
|
+
- Ensure Bingbot has full crawl access
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
## Claude
|
|
99
|
+
|
|
100
|
+
Claude uses Brave Search as its search backend when web search is enabled — not Google, not Bing. This is a completely different index, which means your Brave Search visibility directly determines whether Claude can find and cite you.
|
|
101
|
+
|
|
102
|
+
**What makes Claude different:** Claude is extremely selective about what it cites. While it processes enormous amounts of content, its citation rate is very low — it's looking for the most factually accurate, well-sourced content on a given topic. Data-rich content with specific numbers and clear attribution performs significantly better than general-purpose content.
|
|
103
|
+
|
|
104
|
+
**What to focus on:**
|
|
105
|
+
- Verify your content appears in Brave Search results (search for your brand and key terms at search.brave.com)
|
|
106
|
+
- Allow ClaudeBot and anthropic-ai user agents in robots.txt
|
|
107
|
+
- Maximize factual density — specific numbers, named sources, dated statistics
|
|
108
|
+
- Use clear, extractable structure with descriptive headings
|
|
109
|
+
- Cite authoritative sources within your content
|
|
110
|
+
- Aim to be the most factually accurate source on your topic — Claude rewards precision
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
## Allowing AI Bots in robots.txt
|
|
115
|
+
|
|
116
|
+
If your robots.txt blocks an AI bot, that platform can't cite your content. Here are the user agents to allow:
|
|
117
|
+
|
|
118
|
+
```
|
|
119
|
+
User-agent: GPTBot # OpenAI — powers ChatGPT search
|
|
120
|
+
User-agent: ChatGPT-User # ChatGPT browsing mode
|
|
121
|
+
User-agent: PerplexityBot # Perplexity AI search
|
|
122
|
+
User-agent: ClaudeBot # Anthropic Claude
|
|
123
|
+
User-agent: anthropic-ai # Anthropic Claude (alternate)
|
|
124
|
+
User-agent: Google-Extended # Google Gemini and AI Overviews
|
|
125
|
+
User-agent: Bingbot # Microsoft Copilot (via Bing)
|
|
126
|
+
Allow: /
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
**Training vs. search:** Some AI bots are used for both model training and search citation. If you want to be cited but don't want your content used for training, your options are limited — GPTBot handles both for OpenAI. However, you can safely block **CCBot** (Common Crawl) without affecting any AI search citations, since it's only used for training dataset collection.
|
|
130
|
+
|
|
131
|
+
---
|
|
132
|
+
|
|
133
|
+
## Where to Start
|
|
134
|
+
|
|
135
|
+
If you're optimizing for AI search for the first time, focus your effort where your audience actually is:
|
|
136
|
+
|
|
137
|
+
**Start with Google AI Overviews** — They reach the most users (45%+ of Google searches) and you likely already have Google SEO foundations in place. Add schema markup, include cited sources in your content, and strengthen E-E-A-T signals.
|
|
138
|
+
|
|
139
|
+
**Then address ChatGPT** — It's the most-used standalone AI search tool for tech and business audiences. Focus on freshness (update content monthly), domain authority, and matching your content structure to how ChatGPT formats its responses.
|
|
140
|
+
|
|
141
|
+
**Then expand to Perplexity** — Especially valuable if your audience includes researchers, early adopters, or tech professionals. Add FAQ schema, publish PDF resources, and write in clear, self-contained paragraphs.
|
|
142
|
+
|
|
143
|
+
**Copilot and Claude are lower priority** unless your audience skews enterprise/Microsoft (Copilot) or developer/analyst (Claude). But the fundamentals — structured content, cited sources, schema markup — help across all platforms.
|
|
144
|
+
|
|
145
|
+
**Actions that help everywhere:**
|
|
146
|
+
1. Allow all AI bots in robots.txt
|
|
147
|
+
2. Implement schema markup (FAQPage, Article, Organization at minimum)
|
|
148
|
+
3. Include statistics with named sources in your content
|
|
149
|
+
4. Update content regularly — monthly for competitive topics
|
|
150
|
+
5. Use clear heading structure (H1 > H2 > H3)
|
|
151
|
+
6. Keep page load time under 2 seconds
|
|
152
|
+
7. Add author bios with credentials
|