What BERT meant for writing useful service pages
A practical way to turn customer questions into service pages that explain the right problem, scope, and next step.
In October 2019, Google announced that it was using BERT to better understand language in searches. For a small business owner, the useful takeaway was not that every page needed a new technical trick. It was an opportunity to examine whether the website actually answered the questions people were asking. A page could repeat the name of a service many times and still leave a potential customer unsure whether that service fit their situation.
Consider a Sarasota business looking for a website redesign. The owner might search for help with a slow website, a site that is difficult to update, or a brand that looks inconsistent online. Those searches describe different problems. Sending all three visitors to a page that simply promises beautiful websites leaves important work undone. The page needs to explain the problems the service addresses and the decisions the customer will make.
Start with conversations, not a keyword quota
Collect questions from proposal calls, contact forms, and customer emails. Remove personal information, then group the questions by the decision behind them. Questions about price usually concern scope and risk. Questions about timing often concern an upcoming event. Questions about software may actually concern who will maintain the finished site. These distinctions help a writer choose useful sections rather than merely adding more variations of a phrase.
Create one page for a coherent service, not a separate page for every wording of the same request. A redesign page might explain discovery, content preparation, design approval, development, and launch. A maintenance page should address a different ongoing need. When the two services overlap, connect them with a descriptive link. The visitor should understand why following that link would help, without having to guess from a generic button.
Give the answer before the sales pitch
The beginning of the page should identify who the service is for and what it helps them accomplish. Follow with concrete scope. If content writing is optional, say so. If an existing store requires a separate migration assessment, explain that early. Clear boundaries do not weaken a sales message. They help a prospective client recognize the right fit and prepare a more useful inquiry.
Use examples carefully. An illustrative example of a five-page professional services website can show how information might be organized. It should not become an invented client success story. Real project evidence is stronger when the page explains the original problem, the work performed, and any documented result. A polished image alone cannot answer questions about process, responsibility, or business relevance.
Review the page as a customer would
Ask someone unfamiliar with the business to read the page and explain what they would receive. Then ask what they would need to provide and what happens after contacting the company. If the answers are vague, revise the missing information before spending time on subtle headline variations. The purpose of the exercise is understanding, not approval of the writing style.
After publication, review the search queries that lead to the page alongside the inquiries it produces. A relevant phrase with few visits may still lead to worthwhile conversations. A broad phrase that brings many visitors may not match the service at all. Treat those observations as clues about expectations. Better service content grows from resolving specific uncertainty, not from reaching a prescribed keyword density or promising an automatic ranking improvement.
Sources & further reading
Linked documentation may reflect updates made after the historical period discussed.
Explore Commit’s approach to strategy, design, and development.
Explore our services ↗