FULLSIX,
fren
S
BETC Fullsix

SEO / GEO

Measurable visibility on classic search engines and generative AI engines - two disciplines in one, wired into the foundation.

JSON-LDschema.org structured data
CWVCore Web Vitals monitored
GEOcited by generative AI
Go deeperBook a demo

Technical SEO alone is no longer enough: ChatGPT, Perplexity and Google AI Overviews answer questions directly without linking back to a site. Ranking well on Google AND being cited correctly by generative AI requires a unified approach - shared technical foundations, distinct metrics.

Solid technical SEO

Server rendering (SSR/SSG), semantic HTML, optimised Core Web Vitals, clean sitemaps, careful redirect and canonical management. Everything Google expects from a healthy site - without sacrificing performance.

GEO - readable by AI

Generative engines read the rendered HTML, JSON-LD and metadata. We structure content with schema.org (Article, FAQPage, Product, Organization) and fine-tune the signals ChatGPT, Perplexity and Claude use to attribute a source.

Measurable at every step

SEO rankings (Google Search Console, Ahrefs), Core Web Vitals (Lighthouse CI), Cloudflare cache hit rate, and for GEO: regular tests on target generative engines with a fixed set of queries. Nothing improves without measurement.

Technical SEO: the foundations

A poorly rendered site sabotages its own crawl. Our Next.js projects produce complete server-side HTML (SSR or SSG): the Googlebot - and the generative-AI bot - receives a readable page without executing any JavaScript.

Systematic technical levers:

  • Server rendering (SSR / SSG / ISR): no key content hidden in the client DOM. Metadata (title, description, canonical, hreflang, Open Graph) is injected into the server-rendered <head>.
  • Semantic HTML: hierarchical headings, properly structured <ul>/<ol> lists, ARIA landmarks, alt attributes on all meaningful images. This is not just accessibility - it is also what LLMs parse to understand page structure.
  • Core Web Vitals: LCP below 2.5 s, CLS below 0.1, INP below 200 ms. Measured continuously on key pages via Lighthouse CI integrated into the GitLab CI/CD pipeline.
  • Sitemaps and robots.txt: dynamically generated sitemaps, robot policies tuned per bot type (GPTBot, ClaudeBot, PerplexityBot, Google-Extended).
  • Redirects and canonicals: a documented redirect plan (301/410) deployed via SEOPress Pro or middleware configuration, systematically validated with a Googlebot UA curl before going live.

GEO - Generative Engine Optimization

GEO builds on the same HTML as SEO, adding signals that LLMs value:

  • schema.org JSON-LD: every page type gets appropriate schemas (Article, FAQPage, Product/Offer, Organization, BreadcrumbList, MedicalCondition where relevant). Schemas are generated server-side and injected into the <head> as <script type="application/ld+json">.
  • llms.txt and ai.txt files: declarations of content authorised for AI bots, editorial credibility signals.
  • Reference content: LLMs cite authoritative sources on a topic. We structure content to answer questions directly - not only to appear in results.
  • Clear source attribution: brand name, authors, dates, Organization schema.org with sameAs pointing to Wikipedia/Wikidata where relevant.

What this means for your CIO

  • No SEO vendor lock-in: all redirect rules and JSON-LD schemas live in the codebase and CMS, not in a proprietary third-party tool.
  • Built-in CI/CD: Lighthouse CI blocks a build if the LCP exceeds the target threshold. Performance regressions never reach production.
  • GEO measurement: periodic tests on Perplexity, ChatGPT and Claude using a fixed query corpus, tracking citation rank over time.
  • Measurable gains: Google Search Console rankings, Core Web Vitals via Search Console and RUM, LLM citation rate before and after.