Technical intake that captures backend access up front
Ask about crawling and indexing issues, backend access, and approval ownership before your first call, then collect Search Console screenshots straight through the intake so unqualified requests don't turn into a proposal that never lands.
The exact intake your technical seo leads complete
This is the real 7-question guided intake for Technical SEO — the same flow your customers finish before you ever pick up the phone.
What a qualified technical seo lead should tell you
Diagnosis and repair of website crawling, indexing, speed, and structural issues that affect organic search visibility and rankings.
- Main Technical Issue Want
- Platform Website Run On
- Have Access Website'S Backend
- Have Access Google Search
- How Many Pages Website
- Would Be Responsible Approving
- Soon Start This Project
The questions your team needs answered
Every technical seo intake asks these — and why each one matters.
| Question | Why it matters |
|---|---|
| What is the main technical issue you want addressed? | The specific issue selected, like indexing failures or a traffic drop, carries the heaviest weight in the catalog and shapes how urgently the lead should be handled. |
| What platform does your website run on? | Segments the lead so you can route, price, and prioritize it correctly. |
| Do you have access to your website's backend or hosting to make changes? | Without backend or hosting access, recommended fixes can't be implemented, so this answer directly gates whether the project is actionable. |
| Do you have access to Google Search Console or Google Analytics for this site? | Console or Analytics access determines whether you can actually diagnose the problem before the call, not just discuss it in the abstract. |
| Approximately how many pages does your website have? | Segments the lead so you can route, price, and prioritize it correctly. |
| Who would be responsible for approving and implementing recommended changes? | Knowing whether the client, an internal developer, or an outside agency will implement changes affects how fast recommendations can actually move. |
| How soon are you looking to start this project? | Timeline weighting separates leads ready to start immediately from those just exploring options, which changes how a proposal should be prioritized. |
How Cliont scores technical seo leads
Every answer is weighted automatically — no manual review required.
Value signals
- Pages not indexing or crawling properly
- Slow site speed or performance
- Sudden drop in search traffic
- Site migration or redesign issues
- Mobile usability or site structure issues
- Not sure, need an audit
Urgency signals
- Immediately
See the lead your team receives
Technical Intake Lead
From first click to qualified lead
Follow prospects and clients through one smooth, guided flow.
They land & meet you
Your video greeting plays instantly — a real face instead of a blank form.
They explain the project
Smart questions adapt to their project and capture the full scope.
They share the details
The scope and any documents come attached, so you can scope before the first call.
You get a ready lead
Scored and qualified — waiting for you to win it.
Built for technical seo workflows
| Cliont capability | Technical SEO application |
|---|---|
| Platform-aware capture | Uses the platform answer to flag whether a lead needs WordPress, Shopify, Webflow/Squarespace/Wix, or custom-build handling before you scope the work. |
| Access gating | Flags leads who lack backend or hosting access so you know upfront whether a fix can actually be implemented before writing anything. |
| Evidence capture | Collects Search Console or Analytics access details alongside the reported issue, giving you real diagnostic context instead of a vague complaint. |
| Scope sizing | The page-count answer feeds directly into how you size an audit or migration cleanup before the first call. |
| Decision-maker tagging | Flags whether the person on the call can approve and implement changes directly, or whether an outside agency sits between you and the fix. |
Common technical seo lead scenarios
Sudden traffic drop after an update
The client flags a ranking or traffic decline and wants to start immediately, which the intake surfaces as a top-weighted issue paired with an urgent timeline.
Migration launched without review
A redesign or platform move already went live and something broke; the intake captures the platform, page count, and whether an outside agency will actually implement fixes.
Crawl errors stacking up in Search Console
The client has console access and wants specific indexing problems fixed, so the intake routes it as a scoped, evidence-backed request rather than a vague inquiry.
Mobile usability failing checks
Structure or mobile issues are flagged but the client is still exploring options, so the intake captures the detail without treating it as urgent.
Not sure what's broken, wants an audit
The client can't name the issue and needs a full diagnostic; the intake still gathers platform, access, and page count so the audit scope can be estimated before the call.
Connect Cliont to your workflow
Send leads
HubSpot, HighLevel, Salesforce, JobNimbus
Book projects
Google Calendar, Outlook Calendar, Calendly
Notify your team
Email, SMS, Slack
Automate follow-up
Zapier, Webhooks, API
Simple, transparent pricing
Choose the plan that works for your business.
Professional
Unlimited intake forms and leads for your growing business.
- Unlimited intake forms
- Custom video greetings
- AI-powered voice bot
- English + Spanish support
- Automatic lead scoring
- Digital estimates & e-signatures
- Photo, video & file upload
- Advanced analytics dashboard
Pay Per Lead
Only pay when you receive a qualified lead.
- Unlimited intake forms
- Custom video greetings
- AI-powered voice bot
- English + Spanish support
- Automatic lead scoring
- Digital estimates & e-signatures
- Photo, video & file upload
- Charged only for submitted leads
More search engine optimization intake templates
Technical SEO lead-intake FAQs
How does the intake decide which technical issues are worth a strategy call?
It weighs the main issue selected, such as crawling and indexing failures, a traffic drop, or a migration problem, alongside whether the client can act on the fix, so higher-impact, actionable requests surface first.
What happens if the client doesn't have backend or hosting access?
That answer is captured and weighted lower, since without access no fix can actually be implemented, which helps you avoid drafting a proposal for a project that can't move forward.
Does the intake ask what platform the site is built on?
Yes, the platform question (WordPress, Shopify, Webflow/Squarespace/Wix, or custom) is captured up front so you can gauge scope and tooling before the call.
How does site size affect how a lead is handled?
The page-count answer, from under 20 pages up to over 1,000, gives you a rough sense of scope so a large migration cleanup isn't scoped the same as a small brochure site.
Can the intake tell me who will actually implement the fixes?
Yes, the approver question distinguishes between the client handling it directly, an internal developer, an outside agency, or no one determined yet, which changes how fast a project can move.
Is this different from a stand-alone site audit engagement?
The catalog includes a 'not sure, need an audit' option under the main issue question, so audit-only requests still flow through the same intake but are flagged distinctly from a known, specific fix.
Turn technical seo visitors into qualified clients
Give every technical seo visitor a guided intake instead of a dead contact form — and get a scored, qualified lead before you take the first call.