geo-technical

Audits websites for technical SEO and AI crawler accessibility across eight scored categories.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/finedesignz/geo-seo-claude --skill geo-technical-finedesignz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: geo-technical
Source: https://github.com/finedesignz/geo-seo-claude/tree/main/skills/geo-technical
Command: npx skills add https://github.com/finedesignz/geo-seo-claude --skill geo-technical-finedesignz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Websites that are technically broken cannot be crawled, indexed, or cited by search engines or AI platforms like ChatGPT, Perplexity, and Claude. This Skill diagnoses technical issues — especially client-side rendering that hides content from AI crawlers and robots.txt rules that block them — and produces a scored, prioritized audit report. ## Core Features & Use Cases - Eight-Category Scored Audit: Evaluates crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals, server-side rendering, and page speed on a 100-point rubric. - AI Crawler Access Check: Verifies robots.txt rules for GPTBot, ClaudeBot, PerplexityBot, Googlebot, and other AI crawlers, flagging blocks that hurt AI search visibility. - SSR Detection: Compares raw curl-fetched HTML against rendered content to detect client-side rendering that AI crawlers cannot parse. - Use Case: Run the audit against a marketing site before a GEO campaign to discover that GPTBot is blocked in robots.txt and that product pages render only via JavaScript, then fix both before expecting AI citations. ## Quick Start Ask the assistant to run a GEO technical audit on your website URL and generate the GEO-TECHNICAL-AUDIT.md report.

Frequently Asked Questions about geo-technical

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

FAQPage Schema
How do I check if AI crawlers can access my website?▼

Fetch your robots.txt file and look for Disallow rules targeting GPTBot, ClaudeBot, PerplexityBot, Googlebot, and Bingbot. This audit checks all major AI crawler user-agents and scores access, flagging blocks that reduce AI search visibility.

How to detect if a website relies on client-side rendering?▼

Fetch the page with curl, which does not execute JavaScript, and compare the raw HTML to the rendered DOM. If headings, body text, or links are missing from the raw HTML, the site depends on client-side rendering that AI crawlers cannot parse.

Does blocking Google-Extended affect Google search rankings?▼

No. Blocking Google-Extended only controls AI training data usage, not search indexing, since Googlebot handles indexing separately. However, blocking it may reduce presence in Google AI Overviews.

What Core Web Vitals thresholds does the audit use?▼

The audit uses 2026 thresholds measured at the 75th percentile of field data: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. INP replaced FID as the interactivity metric in March 2024.

Why is server-side rendering critical for AI search visibility?▼

AI crawlers like GPTBot, PerplexityBot, and ClaudeBot do not execute JavaScript and only parse raw HTML. Content rendered client-side by React, Vue, or Angular appears as an empty page to these crawlers, preventing citation.

What are the limitations of this technical audit?▼

The audit estimates Core Web Vitals from page characteristics when real user CrUX data is unavailable, which is less precise than field data. Agent-readiness checks like Markdown content negotiation are non-scoring and informational only.