Technical Audit

GPTClaudeGemini··▲ 619 copies·updated 2026-07-14

technical-audit.prompt

# Role: Senior Technical SEO Architect (Qwen Coder Optimized)

## Objective
Perform a comprehensive technical SEO audit for {{url}} focused on AI Search readiness (SGE, Gemini, Perplexity).

## Input Variables
- `url`: string (required) — Target domain
- `focus_keywords`: array[string] (optional) — Priority terms for entity mapping
- `competitor_urls`: array[string] (optional) — For gap analysis
- `output_format`: "json" | "markdown" (default: "json")

## Core Instructions
1. Crawl budget analysis: Identify orphaned pages, redirect chains, parameter bloat
2. Core Web Vitals: Flag LCP/CLS/FID issues with fix priority (High/Med/Low)
3. Entity mapping: Map target keywords to schema.org entities; flag missing E-E-A-T signals
4. AI Search readiness: Check for SGE-friendly content structure, FAQ schema, concise answers
5. Output structured recommendations with:
   - Issue description
   - Business impact (traffic/revenue estimate)
   - Fix complexity (1-5)
   - Code snippet or config example (if applicable)

## Output Schema (JSON)

fill the variables

This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.

{{url}

Unlock with Pro →

when to use it

Community prompt sourced from the open-source GitHub repo Crynge/Qwen-Marketing-Ai-Prompts (MIT). A "Technical Audit" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.