Should Your Page Tell People Who It Is Not For?

Should your page tell people who it is not for?

Yes, on any page where the wrong buyer costs you real time. A short section naming who should not buy raises trust with everyone else, filters out conversations you would have lost anyway, and answers the question a careful reader is already asking silently.

This is the section most teams cut in review. Someone points out that it turns people away, which is technically true and completely misses why it works.

I put one on my own services page and I recommend it on most client sites, but not all of them. Here is when it earns its place and how to write it without sounding smug.

Why does disqualifying people build trust?

Because it proves you have a point of view about fit. A page that claims to suit everyone reads as a page written by someone who has not done the work often enough to notice who it goes badly for. Naming the bad fit is evidence of experience.

It also changes the emotional position of the reader. Most landing pages are trying to persuade, and readers arrive braced for it. A paragraph that risks losing them is the one moment on the page where their guard drops.

The practical effect is that the reader starts checking whether they qualify rather than whether they believe you. That is a much better conversation to be having.

Where should the section go?

After the offer is clear and before the call to action. The reader needs to understand what you do first, or the disqualification is meaningless, and they need to read it before they decide to act, or it has no filtering effect.

On a long services page, that usually means somewhere in the lower middle, next to pricing or scope. On a shorter page it can sit directly above the final call to action as the last thing before the decision.

Do not hide it in a frequently asked questions block at the bottom. A disqualification that only the most diligent reader finds is a disqualification that does no work.

How long should it be?

Three or four short statements, no more, and each one should fit on a single line. Name a situation rather than a personality, and make each statement specific enough that a real person reading it would recognise themselves immediately and stop reading without resentment.

Length is the tell for whether you have thought about it. A long list reads as defensive, as though you have been burned repeatedly and are now writing terms and conditions in public.

The wording pattern that works is a plain conditional. If this is your situation, you will be better served by something else. No judgement, no irony, just a fact about fit.

What should you actually name?

The situations where your work reliably disappoints, described plainly. Budget ranges you cannot serve well, timelines you cannot meet without cutting corners, problems that genuinely need a different specialism, and working styles that do not match how you deliver. Four honest lines are usually enough.

For my own practice the honest version is direct. I price fixed fee, with most projects between one thousand and ten thousand dollars, so if you need someone for an hour a week on an open ended basis, that is not the shape of what I do.

Say the one people expect you to hide. Naming your own limitation costs you very little and buys disproportionate credibility, which is the same reason writing a service page around outcomes rather than features reads as more honest than a feature list.

What should you never put in it?

Anything that insults the reader. Statements along the lines of this is not for people who are not serious about growth are not disqualification at all, they are a dare, and they make the writer look defensive rather than experienced. That line has been used so often it now reads as a warning about the seller.

Also avoid using it to smuggle in a boast. If the section is a list of demanding requirements designed to signal exclusivity, readers notice, and it reads as marketing rather than honesty.

The test is whether the person you are excluding would feel respected reading it. If they would feel mocked, rewrite it.

How does this help with AI answer engines?

It gives an engine an explicit statement about fit that it can quote. When a system summarises what you do, a clear sentence about who your work suits is far more useful to it than a page of adjectives, and far more likely to be reproduced accurately.

It also reduces one of the ways engines misrepresent businesses. If your page never states a boundary, a summary will extrapolate one, and the extrapolation may be worse than the truth.

Write it as a complete, self contained statement for that reason. A section that only makes sense in the context of the three paragraphs above it will not survive being quoted on its own, which is the same principle behind designing a page for visitors who arrive from an AI answer.

What does it look like visually?

Quiet. This is not a section that needs a coloured background, an icon set, or a heavy border. Setting it apart with weight or colour signals a warning, when what you want is the tone of a straight answer from someone who knows their trade.

What I usually do is keep the same body text style, with a clear heading and slightly more space around the block. The visual message should be that this is part of the explanation, not a disclaimer.

Resist the urge to use a cross or a red colour. You are describing fit, not failure, and the design should not imply that the excluded reader has done something wrong. The same restraint applies to the heading: a plain question works better than a clever label, because a reader scanning the page should be able to tell in one glance what the section is for.

When should you leave it out?

On a product page for something with a low price and a broad audience, where almost anyone can use it and a wrong purchase costs the buyer very little. There, disqualification introduces doubt where none was needed.

Also leave it out if you cannot name the bad fit specifically. A vague section written because someone read that it works is worse than nothing, because it adds words and removes clarity.

And if your problem is too few enquiries rather than too many wrong ones, fix that first. Filtering an empty pipeline is a way of feeling productive without changing anything.

What should you do next?

Write down the last three enquiries you wished had not arrived, and find the one thing they had in common. That sentence is your disqualification section, and it usually already exists in something you have said out loud to a colleague.

Put it on the page above your call to action, in plain body text, in three or four short statements. Then watch the enquiries you get for a month, not the number but the quality of them.

If you want a second opinion on where the boundary should sit for your business, reach out. It is one of the fastest improvements I know of on a services page. Let's chat.