The explainer
What AI needs from a website.
An assistant answering a question about your profession is doing three things: finding pages, working out which business each page describes, and quoting that business without inventing anything. Each of those is a technical requirement, and each one is met or missed on the page itself. Below is what is needed, and what every ProfessionalFolio page does about it.
01
What AI needs
A name, a place and a trade it can resolve
Asked for “someone who handles commercial leases in Melbourne”, an assistant has to match a business name, a discipline and a city. If those words are not on the page as text, there is nothing to match against.
How the page provides it
The headline, tagline and city sit in the first screen as plain text, and the same three facts are written into the page's structured data. Nothing important lives only in an image.
02
What AI needs
Facts in a machine-readable format
Readable prose is not enough. Search engines and assistants look for structured data that names the business type, the services offered, the contact details and the location.
How the page provides it
Every published page carries a JSON-LD graph: the practice as a ProfessionalService, LegalService or the matching type, the principal as a Person, each service as an offer, and the questions as a FAQ page.
03
What AI needs
One clean record of those facts
Given the choice between parsing a designed page and reading one tidy record, an assistant takes the record: fewer tokens, less guesswork, nothing to misread.
How the page provides it
Each page also publishes an AI-readable profile: services, credentials, contact details and questions as one JSON file, linked from the page head and from the AI-ready badge on the page itself.
04
What AI needs
Answers written to be quoted whole
Assistants lift a complete answer, not a fragment. A question answered in one sentence and qualified three paragraphs later gets misquoted, or dropped.
How the page provides it
Each question is written as a self-contained answer and published twice: visible on the page for people, and as FAQ data alongside it for machines. The two never disagree.
05
What AI needs
Proof it can cite
A recommendation needs something checkable behind it: admitted where, registered with whom, practising since when, and what clients actually said.
How the page provides it
Credentials are stored as label and value pairs and testimonials as attributed quotes. Both appear on the page and are written into the structured data as facts, not adjectives.
06
What AI needs
Something recent to read
A page that has not changed in three years reads as dormant. Crawlers revisit, and assistants prefer a site that keeps answering new questions.
How the page provides it
One article a month is published to the site's journal with Article structured data, written to answer the questions clients actually ask, not to fill a calendar.
One page, not five
One page is enough, if it carries everything.
A five-page brochure site spreads the same facts across several addresses. A visitor arrives with one question and has to hunt for the answer, and an assistant has to guess which of your pages is the one that describes the business. One page, complete, is easier for both of them.
Everything a client would ask on a first call belongs on that single page: who you are, what you do, where, what it costs to start, proof you can do it, and how to reach you. Anything that is missing becomes a question they ask someone else.
What the one page has to carry
- The practice name, discipline and city, as plain text
- Every service, written in the words clients actually search
- Credentials as label and value: admitted where, registered with whom
- Testimonials, attributed, never invented
- The questions clients ask, each answered whole
- Phone, email and address, matching everywhere else online
New articles go to the journal, which is what keeps the page current without splitting the facts that describe you.
Speed and screen size
Built for people and for agents alike.
A page can be well written and still lose the reader, or the crawler, before the first line appears.
01
Load speed
Visitors leave a page that takes more than a few seconds, and a slow page is read less often by crawlers too. There are no page builders, sliders or heavyweight plugins carrying the page: it is one lean document, with images sized for the screen they land on.
02
Small screens
More than half of the people who read your page arrive on a phone. The same facts sit in the same order at every width, with nothing cut, hidden behind a tap, or shrunk until it cannot be read.
03
For people and for agents
The one page is built twice over for the same content: quick and clear for a person deciding whether to call you, and plain, structured and complete for the assistant answering their question afterwards. Neither version is an afterthought.
An honest promise
We help you be found. We do not promise to be chosen.
No one can promise an assistant will recommend you, and we would rather say that plainly than oversell it. What we can promise is the input: clear, consistent facts an assistant can read and check with confidence. Assistants also differ from one another, so one may read your page well while another has not visited it yet.
Kept simple on purpose
- Only facts you have confirmed. We never add credentials, awards, years of service or client results on your behalf, so an assistant is never left describing you wrongly.
- No short cuts. We skip fake review markup, hidden keywords and borrowed testimonials — the things that quietly cost a domain the trust it needs to be quoted.
- Everything written as text. If a detail only exists inside an image or a document, we say it in words on the page, so it can actually be found and read.
The quickest way to see it is to open a sample page and take the tour: every section explains what it gives an assistant, as you look at it.