CAMBRIDGE / SEARCH + AI VISIBILITY / ND MEDIA LTD, CO. 10784524
What a Cambridge Spinout Should Build First for Search and AI
A new Cambridge spinout has no entity yet, only a technology and a company number. Four pages establish that entity: a homepage with a plain capability sentence, a technology page, a team page, and a contact page carrying the registered address. Everything else is safe to defer until those four are accurate and indexed.
4
FIXEDpages that establish a spinout as a resolvable entity, before anything else is written.
Why does a spinout start from zero rather than from behind?
A spinout out of a Cambridge Enterprise licensing process usually arrives with a strong reputation and no public record of its own. The science is documented under the university's name. The company itself has a placeholder domain, a LinkedIn page, and very little a crawler or an assistant can read.
That position is better than it sounds. No legacy content needs correcting and no historic description needs unpicking. The first properly written page is therefore the definitive one. The risk is leaving the placeholder in place for a year while the fundraising runs.
Timing matters more than polish at this stage. A domain that has carried four accurate pages for six months is easier for an engine to trust than a beautiful site published the week before a funding announcement. Publish early, then improve the pages as the company learns what its buyers ask.
1.Cambridge Enterprise is the University of Cambridge's commercialisation arm, handling licensing, spinout formation, and early investment for university-derived technology.
Which four pages carry the load?
-
A homepage with one plain sentence
The first sentence states what the company makes or does, in the words a buyer or an investor uses. The technical detail follows immediately underneath. This sentence is what both a search engine and an assistant lift when they summarise you.
-
A technology page written for two readers
An expert needs the mechanism, the data, and the boundaries of the claim. A generalist needs to know what problem it solves. Write the second at the top and the first below it, on the same page.
-
A team page with real names and histories
Founder names, prior institutions, and roles give a model something to corroborate against public records. It is also the page investors read first. Publishing it accurately costs nothing.
-
A contact page with the full registered address
Registered office, company number, and a working email. This page resolves the identity questions everything else depends on.
How should the university relationship be described?
State it factually and once. Name the technology licensed, the department or institute it originated in, and the year the company was formed. A short, accurate paragraph does more good than a page of association language.
Vagueness here is expensive. A company that describes itself only as Cambridge-affiliated invites the exact confusion that costs it citations later. A model reading that phrase cannot tell whether the entity is the university, a department, or an independent business. Precision is the cheapest disambiguation available.
Respect the boundaries as well. Publish what the licensing agreement and any confidentiality terms permit. Check anything uncertain with the technology transfer office before it goes live.
| Stage | What exists | What to build next |
|---|---|---|
| Formation | Company number, licensed technology | Domain, four core pages, Organization schema |
| First hires | Team taking shape | Team page detail, a careers page naming the Cambridge base |
| First customers or pilots | An applied use of the technology | A capability page in buyer language, plus a citation baseline |
| Seed round | Public funding coverage | Consistency pass across site, LinkedIn, and Companies House |
| Scale-up | Repeatable sales conversations | One technical reference page per recurring buyer question |
What belongs in the markup at launch?
Organization schema is the priority, carrying the legal name, the trading name, the company number, the registered address, and the profiles you control. Those fields are what an engine cross-checks against Companies House and LinkedIn. Agreement between the three is the point of the exercise.
Keep the robots file permissive from day one. GPTBot, PerplexityBot, ClaudeBot, and Google-Extended all need access. A default template that blocks them is a silent and completely avoidable loss.
Submit a sitemap at launch and check indexation coverage a fortnight afterwards. A new domain is exactly when an indexation fault is cheapest to find.
What is safe to defer?
Defer the blog. A publishing schedule nobody has capacity for is worse than no blog at all. An abandoned news section dated eighteen months ago reads as a dormant company.
Defer case studies and testimonials until there is real permission and a real result to describe. Inventing either is the fastest way to lose a technical buyer.
Defer gated content entirely at this stage. Material behind a form is invisible to every engine. A spinout with almost no public record cannot afford to hide the little it has.
Defer the rebrand as well. A name change after the entity has begun to resolve costs you every piece of corroboration you have accumulated. The naming decision belongs at formation.
What this page does not claim
It does not claim that four pages produce enquiries. They produce a resolvable entity. That is the precondition for everything else rather than a result in itself.
This page sits inside the Cambridge deep-tech field guide. The mechanism behind AI citations is covered in how AI assistants decide which Cambridge firm to cite. The diagnosis order for an existing site is on the zero-presence page.
Which pages should a Cambridge spinout publish at launch?
Four pages carry the load: a homepage with a plain capability sentence, a technology page, a team page, and a contact page with the full registered address.
Is a coming soon page harmful for a new spinout?
Yes, once it stays up for months. A holding page teaches every engine that the domain has nothing to describe. That impression takes time to correct.
How should the university licensing relationship be described?
State it plainly and factually: the technology licensed, the department or institute it came from, and the year of formation. Vague association language creates exactly the entity confusion the page is meant to prevent.
When should a spinout start publishing technical content?
Once the four core pages are accurate and indexed. One genuinely useful technical reference page is worth more at that stage than a publishing schedule nobody can sustain.