What to Look For in a Website Before You Pay for It

Buying a website is uncomfortable because you cannot evaluate the product. You can tell whether a fence is straight. You cannot tell whether a website is well built by looking at it, and the difference between a good $3,500 site and a bad one is invisible until something goes wrong eighteen months later.

These are the questions that surface the difference before you pay.

The judging problem

Two quotes for the same money can be wildly different products: one you own outright, one you rent forever. One that loads in a second, one that takes six. One you can hand to any developer, one that only works inside a proprietary platform. Nothing on the surface tells you which is which — you have to ask.

Ask who owns it

"When this is finished and paid for, what exactly do I own, and what happens if I want to move it somewhere else?"

You want: the files, the code, the content, and every account in your name. What you do not want is finding out that the site lives on the builder's platform, and leaving means starting over. Ask specifically whether the domain will be registered in your name — this is where people get trapped, because a builder holding your domain holds your business.

Ask what it costs to keep

"What will I be paying monthly a year from now, and to whom?"

There are legitimate ongoing costs: a domain runs $12–20 a year, and hosting is anywhere from free to $15 a month for a small business site. What deserves scrutiny is a monthly fee to the builder with no defined deliverable. Sometimes that is a fair maintenance arrangement. Sometimes it is rent on your own website. Ask which, and ask what happens if you stop paying — the answer tells you everything.

Ask how fast it will be

"What will this score on PageSpeed Insights on a phone, and will you show me after launch?"

A builder who cares will have an answer. Speed is measurable, it affects rankings, and it affects whether visitors on patchy rural signal ever see your page. Sites built on heavy page-builder platforms with a dozen plugins are slow almost by construction, and no amount of design covers it.

Ask how it gets found

"What is included for search — and what is not?"

At minimum a real build should include proper page titles and descriptions, structured data, a sitemap, sensible URLs, and pages that match how people actually search. Google Business Profile setup should be in there or clearly quoted separately. See the local SEO checklist for what "the basics" should actually cover.

Be suspicious of anyone guaranteeing rankings. Nobody can, and offering to is a reliable signal about everything else in the quote.

Ask what happens when you need a change

"In six months I want to add a service and change a price. What does that cost and how long does it take?"

Fine answers: you can do it yourself, here is how; or, it is a small hourly job, usually same week. Concerning answers: a mandatory retainer, or a two-week turnaround for a price change, or a system so complex only they can touch it.

Answers that should end the conversation

• "You do not need to worry about the technical side." Translation: you will not own it.
• "We guarantee page one." Nobody can.
• "The domain is easier if we hold it." Easier for them.
• "It is a monthly plan, the site is included." Sometimes legitimate — but understand you are renting, and find out what remains yours if you leave.
• A quote with no written scope. If nobody will write down what is included, nothing is.

None of this requires technical knowledge. It requires asking six questions and listening to whether the answers are specific. A builder doing good work will enjoy the questions. One who does not want to answer has told you something useful.