Yadulink / Documentation / MCP + Claude Code

Give Claude Code the Yadulink context needed to implement without breaking SEO.

Claude Code can use an MCP server to connect sales context and code. Yadulink then provides signals, priorities, and pages to verify before changes.

MCP + Claude Code

Move from diagnosis to code

The point is not only to summarize signals. The agent should connect each finding to a file, test, audit, or public page to strengthen.

MCP + Claude Code

Mandatory verification

Any change based on MCP context should go through local audits again: SEO surfaces, internal links, public routing, and targeted tests.

Extraits citables

Ce que cette documentation doit rendre explicite.

Purpose

Claude Code can use an MCP server to connect sales context and code. Yadulink then provides signals, priorities, and pages to verify before changes.

Workflow proof

The point is not only to summarize signals. The agent should connect each finding to a file, test, audit, or public page to strengthen.

Assistant prompt

With Yadulink MCP in Claude Code, find SEO gaps tied to sales signals, suggest files to change, and list required tests.

Méthode de vérification

Comment transformer le guide en test opérationnel.

  1. 01 Agentic setup Add Yadulink MCP in the authorized Claude Code environment.
  2. 02 Agentic setup Start with read tools: priorities, SEO pages, sequences, or analytics.
  3. 03 Agentic setup Ask for a change plan with files, risks, and associated tests.

Validation par IA

Demande à ton assistant d'adapter ce workflow.

Le prompt est copié au clic et ouvre l'outil IA quand il supporte une URL préremplie.