geo-crawl-browser-rendering

Audit public web surfaces for GEO readiness using Cloudflare Browser Rendering.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill geo-crawl-browser-rendering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: geo-crawl-browser-rendering
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/geo-crawl-browser-rendering
Command: npx skills add https://github.com/clawperator/clawperator --skill geo-crawl-browser-rendering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audits GEO readiness and agent-ingestibility of Clawperator's public web surfaces using Cloudflare Browser Rendering, turning scattered observations into actionable findings.

Core Features & Use Cases

  • Browser Rendering-based crawl, markdown extraction, and link discovery audits for landing and docs surfaces.
  • Evaluates GEO posture, rendering stability, and API anomalies to surface actionable risks for engineering teams.
  • Use Case: Validate that landing pages and documentation are reliably renderable and machine-friendly before enabling agent-driven automation.

Quick Start

Run the included Python script with required environment variables to start a GEO audit against clawoperator.com and docs.clawoperator.com.

Frequently Asked Questions about geo-crawl-browser-rendering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit web pages for agent-ingestibility and GEO readiness?

You can assess agent-ingestibility and GEO readiness by running a Cloudflare Browser Rendering script that audits landing and docs surfaces for crawl coverage, markdown extraction quality, and JS dependency risk.

Can I use Cloudflare Browser Rendering to check if my documentation is machine-friendly?

Yes, Cloudflare Browser Rendering evaluates whether documentation surfaces are reliably renderable and machine-friendly by auditing link discovery, rendering stability, and markdown extraction quality.

What environment variables do I need to run a Browser Rendering crawl script?

Running the crawl script requires CLAWPERATOR_CLOUDFLARE_ACCOUNT_ID and CLAWPERATOR_CLOUDFLARE_DOCS_WRANGLER_API_TOKEN, with optional GEO_LANDING_BASE_URL and GEO_DOCS_BASE_URL overrides for targeting specific surfaces.

What is the best way to identify JS dependency risk and API anomalies on public web surfaces?

Performing a deterministic browser-rendered crawl is the best way to identify JS dependency risk and API anomalies, evaluating rendering stability and surfacing actionable risks for engineering teams.

Does this GEO audit approach work for validating landing pages before enabling agent-driven automation?

Yes, this GEO audit approach validates that landing pages are reliably renderable and machine-friendly by assessing crawl coverage and markdown extraction quality before enabling agent-driven automation.

What are the limitations when auditing markdown extraction quality from JavaScript-heavy web surfaces?

Limitations when auditing markdown extraction quality include encountering JS dependency risks and rendering instability, which the browser-rendered crawl detects to surface actionable risks for engineering teams.