The call that comes three months after you deliver

The client loved the site. It looked better than anything they had, and it arrived in a week. Then the phone did not ring, and now they want to know why, and they are asking you.

Run the free check

A client who commissioned a website assumes being findable was part of it, whether or not the contract said so. The way to prevent the conversation is to separate the two deliverables explicitly before work starts: the site, and the work of making it findable, which is ongoing and which somebody has to own. Delivering a technically sound site and saying so in writing protects you when the second conversation arrives.

Why the conversation happens

There is a gap between what you sold and what the client believes they bought, and it is almost never dishonest on either side.

You sold a website. Design, build, deploy, working. That is what you quoted for and it is what you delivered.

The client bought, in their mind, a way for customers to find them. The website is the thing they can see, so it is the thing they paid for, and being found is the outcome they expected it to produce.

Neither of you said anything wrong. The gap sits in what went unstated, and it surfaces around three months later when nothing has happened.

Separating it before you start

The fix is a five-minute conversation at the beginning, and it is worth having even when it makes the sale slightly harder.

Say plainly that there are two different jobs. Building the site is one, and it is finite, and it is what you are quoting for. Making it findable is the other, it is partly technical and mostly ongoing content work, and somebody has to own it.

Then ask who is going to own the second one. Sometimes the answer is you, at additional cost. Sometimes the client will do it themselves. Sometimes nobody will, and the important thing is that this was said out loud rather than assumed.

Clients respond well to this conversation, because it is the first time anybody has explained why their previous site did nothing.

What you should include regardless

There is a baseline that should be part of any site you hand over, whether or not anybody is paying for ongoing work, because delivering a site without it is delivering something that cannot succeed.

  • Real HTML for crawlers, verified on a deep route rather than the homepage.
  • The client's own domain, connected properly, with one canonical version and the other redirecting.
  • A different title and description on every page, written as answers rather than as slogans.
  • A sitemap, generated rather than hand-written if the pages come from data, and submitted in Search Console.
  • A robots.txt that blocks nobody you want, including the AI search crawlers.
  • Search Console verified and handed over in an account the client owns, not yours.
  • A working social preview image, so shared links do not render as bare URLs.

Hand over the accounts

This one is worth its own section because getting it wrong causes disputes months later.

Every account should be created in the client's name, owned by the client, with you added as a user. The domain registration, the hosting, Search Console, analytics, every directory listing.

It is faster to create everything under your own accounts and it creates a relationship where the client cannot leave without losing things, which is a poor foundation and produces bad endings.

It also protects you. A client who owns their own domain and analytics cannot later claim you are holding their business hostage, and that accusation is unpleasant even when it is unfounded.

Answering the call when it comes

If the conversation happens anyway, and it will sometimes, the answer that works is specific rather than defensive.

Do not explain that SEO was not in scope, even if it is true, because it sounds like an excuse regardless of its accuracy. Start with what the site actually does have, which is why the baseline above matters: you can show that the technical foundation is correct and verifiable.

Then explain the real constraint in plain terms. The site has, let us say, five pages, all of which describe the business. There are five things it can be found for. The customers they want are searching for their problem, in their own words, and each of those questions is a page nobody has written.

That reframes the conversation from a complaint about your work into a discussion about what to do next, which is a conversation you can be paid for.

The opportunity in this

There is a straightforward commercial point here, offered plainly.

Building sites with AI tools is fast, which is excellent for you and also means the price of a site is under pressure, because the thing you are selling got easier for everybody.

The work of making a site findable did not get easier. It is ongoing, it compounds, and it is the part clients actually want, since being found is the outcome they were buying all along.

So the shift worth considering is from selling a one-off build to selling the build plus ownership of the outcome. It is better work, it is recurring, and it is considerably harder for the next person with an AI builder to undercut.

Part of a larger guide

This page is one part of Vibe coding SEO. The other parts:

Questions people ask

My client says their new site is not on Google. What do I tell them?
Start with what the site does have technically rather than explaining that SEO was out of scope, which sounds like an excuse regardless of accuracy. Then explain the real constraint plainly: a five-page site describing the business can be found for five things, and their customers are searching for their problem in their own words.
How do I avoid this conversation entirely?
Separate the two deliverables in a five-minute conversation before work starts. Building the site is finite and is what you are quoting for. Making it findable is partly technical and mostly ongoing content work, and somebody has to own it. Ask who, and get the answer said out loud.
What should I always include in a client site?
Real HTML verified on a deep route, the client's own domain with one canonical version, unique titles and descriptions per page, a submitted sitemap, a robots.txt that blocks nobody you want, Search Console verified in the client's own account, and a working social preview image.
Should accounts be in my name or the client's?
The client's, with you added as a user, for every account including the domain, hosting, Search Console and analytics. Creating them under your own accounts is faster and builds a relationship the client cannot leave cleanly, which produces bad endings and exposes you to accusations you would rather not face.
Is it dishonest to deliver a site without SEO?
Not if it was scoped that way and said out loud. What is not defensible is delivering a site that cannot succeed technically, such as one serving empty HTML or blocking crawlers, since that is a build quality issue rather than a scope issue.
How should this change what I sell?
Building sites got faster for everybody, which puts the price of a build under pressure. The work of making a site findable did not get easier, it compounds, and it is the outcome clients were buying all along. Selling the build plus ownership of that outcome is harder to undercut.

Check a client site before you hand it over

Run the free Get Found Check on any site you are about to deliver. It takes a minute and it is the difference between a confident handover and a call in three months.

Run the free check Talk to Licheo about partnering