Digital presence
Why a business website still matters in the age of AI search
'Most of our work comes through referrals. Do we really need a website?' It's a fair question for a service business. But consider what happens after someone forwards your name: the recipient still needs to check what you do, see a relevant project and find a way to contact you. Your website can handle that part of the introduction.
The visitor may already know your name
A founder may send your proposal to an operations colleague who wasn't on the call. A procurement team may look up the company before a meeting. Neither visit begins with a generic search for a supplier, but both can affect whether the enquiry moves forward.
Give those readers something they can check without asking you to repeat the pitch. What did your team contribute to the project? Which part resembles their problem? Who should they speak to? Answers scattered across old social posts and private decks are hard to pass around a buying team.
Give each important question a stable home
Start with three pages you can keep accurate: a service page that explains the work, a case study that shows your contribution, and a contact page that reaches a person. A small site with those answers can do more for a buyer than a large one filled with claims about innovation.
Rubix Labs uses separate service pages, portfolio case studies and planning resources for this reason. The LuckyTruck case study has room to explain integrations and document work, while an engagement page explains how scope and quoting are agreed. A reader can follow the part relevant to their decision without decoding a broad claim about innovation.
Make the evidence accessible to search
Google's SEO guidance emphasizes understandable content, useful titles and links that help readers and crawlers find related pages. Its guidance for AI features says the usual SEO foundations still apply; there is no special requirement that guarantees inclusion in AI Overviews or AI Mode.
Publish important information as readable page content, use descriptive headings and connect related pages with ordinary links. Keep the sitemap current and the canonical URL consistent. Structured data should describe what the visitor can actually see. An llms.txt index can provide another convenient reference, but it is not a ranking switch.
Then check what actually happens. Can the search engine retrieve the page? Has it indexed it? Does the page appear for a relevant query? These are separate questions. Publishing an accessible page gets the process started; it doesn't establish that anyone will find or recommend it.
Review the site as a prospective customer
Open it on a phone and follow a realistic journey. Find the service, inspect the supporting work and try the contact route. Check whether a colleague can understand the same pages without the explanation you would give on a call. Pay attention to missing context as well as broken links.
Then connect the review to business evidence. Which search queries bring people in? Which pages lead to relevant enquiries? What do prospects still ask because the site did not answer it? Small traffic numbers call for patience and careful reading, not elaborate conclusions from a handful of visits.
The next time you send a referral or proposal, include the page that answers the buyer's most likely question. If you can't find one, that's a good candidate for the next thing to publish.
Let social channels lead somewhere useful
Social profiles help people encounter your work and stay in touch. Give an interested reader a durable page to visit next: the actual project, the relevant service or the article behind a short post. A homepage is not always the best destination.
Think about the person forwarding the link. They should be able to write, 'This is the project I mentioned,' and know the next reader will find it. Keep that page accurate after the campaign ends, and redirect its old URL if you move it.