Consider a company preparing a website redesign. Its existing site is maintained by an outside vendor, the marketing team wants more qualified organic inquiries, and management is also paying attention to how the brand appears in AI search. Procurement should not begin with “improve rankings.” Prepare a brief covering audiences, product pages, markets and languages, commercial queries, conversion events, current traffic sources, CMS access, and the redesign timetable. Ask each candidate which issues SEO can address and which require product, content, development, or sales involvement. Require priorities, dependencies, and exclusions in the proposal.

Separate the brief into comparable layers. The technical layer should cover crawling, indexing, speed, structure, and internal linking. The content layer should cover research, page mapping, editorial ownership, and review. The business layer should define valid inquiries such as forms, calls, bookings, or quote requests. Ask each agency to demonstrate a diagnosis using one core service page, including its data sources, recommended change, owner, and completion condition. A generic checklist is not enough; if the current site has not been validated, request an exploration phase before comparing ongoing work.

Service labels do not reveal delivery depth. Translate every activity into an item that can be checked off: a keyword-to-URL map, technical issue register, content brief, edited copy, structured-data recommendations, development tickets, launch checks, and a recurring observation report. State who prepares, approves, and deploys each item. If an agency also offers website design, advertising, GEO, tools, or training, ask it to separate the core scope from options rather than blending different disciplines into “integrated service.” Businesses operating across markets should also clarify research languages, local review, and ownership of each site version.

The working model must match internal capacity, not just the service menu. If the company has developers, ask for actionable tickets, priorities, validation steps, and rollback procedures. If it lacks editorial resources, clarify who writes, who checks facts, and how revisions are handled. Every monthly meeting should review completed work, decisions required, blockers, next steps, and access needs. At handover, the business should receive usable accounts, settings, source documents, report definitions, and change history. Make the boundary between staging and production a formal approval condition.

Measurement should begin with repeatable observation conditions, not a desired ranking. Ask candidates to fix the keyword set, country, language, device, primary page, and observation period. Separate impressions, clicks, organic visits, qualified inquiries, and later opportunities, and state the data source and how branded queries or test forms are handled. If AI search is in scope, define a separate method for recording mentions, citations, source pages, and question sets. Traditional rankings, AI answers, and business conversion should not become one blended metric. Reports should also identify redesigns, seasonality, and tracking changes.

Use scenario questions to test whether the agency understands procurement risk. If development is delayed for a month, what can proceed? If traffic rises but inquiry quality falls, how would the team investigate? If legal review is required for content, how does the workflow change? If the engagement ends, what data and settings are returned? Before signing, request a small initial work plan with assumptions, required inputs, meeting rhythm, sample acceptance items, and an escalation contact. Marketing, product, engineering, and management should jointly assess communication, documentation, and decision logic before selecting a partner.