geo-technical

Audit websites for crawlability, indexability, security, and AI crawler access.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/engineai-nz/engineai-skills --skill geo-technical-engineai-nz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: geo-technical
Source: https://github.com/engineai-nz/engineai-skills/tree/main/geo/geo-technical
Command: npx skills add https://github.com/engineai-nz/engineai-skills --skill geo-technical-engineai-nz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify technical issues that prevent websites from being crawled, indexed, and cited by AI systems and search engines—especially when server-side rendering and AI crawler access are broken.

Core Features & Use Cases

  • GEO-focused technical audit: Scores crawlability, indexability, security, URL structure, mobile readiness, Core Web Vitals, server-side rendering, and server performance in a single workflow.
  • AI crawler access checks: Evaluates robots.txt rules for major AI bots (e.g., GPTBot, PerplexityBot, ClaudeBot) to reduce AI visibility failures.
  • Server-rendering validation: Detects whether key content, meta tags, and structured data exist in raw HTML instead of being JavaScript-only.
  • Actionable GEO deliverable: Produces a consolidated GEO-TECHNICAL-AUDIT.md report with category scores and prioritized issues.

Quick Start

Run the GEO Technical SEO Audit on your target by providing the homepage URL plus 2-3 key inner pages, then generate GEO-TECHNICAL-AUDIT.md with the scored findings.

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 like GPTBot and ClaudeBot can access my site?

To check AI crawler access, audit your robots.txt rules for major bots like GPTBot, PerplexityBot, and ClaudeBot. This evaluates whether critical pages are approved for fetching, reducing AI visibility failures and ensuring AI systems can crawl your content.

Why does my server-side rendering fail technical SEO audits for AI crawlability?

Server-side rendering fails technical SEO audits when key content, meta tags, and structured data are JavaScript-only instead of existing in raw HTML. Validating SSR via curl-based HTML inspection detects if critical pages can be fetched in raw HTML for AI crawlers.

How do I perform a technical SEO audit for server-side rendering and Core Web Vitals?

Perform a technical SEO audit by fetching HTML and headers for multiple pages to score Core Web Vitals, server performance, and server-side rendering. This evaluates crawlability, indexability, and mobile readiness to produce a structured GEO-TECHNICAL-AUDIT.md report.

What is the best way to audit robots.txt and sitemaps for GEO technical SEO?

The best way to audit robots.txt and sitemaps for GEO technical SEO is evaluating them alongside canonicalization and duplication controls. This verifies critical pages can be fetched in raw HTML and are approved by robots.txt for major AI bots.

Can I validate security headers and HTTPS configuration during a technical SEO audit?

Yes, you can validate security headers and HTTPS configuration during a technical SEO audit. The workflow verifies security headers, checks HTTPS implementation, scores mobile and performance signals, and identifies AI crawler access gaps in a single process.

Do I need to provide specific URLs to audit crawlability and indexability for AI systems?

Yes, you need to provide the homepage URL plus 2-3 key inner pages to audit crawlability and indexability for AI systems. This allows fetching HTML and headers for multiple pages, evaluating whether critical content can be accessed by AI crawlers.