hitkeep

Analyze HitKeep AI visibility data: AI crawler fetches, AI-referred visits, assistant names and families, citation yield, resource types, top paths, fetch failures, and Search Console correlation. Use when the user asks about GPTBot, ClaudeBot, ChatGPT, Claude, Perplexity, AI search, AI referrals, crawler access, LLM visibility, or whether AI assistants are discovering and sending traffic to a site.

Official parent skill for analyzing HitKeep data through HitKeep MCP and official docs. Use whenever the user asks an AI assistant to analyze HitKeep traffic, events, ecommerce, Web Vitals, AI visibility, Search Console, opportunities, tracking health, or "Ask AI" style questions; when setting up or validating HitKeep MCP access or help; or when deciding whether to use MCP, the dashboard, REST API, open exports, or takeout. Prefer this spine skill alongside narrower HitKeep analytics skills when they are installed.

Analyze HitKeep ecommerce and conversion data through aggregate reports. Use when the user asks about revenue, orders, average order value, products, sources, ecommerce funnels, conversion changes, city/provider/ASN aggregates, UTM performance, or whether traffic quality changed in revenue terms. Use with HitKeep MCP when available and keep analysis aggregate-only.

Verify HitKeep tracking setup and automatic event collection. Use when the user asks whether HitKeep is installed, whether tracking is live, why pageviews or events are missing, how to validate WordPress or script installs, how automatic outbound click, file download, or form submit events should appear, or how to distinguish tracker setup problems from analytics interpretation problems.

Diagnose HitKeep traffic drops, spikes, source shifts, and suspicious changes. Use when the user asks why traffic changed, whether a deploy hurt traffic, whether organic/search/referral/direct traffic moved, whether a spike is real or bot-like, or what happened to sessions, visitors, pageviews, events, or conversions in HitKeep. Use with HitKeep MCP when available and follow the parent hitkeep-analytics skill when it is also loaded.

Maintain HitKeep dashboard localization. Use whenever an AI assistant or contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, PrimeNG locale behavior, language switching, translated labels, date/number/duration formatting, or supported dashboard languages.