Technical checks should prove that search engines can reach, render, understand, and index the pages that matter to the firm.
Image delivery and portfolio rendering - Evidence required: a crawl sample of portfolio pages, image requests, rendered mobile pages, and file-size findings. Pass when primary portfolio content loads without broken assets and image delivery does not create an obvious usability or crawl barrier.
Severity: high when core project pages fail to render or become materially slow. Owner: developer for implementation, SEO specialist for diagnosis. Corrective action: resize oversized assets, use appropriate compression and delivery formats, preserve useful image descriptions, and avoid replacing important visual content with inaccessible scripts. Validation: rerun the same page tests and compare the evidence.
Structured data accuracy - Evidence required: the visible page content, implemented markup, and a validation result from an appropriate testing tool. Pass when markup reflects content users can actually see and contains no material validation errors.
Severity: medium unless broken markup interferes with broader technical quality. Owner: developer with SEO review. Corrective action: remove unsupported or inaccurate properties and align markup with current documentation. Validation: retest the final rendered page.
Core page performance - Evidence required: field or lab diagnostics for key templates, with attention to loading and layout behavior. A useful internal benchmark can compare the site against the top 20-30 percent of the firm's own tested page set without treating that comparison as a Google requirement.
Pass when priority pages have no unresolved performance issue that materially impairs use. Severity: high for sitewide template problems. Owner: developer. Corrective action: address oversized hero media, layout instability, render-blocking assets, and inefficient template behavior. Validation: repeat the same diagnostics after deployment.
Mobile navigation and interaction - Evidence required: hands-on testing of menus, project galleries, forms, and calls to action on representative devices. Pass when a visitor can reach important services, projects, and contact actions without hidden controls or broken interactions.
Severity: high when navigation or forms fail. Owner: developer or design team. Corrective action: simplify interactions and fix mobile layout defects. Validation: retest the complete user path.