Technical foundation
Crawling, indexing, performance, rendering, canonicals, structured data, security and template stability.
GUIDE 1301
Build a presence that search engines discover, people understand and generative systems can cite accurately.
Operational briefOperational brief
SEO organises discovery and understanding in search engines. SXO connects that promise to a fast, clear and credible experience. GEO prepares explicit, structured and verifiable content for generative answers. Treating them separately creates inconsistency; connecting them creates an architecture serving search, decisions and conversion.

Classical search, conversational interfaces and generative answers observe the same public space through different mechanisms. Architecture must preserve a coherent entity, evidence base and promise across every journey.
02 / Intervention areas
Crawling, indexing, performance, rendering, canonicals, structured data, security and template stability.
Questions, needs, knowledge levels, decision situations and their mapping to genuinely useful pages.
People, organisations, expertise, places, services, publications, evidence and consistently expressed relationships.
Result promise, visible first answer, readability, navigation, trust, reassurance and the next useful action.
Short definitions, sourced depth, explicit limits, identifiable authors and extractable formats that preserve context.
Impressions, clicks, journeys, conversions, AI citations, answer accuracy and share-of-presence change.
03 / FIELD NOTES
SEO, SXO and GEO symptoms often reveal the same structural or representation problem.
Pages are technically accessible without forming clear topical authority or answering priority intent.
The result promise is not fulfilled, the answer arrives too late or the journey prevents verification and action.
Public sources are weak, contradictory, disconnected or insufficiently explicit for assistants.
URLs, content, links, structured data and entity signals must transfer without avoidable disruption.
04 / OUTPUTS
The outcome is not a keyword list. It is a transferable set of decisions, templates and measurements.
Questions, segments, maturity, priorities and responsible pages.
Identifiers, relationships, public sources, ambiguity and data to consolidate.
Hierarchy, cornerstone pages, clusters, internal links, URL rules and navigation depth.
Reading order, first answer, evidence, objections, calls to action and mobile variants.
Answer formats, citations, provenance, authors, freshness and relevant structured data.
Search, experience, conversion, AI-answer, quality and review-frequency indicators.
05 / Method
Every change should improve at least one decision: discover, understand, verify, compare, choose or return.
06 / FAQ
Clear answers on scope, limits, methods and engagement conditions.
No. Assistants rely on a crawled, structured and connected web. GEO extends the work toward synthesis, provenance and citation.
UX covers the complete experience. SXO begins with expressed search intent and tests continuity between result, page and useful action.
No. A page should own a distinct intent or object. Multiplying similar pages dilutes signals and raises maintenance.
Length is not the objective. A page should answer quickly, then provide the depth, evidence and nuance required.
Using a stable question set, several models, dated measurements, citations, accuracy and observed variation.
No. It reduces ambiguity, while engines retain display control and combine many other signals.
Yes, while hierarchy, contrast, speed, keyboard navigation and mobile readability remain controlled.
When architecture durably blocks indexing, understanding, maintenance or content evolution. Focused correction is often enough.
A baseline connected to objectives: technical state, responsible pages, journeys, authority sources and representation across search and assistants.
08 / CONTACT
State the context and objective. You will receive a clear initial reading.