respira-site-audit

# Respira Site Audit ## Common Mistakes | Mistake | Correct approach | |---|---| | Running analyzers without knowing which page to audit | Always confirm the target. Site-wide (all public pages) or a specific page URL or ID. | | Reporting raw analyzer output without prioritising | Group findings by severity (CRITICAL, WARNING, SUGGESTION) and surface quick wins first. | | Running all analyzers in sequence when only one is needed | Match the analyzer to the question. If the user asks about SEO only, run `respira_analyze_seo` and skip the rest. | | Skipping `respira_get_builder_info` before reporting element-level issues | Builder type affects which fixes are possible. Elementor, Divi 4, Divi 5, Bricks, Beaver, and Oxygen all have different fix paths. | | Treating AEO and SEO as interchangeable | SEO targets search rankings. AEO targets AI-generated answers. Both analyzers cover different signals and you usually want both. | | Not checking whether the page is published before auditing | Drafts and private pages may produce incomplete results. Confirm `status: publish` first. | | Using `extract_builder_content` when you only need structure | Use `respira_get_page_outline` for the "what is on this page" read. It is lighter and includes the primary heading per row. | ## Inputs - Target: a specific page URL, page ID, or "the whole site". - Scope: which analyzers to run. Default is all eight. - Output format: a summary for the user, or JSON for a CI / CD pipeline. ## Workflow ...