All documentation

    Website Analyser & Site Audit

    Rank Pilot AI SEO gives every website two complementary diagnostic tools: the Website Analyser (WebsiteAnalyser.tsx), an AI-driven deep-dive into content, technical SEO, competitors and backlink authority, and the Site Audit (SiteAuditPage.tsx), a scored technical, performance and accessibility check. Both are entry points into the platform's fix workflow, so an issue found here can usually be resolved without leaving the page.

    Website Analyser

    The analyser is reached per-website and triggers the website-analyse edge function, passing the website ID and any tracked competitor domains. A run typically takes 30–60 seconds while the AI reviews the site and its rivals. Results are stored in the website_analyses table and the page always shows the five most recent runs, defaulting to the latest.

    Each analysis returns four scored sections, shown as an overview strip and then as detailed tabs:

    • Content — readability, keyword density assessment, content strengths, content gaps and specific recommendations.
    • Technical — a list of issues, each with a severity (critical, warning, info), a plain-English fix, an estimate of Core Web Vitals impact, crawlability notes and structured data status.
    • Competitor comparison — how the site stacks up against the competitor domains supplied.
    • Backlink authority — link profile commentary.

    An overall score and per-section scores (0–100) are colour-coded: green from 80, amber from 50, red below that.

    Fixing issues from the analyser

    Each technical issue carries a "Fix" button. The page classifies issues as Core Web Vitals-related (matching patterns like LCP, CLS, INP, lazy-loading, render-blocking scripts) versus general technical issues, and gates each accordingly behind the auto_fix_cwv or auto_fix_core plan features — locked issues show an "Upgrade" button with a crown icon instead. When access is available, clicking Fix invokes autopilot-cwv (for Core Web Vitals issues) or autopilot-wordpress (for general fixes) against the connected CMS. If no CMS connection exists, the analyser falls back to generating a downloadable HTML patch via the generate-fix-patch function that the user can paste into their site's <head>. Successful fixes report how many changes were made and, where available, the before/after PageSpeed Insights (PSI) score.

    The analyser page also embeds the Ahrefs Insights panel and an Improvement Agents component that surface further AI-generated recommendations tied to the same website.

    Site Audit

    Site Audit is a separate, gated feature (basic_site_audit) focused on a broader SEO, performance and accessibility scan of the whole site rather than an AI content review. Running an audit calls the seo-audit edge function with the website ID; results are stored in site_audits and rendered through the shared AuditResultsPanel component, which presents scores and prioritised recommendations. Only the latest audit per website is kept in view, with a "Re-run audit" action to refresh it.

    Auto-fix Core Web Vitals

    Alongside the standard audit run button, the Site Audit page offers a dedicated Auto-fix Core Web Vitals action, gated behind the same auto_fix_cwv feature used on the analyser. It calls autopilot-cwv with action: "run_all", which works through the enabled CWV-related fixes across the site. Outcomes are reported as a count of fixes applied and pages touched, with PSI before/after scores when available. If the site has no CMS connection registered in Autopilot, the user is prompted to connect one first rather than being offered a downloadable patch on this page.

    Issue types and severities

    Across both tools, issues are described with a severity level (critical, warning or informational) and a specific remediation, rather than a generic checklist item — for example "missing meta description on 4 pages" paired with the exact fix text. Core Web Vitals issues are detected by keyword matching against the issue and fix text (LCP, CLS, FID, INP, image weight, render-blocking scripts, deferred/lazy-loaded assets) so that they can be routed to the specialised CWV auto-fix pipeline rather than the general WordPress fixer.

    Access control

    Both pages sit behind FeatureGate wrappers tied to plan features (basic_site_audit for the audit; analyser access follows the website's plan). Auto-fix actions are separately gated by auto_fix_core and auto_fix_cwv, so a user can have audit visibility without automated remediation, and vice versa depending on their subscription tier. Where a gate blocks an action, a FeatureGateModal is shown explaining the required upgrade rather than silently failing.