shield_lock
JinDaGe
← Back to skills
extension
Category: Data & AnalyticsAPI key required

品牌AI搜索曝光与竞品差距｜简诗 AI

通过外部分析服务检查网站在ChatGPT和Google AI中的品牌可见性、市场机会与竞品格局，生成客户级分析报告。

personAuthor: user_fccf428bhubcommunity
downloadDownload package

GEO Analysis

使用范围与安全规则

本 Skill 只用于“品牌AI搜索曝光与竞品差距”场景，围绕用户当前提供或明确授权处理的材料完成任务。功能目标：通过外部分析服务检查网站在ChatGPT和Google AI中的品牌可见性、市场机会与竞品格局，生成客户级分析报告。

  • 默认先在回复中交付分析、方案、草稿、代码建议或检查清单，不主动读取任务范围外的文件、账号和数据。
  • 信息不足时先标记缺口并向用户确认，不用猜测内容填补事实、数字、姓名、结论或权限。
  • 需要联网检索或调用接口时，先说明访问目标、拟发送的数据和用途并取得用户明确同意；只访问用户指定或公开合法来源，不绕过登录、付费墙、验证码、访问控制或平台限制。
  • 涉及发送、发布、上传、删除、支付、投放、部署、同步或其他外部写入时，先展示目标、内容和影响，获得用户对该次动作的明确确认后再执行。
  • 不要求用户在对话里粘贴密码、Cookie、Token、API Key 或私钥；凭据仅用于用户指定的对应官方服务，不回显、不记录、不写入交付物，也不转发到无关地址。
  • 命令和脚本默认作为可审查的参考方案；只有用户明确要求执行、目标路径与影响范围清楚且完成预检后，才运行必要的最小步骤。
  • 营销与增长输出只做合规方案、内容草稿和测试建议，不承诺流量、排名、成交或收益；不刷量、不群发骚扰、不伪造背书，不设计规避平台规则的做法。
  • 涉及客户、员工、联系人或其他个人信息时，只使用完成任务所需的最少字段；默认脱敏，不抓取、拼接、买卖或外传未经授权的个人数据。
  • 交付前复核事实依据、隐私、版权、平台规则和可执行边界；发现高风险或越权请求时停止相关动作，并给出合规替代方案。

Run a full GEO/SEO analysis for a domain and get a client-ready PDF report: AI visibility (is the brand recommended by ChatGPT / Google AI), deep market research, and competitor landscape.

Thin wrapper over the Enception client-analysis API. Three operations: start, status, report (plus an optional brand-name correction).

Disclosure: contributed by Enception AI and calls Enception's paid external API. Docs: https://www.enception.ai/doc/api-client-analysis

Requirements

  • ENCEPTION_ANALYSIS_API_KEY — sent as the x-api-key header. Self-serve: sign up at https://www.enception.ai, then generate a free-tier key under Account → API Key (2 analyses/month free; contact the team for higher limits). Rate limit: 10 requests/minute.

1. Start

POST https://www.enception.ai/api/external/client-analysis/start

Required: website_url, primary_region, core_goals. Sensible defaults: primary_region=us, core_goals=traffic, output_language=en, competitors=[]. The API normalizes URLs to a bare domain and rejects IPs. Returns { id, message } — save the id.

Pick output_language from an explicit request first, then the user's conversation language, then the domain TLD (.cn → zh; otherwise en).

curl -s -X POST "https://www.enception.ai/api/external/client-analysis/start" \
  -H "x-api-key: $ENCEPTION_ANALYSIS_API_KEY" -H "Content-Type: application/json" \
  -d '{"website_url":"https://example.com/","primary_region":"us","competitors":[],"core_goals":"traffic","output_language":"en"}'

Only override primary_region / core_goals / competitors if the user specifies. core_goals is free text (e.g. traffic, ranking). Competitors: [{"name":"X","domain":"x.com"}, ...] (max 5). For multiple domains, fire one POST each and collect the ids.

2. Status

POST https://www.enception.ai/api/external/client-analysis/status with body { "id": "<id>" } and the same x-api-key header. Returns { status: 'pending' | 'failed' | 'succeeded', progress_percent?, pdf_url? }.

A full run takes ~20–45 minutes — the bottleneck is the deep market-research step. Poll on a long interval (minutes, not seconds). succeeded ⇒ ready to fetch the report. If a run fails or stalls indefinitely, report that to the user rather than inventing results.

3. Report

GET https://www.enception.ai/api/external/client-analysis/report/<id> — public, no auth; shareable by id. Works once status is succeeded (also serves partial runs).

curl -s -o geo-analysis-example.pdf \
  "https://www.enception.ai/api/external/client-analysis/report/<id>"

Confirm it's a real PDF (file geo-analysis-example.pdf), then give the user the file and/or the public URL.

4. Fix "zero visibility" (brand-name correction)

POST https://www.enception.ai/api/external/client-analysis/update-brand with body { "id", "brand_name"?, "alternative_names": [...] } and the x-api-key header.

When a report shows zero/low AI visibility but the brand IS recommended by ChatGPT/Google, it's almost always because the brand is only known by its fused domain label (e.g. pudurobotics) while AI engines say "Pudu Robotics". Supply the real name + aliases and the route recomputes visibility from the already-stored answers (no re-query — fast), then re-fetch the report.

curl -s -X POST "https://www.enception.ai/api/external/client-analysis/update-brand" \
  -H "x-api-key: $ENCEPTION_ANALYSIS_API_KEY" -H "Content-Type: application/json" \
  -d '{"id":"<id>","brand_name":"Pudu Robotics","alternative_names":["Pudu","PuduBot"]}'

Returns { success, mention_rate, overall_score, average_position, analysis_regenerated }. New analyses resolve the brand name automatically; this is the manual correction path for existing reports.