Your website can generate plenty of inquiries and still waste your team’s time.
The usual problem isn’t a weak contact form. It’s that the site never says, in plain English, who the company is built to serve. Buyers have to guess whether you cover their area, handle their type of job, work at their budget, or support their industry. Some leave. Others submit a form and let your salesperson sort it out.
That information gap matters even more as people use AI tools to build shortlists. In Yext’s 2026 survey of 3,848 consumers, 42.7% said they had used an AI tool for local search in the previous month, and 28% had tried a new local business because of an AI recommendation. Yet only 5% went straight from an AI answer to a purchase. Most verified the recommendation through search, the company’s website, citations, reviews, or social media.
A focused “Who We Help” page can do two jobs at once: help a prospect decide whether to contact you and publish specific facts that search systems can retrieve. It isn’t a substitute for service pages, location pages, or sales conversations. It’s the filter that connects them.
Why general website copy produces poor-fit leads
Many small-business homepages rely on phrases like “solutions for businesses of all sizes” or “serving a wide range of clients.” They sound safe because they don’t exclude anyone. They also tell a serious buyer almost nothing.
Imagine a commercial HVAC contractor whose best projects are replacements and maintenance agreements for buildings between 20,000 and 150,000 square feet within a 45-mile radius. “Quality commercial HVAC services” hides nearly every useful buying fact. A facilities manager can’t tell whether the contractor handles a six-building portfolio. A restaurant owner can’t tell whether a one-unit repair is too small. Both may call.
AI search makes vague positioning harder to defend. Google’s 2026 guide explains that its generative search features use retrieval-augmented generation and query fan-out to retrieve pages for an original question and related subquestions. A prompt such as “Which HVAC company near Dayton handles preventive maintenance for a 60,000-square-foot warehouse?” contains several conditions. A page that clearly addresses building type, service, size, and geography gives the system relevant text to retrieve. A generic claim does not.
Google does not promise that adding those details will earn an AI citation or a ranking. Its official guidance says there are no extra technical requirements for AI Overviews or AI Mode, and the same core SEO practices still apply. The business case is simpler: useful facts help humans make decisions, and they also make the page easier for machines to interpret.
What belongs on a “Who We Help” page
The page should answer the questions your team uses to accept, route, or decline an opportunity. Start with the criteria that actually change what happens next.
1. Customer types
Name the customer categories you understand. A bookkeeping firm might serve multi-location restaurants, medical practices, and contractors. A machine shop might focus on OEM engineering teams that need prototypes and short production runs. A managed service provider might work with organizations that have 25 to 250 employees and no full-time internal IT department.
Don’t stop at industry labels. Add the operating situation that makes your service valuable. “We help dental groups with three or more locations standardize IT support and security” is more useful than “We serve healthcare.” The first version lets a buyer recognize a match.
2. Problems and trigger events
Describe the moment when a good client usually calls. Examples include opening a second location, replacing an unsupported system, missing response-time targets, preparing for an audit, or outgrowing a do-it-yourself process.
This content should come from real sales and service conversations. Google specifically recommends creating non-commodity content based on first-hand expertise, rather than publishing summaries that could have come from any company. Your team’s pattern recognition is an asset. Put it on the page.
3. Service area and delivery limits
State where you work and what geography means in practice. “Serving Central Ohio” may not be enough. List the counties, cities, drive-time radius, or states that define your territory. Explain whether remote work is available and whether on-site work costs more outside the core area.
Keep the same facts current in your Google Business Profile. Google’s AI-features documentation specifically advises site owners to keep Business Profile information up to date, and Google’s profile guidelines require service-area businesses to use one profile for the central office or location and define their service area accurately. Your website and profile shouldn’t give two different answers.
4. Project size, budget, or minimum engagement
You don’t always need a fixed price. You do need enough context to prevent a $500 buyer from requesting a $15,000 service.
Use the qualification measure your company actually uses: starting price, typical range, minimum order, annual spend, square footage, seat count, production volume, or project duration. If the number varies, explain the variables. For example: “Most website redesigns fall between $8,000 and $25,000. Page count, custom integrations, and copywriting are the main cost drivers.”
Some owners worry that a minimum will drive leads away. It will. That’s the point when those leads could never buy. A clear range also gives qualified prospects a reason to continue instead of assuming your service is outside their budget.
5. Poor-fit situations
An honest “We’re probably not the right fit if…” section saves time and builds credibility. Keep it factual, not dismissive. A contractor could say it doesn’t handle residential emergency calls. An agency could say it doesn’t take commission-only projects. A manufacturer could explain that it isn’t set up for one-off consumer parts.
Give people a useful next step where possible. Refer residential callers to a partner, link tiny orders to a distributor, or suggest a software product for teams that aren’t ready for managed service. A firm boundary feels more helpful when it points the visitor somewhere useful.
A page structure you can hand to your web team
You don’t need an elaborate design. A useful page can follow this order:
- Opening statement: Name the primary customer and result in one or two sentences.
- Best-fit criteria: Cover customer type, situation, geography, and engagement size.
- Problems you solve: Show four to six recognizable trigger events.
- Examples: Include two or three short client scenarios with concrete details.
- Not a fit: State the requests you don’t handle and provide alternatives when available.
- What happens next: Explain the first call, expected response time, and information a prospect should bring.
- Call to action: Send qualified visitors to the appropriate form or scheduling page.
Use headings that carry meaning. “Who this is for” is better than “Solutions.” “Projects starting at $10,000” is better than “Flexible options.” Google advises making important content available in textual form and easy to find through internal links, so don’t bury eligibility rules in a graphic, video, accordion that fails to render, or downloadable PDF.
Link the page from your main navigation when customer fit is central to the sale. Otherwise, link it from each relevant service page, the About page, pricing content, and the contact form. The goal is to place it wherever a prospect starts asking, “Is this company for someone like me?”
Use examples without exposing private client information
Specific examples make the criteria believable. You can write them without naming a client or revealing sensitive results.
Consider these formats:
- “A 42-person law firm moving offices and replacing its network before the move date.”
- “A regional food manufacturer that needs 300 stainless assemblies per quarter, with material certificates.”
- “A home-services company spending $12,000 per month on ads but unable to trace booked jobs back to campaigns.”
Each example combines identity, scale, event, and need. That is much stronger than a logo wall. If you have permission and measurable results, link to a full case study. If you don’t, label the examples as representative situations and avoid inventing performance numbers.
High-quality original photos or video can reinforce the text. Google’s current guidance says relevant visual assets can create additional opportunities to appear in generative search. For a contractor, show the type of jobsite. For a manufacturer, show the equipment and finished tolerances. For a professional service firm, a short expert video can explain the point where clients usually need help. Always keep the qualifying facts in HTML text too.
Add structured data, but don’t expect special AI markup
Once the visible page is accurate, use normal structured data where it fits. Google’s LocalBusiness documentation supports properties such as business type, address, hours, phone number, price range, and service information. The markup must match what a visitor can see.
Don’t invent a special “AI schema” layer. Google’s 2026 guide says structured data isn’t required for generative AI search and no special schema is needed. Standard Organization, LocalBusiness, Service, Product, or other supported markup can help search engines understand a page, but it cannot repair vague or contradictory copy.
The order of work matters. Fix the visible facts first. Check that service names, areas, hours, contact details, and price statements agree across the website and profiles. Then add or update markup. Test it with Google’s Rich Results Test and inspect the live URL in Search Console.
Connect qualification to the contact form
The page should change the handoff, not just explain it. Carry its criteria into the form with a few fields that help route the inquiry. Ask for the project location, service needed, timing, and the one scale measure that matters most. That might be employee count, square footage, monthly ad spend, order quantity, or expected budget.
Keep the questions proportional to the sale. A six-figure industrial project can justify a longer intake form than a $150 service call. Explain why you’re asking, and don’t request information your team won’t use.
Send the form submission into a simple routing rule. Good-fit leads should reach the right person quickly. Borderline leads may need a short screening call. Clear non-fits can receive a polite response with an alternative. The website has then done real operational work instead of merely collecting names.
Measure whether the page improves lead quality
Traffic isn’t the primary score. Track what happens to inquiries after they read the page.
Record a four-week baseline before publishing, then compare it with the next four to eight weeks. Watch qualified inquiry rate, sales-accepted lead rate, calls spent on obvious non-fits, form completion rate, and close rate. Segment visitors who viewed the “Who We Help” page before converting. A lower raw inquiry count can still be a win if the sales team receives more viable opportunities.
Also listen for language from the page in calls. When prospects say, “We have five locations, so it sounds like we’re in your range,” the content is doing its job. When the same disqualifying question keeps appearing, add the answer.
Yext’s study found that after an AI recommendation, 49% of users visited the business’s website and 42% clicked a cited source. Your page should be ready for that verification step. The visitor doesn’t need more slogans. They need enough evidence to decide whether the recommendation fits.
Make the decision easier
A useful “Who We Help” page is a sales filter built from facts your company already knows. Publish the customers you serve, the problems you handle, the territory you cover, the engagement size that works, and the situations you decline. Add real examples. Keep every channel consistent. Measure lead quality after launch.
If your website attracts traffic but leaves your team sorting through the wrong inquiries, talk with Your Web Team. We’ll help you turn the site’s positioning, service pages, and conversion path into a clearer qualification system.
