Skip to content
AURENAUREN — digital studio
← Insights

Generative engine optimisation · · 7 min read

Why your site is invisible to AI search

In short

  • If a sentence only exists after JavaScript runs, assume no answer engine will ever see it.
  • Write one self-contained definitional sentence per page. Pronouns pointing backwards make a paragraph unquotable.
  • An entity graph — named person, linked profiles, consistent organisation — is what turns a studio from a string into something citable.

Generative engine optimisation is the practice of structuring a site so AI answer engines can quote it. It overlaps heavily with classic SEO — fast pages, semantic markup, structured data — but it rewards a different kind of writing, because the unit of success is no longer a ranked link. It is a sentence lifted out of your page and placed inside someone else's answer.

That difference has consequences, and most of them are unkind to exactly the sort of site a design studio likes to build.

The canvas problem

A motion-led site often puts its most important statement inside a canvas, a WebGL scene or a scroll-driven animation that only assembles after hydration. To a person it reads as the boldest thing on the page. To a crawler it is nothing at all — there is no text node, so there is no text.

This is the single most expensive mistake available to a studio site, because the more ambitious the execution, the more likely it is. The fix is not to abandon the motion. It is to make the motion decorative by definition: the headline is real HTML, the instrument sits behind it, and the page still says everything it needs to say with the canvas removed.

Write sentences that survive being moved

A paragraph that begins "This approach lets you…" cannot be quoted, because "this approach" refers to something two paragraphs up that will not travel with it. Every page should carry at least one sentence that names its subject, states what it is, and depends on nothing around it.

Test it by cutting the sentence out and reading it cold. If it still makes sense to someone who has never seen the page, it is quotable. If it does not, it is decoration with a full stop at the end.

Become an entity, not a string

Retrieval systems resolve names to entities. A studio name on its own is ambiguous — it could be a font, a band, a town. What disambiguates it is structure: an Organization node with a stable identifier, a named Person linked to it as founder, and profile URLs that corroborate both.

This is the part most agency sites skip, and it costs them more than any keyword decision. A business that cannot be resolved gets paraphrased without attribution. One that can gets cited by name.

The unglamorous checklist

  • Server-render every sentence that matters. Nothing important behind hydration.
  • One definitional sentence per page, written to stand alone.
  • Real questions with direct answers, marked up as FAQPage.
  • Organization, Person and Service nodes with stable identifiers that reference each other.
  • A robots file that refuses to index preview deployments — otherwise a staging clone competes with you.
  • An llms.txt describing the site in plain language.
  • Headings that describe content rather than perform for it.

None of this is glamorous and none of it requires giving up a distinctive site. It requires deciding, before the first component is written, that the copy is not allowed to live inside the animation.

Next step

Have something worth building?

Tell us what you are building or trying to fix. You will get a considered reply, not a calendar link.