Seo Technical Audit

What it does

This skill provides a framework for conducting comprehensive technical SEO audits, aligning with best practices expected in 2025. It enables AI agents to systematically analyze website crawlability, indexation, Core Web Vitals, site architecture, mobile-friendliness, security, structured data implementation, and AI crawler configurations. The process is designed to identify and diagnose issues impacting search engine visibility and performance.

When to use it

• Performing full technical SEO audits for websites.
• Diagnosing crawling or indexation problems that are hindering site appearance in search results.
• Analyzing Core Web Vitals (LCP, INP, CLS) to ensure a good user experience.
• Reviewing website architecture and URL structure for optimal navigation and SEO.
• Validating the implementation of schema markup for enhanced rich result visibility.

Key capabilities

• Crawlability & Indexation Analysis: Robots.txt analysis, XML sitemap validation, indexation status checks (using Google Search Console).
• Core Web Vitals Assessment: Evaluation of LCP, INP, and CLS metrics using data from Google Search Console, CrUX Dashboard, and PageSpeed Insights.
• Site Architecture Review: Analysis of URL structure, internal linking strategy, and navigation depth.
• Mobile-First Readiness Check: Verification of mobile usability and responsiveness.
• Schema Markup Validation: Testing and validation of structured data using Google's Rich Results Test and Schema.org validator.
• AI Crawler Configuration Audit: Reviewing robots.txt to ensure proper access for AI search crawlers (e.g., OAI-SearchBot, ChatGPT-User).

Example prompts

• "Perform a technical SEO audit of [website URL]."
• "Analyze the Core Web Vitals performance for [website URL] and suggest improvements."
• "Check the XML sitemap for [website URL] and identify any errors."
• “Review the robots.txt file for [website URL] to ensure AI crawlers can access all content.”

Tips & gotchas

• The audit workflow should be executed in priority order, starting with crawlability issues as they impact subsequent steps.
• Data sources are prioritized: Google Search Console (field data) is considered the most important, followed by CrUX Dashboard and PageSpeed Insights.
• Focus on warnings during schema validation, not just errors, as these often indicate areas for improvement.