What to put in a useful search audit brief

A useful search audit brief tells the reviewer what decision the business needs to make. It also tells the business what evidence to expect back. Before sending a list of URLs to an agency or consultant, spend a little time defining the question, the people involved and the limits of the investigation. That work makes the eventual recommendations easier to assess and assign.

For a cannabis marketing team, the brief might concern a site migration, a group of location pages or a publishing process that has become difficult to maintain. Those are different jobs. A single broad request can mix them together until nobody knows whether the audit should produce a developer backlog, an editorial plan or a management decision. Choose the primary job first.

Write the decision in one sentence

Begin with a sentence such as: “Before replacing the location-page template, we need to identify technical and content problems that the new template must address.” This gives the reviewer a reason to investigate the template, a boundary for the work and a practical use for the result. It also allows the project manager to explain why an interesting but unrelated finding belongs in a later discussion.

Add two or three supporting questions. Which page types need separate treatment? Are important visitor details available on the current pages? Which findings require a developer, and which require a business owner to verify the information? Keep the questions in the client's language. The reviewer can translate them into technical checks while preserving the decision the brief was written to support.

Describe the website people will inspect

Provide the main domain, relevant subdomains, content platform and any separate systems that render important parts of a page. Identify the page families in scope: location pages, editorial articles, category pages or a contact flow. List recent changes with approximate dates and the person who can explain each change. A reviewer needs context for what is already known, what is currently changing and what is scheduled next.

Include a short inventory of the teams involved. The marketing lead may approve content, a developer may control the template and an operations manager may own hours and addresses. A single recommendation can depend on all three. Put names or roles beside those responsibilities so the reviewer can direct questions to the right person instead of sending every question through the project sponsor.

Choose a sample with a reason

Do not let the sample be determined entirely by whichever URLs are easiest to copy. Select examples that exercise the main variations in the site. A typical location page shows the common pattern. A location with unusual hours tests exceptions. A newly published page may reveal the current publishing process, while an older page can show what has accumulated over time.

Record why each sample URL was selected. If the brief requests a full crawl, distinguish that broader collection from the pages that will receive detailed manual review. The two activities answer different questions. A crawl can expose patterns across many URLs; a close review can explain the experience and context of a specific page. The final proposal should say which activity is included and how its findings will be used.

Supply access through the right process

List the data sources the reviewer needs and the person who can grant access. Use each platform's own account permissions rather than putting passwords in the brief. Specify whether the engagement needs read-only access or requires someone to make changes. Most diagnostic work can begin with observation and exports while implementation remains a separate, controlled task.

For search data, identify the correct property and the period the reviewer should examine. Google's Search Console performance documentation explains metrics and filtering for search-result performance. In the brief, ask the reviewer to retain the date range and filters used for each observation. A graph without that context is difficult for another person to reproduce or compare later.

Define an evidence standard

Request a consistent record for each material finding: affected URL or page group, observed behavior, observation date, reproduction steps, supporting source and proposed action. Screenshots can help explain a visual problem, while response details or page markup may be more useful for a technical issue. Let the form of evidence follow the finding rather than requiring the same attachment for every row.

Ask the reviewer to distinguish observations from explanations that still need testing. A page returning an error is an observation. A theory about why demand changed is a different kind of statement. The distinction helps the client decide what can be fixed immediately, what needs further research and what should remain an open question in the final report.

Agree how priorities will be assigned

An audit becomes difficult to use when every row is marked urgent. Ask for a priority method connected to the brief's decision. A problem that prevents the planned template launch may need attention before an unrelated improvement. A repeated error affecting a whole page family may deserve a different response from a small issue on one seldom-used page.

Include effort and dependencies alongside priority where the reviewer can reasonably assess them. The developer should confirm implementation estimates. The reviewer can still identify whether a recommendation depends on new business information, a template change or a decision about page purpose. Those dependencies make the handoff easier to schedule and prevent a seemingly simple task from sitting unresolved in a backlog.

Use primary guidance precisely

Google's SEO Starter Guide covers helping search engines crawl, index and understand content. It is a useful source for basic practices, but a source link alone is not an explanation of a finding. Ask the reviewer to connect the relevant guidance to the observed page behavior and the proposed action. That connection is what makes a citation useful in a working document.

The brief should also identify who reviews recommendations involving business facts or specialized claims. A search reviewer may identify a gap in a page, while the business remains responsible for supplying accurate information. Build that review into the schedule. Otherwise, an apparently complete audit can leave editors waiting for answers that were never assigned to anybody.

Walk through the expected handoff

Consider a hypothetical team with eighteen location pages preparing for a template replacement. Its brief identifies four representative pages, a planned release window, the template owner and the operations contact. The reviewer returns a short decision memo and an evidence table. The memo names the changes needed before release; the table gives the developer and editor enough detail to act on each accepted item.

At the handoff meeting, the team assigns an owner, a next action and a verification method to each accepted recommendation. Some rows become implementation tasks. One becomes a request for corrected hours. Another remains a research question because the available data does not explain the pattern. That is a useful outcome: the team can see the different kinds of work instead of treating a report as one undifferentiated list.

Finish with acceptance criteria

Define what it means for the audit itself to be complete. The promised page groups have been reviewed. Material findings have evidence. Open questions are visible. Recommendations are connected to the original decision. A named person has received the working files and can reproduce a sample finding. These are concrete acceptance checks for the deliverable, separate from any later outcome of implementation.

A one-page brief can hold the decision, scope, sample, access owners, deliverables and acceptance criteria, with supporting inventories attached. Draft that page before requesting a quote. Then ask the prospective reviewer to explain how their method answers the stated questions. The conversation will be about a real piece of work, and the final report will have a clear place to go.