How to Brief an SEO Agency for Technical Site Health and Google Lighthouse Scoring

When you engage an SEO agency for technical optimization, the difference between a productive partnership and a wasted retainer often comes down to the quality of your initial brief. Technical SEO—encompassing crawl budget management, Core Web Vitals compliance, and site architecture—is not a set-it-and-forget-it exercise. It requires precise diagnostic work, ongoing monitoring, and a clear understanding of what signals search engines actually reward. This guide walks you through constructing a brief that yields actionable technical audits, realistic Lighthouse score improvements, and sustainable ranking gains, while steering clear of the promises that no agency can ethically deliver.

Why Technical SEO Demands a Different Kind of Brief

Unlike content strategy or link building, technical SEO is largely invisible to site visitors but immediately detectable by search engine crawlers. A poorly structured brief can lead an agency to focus on vanity metrics—such as a perfect Lighthouse score on a staging environment—while ignoring the underlying issues that suppress organic visibility. The goal of your brief should be to establish a shared diagnostic framework, not to dictate specific outcomes. For example, rather than demanding "a 90+ Performance score in Lighthouse," ask for a documented analysis of how each Core Web Vitals metric (LCP, CLS, FID/INP) currently performs on real user data from the Chrome User Experience Report (CrUX), alongside prioritized remediation steps. This shifts the conversation from abstract targets to measurable, user-centric improvements.

A well-constructed brief also protects you from agencies that promise "guaranteed first page rankings" or "instant SEO results." No ethical firm can guarantee rankings because search algorithms are proprietary and constantly evolving. What they can guarantee is a methodical process: crawling, indexing analysis, performance profiling, and iterative fixes. Your brief should demand evidence of that process, not assurances of outcomes.

Step 1: Define the Scope of the Technical Audit

The first section of your brief must specify what a technical SEO audit covers. A comprehensive audit goes beyond a simple crawl report. It should include, at minimum:

• Crawlability and Indexation: Analysis of robots.txt directives, XML sitemap structure, and crawl budget allocation. For large sites (over 10,000 URLs), crawl budget becomes critical—you need the agency to identify pages that waste crawl capacity, such as thin content, infinite scroll traps, or parameter-laden URLs.
• Core Web Vitals Baseline: Extraction of field data from CrUX and lab data from Lighthouse. The agency should differentiate between opportunities (optimizations that may improve scores) and diagnostics (issues that do not directly affect scores but indicate underlying problems).
• Duplicate Content and Canonicalization: Identification of exact or near-duplicate pages, missing or conflicting canonical tags, and improper use of noindex directives.
• Site Architecture: Evaluation of internal linking depth, orphan pages, and URL hierarchy. A flat architecture (any page reachable within three clicks from the homepage) is generally preferable, but the audit should justify recommendations with crawl data.

Request that the audit deliver a prioritized list of issues ranked by potential impact on organic traffic and crawl efficiency, not by how easy they are to fix. This prevents the agency from cherry-picking low-effort wins while ignoring structural problems.

Step 2: Specify Google Lighthouse Scoring Parameters

Lighthouse scoring is a frequent source of misalignment between clients and agencies. A brief that simply says "improve Lighthouse scores" invites the agency to optimize for the tool rather than for users. To avoid this, define the following in your brief:

Agencies often propose lazy loading every image or deferring all third-party scripts. While these tactics can boost Lighthouse scores, they may harm user experience if implemented aggressively. Your brief should require the agency to document the user-facing impact of each optimization before deployment.

Step 3: Outline Crawl Budget and Indexation Requirements

Crawl budget management is one of the most misunderstood areas of technical SEO. Many agencies treat it as a binary issue—either your site is crawlable or it isn't. In reality, crawl budget is a finite resource that search engines allocate based on site authority, update frequency, and server response times. Your brief should ask the agency to:

• Analyze Current Crawl Allocation: Use Google Search Console's Crawl Stats report to identify how Googlebot spends its time. If too many resources go to low-value pages (e.g., faceted navigation filters, paginated archives), the agency must propose a solution, such as consolidating parameters via robots.txt or implementing rel="nofollow" on crawl sinks.
• Optimize XML Sitemaps: The sitemap should contain only indexable, canonical URLs. Remove pages with noindex, redirects, or 4xx/5xx status codes. The agency should split large sitemaps into thematic files (e.g., products, blog, categories) and reference them in a sitemap index.
• Validate robots.txt: Ensure that critical resources (CSS, JS, images) are not blocked. A common mistake is disallowing all crawlers during a site migration and forgetting to revert the directive. The brief should require a weekly robots.txt check for the first month post-launch.

Avoid any language that suggests "increasing crawl budget." You cannot increase it; you can only use it more efficiently. A good agency will explain this distinction rather than promise more frequent crawling.

Step 4: Integrate On-Page Optimization with Technical Findings

Technical SEO and on-page optimization are interdependent. A technically sound site with poor content will not rank, and great content on a slow, unindexable site is invisible. Your brief should bridge these disciplines by asking the agency to:

• Map Search Intent to Site Architecture: After keyword research and intent mapping, the agency should propose a content strategy that aligns with the site's technical capabilities. For example, if the site cannot handle dynamic rendering for JavaScript-heavy pages, the agency should prioritize static HTML content for high-value keywords.
• Implement Structured Data: The brief should specify which schema types are relevant (e.g., Product, FAQ, HowTo, Article) and require validation via Google's Rich Results Test. Schema must be tested on live pages, not in a sandbox.
• Audit Internal Linking for Authority Flow: The agency should identify pages with high Domain Authority or Trust Flow that are not linked from the homepage or main navigation. These pages represent untapped equity that can be redistributed via strategic internal links.

A common failure point is treating on-page optimization as a one-time task. Your brief should include a maintenance schedule: monthly content refreshes for cornerstone pages, quarterly schema audits, and continuous monitoring of click-through rates from search snippets.

Step 5: Define Link Building Parameters Within a Risk-Aware Framework

Link building is where technical SEO intersects most dangerously with black-hat tactics. A brief that does not explicitly forbid certain practices invites trouble. Use your brief to establish a risk-aware policy:

• Prohibited Tactics: Private blog networks (PBNs), paid links, automated outreach, link exchanges, and any form of cloaking. The agency should sign a statement that they will not use these methods.
• Approved Methods: Digital PR, guest posting on authoritative domains with editorial relevance, resource page link insertion, and broken link replacement. All links must be dofollow and placed within contextual content, not in footers or sidebars.
• Backlink Profile Monitoring: The agency should provide a monthly report showing new links gained, lost links, and changes in Domain Authority/Trust Flow. Any sudden spike in low-quality links (e.g., from .xyz domains or casino sites) should trigger an immediate review and potential disavowal.

The brief should also require the agency to explain how they will handle negative SEO attacks—malicious competitors pointing spammy links at your site. A response plan, including a disavow file and Google reconsideration request process, should be part of the engagement.

Step 6: Set Success Criteria for Core Web Vitals and Site Speed

Core Web Vitals are not a one-time fix. They require continuous monitoring because third-party scripts, new content, and platform updates can degrade performance overnight. Your brief should establish:

• Baseline Measurement: The agency must record current LCP, CLS, and FID/INP values from CrUX and Lighthouse before any changes. This baseline is the reference point for all future optimizations.
• Target Thresholds: Good thresholds are LCP < 2.5 seconds, CLS < 0.1, and FID < 100ms (or INP < 200ms). The agency should commit to achieving these on the 75th percentile of page loads, as measured by CrUX.
• Monitoring Cadence: Weekly Lighthouse runs via Pagespeed Insights API and monthly CrUX reports. Any regression beyond 10% of the baseline should trigger an alert and a remediation plan.
• Optimization Sequence: The agency should prioritize server-side fixes (TTFB reduction, CDN implementation, image optimization) over client-side hacks (deferring scripts, lazy loading everything). Server-side improvements are more durable and less likely to break with browser updates.

Demand that the agency document the trade-offs of each optimization. For example, compressing images to WebP may reduce LCP but could increase CLS if dimensions are not explicitly set. A transparent agency will flag these risks before implementation.

Step 7: Build a Reporting and Communication Cadence

A technical SEO engagement without structured reporting is a recipe for scope creep and misaligned expectations. Your brief should specify:

• Monthly Technical Health Report: A dashboard showing crawl errors, indexation status, Core Web Vitals trends, and backlink profile changes. Use tools like Chrome DevTools Performance and Web Vitals Extension for real-time checks between reports.
• Quarterly Deep-Dive Audit: A full re-audit of site architecture, robots.txt, sitemaps, and canonical tags. This is especially important after major site updates (redesigns, platform migrations, new product launches).
• Incident Response Protocol: Define what constitutes a critical issue (e.g., a sudden drop in indexed pages, a site-wide 500 error, a Core Web Vitals regression) and the expected response time (e.g., 4 hours for critical, 24 hours for high priority).

The reporting structure should also include a "lessons learned" section after each optimization cycle. What worked? What didn't? This turns the engagement into a learning partnership rather than a transactional service.

Common Pitfalls to Avoid in Your Brief

Even a well-structured brief can fail if it contains hidden assumptions. Watch for these common pitfalls:

• Over-specifying Technical Solutions: Telling the agency to "implement lazy loading on all images" assumes that lazy loading is always appropriate. It is not—hero images above the fold should load immediately. Instead, state the desired outcome ("reduce initial page weight without sacrificing above-the-fold content") and let the agency propose the method.
• Ignoring Mobile vs. Desktop Differences: Many agencies optimize for desktop because it is easier to test. Your brief should explicitly state that mobile performance is the priority, and any desktop optimizations must not degrade the mobile experience.
• Equating Tool Scores with User Experience: A Lighthouse score of 95 does not guarantee a fast-feeling site. The brief should include user-centric metrics like Time to Interactive and First Input Delay, not just composite scores.
• Failing to Plan for Rollbacks: Every optimization carries risk. The brief should require the agency to have a rollback plan for each change, including version control for code changes and a staging environment for testing.

Conclusion: From Brief to Partnership

A technical SEO brief is not a shopping list; it is a framework for collaboration. By specifying data sources, defining acceptable trade-offs, and banning risky tactics, you create an environment where the agency can do their best work without cutting corners. The best technical SEO engagements are those where the client understands that site health is a continuous process—not a project with a fixed end date.

After the initial audit and optimizations, use the Site Speed Optimization guide to maintain momentum. Revisit your brief quarterly to adjust priorities as search algorithms evolve and your site grows. With a clear, risk-aware brief, you turn your agency from a vendor into a strategic partner in your organic growth.