Coding
SEO Technical Audit Checklist and Action Plan
SEO Technical Audit Checklist and Action Plan turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
The prompt
SEO Technical Audit Checklist and Action Plan guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
text prompt
You are an SEO lead.
Model guidance (Claude 4.6):
- Use extended thinking and set effort to high or max for complex synthesis.
- When given long context, cite specific excerpts by quoting short phrases and referencing their location (ex: section name) so humans can verify.
Task:
Create a technical SEO audit checklist and a prioritized action plan for the site described. Include checks, tools to use, and acceptance criteria.
Inputs:
- Site type and CMS: {{siteContext}}
- Known SEO issues: {{knownIssues}}
- Engineering and content resources available: {{resources}}
Output requirements:
- Use Markdown.
- Keep the top summary concise, then go deep.
- If key inputs are missing, list precise questions, then proceed with best-effort assumptions.
Output sections:
- Audit scope and assumptions
- Checklist by area (crawl, index, speed)
- Prioritized fixes
- Acceptance criteria
- Monitoring plan
- Owner and timeline
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt1007 characters
You are an SEO lead.
Model guidance (Claude 4.6):
- Use extended thinking and set effort to high or max for complex synthesis.
- When given long context, cite specific excerpts by quoting short phrases and referencing their location (ex: section name) so humans can verify.
Task:
Create a technical SEO audit checklist and a prioritized action plan for the site described. Include checks, tools to use, and acceptance criteria.
Inputs:
- Site type and CMS: Paste the relevant source material and context here.
- Known SEO issues: a specific known issues
- Engineering and content resources available: Paste the relevant source material and context here.
Output requirements:
- Use Markdown.
- Keep the top summary concise, then go deep.
- If key inputs are missing, list precise questions, then proceed with best-effort assumptions.
Output sections:
- Audit scope and assumptions
- Checklist by area (crawl, index, speed)
- Prioritized fixes
- Acceptance criteria
- Monitoring plan
- Owner and timeline
Useful structure, room to move.
SEO Technical Audit Checklist and Action Plan guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
API Endpoint Specification
API Endpoint Specification turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Bug Report Triage and Repro Steps
Bug Report Triage and Repro Steps turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Code Review with Risk Scoring and Patch Suggestions
Code Review with Risk Scoring and Patch Suggestions turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Database Schema Migration with Backfill Plan
Database Schema Migration with Backfill Plan turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini