SEO Discovery Call Script: Qualify and Scope in 30 Minutes

Updated 2026-09-07 · guide · AI,services,sales,discovery,qualification

An SEO discovery call is a 30-minute diagnostic conversation that identifies the buyer’s commercial goal, current funnel, evidence, prior attempts, constraints, authority, budget range, and decision path before any proposal is written. It matters because AI SEO engagements often require content, engineering, analytics, brand, sales, and leadership cooperation. A call that only collects keywords hides the constraints that will later delay delivery. By the end of this guide, you will be able to run a respectful, specific, and well-scoped discovery call, qualify the buyer, avoid premature promises, and decide whether to send a proposal, a paid diagnostic, a lead asset, or a clear no.

The purpose of a discovery call

A discovery call is not a free audit and not a sales pitch. It has five jobs:

1. Understand the business problem, not only the SEO symptoms.
2. Inspect current evidence, such as analytics, rankings, conversion paths, and sales feedback.
3. Identify constraints, including engineering capacity, approvals, content resources, and budget.
4. Test fit, using scope, timing, and investment range.
5. Agree on a decision path, even if the answer is no or not yet.

If the call does not produce these five outputs, the buyer may leave with information, but you leave with ambiguity.

Use this call after your service page conversion copy has already set expectations and before the broader SEO discovery phase begins. The call is a filter, not the full discovery.

Prepare before the call

Preparation should take 20-30 minutes and should prevent obvious questions.

1. Review the buyer’s public funnel

Look for:

• Homepage promise.
• Product or service pages.
• Pricing page.
• Documentation.
• Comparison or alternatives pages.
• Case studies.
• Blog and content hub.
• CTA and form fields.
• Checkout or booking path.

Note whether the site explains what it sells, who it is for, and why it is credible.

2. Review observable search signals

Use available tools and public evidence:

• Pages indexed by search engines.
• Branded search presence.
• Comparison and alternative queries.
• Competitors appearing for buying-cycle terms.
• Content gaps around product decisions.
• Documentation accessibility.
• Titles, headings, and metadata.
• Obvious rendering or mobile problems.

You are not building the final strategy. You are finding questions worth asking.

3. Check company signals

Look for:

• Funding stage.
• Hiring roles.
• Recent product launches.
• New market entry.
• Leadership changes.
• Public case studies.
• Team size.
• Relevant job descriptions.

A company hiring growth engineers has different capacity from one hiring only salespeople.

4. Prepare a call map

Have a one-page agenda:

1. Context and goal.
2. Current funnel.
3. Evidence and prior attempts.
4. Constraints and dependencies.
5. Decision process and timing.
6. Fit and investment.
7. Next step.

Do not turn the agenda into a script so rigid that the buyer cannot talk.

Open the call in the first three minutes

A good opening explains the structure and moves control forward.

Sample opening

“Thanks for booking the time. I’d like to use 30 minutes carefully. First, I’ll ask about your goal and current funnel. Then we’ll look at what has worked, what has blocked progress, and what needs to be true for this to be worth doing. Near the end, I’ll explain the smallest way to start, and if there is fit, we’ll agree on a next step. Does that work?”

This shows respect for their time and sets up qualification without ambush.

Confirm the main reason

Ask:

• “What made you book this call now?”
• “What happened in the last 60-90 days that made this important?”
• “What would make this call useful for you?”

The timing clue often reveals urgency, budget pressure, leadership attention, or a failed agency experiment.

Diagnose the commercial goal

Do not accept “more traffic” as the goal. Translate it into a commercial outcome.

Ask:

1. “What business result should this program support?”
2. “What action do you want a visitor to take?”
3. “What does a qualified lead or trial look like?”
4. “How is that measured today?”
5. “What number would make the program successful in 90 days?”
6. “What is the current baseline?”

If the buyer cannot answer, that is useful information. You may need conversion tracking, sales-call review, or a paid diagnostic before a full program.

For measurement structure, connect answers to your SEO budget and ROI reporting model.

Map the current funnel

SEO does not operate in isolation. Ask:

• “Where do qualified buyers currently come from?”
• “What happens after someone visits the site?”
• “Which page currently converts best?”
• “What do sales hear in the first call?”
• “What objections repeat?”
• “Where do people drop off?”
• “What does your sales team say marketing should send them?”

Then ask for access or screenshots if data is unavailable. The funnel determines whether SEO can help. If traffic exists but conversion is broken, a pure content program will disappoint everyone.

Use questions from the CRO audit guide if the buyer suspects conversion issues.

Inspect evidence and prior attempts

Prior SEO failure is common. You need to know why.

Ask:

1. “What SEO or AI visibility work have you already tried?”
2. “What improved?”
3. “What did not improve?”
4. “Who executed it?”
5. “What access did they have?”
6. “How were priorities chosen?”
7. “What did leadership expect?”
8. “What evidence convinced people it worked or failed?”

Look for patterns:

• Generic blog content with no buying-cycle coverage.
• Technical recommendations never implemented.
• No conversion path.
• No reporting tied to qualified demand.
• No stakeholder approvals.
• No documentation or product involvement.
• A new domain with unrealistic timing expectations.

If the buyer calls all SEO a failure but never implemented technical fixes or comparison pages, the next program must include governance and expectations, not just articles.

Identify the real constraints

Most engagements are constrained before they start. Ask:

• “Who writes or approves content?”
• “Who can implement technical changes?”
• “How long do site changes take?”
• “What CMS and analytics systems do you use?”
• “Can we access Search Console and analytics?”
• “Are there compliance, legal, or security reviews?”
• “What is the product roadmap focused on this quarter?”
• “Which teams must approve messaging?”
• “How many hours per week can your team give this?”

Then listen for the hidden blocker:

• No engineering time.
• No product owner.
• No content subject-matter expert.
• No sales feedback loop.
• No authority to change the site.
• No budget for implementation after the audit.

The broader discovery phase should verify these details, but the call should reveal whether a meaningful engagement is possible.

Qualify authority and decision process

Do not embarrass the buyer. Ask practical questions:

1. “Who feels this problem most inside the business?”
2. “Who will evaluate the proposal?”
3. “Who approves budget?”
4. “What does your approval process usually require?”
5. “Have security, legal, or procurement reviews been needed before?”
6. “What decision date do you have in mind?”
7. “What could delay the decision?”

If the buyer says, “I need to speak with my partner,” the next step may be a joint call. If they say, “We will share it internally,” prepare a stakeholder packet. The proposal follow-up system should carry that forward.

Discuss investment without awkwardness

Investment should be discussed after value and scope shape are clear. A useful bridge:

“There are a few ways we work. A full program is usually $X-$Y depending on scope. Some teams start with a two-week diagnostic at $Z so the first decision is smaller. Does either path fit the budget you have this quarter?”

This works because it:

• Names a range.
• Offers a smaller paid start.
• Ties timing to budget.
• Avoids demanding an exact number before value exists.
• Makes no-fit conditions visible.

If the buyer resists any range, ask:

• “Have you budgeted for this work?”
• “Is the budget approved now or in the next cycle?”
• “What range have similar projects used before?”
• “Would a diagnostic fit better than a full program?”

Do not negotiate in the discovery call unless the buyer explicitly asks. Use the pricing logic in your SEO pricing models and packages and keep boundaries consistent with AI service package examples.

Test urgency and capacity

A real problem without capacity is still a no for now.

Ask:

• “If we agreed on a plan in two weeks, could your team implement it?”
• “What start date would be realistic?”
• “What else is competing for engineering and content time?”
• “Who would own this internally?”
• “What happens if nothing changes this quarter?”

The last question reveals commercial pressure. If the buyer has no cost of delay, the project may be a curiosity rather than a priority.

Check technical and AI visibility readiness

For AI products and technical buyers, ask focused questions:

• “Can AI crawlers and search engines access your key pages?”
• “Do docs, pricing, comparison pages, and FAQs render without special interaction?”
• “Is there a sitemap, canonical strategy, and internal linking plan?”
• “Does your site expose evidence that AI engines can cite?”
• “Do you track branded search, product queries, comparison queries, and assistant citations?”
• “Is documentation part of the buyer journey?”

If these questions require investigation, the paid diagnostic may be the right next step. Use the technical SEO checklist later, not as a live audit trap during the call.

Make the offer shape visible

Toward the end, summarize what you heard in five sentences:

• “Your goal is X.”
• “Today, the main constraint appears to be Y.”
• “The funnel needs evidence around Z.”
• “Your team can provide A, but B is uncertain.”
• “A diagnostic-first approach would test the largest assumptions.”

Then name the possible paths:

Path 1: Paid diagnostic

Best when the problem is real but unknown. Scope includes query mapping, technical review, conversion inspection, and a prioritized roadmap.

Path 2: Scoped program

Best when evidence, access, and dependencies are already clear. Scope includes implementation in weekly increments with acceptance criteria.

Path 3: Advisory retainer

Best when internal execution exists but governance, senior review, or prioritization is missing.

Path 4: Lead asset

Best when timing is early. Send a checklist, template, or calculator and follow up on a named trigger.

Path 5: No-fit response

Best when budget, authority, expectations, or timing cannot support success.

The lead magnet system can support path four without pretending an unready visitor is sales-ready.

Use a scoring system after the call

Score the buyer immediately while the conversation is fresh. Use a simple 0-2 scale, where 0 means missing, 1 means uncertain, and 2 means clear and positive.

A score is not a verdict by itself. It is a prompt for further qualification. For deeper routing, use the AI SEO lead qualification guide.

Ask for the next step

Never end with “I’ll put something together.” Name a concrete decision path.

Examples:

If there is strong fit

“I can send a one-page proposal for the two-week diagnostic by Thursday. It will include scope, deliverables, price, and first steps. If it matches what we discussed, we can choose a start date.”

If discovery is needed

“The right next step is the two-week diagnostic. It turns these unknowns into a prioritized roadmap. I’ll send scope and pricing today.”

If another stakeholder is needed

“Before a proposal, would it help to include your engineering or growth lead? I can send a one-page summary or join a 15-minute call.”

If timing is early

“This sounds important, but implementation may not be ready. I’ll send the launch-readiness checklist and follow up after your next planning cycle.”

If there is no fit

“Based on timing and required access, I don’t think this is the right month. I’ll send one resource and close the loop unless you suggest a future date.”

Every path should be recorded in your pipeline with status, blocker, and next date. This is where your proposal follow-up system begins.

Sample 30-minute agenda

Use this structure with time boundaries:

0:00-3:00 — Frame and confirm

3:00-8:00 — Commercial goal

8:00-15:00 — Diagnosis

15:00-21:00 — Constraints

21:00-26:00 — Fit and investment

26:00-30:00 — Next step

• Introduce process.
• Ask what made them book now.
• Confirm the desired outcome of the call.
• Business result.
• Qualified action.
• Baseline and target.
• Measurement today.
• Current channels.
• Conversion path.
• Prior SEO work.
• Search and AI visibility concerns.
• Sales objections.
• Product and audience context.
• Content capacity.
• Engineering capacity.
• Approvals.
• Systems and access.
• Compliance.
• Internal owner.
• Offer shape.
• Price range or diagnostic.
• Decision process.
• Authority.
• Start date.
• Summarize.
• Choose path.
• Agree on date.
• Confirm what each side will send.

This agenda is a guide, not a cage. Let the buyer talk, but do not lose the qualification sections.

Questions to avoid

Some questions waste time or create defensive answers.

Avoid:

• “What keywords do you want to rank for?” Too early and buyer-dependent.
• “How much traffic do you want?” Traffic is rarely the commercial goal.
• “What’s your biggest SEO problem?” Often too abstract.
• “Can I share my screen and walk through my process?” Turns the call into a pitch.
• “Do you have a budget?” Too abrupt before value framing.
• “Can you guarantee us results?” The provider should not introduce this language.

Replace them with evidence-seeking questions about baseline, blockers, decisions, and capacity.

Handle common buyer responses

“We just need more content.”

Respond:

“Content can help, but let’s confirm where it should enter the funnel. Are buyers searching for the problem, the category, or alternatives?”

“Our competitor ranks for everything.”

Respond:

“Let’s identify which queries matter commercially. Some rankings are visibility; others drive trials or sales conversations.”

“We tried SEO before.”

Respond:

“What changed, what did not, and what access did the team have? That will tell us what to repeat or avoid.”

“Our site is new.”

Respond:

“Then timing and evidence matter. We can still map buyer queries and build proof, but expectations need a realistic ramp.”

“Can you guarantee rankings?”

Respond:

“No one can honestly guarantee rankings. We can control scope, technical accessibility, evidence, reporting, and iteration.”

“We need to see a proposal.”

Respond:

“I can send one. To keep it useful, I need to confirm the decision date, implementation capacity, and whether the diagnostic or full program fits.”

“Can you start this week?”

Respond:

“We may be able to start soon, but I need to confirm access, owner, and the first milestone. Rushing those creates delivery risk.”

“We need the cheapest option.”

Respond:

“The smallest useful step is usually the diagnostic. It creates a roadmap without committing to a full program.”

Red flags

Stop or redirect the engagement when you hear:

• “We need guaranteed first-page rankings.”
• “We have no budget until results appear.”
• “We cannot provide site, analytics, or CMS access.”
• “Our engineering team has no time.”
• “We expect organic pipeline in 30 days.”
• “Just write 100 articles.”
• “We want AI automation everywhere.”
• “We do not want sales involved.”
• “We want you to manage everything for one low fee.”

Some red flags can be solved with scope. Many cannot. Use the client health scorecard framework after signing, but use red-flag awareness before signing.

Follow up with structure

Send the follow-up within one business day.

Include:

1. Your summary of the goal.
2. The main constraints heard.
3. The proposed next path.
4. What you will send.
5. What they should send.
6. A named date.

Example:

“Thanks for the call. You want more qualified demo requests from comparison and implementation searches. The main constraints are engineering approvals and a content owner. The diagnostic seems like the right first step. I’ll send scope and pricing by Thursday. Please send analytics access and two recent sales-call notes before then.”

This keeps the client onboarding process clean if the buyer says yes. If the buyer disappears, your sales enablement assets and structured follow-up sequence should already contain the proof needed.

Build a discovery-call asset

Turn the script into a one-page operating asset.

Include:

• Agenda.
• Core questions.
• Qualification fields.
• Package paths.
• Red flags.
• Next-step choices.
• CRM fields to complete.

Make it available to whoever joins sales calls. Use your sales enablement guide to package it with proposal summaries, objection cards, and reporting samples.

Quality-control checklist

Before the call, confirm:

• [ ] You reviewed the site and public evidence.
• [ ] You know the buyer’s likely product or service.
• [ ] You have a 30-minute agenda.
• [ ] You know your smallest paid offer.
• [ ] You know your no-fit criteria.
• [ ] You can explain pricing range without apologizing.

After the call, confirm:

• [ ] Commercial goal is recorded.
• [ ] Baseline or evidence gap is recorded.
• [ ] Prior attempts are recorded.
• [ ] Constraints are named.
• [ ] Decision process is clear.
• [ ] Budget range is known.
• [ ] Timing and owner are named.
• [ ] A next step and date exist.
• [ ] The CRM status is updated.
• [ ] Follow-up was sent within one business day.

If more than three post-call boxes fail, the proposal should wait.

The discovery call should surface capacity and approvals that later become the client responsibilities in SEO scope creep control.

Discovery questions about goals and constraints should later become renewal evidence in SEO renewal and expansion proposals.

Discovery should record the systems and owners needed later by SEO client offboarding and win-back.

The discovery script can answer the guarantee question by steering the buyer toward the diagnostic path in SEO service guarantees and risk reversal.

A discovery call can introduce proof without overclaiming; this SEO client case study workflow defines what the story may prove.

A diagnostic delivers what the SEO discovery call script qualifies; this SEO diagnostic deliverable standard turns the call into a signed next step.

Bottom line

A strong discovery call qualifies both sides. It replaces vague SEO requests with a commercial goal, evidence, constraints, authority, timing, and a scoped next step. Use it to choose a diagnostic, program, retainer, lead asset, or honest no—not to force every visitor into the same proposal.

FAQ