Technical Seo Auditor
Audit technical SEO issues and implement fixes to improve crawlability, indexing, and site performance.
Use This When
Articles, service pages, AEO/GEO content, interlinking, SERP-informed briefs.
Inputs Needed
URL, target keyword, audience, competitors, location, search intent, internal links, products/services.
Expected Output
SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions.
The Workflow Prompt
You are a technical SEO strategist and editorial content lead. Objective: Technical Seo Auditor Context: Audit technical SEO issues and implement fixes to improve crawlability, indexing, and site performance. Original task: You are a legendary technical SEO expert who has fixed critical crawlability and indexation issues for enterprise websites with 500K+ pages. Your expertise spans server architecture, robots.txt optimization, XML sitemaps, crawl budget management, JavaScript rendering, structured data validation, site speed architecture, and Google Search Console mastery. You've successfully increased organic traffic by 300%+ through technical fixes alone and understand the intersection of development and SEO at a deep level.Conduct a comprehensive technical SEO audit for [YOUR_DOMAIN]. Provide:1. **Crawlability Assessment**: Analyze robots.txt, user-agent blocking, and crawl directives; identify pages that should be crawled but aren't2. **Indexation Analysis**: Compare Google Search Console indexed pages vs. actual discoverable pages; identify unnecessary pages indexed or important pages blocked3. **Site Architecture Review**: Assess URL structure, directory depth, parameter optimization, and hierarchy; recommend improvements4. **XML Sitemap Audit**: Evaluate sitemap quality, prioritization, lastmod accuracy, and frequency hints5. **Redirect Chain Analysis**: Identify redirect chains (>2 hops), unnecessary 301s, and consolidation opportunities6. **International & Hreflang Setup**: Review hreflang implementation, language targeting, and regional configuration7. **Core Web Vitals Analysis**: Provide specific recommendations for improving LCP, FID, and CLS metrics8. **JavaScript Rendering Issues**: Identify JavaScript-dependent content causing indexation problems9. **Mobile-First Indexing Readiness**: Audit mobile experience and identify mobile-specific technical issues10. **Security & HTTPS Verification**: Confirm SSL implementation, security headers, and crawlability over HTTPS11. **Duplicate Content Detection**: Find canonical issues, parameter duplication, and content consolidation opportunities Inputs I may provide: URL, target keyword, audience, competitors, location, search intent, internal links, products/services. Operating instructions: - First, restate the objective in one clear sentence. - If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them. - Use a Detailed response style. - Be specific to the business, audience, channel, and constraints provided. - Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use. - When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources. - Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead. - End with a short QA checklist that helps me verify the output. Required output: SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions. Caution: Avoid generic output; require concrete examples, assumptions, and next steps.
QA Follow-Up Checklist
After the AI returns its output, verify against:
- Output is specific to the provided business/context.
- Assumptions are clearly labeled.
- No unsupported claims without source checks.
- Next actions are clear and usable.
- Search intent, internal links, FAQ, and on-page elements are included.
Follow-Up Prompt
Now turn the result for 'Technical Seo Auditor' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.
Avoid / Cautions
Avoid generic output; require concrete examples, assumptions, and next steps.
How Different Verticals Use This Workflow
Restaurant & Hospitality
A multi-location restaurant group with 60 city pages and broken hreflang feeds in a crawl + GSC data. Output identifies 14 self-canonicalized location pages losing rank to each other and a JavaScript-rendered menu blocking 40% of menu indexation. Fix takes one sprint; organic traffic to location pages lifts 38% in 60 days.
Retail & E-commerce
A Shopify store with 8,000 products and 200K+ faceted URLs feeds in the crawl. Output flags massive crawl waste (Google crawling 180K parameter URLs and ignoring product variants) and recommends parameter rules + canonical fixes. Crawl budget shifts to PDPs; indexation of product pages goes from 4,200 to 7,800 within 8 weeks.
Professional Services & B2B
A SaaS company with 800 docs pages and slow LCP runs the prompt. Output flags blocking JS in the docs theme causing LCP of 5.2s on mobile and identifies 60 redirect chains in the marketing site. After fixes, docs LCP drops to 1.9s and they recover 25% of organic traffic lost in a prior algo update.
Beauty & Personal Care
A 40-location salon brand with one site and city-targeted pages runs the prompt. Output: 28 city pages are noindexed by mistake from a template setting, killing all local visibility. The fix is one line of code; within 6 weeks, the 28 cities are ranking and driving 340 incremental local bookings/month.
Local & Trade Services
An HVAC company with one site and 14 city pages runs the prompt. Output: site has a 3-deep URL structure burying city pages, an XML sitemap that hasn't updated in 8 months, and missing LocalBusiness schema. Fix takes 2 weeks; city pages move from page 3-4 to page 1 within 90 days and lead volume from organic doubles.
Frequently Asked
What's the minimum input set for a useful technical SEO audit?
Three things: a Screaming Frog or Sitebulb crawl export, GSC coverage + Core Web Vitals data, and your top 20 commercial URLs. Without the crawl, the model fabricates issues. Without GSC, it can't tell you what Google actually sees. Without the commercial URL list, every recommendation gets equal priority and your devs ignore the whole document. Don't run this prompt without first running a crawl.
How do I keep this from producing a 60-issue list that the dev team rejects?
Force prioritization with explicit constraints: 'Group findings into Critical (revenue blocking), High (will impact rank within 90 days), Medium (hygiene), and Low (skip). Cap Critical at 5 items.' The default output of any technical SEO audit is overwhelming. The fix is to make the model commit to which 5 things actually matter and call the rest cleanup. Devs will execute 5. They won't execute 60.
When does technical SEO move rankings vs when is content the real bottleneck?
Technical moves rankings when you have indexation issues blocking discovery, severe Core Web Vitals problems (LCP >4s, CLS >0.25), or major crawl waste. If your indexable pages rank where they should given your content quality and backlink profile, technical is hygiene — not growth. The 10-second diagnostic: does GSC show >80% of your important pages indexed and ranking on page 1-3? If yes, fix content. If no, fix technical first.
Should I use Sitebulb, Screaming Frog, or just the AI for the audit?
Crawl with Screaming Frog (or Sitebulb if you need the reports built-in), then feed the data to the AI for prioritization and remediation steps. The AI can't crawl your site — it can only reason about data you give it. The mistake is running this prompt cold and trusting the output. Crawl + AI synthesis + GSC = useful audit. Either tool alone is theatre.