Measured observation
A result from a dated measurement and a public protocol.
Editorial transparency · V3.2
Evidence is not a badge. It must be open to scrutiny.
This registry exposes what supports each documented answer and what its reference cannot establish. Every entry publishes its claim, type, scope, limitation, exact reference role and next review.
Four evidence types. No category confusion.
A method or professional position is not presented as a measured result. The distinction is public and included in the exports.
Edikka method
An explicit working rule whose implementation can be examined.
Editorial position
A stated professional judgment with its scope and limitation.
Public work
A practice that can be examined through public projects or pages.
The linked page is not always a data source. Its role is explicitly classified as data source, method documentation, published position or reviewable work. The same role is included in JSON and CSV.
19 answers you can audit.
The complete answers remain in their FAQ territories. This page gathers only their verification layer.
Digital Strategy
5 documented entries
How does Edikka define the priorities of a digital project?
Published claim
Edikka prioritizes an action according to the constraint it removes, its dependencies and the signal that will be used to check its effect.
- Scope
- Edikka’s framing and prioritization method for digital projects.
- Stated limitation
- The order remains a revisable hypothesis based on usage data, sales feedback and internal constraints.
- Editorial review
- · next review
Why choose Edikka for a digital strategy?
Published claim
Edikka provides work under Bertrand Morel’s direct responsibility, connecting strategy, UX/UI, development, SEO, content and measurement.
- Scope
- Selecting a provider to frame, create, redesign or optimize a digital presence.
- Stated limitation
- This model is not designed for standardized high-volume production, fragmented delivery directed internally or a request for guaranteed results.
- Editorial review
- · next review
How do you tell a visibility problem from an offer problem?
Published claim
Offer clarity, SEO and redesign should be ordered according to the observed constraint, not a universal sequence.
- Scope
- Initial assessment of an existing website before investing in redesign or acquisition.
- Stated limitation
- A progressive path may be preferable; this position does not replace a diagnosis of the foundation, offer and available data.
- Editorial review
- · next review
How much does a digital strategy cost?
Published claim
Strategy investment should remove the uncertainties that would make design and development more expensive later.
- Scope
- Framing before creating or redesigning a website.
- Stated limitation
- No universal budget percentage is claimed; the effort depends on scope, existing evidence and the number of decision-makers.
- Editorial review
- · next review
How do you choose between an insight, a FAQ and an expertise page?
Published claim
The editorial format should reflect its job: organize a territory, demonstrate an angle or resolve a bounded question.
- Scope
- SEO/GEO architecture across pillar pages, expert articles and FAQ answers.
- Stated limitation
- A sufficiently evidenced independent question may deserve its own page; length alone never justifies a new URL.
- Editorial review
- · next review
UX & UI Design
3 documented entries
Is a beautiful website enough to convert?
Published claim
Visual quality alone does not convert when the offer, evidence, actions or journey remain difficult to understand.
- Scope
- UX/UI assessment of pages intended to move a decision forward.
- Stated limitation
- In some fields, contemplation contributes directly to value; it does not remove navigation and action requirements.
- Editorial review
- · next review
Why choose Edikka for UX/UI design?
Published claim
Edikka publishes selected projects whose pages describe context, scope and design decisions.
- Scope
- Public portfolio supporting the answer “Why choose Edikka for UX/UI design?”
- Stated limitation
- A selected portfolio does not by itself demonstrate comparative performance or a causal effect.
- Editorial review
- · next review
Should you redesign everything or optimize the existing interface?
Published claim
A targeted correction suits localized friction; a UX redesign becomes relevant when causes repeat across templates.
- Scope
- Choosing between targeted UX optimization and interface redesign.
- Stated limitation
- The technical foundation matters: on an old architecture, a local fix can be riskier than a new component.
- Editorial review
- · next review
Web Development
3 documented entries
Why choose custom web development?
Published claim
Custom development is justified by a business constraint that creates value, not by prestige.
- Scope
- Architecture choice for a website or web application.
- Stated limitation
- Custom work requires documentation, testing, maintenance and available expertise; a proven solution may be more rational.
- Editorial review
- · next review
Should you choose a CMS, custom development or a hybrid solution?
Published claim
The choice between CMS, custom and hybrid should start with the dominant constraint, exit cost and available skills.
- Scope
- Architecture and editorial-autonomy decisions for a web project.
- Stated limitation
- Project size alone is insufficient; business rules, security, data and maintenance must be examined.
- Editorial review
- · next review
What budget should you plan for a custom website?
Published claim
Hidden website costs primarily come from dependencies that must be migrated, tested, secured, measured and maintained.
- Scope
- Scoping a website creation or redesign.
- Stated limitation
- A website can remain simple when scope, responsibilities and dependencies are genuinely stable and explicit.
- Editorial review
- · next review
SEO & AI Visibility
6 documented entries
How long does it take to get SEO results?
Published claim
An SEO timeline must distinguish deployment, discovery, visibility and effect on demand.
- Scope
- Planning and measuring an SEO intervention from a dated baseline.
- Stated limitation
- The 30- and 90-day windows are checkpoints, not guarantees of processing, rankings or commercial results.
- Editorial review
- · next review
Why choose Edikka for SEO?
Published claim
In the July 15, 2026 wave, 13 of the 30 observed sites published a GEO baseline or protocol.
- Scope
- Public presence of a baseline, corpus or method in the Edikka Observatory panel.
- Stated limitation
- The check assesses neither protocol quality nor an agency’s overall ability and does not support a ranking.
- Observed
- Editorial review
- · next review
Should you optimize existing content or create new pages?
Published claim
An existing URL should be consolidated while intent, proposition and decision stage remain the same.
- Scope
- SEO choice between updating, merging, splitting and creating URLs.
- Stated limitation
- A visible page may need to be split when it mixes distinct offers, audiences or decisions; migration must preserve existing signals.
- Editorial review
- · next review
How do you know which SEO pages to optimize first?
Published claim
A page becomes a priority when business value, a measured deficit, available evidence and deployment capacity meet.
- Scope
- Prioritizing editorial and SEO actions in a digital roadmap.
- Stated limitation
- A crawl, indexation or measurement constraint may come first because it conditions the analysis of other pages.
- Editorial review
- · next review
Should you aim for AI citation or classic conversion first?
Published claim
Conversion remains the priority while a qualified visit does not clearly progress toward trust or an inquiry.
- Scope
- Choosing between AI-visibility measurement and conversion improvement.
- Stated limitation
- Citability can come first only with a conversion baseline and a dated AI question set; no measurement guarantees a future citation.
- Editorial review
- · next review
Why can an FAQ strengthen GEO?
Published claim
In the July 15, 2026 wave, 9 of the 30 observed sites published GEO evidence that a third party could check.
- Scope
- Panel and 18 public checks defined by version 1.0.2 of the Edikka Observatory protocol.
- Stated limitation
- The result does not measure an FAQ’s causal effect and does not guarantee citation by a search engine or AI system.
- Observed
- Editorial review
- · next review
AI & Web Automation
2 documented entries
Which AI use case should you address first to get real ROI?
Published claim
The first AI use case should be frequent, bounded, verifiable and already costly without AI.
- Scope
- Prioritizing an AI prototype or automation within a business process.
- Stated limitation
- An unstable, sensitive or implicit-rule process should be clarified before automation.
- Editorial review
- · next review
How much does web automation with AI cost?
Published claim
A reliable AI prototype budget covers framing, sources, rules, integration, testing and measurement—not only model usage.
- Scope
- Budget framing for an AI prototype integrated into a business use case.
- Stated limitation
- Without a business owner, validated corpus or success criterion, the first investment should fund framing rather than integration.
- Editorial review
- · next review
Changes without silently redating the corpus.
The changelog describes editorial batches. Each answer keeps its own date. JSON and CSV expose the current state; they are not presented as immutable snapshots of past releases.
-
Bilingual evidence registry
Editorial adaptation of 19 documented answers, localized evidence metadata, and publication of the English registry and exports.
Scope: Public registry · immutable snapshot: not retained
-
Qualified reference roles and history
Public qualification of each reference role, distinction between a current export and an immutable snapshot, clarification of the V2 scope and documentation of the Digital Strategy commercial answer.
Scope: Public registry · immutable snapshot: not retained
-
Public registry and verifiable exports
Opening of the HTML, JSON and CSV registry; distinction between observation, method, position and public work; consolidation of a semantic duplicate in the SEO FAQ.
Scope: Public registry · immutable snapshot: not retained
-
First documented-answer selection
Publication of 18 documented answers across five FAQ territories, with an author, review date, canonical reference and explicit limitation.
Scope: FAQ answers · immutable snapshot: not retained
Editorial responsibility
Documentation is not overpromising.
Bertrand Morel is responsible for editorial review. An entry is removed from the public export when its reference, scope or limitation is no longer maintained. The registry is not a ranking, a result guarantee or a promise of citation by an AI system.