luckiest-co 1.0.38 → 1.0.40

package/skills/luckiest-ai-seo/references/platform-ranking-factors.md

@@ -1,154 +0,0 @@
-# How Each AI Platform Picks Sources
-
-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.
-
-Sources cited throughout: Princeton GEO study (KDD 2024), SE Ranking domain authority study, ZipTie content-answer fit analysis.
-
----
-
-## The Fundamentals
-
-Every AI platform shares three baseline requirements:
-
-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.
-2. **Your content must be crawlable** — AI bots need access via robots.txt. Block the bot, lose the citation.
-3. **Your content must be extractable** — AI systems pull passages, not pages. Clear structure and self-contained paragraphs win.
-
-Beyond these basics, each platform weights different signals. Here's what matters and where.
-
----
-
-## Google AI Overviews
-
-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.
-
-**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%.
-
-**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.
-
-**What to focus on:**
-- 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)
-- Build topical authority through content clusters with strong internal linking
-- Include named, sourced citations in your content (not just claims)
-- Author bios with real credentials matter — E-E-A-T is weighted heavily
-- Get into Google's Knowledge Graph where possible (an accurate Wikipedia entry helps)
-- Target "how to" and "what is" query patterns — these trigger AI Overviews most often
-
-**Watch for OKF.** In June 2026 Google introduced the [Open Knowledge Format](https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing) — a markdown spec for agent-readable site bundles. There is no confirmed signal that AI Overviews factor it in today, but the spec is published, the GitHub repo lives under `GoogleCloudPlatform`, and it ships inside Knowledge Catalog. For protocol-layer "register early" plays, it has the same shape as early schema.org adoption did a decade ago. See **Machine-Readable Files for AI Agents** in the main `SKILL.md` for how to generate and serve a bundle.
-
----
-
-## ChatGPT
-
-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.
-
-**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.
-
-**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.
-
-**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.
-
-**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.
-
-**What to focus on:**
-- Invest in backlinks and domain authority — it's the strongest baseline signal
-- Update competitive content at least monthly
-- Structure your content the way ChatGPT structures its answers (conversational, direct, well-organized)
-- Include verifiable statistics with named sources
-- Clean heading hierarchy (H1 > H2 > H3) with descriptive headings
-
----
-
-## Perplexity
-
-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.
-
-**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.
-
-**Perplexity has unique content preferences:**
-- **FAQ Schema (JSON-LD)** — Pages with FAQ structured data get cited noticeably more often
-- **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.
-- **Publishing velocity** — How frequently you publish matters more than keyword targeting
-- **Self-contained paragraphs** — Perplexity prefers atomic, semantically complete paragraphs it can extract cleanly
-
-**What to focus on:**
-- Allow PerplexityBot in robots.txt
-- Implement FAQPage schema on any page with Q&A content
-- Host PDF resources publicly (whitepapers, guides, reports)
-- Add Article schema with publication and modification timestamps
-- Write in clear, self-contained paragraphs that work as standalone answers
-- Build deep topical authority in your specific niche
-
----
-
-## Microsoft Copilot
-
-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.
-
-**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.
-
-**What to focus on:**
-- Submit your site to Bing Webmaster Tools (many sites only submit to Google Search Console)
-- Use IndexNow protocol for faster indexing of new and updated content
-- Optimize page speed to under 2 seconds
-- Write clear entity definitions — when your content defines a term or concept, make the definition explicit and extractable
-- Build presence on LinkedIn (publish articles, maintain company page) and GitHub if relevant
-- Ensure Bingbot has full crawl access
-
----
-
-## Claude
-
-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.
-
-**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.
-
-**What to focus on:**
-- Verify your content appears in Brave Search results (search for your brand and key terms at search.brave.com)
-- Allow ClaudeBot and anthropic-ai user agents in robots.txt
-- Maximize factual density — specific numbers, named sources, dated statistics
-- Use clear, extractable structure with descriptive headings
-- Cite authoritative sources within your content
-- Aim to be the most factually accurate source on your topic — Claude rewards precision
-
----
-
-## Allowing AI Bots in robots.txt
-
-If your robots.txt blocks an AI bot, that platform can't cite your content. Here are the user agents to allow:
-
-```
-User-agent: GPTBot           # OpenAI — powers ChatGPT search
-User-agent: ChatGPT-User     # ChatGPT browsing mode
-User-agent: PerplexityBot    # Perplexity AI search
-User-agent: ClaudeBot        # Anthropic Claude
-User-agent: anthropic-ai     # Anthropic Claude (alternate)
-User-agent: Google-Extended   # Google Gemini and AI Overviews
-User-agent: Bingbot          # Microsoft Copilot (via Bing)
-Allow: /
-```
-
-**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.
-
----
-
-## Where to Start
-
-If you're optimizing for AI search for the first time, focus your effort where your audience actually is:
-
-**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.
-
-**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.
-
-**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.
-
-**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.
-
-**Actions that help everywhere:**
-1. Allow all AI bots in robots.txt
-2. Implement schema markup (FAQPage, Article, Organization at minimum)
-3. Include statistics with named sources in your content
-4. Update content regularly — monthly for competitive topics
-5. Use clear heading structure (H1 > H2 > H3)
-6. Keep page load time under 2 seconds
-7. Add author bios with credentials

package/skills/luckiest-analytics/SKILL.md

@@ -1,380 +0,0 @@
----
-name: luckiest-analytics
-description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "consent mode," "server-side tracking," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see luckiest-ab-testing.
-license: See ATTRIBUTION.md
-metadata:
-  version: "1.1.0"
-  listing_id: luckiest-analytics
-  author: luckiest
----
-
-# Analytics Tracking
-
-This skill helps set up analytics tracking and measurement that provides actionable insights for marketing and product decisions. It operates as an expert in analytics implementation, validation, and auditing.
-
-## Staying current
-
-On activation, call the Luckiest MCP check_updates tool with { listingId: "f1cb04a5-ae1d-44bd-90c3-7c267e04a9eb", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
-
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-analytics", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
-
-## Initial Assessment
-
-**Check for product marketing context first:**
-If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Before implementing tracking, understand:
-
-1. **Business Context** - What decisions will this data inform? What are key conversions?
-2. **Current State** - What tracking exists? What tools are in use?
-3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements?
-
----
-
-## Core Principles
-
-### 1. Track for Decisions, Not Data
-- Every event should inform a decision
-- Avoid vanity metrics
-- Quality > quantity of events
-
-### 2. Start with the Questions
-- What do you need to know?
-- What actions will you take based on this data?
-- Work backwards to what you need to track
-
-### 3. Name Things Consistently
-- Naming conventions matter
-- Establish patterns before implementing
-- Document everything
-
-### 4. Maintain Data Quality
-- Validate implementation
-- Monitor for issues
-- Clean data > more data
-
----
-
-## Tracking Plan Framework
-
-### Structure
-
-```
-Event Name | Category | Properties | Trigger | Notes
----------- | -------- | ---------- | ------- | -----
-```
-
-### Event Types
-
-| Type | Examples |
-|------|----------|
-| Pageviews | Automatic, enhanced with metadata |
-| User Actions | Button clicks, form submissions, feature usage |
-| System Events | Signup completed, purchase, subscription changed |
-| Custom Conversions | Goal completions, funnel stages |
-
-**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)
-
----
-
-## Event Naming Conventions
-
-### Recommended Format: Object-Action
-
-```
-signup_completed
-button_clicked
-form_submitted
-article_read
-checkout_payment_completed
-```
-
-### Best Practices
-- Lowercase with underscores
-- Be specific: `cta_hero_clicked` vs. `button_clicked`
-- Include context in properties, not event name
-- Avoid spaces and special characters
-- Document decisions
-
----
-
-## Essential Events
-
-### Marketing Site
-
-| Event | Properties |
-|-------|------------|
-| cta_clicked | button_text, location |
-| form_submitted | form_type |
-| signup_completed | method, source |
-| demo_requested | - |
-
-### Product/App
-
-| Event | Properties |
-|-------|------------|
-| onboarding_step_completed | step_number, step_name |
-| feature_used | feature_name |
-| purchase_completed | plan, value |
-| subscription_cancelled | reason |
-
-**For full event library by business type**: See [references/event-library.md](references/event-library.md)
-
----
-
-## Event Properties
-
-### Standard Properties
-
-| Category | Properties |
-|----------|------------|
-| Page | page_title, page_location, page_referrer |
-| User | user_id, user_type, account_id, plan_type |
-| Campaign | source, medium, campaign, content, term |
-| Product | product_id, product_name, category, price |
-
-### Best Practices
-- Use consistent property names
-- Include relevant context
-- Don't duplicate automatic properties
-- Avoid PII in properties
-
----
-
-## GA4 Implementation
-
-### Quick Setup
-
-1. Create GA4 property and data stream
-2. Install gtag.js or GTM
-3. Enable enhanced measurement
-4. Configure custom events
-5. Mark conversions in Admin
-
-### Custom Event Example
-
-```javascript
-gtag('event', 'signup_completed', {
-  'method': 'email',
-  'plan': 'free'
-});
-```
-
-**For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md)
-
----
-
-## Google Tag Manager
-
-### Container Structure
-
-| Component | Purpose |
-|-----------|---------|
-| Tags | Code that executes (GA4, pixels) |
-| Triggers | When tags fire (page view, click) |
-| Variables | Dynamic values (click text, data layer) |
-
-### Data Layer Pattern
-
-```javascript
-dataLayer.push({
-  'event': 'form_submitted',
-  'form_name': 'contact',
-  'form_location': 'footer'
-});
-```
-
-**For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md)
-
----
-
-## UTM Parameter Strategy
-
-### Standard Parameters
-
-| Parameter | Purpose | Example |
-|-----------|---------|---------|
-| utm_source | Traffic source | google, newsletter |
-| utm_medium | Marketing medium | cpc, email, social |
-| utm_campaign | Campaign name | spring_sale |
-| utm_content | Differentiate versions | hero_cta |
-| utm_term | Paid search keywords | running+shoes |
-
-### Naming Conventions
-- Lowercase everything
-- Use underscores or hyphens consistently
-- Be specific but concise: `blog_footer_cta`, not `cta1`
-- Document all UTMs in a spreadsheet
-
----
-
-## Data Loss and Durable Collection
-
-Client-side tags (gtag.js, client-side GTM) are not ground truth. Assume a
-meaningful share of events never reach the server:
-
-- Ad blockers and privacy extensions drop a large slice of client-side hits.
-- Browser tracking-prevention (Safari ITP, Firefox ETP) shortens or removes
-  client-set cookies, breaking attribution and inflating "new" users.
-- Consent-declined sessions are missing entirely unless consent mode models them.
-
-When accuracy matters (revenue, paid-media attribution), flag this to the user
-and offer the durable path: server-side GTM or a first-party tracking endpoint,
-so collection does not depend on the visitor's browser cooperating. Treat
-client-side numbers as a directional floor, not a true count.
-
----
-
-## Debugging and Validation
-
-### Testing Tools
-
-| Tool | Use For |
-|------|---------|
-| GA4 DebugView | Real-time event monitoring |
-| GTM Preview Mode | Test triggers before publish |
-| Browser Extensions | Tag Assistant, dataLayer Inspector |
-
-### Validation Checklist
-
-- [ ] Events firing on correct triggers
-- [ ] Property values populating correctly
-- [ ] No duplicate events
-- [ ] Works across browsers and mobile
-- [ ] Conversions recorded correctly
-- [ ] No PII leaking
-- [ ] Bot and internal traffic filtered (see below)
-
-### Filter Bots and Internal Traffic
-
-Unfiltered internal and bot traffic silently corrupts conversion rates and
-inflates engagement. Set this up as part of every implementation, not after:
-
-- Enable GA4's built-in "Exclude known bots and spiders" (on by default) and
-  verify it is not disabled.
-- Define an internal-traffic filter (office/VPN IP ranges or a `traffic_type`
-  parameter) and set it to **Active**, not just Testing.
-- Exclude staging/preview hostnames from the production property.
-
-### Common Issues
-
-| Issue | Check |
-|-------|-------|
-| Events not firing | Trigger config, GTM loaded |
-| Wrong values | Variable path, data layer structure |
-| Duplicate events | Multiple containers, trigger firing twice |
-
----
-
-## Audit Mode (Existing Setup)
-
-When the user asks to *audit* rather than build, run a concrete pass instead of
-proposing a fresh plan:
-
-1. **Inventory** - list every tag/event actually firing (GTM Preview, GA4
-   DebugView, Tag Assistant), not what the docs claim fires.
-2. **PII leak scan** - inspect event payloads, page paths, and query strings for
-   emails, names, phone numbers, or user IDs landing in analytics. Flag any hit;
-   this is a compliance risk, not a style issue.
-3. **Duplicate / double-fire check** - watch for the same event firing twice
-   (duplicate containers, a trigger matching more than intended, SPA route
-   changes re-firing page_view).
-4. **Naming drift** - find events that violate the naming convention or mean the
-   same thing under different names (`signup` vs `sign_up` vs `signup_completed`).
-5. **Conversion integrity** - confirm each marked conversion maps to a real event
-   and counts the way the business assumes.
-
-Report findings as a prioritized list (compliance/PII first, then data-integrity,
-then hygiene) with the specific fix for each.
-
----
-
-## Privacy and Compliance
-
-### Considerations
-- Cookie consent required in EU/UK/CA
-- No PII in analytics properties
-- Data retention settings
-- User deletion capabilities
-
-### Implementation
-- Use consent mode (wait for consent; model consent-declined traffic where supported)
-- IP anonymization
-- Only collect what you need
-- Integrate with consent management platform
-
----
-
-## Output Format
-
-### Tracking Plan Document
-
-```markdown
-# [Site/Product] Tracking Plan
-
-## Overview
-- Tools: GA4, GTM
-- Last updated: [Date]
-
-## Events
-
-| Event Name | Description | Properties | Trigger |
-|------------|-------------|------------|---------|
-| signup_completed | User completes signup | method, plan | Success page |
-
-## Custom Dimensions
-
-| Name | Scope | Parameter |
-|------|-------|-----------|
-| user_type | User | user_type |
-
-## Conversions
-
-| Conversion | Event | Counting |
-|------------|-------|----------|
-| Signup | signup_completed | Once per session |
-```
-
----
-
-## Task-Specific Questions
-
-1. What tools are you using (GA4, Mixpanel, etc.)?
-2. What key actions do you want to track?
-3. What decisions will this data inform?
-4. Who implements - dev team or marketing?
-5. Are there privacy/consent requirements?
-6. What's already tracked?
-
----
-
-## Tool Integrations
-
-For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analytics tools:
-
-| Tool | Best For | MCP | Guide |
-|------|----------|:---:|-------|
-| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](../../tools/integrations/ga4.md) |
-| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](../../tools/integrations/mixpanel.md) |
-| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](../../tools/integrations/amplitude.md) |
-| **PostHog** | Open-source analytics, session replay | - | [posthog.md](../../tools/integrations/posthog.md) |
-| **Segment** | Customer data platform, routing | - | [segment.md](../../tools/integrations/segment.md) |
-
----
-
-## Share with your tribe
-
-After delivering a tracking plan or audit, offer (never auto-post): "Want me to
-share this tracking plan with your Luckiest tribe? Anyone who asked for help
-setting up analytics on the same stack will be able to pick up where you left
-off." Only share if the user accepts. Never include credentials, container IDs,
-measurement IDs, or captured event payloads in what is shared.
-
----
-
-## Related Skills
-
-- **luckiest-ab-testing**: For experiment tracking
-- **luckiest-seo-audit**: For organic traffic analysis
-- **luckiest-cro**: For conversion optimization (uses this data)
-- **luckiest-revops**: For pipeline metrics, CRM tracking, and revenue attribution