yaojingang/GEOInflow

选用指南

AI 根据 README 整理 · 2026/10/26 13:56:29

适用场景

适用于公司网站、内容网站、媒体发布者、开发者文档以及管理多个网站的 GEO 团队，用于分析 AI 爬虫访问、内容覆盖和 AI 搜索带来的转化。

查看 README 依据

| Is there enough evidence for a conclusion? | Identity evidence, source coverage, gaps, missing inputs, and estimates | Review results over the same data scope and keep evidence gaps explicit | GEOInflow is designed for company websites, content sites, media publishers, developer documentation, and GEO teams managing multiple sites. Operators can work at the website and page level, while maintainers can inspect ingestion, queues, source quality, and calculation methods. ## AI crawler analytics ### Crawler identity and purpose

使用方式

通过 Docker 部署，运行脚本后可通过默认地址 http://127.0.0.1:3002 访问。首次登录使用默认用户名 admin 和密码 liekan。

查看 README 依据

Start Docker Engine / Docker Desktop and Docker Compose V2, and ensure that image and dependency download sources are reachable. After obtaining the source code, run this command from the project root: ```sh sh scripts/liekan-deploy.sh ``` The script generates a private `.env` and random secrets, builds the application image, runs migrations, and starts the application, log worker, analytics worker, PostgreSQL, and Redis. The default address is: ```text http://127.0.0.1:3002 ```

For a fresh installation, the initial username is `admin` and the initial password is `liekan`. Change the password after signing in, then create a website using the ingestion guide. Upgrades preserve existing customized passwords and accounts. To try the bundled example after the application starts, run: ```sh docker compose -f docker-compose.liekan.yml exec app node scripts/liekan-seed-demo.mjs ```

部署要求

需要 Docker Engine / Docker Desktop 和 Docker Compose V2。生产环境需要域名、HTTPS 和可信的反向代理。自动服务器日志收集需要公共 HTTPS、摄取密钥和签名安装资产。

查看 README 依据

Start Docker Engine / Docker Desktop and Docker Compose V2, and ensure that image and dependency download sources are reachable. After obtaining the source code, run this command from the project root: ```sh sh scripts/liekan-deploy.sh ``` The script generates a private `.env` and random secrets, builds the application image, runs migrations, and starts the application, log worker, analytics worker, PostgreSQL, and Redis. The default address is: ```text http://127.0.0.1:3002 ```

The example is named “猎看官网（示例数据）”. It initializes from the processed dataset included with the source. On first import, its timestamps are shifted to make the data convenient to explore. Repeated runs preserve existing data and deletion state. See the [default demo guide](docs/default-demo.md). Production access requires a domain, HTTPS, and a trusted reverse proxy. Browser PV collection can continue without a trusted IP ingress, while identity metrics such as UV require reliable ingress evidence. Automatic log ingestion and optional AI analysis have separate configuration requirements.

- GEO extensions, supplemental journeys, complete exports, and analytics acceleration primarily target PostgreSQL. Retained ClickHouse, link, and pixel endpoints follow their existing protocols; support for each GEO extension must be checked separately. - Automatic server collection requires public HTTPS, an ingestion secret, and signed installation assets. Cloudflare integration also requires OAuth, permissions, and the relevant provider capabilities.

已知限制

搜索展示、实际排名、模型答案引用、训练包含和文章完成率需要额外数据。GEO 扩展、补充旅程、完整导出和分析加速主要针对 PostgreSQL。

查看 README 依据

- Search impressions, actual rankings, model-answer citations, training inclusion, and article completion rates require additional data. The detailed guides define the observations and scores this project provides. ## Development and maintenance Development uses Node.js **22.23.3**, pnpm **12.3.4**, and PostgreSQL. Prepare an independent database and private configuration using the [deployment guide](docs/deployment.en.md), then run the following commands. This example uses the separate development port `3302`: ```sh pnpm install --frozen-lockfile pnpm build:db pnpm db:migrate

- GEO extensions, supplemental journeys, complete exports, and analytics acceleration primarily target PostgreSQL. Retained ClickHouse, link, and pixel endpoints follow their existing protocols; support for each GEO extension must be checked separately. - Automatic server collection requires public HTTPS, an ingestion secret, and signed installation assets. Cloudflare integration also requires OAuth, permissions, and the relevant provider capabilities.