□ Strategy and architectureDiscovery, sitemap, practice hierarchy, lawyer relationships, office structure and question coverage.
□ Custom design scopeWhich page types are actually designed and whether the work is custom or adapted from a template.
□ Mobile-first developmentResponsive behavior, real-device testing and clear mobile performance expectations.
□ Content scopeWho writes practice pages, lawyer biographies, office pages and articles, and who reviews legal accuracy.
□ Lawyer evidence structureHow individual practices, biographies and locations are kept distinct from broader firm-level claims.
□ Local and office architectureHow offices, service areas and lawyer locations are represented without creating misleading geographic signals.
□ Structured dataWhich schema types are used, how they match visible content and who maintains them.
□ Intake routingForms, acknowledgments, urgency handling, source attribution and integration with existing workflows.
□ Analytics and conversion eventsForm submissions, click-to-call, booking, campaign attribution and other meaningful actions.
□ Performance targetsImage optimization, caching, script discipline and measurable page-performance expectations.
□ AccessibilityKeyboard use, labels, contrast, semantic structure and the standard the provider is targeting.
□ Security and privacyHTTPS, security headers, updates, form handling, access controls and retention considerations.
□ Migration planRedirects, canonical URLs, sitemap changes, preservation of valuable URLs and post-launch crawl monitoring.
□ OwnershipDomain, content, code, analytics, credentials, structured data and any private knowledge assets.
□ TrainingWhat the firm's staff can update themselves and what requires the provider.
□ Post-launch supportWhat is included, what is billed separately and how quickly critical issues are handled.
□ Future-search readinessCrawl access, entity clarity, answerability, source attribution and a plan for measuring important client-question coverage.
□ Private knowledge optionsIf relevant, how approved structured information or a vector layer can be exported, governed and maintained.
