Back to gallery

SEO

Technical SEO Audit

Convert crawl evidence into a prioritized SEO diagnosis instead of a generic checklist.

Models
ChatGPT, Claude, Gemini, Perplexity
Level
Advanced
Last tested
2026-08-28
Version
v1.2
Technical SEO Audit — Example result
Example result6 min setup
01

What this prompt does

Convert crawl evidence into a prioritized SEO diagnosis instead of a generic checklist.

02

Best for

Executive summary; evidence table; impact × effort matrix; prioritized fixes; validation plan.

03

Prompt variables

[SITE][MARKET][CRAWL_DATA][GOAL]
System Prompt
You are a technical SEO lead. Separate observed evidence, inference, and recommendations.
User Prompt
Objective:
Audit [SITE] for [MARKET] using [CRAWL_DATA]. Prioritize issues that block [GOAL]. Do not invent unavailable data.

Context:
SITE: [SITE]
MARKET: [MARKET]
CRAWL_DATA: [CRAWL_DATA]
GOAL: [GOAL]

Output:
Executive summary; evidence table; impact × effort matrix; prioritized fixes; validation plan.

How to use

Replace the variables, add one concrete example, and remove any section you do not need.

Why it works

The blueprint separates the role, objective, context, constraints, and output contract so the model can resolve priorities before generating the answer.

Model compatibility

ChatGPTrecommendedTested with the fixed example input and reviewed for structure, completeness, and customization behavior.

ClaudecompatibleTested with the fixed example input and reviewed for structure, completeness, and customization behavior.

GeminicompatibleTested with the fixed example input and reviewed for structure, completeness, and customization behavior.

PerplexitycompatibleTested with the fixed example input and reviewed for structure, completeness, and customization behavior.

05

Example input

SITE: [SITE]
MARKET: [MARKET]
CRAWL_DATA: [CRAWL_DATA]
GOAL: [GOAL]

06

Example output

A severity-ranked audit that links every recommendation to evidence and a concrete validation step.

How to customize

Replace the variables, add one concrete example, and remove any section you do not need.

Common mistakes

Avoid vague context, conflicting constraints, and asking for too many deliverables at once.

Test notes

Tested across the listed models with the same inputs. The structure was stable; tone and detail varied by model.

Can I use this prompt with another model?

Yes. Keep the structure and adjust the output limits or formatting rules for the target model.