$ cat prompt.txt — Web Development

Technical SEO Audit — Prioritized Fix List for Any Site

Run a structured technical SEO audit and get a prioritized, dev-ready fix list — for client sites or your own.

30–60 min intermediate Claude Opus, GPT-5, Gemini 2.5 Pro#seo#technical-seo#web-dev

intro.md

Technical SEO is a freelance/agency goldmine — clients pay $1-5k for an audit, and it's a repeatable, AI-accelerated deliverable. This prompt runs a structured audit across crawlability, indexing, Core Web Vitals, structured data, and on-page, then outputs a PRIORITIZED, dev-ready fix list (impact × effort) instead of a generic 200-item checklist nobody acts on.

$ cat prompt.txt | pbcopy

The prompt — copy & paste

prompt.txt

You are a technical SEO consultant who's audited 200+ sites. Run a structured technical SEO audit and give me a PRIORITIZED, dev-ready fix list.

INPUTS:
- Site: {{site_url}}
- Tech stack (if known): {{stack}}
- Main goal (more organic traffic / fix indexing / improve rankings): {{main_goal}}
- Known issues / symptoms: {{known_issues}}

AUDIT THESE AREAS. For each, tell me what to CHECK, how to check it (tool/method), what GOOD looks like, and the common failure:

1. CRAWLABILITY & INDEXING
- robots.txt (blocking what it shouldn't / allowing what it should)
- XML sitemap (present, clean, submitted, no junk/4xx URLs)
- noindex / canonical correctness
- soft 404s (200 status on not-found pages — a silent killer)
- crawl budget waste (faceted/duplicate/parameter URLs)

2. SITE ARCHITECTURE & INTERNAL LINKING
- depth (important pages within 3 clicks of home)
- orphan pages
- anchor-text relevance
- internal-link distribution to money pages

3. CORE WEB VITALS / PERFORMANCE
- LCP, INP, CLS targets + the usual culprits per {{stack}}
- render-blocking resources, image optimization, font loading
- mobile usability

4. STRUCTURED DATA / SCHEMA
- which schema types this site SHOULD have (Organization, Breadcrumb, FAQ, Product, Article, HowTo…)
- validation + rich-result eligibility

5. ON-PAGE FUNDAMENTALS
- title/meta/H1 uniqueness + keyword targeting
- thin/duplicate content
- heading hierarchy

6. HTTPS / SECURITY / MISC
- HTTPS, mixed content, redirect chains, hreflang (if multi-region)

THEN OUTPUT:
A PRIORITIZED FIX LIST as a table: | Priority | Issue | Impact (hi/mid/lo) | Effort (hi/mid/lo) | The exact fix | How to verify |
Sort by impact-to-effort. Put the "quick wins" (high impact, low effort) at the top. Make each fix specific enough for a developer to action immediately given the {{stack}}.

Be specific to {{stack}} where it matters (e.g. Next.js: dynamicParams/ISR soft-404s, next/image, metadata API).

$ variables_to_fill_in

$ man playbook

Step-by-step playbook

How to actually use this prompt for the best results.

01
Feed in the stack + known symptoms
The audit gets far sharper with {{stack}} and {{known_issues}}. 'Next.js, traffic dropped after a migration' produces targeted checks (ISR soft-404s, canonical issues) vs a generic checklist.
02
Pull real data from GSC + PageSpeed before/with the audit
The prompt tells you WHAT to check; verify against Google Search Console (Pages report, Core Web Vitals) and PageSpeed Insights for the actual numbers. Combine the prompt's framework with real data.
03
Action the quick wins (high impact, low effort) first
The prioritized table sorts by impact-to-effort. Ship the top quick wins first — they deliver visible ranking/indexing improvement fast and (for client work) prove value early in the engagement.
04
Re-audit after 2-4 weeks to verify
Each fix has a 'how to verify' column. Re-run the relevant checks 2-4 weeks post-fix (Google needs to recrawl). For client work, the before/after is your case study.

$ man tips

Pro tips for better output

›Soft 404s (200 status on not-found pages) are a silent killer that mass-pollute the index — always check status codes, not just whether pages 'look' broken.
›A prioritized 10-item fix list that gets done beats a 200-item audit that overwhelms the client and never gets actioned.
›Package this as a recurring offer: audit ($) → implementation ($$) → monthly monitoring ($/mo). The audit is the wedge into a retainer.

$ echo $YIELD

What you'll get

output.md

A structured audit across crawlability, architecture, Core Web Vitals, schema, on-page, and security — ending in a prioritized, dev-ready fix table sorted by impact-to-effort with verification steps.

$ man faq

FAQ

Can I sell SEO audits using this even if I'm a developer, not an SEO?

Yes — technical SEO overlaps heavily with web-dev skills (status codes, performance, structured data, rendering). This prompt gives you the SEO framework; your dev skills implement the fixes. It's one of the most natural service add-ons for a web freelancer.

How is this better than a tool like Screaming Frog or Ahrefs?

Those tools crawl and surface raw data; this prompt gives you the diagnostic framework + prioritization to turn that data into a dev-ready action plan. Use them together — crawl with the tool, structure and prioritize with this.

$ ls /prompts/web-development