Begin with indexability and intent
Confirm that valuable URLs return the right status, are crawlable, declare coherent canonicals, and satisfy the intent they target. A technically perfect page with no purpose is not a priority.
Follow the templates
A defect affecting one page is different from a defect generated by a template across thousands of URLs. Group findings by source pattern so one engineering fix can remove an entire class of problems.
Connect performance to page value
Use lab diagnostics to find causes and field data to understand real experience when enough data exists. Prioritize slow templates that receive meaningful organic entrances or support conversion.
Validate after release
A ticket is not complete when code ships. Recrawl affected patterns, confirm rendered output, check monitoring, and record the release so performance changes can be explained later.