Targeting by Design: Problem, Industry, and Job-Title Pages

A homepage written for everyone convinces no one. Visitors arrive with a problem, from an industry, in a job. When the page names none of those, they leave. The ones who stay often fill out a form you should not have accepted.

Targeting by design means the site is a set of pages, and each page is built for one buyer. That page draws the buyer in and lets everyone else see they are in the wrong place.

A Broad Page Wastes the Visit

Brand, process, and creative choices still tell a visitor whether you are their kind of company. A transparent price, a workshop before any visuals, or a point of view in the design will turn some people away. That filter only works when the page was written for someone specific. A bold brand wrapped around a generic story still attracts the wrong form fill.

Replace the single catch-all page with three kinds of pages: one for the problem, one for the industry, and one for the job title. Then give each of those pages its own way to convert.

Short Queries Became Full Requests

For years, a buyer typed two or three words into Google. A page could win that visit by repeating the phrase. That short search still happens. It is no longer the hardest request you have to answer.

The same buyer now gives a frontier artificial intelligence (AI) model the whole situation: the problem, the industry, the job, and the constraint. An artificial intelligence overview (AIO) answers that kind of request at the top of search results. A generic homepage cannot satisfy a request that specific. A page written for one problem, one industry, or one job title can, because the request already named the buyer.

Target by the Problem

Write a page for each problem your best buyers are trying to solve. Use their words, not your category name. Show what the problem costs if it stays in place, how you approach it, and proof from a customer who had it. A visitor searching for that problem should recognize themselves in the first screen.

This is search engine optimization (SEO) aimed at a problem, not at a slogan. Look in Google Search Console for the phrases people already use to find you. If a phrase describes a problem you solve, it deserves its own page. If you cannot explain the problem without leaning on your product name, the page is not ready. Write the page so it still makes sense when the question arrives as a paragraph, not only as two words.

Target by the Industry

Publish an industry page only when you can speak that industry’s language and show a result from it. Name the buying cycle, the constraint that industry lives with, and a customer in it. A manufacturer should not have to translate a page written for a hospital.

This matters most in business-to-business (B2B) sales, where a generic page reads as inexperience. If you do not have proof in that industry, do not publish the page. A thin industry page teaches the right buyer that you are guessing.

Target by the Job Title

The person who pays, the person who uses the work, and the person who can block the purchase do not want the same page. A finance lead wants cost and risk. An operator wants the workflow. A technical reviewer wants how it fits what they already run. Write the page to the title, and say who it is not for.

The user experience (UX) should feel like that job’s day. The examples, the objections, and the next step belong to that title. A page that tries to satisfy every title satisfies the one who was never going to buy.

A Diagram Has to Do the Work

Words are not enough on these pages. A diagram, a simple chart, or a before-and-after shows the problem and the fix in one glance. Draw the industry’s workflow. Draw the decision that job title has to make. Caption the figure in that buyer’s words, and write the alt text to match the caption.

Imagery matters more when the request is long. A frontier model and an AIO summary have to explain a specific situation. A labeled diagram gives that answer a concrete figure to describe, and it gives the reader something to trust. Stock art that could sit on any company’s page does neither. The image should be as targeted as the headline.

Build Confidence, Then Invite the Conversation

One caution: do not try to illustrate the entire solution on a single page. A fully comprehensive list of product features can disqualify the visitor. They look for the one capability they already have in mind, do not see it named, and leave believing you cannot help.

The page has a smaller job. Build confidence that you understand the problem and can solve it, then have the person engage. The diagram, the proof, and the offer should open that conversation. Save the full feature list for the conversation, where you can ask what they need instead of letting a checklist answer for them.

Give Every Page a Way to Convert

A targeted page without a conversion is a brochure. Each problem page, industry page, and job-title page needs its own next step: a form, a short call, a checklist, or a meeting. Do not send all of them to one generic demo form. The call to action (CTA) should name the outcome that page promised.

Segment the offer. The headline should name the ideal customer profile (ICP) for that page. The promise should be the unique value proposition (UVP) that this buyer cares about, not the slogan you use for everyone else. A finance page offers a cost case. An operator page offers a walkthrough of the workflow. An industry page offers proof from that industry.

Pass the page’s segment into your customer relationship management (CRM). A field for the problem, the industry, and the job title keeps that context after the form is submitted. HubSpot and Salesforce can both store the field with the lead, so the follow-up matches the page the visitor actually read.