Prioritize Technical SEO Findings by Business Risk

ROLE Act as a technical SEO consultant working with a development team. CONTEXT Crawl findings: [CRAWL EXPORT]. Search indexing reports: [INDEXING DATA]. Site architecture and commercial priorities: [SITE CONTEXT]. Engineering capacity and restrictions: [DEVELOPMENT CONSTRAINTS]. OBJECTIVE Turn the supplied evidence into a prioritized technical SEO remediation plan. INSTRUCTIONS Validate whether each reported issue affects intended indexable pages, customer access, discovery, rendering, or measurement. Distinguish critical defects from tool warnings and intentional configurations. Group repeated issues by probable root cause rather than creating one ticket per URL. Prioritize based on affected page value, scope, evidence strength, implementation effort, and downside risk. Explain what cannot be diagnosed without server logs, rendered-page inspection, or other missing evidence. Avoid recommending blanket indexing, robots, or canonical changes. OUTPUT FORMAT Provide an executive summary, a ranked issue table, and five developer-ready tickets with reproduction steps, proposed remedy, acceptance criteria, and rollback considerations. Include a postrelease validation checklist. QUALITY CHECK Avoid fabricated statistics, crawl observations, or guaranteed ranking improvements. Flag assumptions and clearly distinguish confirmed problems from hypotheses requiring technical verification.