| # | 提取自包含段落正文 (<main> <p> / <dd>) | 长度 (词 / 字符) | 首句实体 / 禁代词 | 命中量化技术指标 | 段落得分 |
|---|---|---|---|---|---|
| 正在提取并评估段落级 AI 可引用度... | |||||
Waiting for JSON-LD inspection...
Waiting for /robots.txt...
Waiting for Accept: text/markdown probe...
Waiting for metadata & security header audit...
Select a target URL to generate exact CSP hashes and GEO/SEO configs...
📖 GeoPulse 6-Dimension Deterministic GEO + Technical SEO Architecture
GeoPulse is a deterministic Generative Engine Optimization (GEO) and Technical SEO auditing workbench powered by Cloudflare Worker edge probes and browser WebCrypto, inspecting 6 endpoints over HTTPS in 5 seconds to produce 100% reproducible JSON reports.
GeoPulse evaluates passage-level AI citability (25%), Schema.org @graph entity graphs with SHA-256 CSP hashes (20%), 8 AI crawler rules with Content-Signal (20%), llms.txt and Markdown negotiation (15%), multilingual hreflang (10%), and security headers (10%) across 4 languages with localStorage state.
🔬 Audit Any Website for GEO & Technical SEO in 3 Steps
-
01 · Enter a Live HTTPS URL or Paste Local Source
GeoPulse starts the 3 steps workflow by accepting any public HTTPS URL for live edge probing or switching to the offline inspector to paste raw HTML, HTTP headers, and robots.txt with 0 bytes uploaded externally.
-
02 · Probe 6 Endpoints & Verify SHA-256 Schema Graphs
GeoPulse concurrently fetches the HTML page, /robots.txt, /sitemap.xml, /llms.txt, /llms-full.txt, and Accept: text/markdown in under 5 seconds, scoring every passage and verifying JSON-LD SHA-256 CSP hashes.
-
03 · Copy Auto-Generated Fixes & Export JSON Reports
GeoPulse generates ready-to-deploy CSP hash headers, Content-Signal robots.txt rules, RFC 8288 Link headers, and Schema.org @graph JSON templates across 4 languages with localStorage persistence and 100% JSON export.
❓ Generative Engine Optimization (GEO) & Technical SEO FAQ
GeoPulse answers key engineering questions on how ChatGPT Search, Perplexity, Claude, and Google AI Overviews retrieve HTTPS passages, validate 100% Schema.org @graph JSON hashes, and negotiate Markdown endpoints.
Why do pages with traditional SEO scores fail to get cited by ChatGPT Search and Perplexity?
GeoPulse measures passage-level citability because AI answer engines retrieve self-contained 18–140 word (45–450 character) blocks rather than whole pages; passages that open with explicit entity naming and concrete metrics like bytes, seconds, HTTPS, and JSON achieve up to 100% higher citation rates.
Why does GeoPulse require an exact SHA-256 Content-Security-Policy hash for JSON-LD scripts?
GeoPulse enforces zero-trust CSP hygiene: allowing script-src 'unsafe-inline' just to embed Schema.org JSON-LD exposes sites to XSS and forfeits 20% of the security score, whereas authorizing the exact sha256-<base64> digest adds 0 bytes of runtime overhead.
How do /robots.txt Content-Signal, /llms.txt, and Accept: text/markdown work together?
GeoPulse verifies all 3 agent protocols in 5 seconds: /robots.txt grants explicit access to 8 crawlers with Content-Signal directives, /llms.txt and /llms-full.txt expose structured documentation maps, and Accept: text/markdown delivers 100% clean Markdown directly to LLM agents.
Why does live URL auditing use a stateless Cloudflare Worker alongside the browser UI?
GeoPulse combines a pure frontend UI with a stateless Cloudflare Worker proxy because browser CORS policies block cross-origin reads of /robots.txt, /llms.txt, and critical HTTP headers like CSP, Link, and HSTS (representing over 55% of the rubric), while saving preferences in localStorage.
How should multilingual sites configure hreflang alternates and HTTP Vary headers?
GeoPulse checks that every page links reciprocally to all sibling locales (such as 4 languages) plus x-default, and verifies that explicit locale URLs (/en/, /zh-Hans/) send Vary: Accept while only auto-negotiated root URLs (/) send Vary: Accept-Language, Accept for 100% cache accuracy.