LIBRARY / GUIDES

Field guides

Reference material designed to understand a subject, frame a diagnosis and act without depending on opaque jargon.

Start with the central guide
Illustrative scene.

01 / SEO · SXO · GEO

SEO, SXO & GEO visibility architecture

Build a presence that search engines discover, people understand and generative systems can cite accurately.

Read guide

AI-generated illustration

TOOLS / REGISTERS

Turn a diagnosis into a verifiable record

Each grid presents information to record and a review rule. Link observations to their sources, dates and scope.

Choose a template Compose a public-source reference Review checks before a decision

02 / INDEX

The operational library

Each guide answers a precise question and sets out a method, outputs, limits and the next useful decisions.

Patch panel and fiber-optic connections. Illustrative scene.
SEO · INDEXING

Crawling and indexing audit

A practical protocol to diagnose URLs, status codes, canonicals, languages, rendering and images before publishing more content.

Read guide

AI-generated illustration

Two screens and reference documents. Illustrative scene.
AI · CITATIONS

AI citation observatory

A repeatable protocol for tracking generative answers, cited sources, errors and differences between interfaces.

Read guide

AI-generated illustration

Ethernet switch and network cables. Illustrative scene.
AI · CRAWLERS

Control AI crawler access

Separate search crawling, indexing and training collection, then test robots rules and actual HTTP responses.

Read guide

AI-generated illustration

Open reference book on a desk. Illustrative scene.
ENTITY · SOURCES

Build a verifiable entity profile

Align names, roles, sources, public profiles and structured data to identify a person or organisation without visibility promises.

Read guide

AI-generated illustration

Multilingual keyboard on a research desk. Illustrative scene.
LANGUAGES · QUALITY

Audit a multilingual website

A method to check each language, hreflang links, canonicals, real content and user journeys without confusing translation with localization.

Read guide

AI-generated illustration

Computers linked by cables. Illustrative scene.
AI · DEPENDENCIES

Map AI system dependencies

A protocol to inventory models, data, tools, vendors, costs and exit options before a dependency becomes critical.

Read guide

AI-generated illustration

Screen and data cards. Illustrative scene.
SCHEMA · VALIDATION

Audit structured data

A protocol for checking that markup matches visible content, stays consistent across languages and passes validation without promising rich results.

Read guide

AI-generated illustration

Where to start?

Find a method for your task

Choose your question. Each path connects existing methods, useful sources and an outcome you can document. Stop at the step that answers your need.

Work through the data before drawing conclusions

Match entities without merging namesakes

Before merging records, check object type, identifier system, dates and contradictions. Distinguish duplicates, namesakes, establishments and related organisations.

Record my observations

Use the local tool

In-depth practical guides

Methods for reading, searching, monitoring, migrating and testing a multilingual corpus with evidence and inspection criteria.

Worked exercises available : 49

Read and verify sources

Start from a claim and find the document, version and status. The expected output is a verifiable reference retaining the qualifications that limit the conclusion.

Prepare and compare data

Check keys, schema and units before matching tables. Local tools help detect duplicates, changes between versions and differences in scope.

Publish and maintain a site

Connect each check to a URL and a real journey: HTTP response, languages, redirects, rendering and recovery. Keep defect evidence and correction checks.

Organise measurement and monitoring

Define what is counted, when and under which conditions. Retain failures, denominators and calculation rules when interpreting a change.

Choose a source family

Topic pages to select a service and understand what its result can establish.

03 / METHODS

Which protocol should you use?

Start with the decision at hand. Each method produces a different form of evidence; the protocols can then be combined.

SEO · INDEXING

Crawling and indexing audit

An important page is missing from search or a migration changed URLs.

Expected result : A register of URLs, obstacles and fixes to recheck.

Open protocolSOURCES · EVIDENCE

Evidence and source register

Public claims need verification and maintenance.

Expected result : Dated sources, their scope and an update owner.

Open protocolAI · CITATIONS

AI citation observatory

You need to observe how assistants describe an entity or cite content.

Expected result : Comparable observations, with errors and verified links.

Open protocolAI · CRAWLERS

Control AI crawler access

Crawler access rules should match intended uses.

Expected result : A matrix of page, crawler and actual served response.

Open protocolENTITY · SOURCES

Build a verifiable entity profile

A person or organization is confused with another.

Expected result : A consistent identity, official links and sourced assertions.

Open protocolLANGUAGES · QUALITY

Audit a multilingual website

Language versions exist but journeys switch language or meaning.

Expected result : A matrix of variants, signals and editorial gaps.

Open protocolAI · DEPENDENCIES

Map AI system dependencies

A function relies on a poorly understood model, vendor or data flow.

Expected result : A component map, failure points and a tested fallback.

Open protocolSCHEMA · VALIDATION

Audit structured data

Markup misrepresents the page or has errors.

Expected result : A record of fields, discrepancies and post-fix validation.

Open protocolAGENTS · TESTING

Evaluate an AI agent before release

An agent will act through tools and permissions.

Expected result : A test set, traces and a bounded release decision.

Open protocolCONTENT · MAINTENANCE

Maintain a reliable editorial corpus

Pages become outdated, redundant or uneven across languages.

Expected result : A review register, merge decisions and verified corrections.

Open protocolACCESSIBILITY · JOURNEY

Audit accessibility across a web journey

A journey excludes users or remains difficult by keyboard.

Expected result : Scenarios, reproduced defects and post-fix retests.

Open protocolWEB · PERFORMANCE

Measure the performance people experience

A page feels slow or scores and experience disagree.

Expected result : A measurement distribution and verified technical causes.

Open protocolFORMS · USABILITY

Audit a form from start to finish

Requests fail or error messages do not support recovery.

Expected result : A case matrix, server responses and a retested journey.

Open protocolIMAGES · EDITORIAL

Audit a site’s editorial images

Images lack context, rights evidence or alternatives.

Expected result : An image register with roles, rights and corrections.

Open protocolOSINT · SOURCES

Qualify an open source before using it

A public claim circulates without a clear origin or corroboration.

Expected result : A provenance record, reuse chain and bounded conclusion.

Open protocolOSINT · TIMELINE

Reconstruct a timeline of public signals

Announcements and captures appear to tell different sequences.

Expected result : A dated timeline separating event, publication, observation and correction.

Open protocolOSINT · ACTORS

Map actors using public sources

Organizations or accounts appear connected without an established relation.

Expected result : An entity map with documented links and unconfirmed hypotheses.

Open protocolOSINT · IMAGES

Verify the context of a public image

An image is tied to a disputed place, date or event.

Expected result : Known versions, context clues and limits of the conclusion.

Open protocolOSINT · DECISIONS

Read and cite a public decision

A public decision is cited from a summary or without its procedural state.

Expected result : An exact citation, bounded passage and later steps to check.

Open protocolDATA · QUALITY

Assess a public dataset before reuse

A dataset looks current and complete, but its file and method have not been checked.

Expected result : A reuse decision grounded in coverage, version, licence and limitations.

Open protocol

04 / READING PATHS

Choose a reading path

Four short paths start from the problem to solve: visibility, evidence, decisions or data reuse.

01 / VISIBILITY

Be found, understood and cited

SEO, SXO and GEO → editorial architecture → AI visibility measurement.

Follow this path02 / EVIDENCE

Build verifiable authority

Evidence doctrine → AI citations → source architecture.

Follow this path03 / DECISION

Choose a proportionate intervention

Measurement → intervention scenarios → strategic audit.

Follow this path04 / DATA

Reuse a public dataset with care

Listing and licence → file and method → version and limitations → traceable claim.

Follow this path

05 / GLOSSARY

Need to clarify the language?

The glossary defines the essential concepts before methods and trade-offs are explored.

Open the glossary

06 / CONTACT

Contact

Have a precise context? State the decision, exposure level and deadline.

ContactDossiers

DEEPER READING / PRACTICE

Transition from reading to a re-use method

The aim is to make the need, choices and next steps clear to everyone involved. Defining the scope is useful when it helps people make decisions and check the effects of an action.

Editorial supplement added on .

Starting situation

A guide becomes useful when it allows you to conduct a check and explain the result. The reading should therefore focus on the information to be kept as well as on the succession of the steps.

Priority checks

Identify the necessary entries, the expected output and the limits of the method. Try the protocol on a simple case before applying it to a large corpus.

Interpretation pitfalls

Following the steps without understanding their purpose can give a facade conformity. An unexpected outcome deserves an investigation, even if all the cases of the procedure are scratched.

Working record to retain

A application sheet preserves the chosen case, the steps carried out, the differences encountered and the authorized conclusion. It makes it easier to compare two executions of the same guide.

Apply the approach to an initial case

Starting with a delimited case allows to confront intentions with real constraints. In this case, specify the purpose, the available information and the person who can arbitrate. Then extend the scope when the first observations justify that change, rather than fix all the steps on the basis of unverified assumptions.

Present the result and its limitations

When presenting the results, separate the decisions taken from the topics still open. A expected result must be described accurately enough so that the team can recognize its achievement. The next checkpoint focuses on a observable change and provides for what to be revised if the result is not obtained.

PRACTICAL CASE / WORKED EXAMPLE

Apply a method to an imperfect document

The following case illustrates an approach to defining the need. Situations are pedagogical: they serve to examine the choices and conditions of success, without describing a fulfilled mission or announcing a guaranteed result.

Example context

A guide provides a precise identification and date, but the available document provides only a title and an approximate period. The application requires to process the missing information.

Suggested approach

Execute the possible steps and record the unknown fields. Search for a document or other source. Differentiate possible conclusions from those that still depend on an absent element.

Conclusion and next step

The application sheet keeps the partial result and the next verification. The protocol remains useful without converting assumptions into confirmed values to artificially complement the model.

Checklist for applying this example

  • Formulate the expected decision and identify the person who can arbitrate.
  • Describe the known restrictions and the information still needed.
  • Compare options according to criteria understandable by the participants.
  • Join the next action to a observable result and a review.

Questions for deeper practice

What to do when a step of the guide is impossible?

Document the obstacle, its effect and replacement solutions examined. The conclusion should indicate whether this step only lacks context or actually prevents the answer to the question.

How to move from a diagnosis to a concrete action?

Choose an action whose role in the problem is explicit, check the requirements and designate a manager. describe what will show improvement. The first step should also produce useful information if the result is not the expected, so that the choice is revised instead of automatically extending the plan.

How to keep a trace of decisions without delaying the project?

A short report can record question, options, choices, reason and next control. The detailed subjects remain linked to the report for a thorough reading. Updating decisions when their conditions change is more useful than accumulating accounts made without indicating the actions and responsibilities that arise from them.

DETAILED WORKSHOP / APPLICATION

Documenting a partial application of the Protocol

This workshop offers a five-step sequence to apply the page labels. The entries, observations and conclusions are kept together in order to facilitate the verification and recovery of the work.

  1. 01 / Prepare the necessary information

    Choose a simple case and collect the entries requested by the guide. Mark the information available, uncertain and absent before starting the verification.

  2. 02 / Carry out the approach

    Implement the possible steps and note the differences. For a missing entry, consider a replacement source or a complementary method. Relate each limit to its effect on the conclusion.

  3. 03 / Examine an alternative situation

    If the blocked step is decisive, produce a temporary result and a precise next search. An incomplete application remains informative when its scope is clearly described.

  4. 04 / Decide on the next step

    The protocol may be considered to be applied to the announced scope when the steps and reserves are traceable. Unfitted steps remain distinct from successful checks.

  5. 05 / Hand over the verification records

    Transmit the application sheet with cases, entries, observations and conclusions. Another reader must be able to know what remains to check before using the result.

ANNOTATED WORKING DOCUMENT / REVIEW GRID

An application sheet that keeps the deviations in the protocol

The list indicates cases, entries, steps carried out and conclusion. It shows how missing information or adaptations have affected the result rather than hiding a partial application.

On a small screen, scroll the grid horizontally to read all three columns.

Example situations to assess
ObservationSupported interpretationNext step
All useful steps are done.The method was applied to the announced scope with traceable observations.Keep the evidence and check the conditions of use of the result.
A secondary step remains impossible.The result may remain useful if the limit and its effect are explicit.Describe the gap and clarify the conclusions that do not depend on it.
The missing step supports the main conclusion.The answer remains insufficiently established despite the other controls carried out.To produce a temporary result and a subsequent precise verification.

Reviewing the working document

The person responsible for the verification distinguishes the failed step, the successful step and the uncertain result. The file should allow the work to be restored to the right place without the already documented consultations.

REPORTING / EXAMPLE WORDING

Presentation of results: Transition from reading to a re-use method

Point to clarify

A partial application must indicate which conclusions remain possible despite the missing stage.

Before handing over

Verify that the result does not implicitly regain the benefit of a non-executed control.

Example of a qualified conclusion

The accomplished steps establish the elements described. The main conclusion remains provisional as long as the information required at the indicated stage has not been obtained.