Blog · AI Access

Setting Internal Links: How the AI Access Helps

Internal links connect your pages meaningfully and help visitors navigate your website. Recently, you've been able to set them directly in the webentwickler.io CRM via the AI Access (MCP) – simply by writing to Claude in your own words what should be linked.

Arrange a call Explore the CRM

Published on · By Nina Benfer · webentwickler.io · Auf Deutsch lesen

Overview in the webentwickler.io CRM: The overview of a sample website builds up: online status, last backup, key figures for loading time, SEO, AI search and visits. Then the home page heading is changed in the editor and published, and a new enquiry appears as a notification.
Key points

The Essentials at a Glance

These updates around internal links and the AI Access directly affect website operators.

Request links in body text in your own words

You ask your AI assistant in the chat, for example, to link place names on a specific page to the matching location pages – it sets the links in the text.

Verification of actual existence

Before a link is set, the assistant checks that the target page actually exists.

Changes initially as draft

Every change is first saved as a draft, which you can review at your leisure before publishing.

Connect without keys

Claude is registered as a connector: you click "Connect", sign in to the webentwickler.io CRM and confirm your website and permissions.

Public documentation

Everything about the AI Access is available on a public page in German and English – also for your IT or agency.

Why internal links are often overlooked

Internal links are one of the underestimated building blocks of a website. They guide visitors from one page to the next, for example from general service text to a matching subpage or from a blog post to a thematically related page. For search engines, internal links also signal which pages belong together and how important individual content is within the website.

In practice, typical mistakes occur here. Links are set when creating text and then never touched again – even when pages change or disappear. The result is links that lead nowhere because the target page no longer exists or has been renamed. Another mistake is the opposite: text without any internal links, even though suitable target pages would exist. Especially on larger websites with many subpages – such as service or location pages – linking quickly becomes tedious work that falls by the wayside in everyday operations.

What matters is fundamentally simple: links should be placed in body text at points where they provide added value to the reader, and they should actually point to existing pages. Both can only be reliably ensured if setting and checking links doesn't have to be repeated manually with every text change.

AI Access (MCP)

How the AI Access (MCP) makes linking easier

This is exactly where the AI Access (MCP) in the webentwickler.io CRM comes in. Instead of manually searching for and setting links in the editor, you formulate the task in your own words to your connected AI assistant – for example: "Link the place names on the Sell Property page to the matching location pages." The assistant sets the links in the body text and checks that each target page actually exists. Similarly, a link can be removed at your command if it no longer fits.

Importantly: content yes, technology never. Every change is backed up before execution, and everything can be undone. This also applies to structure – the AI assistant can switch heading levels, create lists, and add, remove or move cards; on service pages, it can also edit paragraphs and subheadings, with the same rules and safeguards as in the tool itself.

All these changes are initially saved as drafts rather than going live immediately. You can see what's in the draft, list texts without a visible location, set image descriptions, discard your own drafts, and retrieve your wishes and current status at any time. This way you maintain control over what actually gets published, even when the AI does the actual work.

About this feature: AI Access (MCP)BASIC

Claude adds a paragraph: In the chat, someone asks Claude: "Add a paragraph about the energy certificate to the "Sell" page." Claude replies: "Done. The paragraph is on the "Sell" page as a draft. A backup was made first. You can review and approve it in the CRM." In the CRM, the draft "Sell · new paragraph" is ready and gets approved. Finally: Content yes, tech never – everything as a draft.

AI Access (MCP)

How to set internal links with the AI Access

The process from connection to publication in a few steps.

  • 1
    Connect Claude You register the AI Access in claude.ai or Claude Desktop as a connector, click "Connect", sign in to the webentwickler.io CRM and select your website and permissions.
  • 2
    Formulate task in your own words You tell your AI assistant in the chat, for example, which terms on a specific page should be linked to which target pages.
  • 3
    Links are checked and set The assistant sets the links in the body text and checks that each target page actually exists.
  • 4
    Review draft The change is available as a draft, which you can review carefully before publishing anything.
  • 5
    Publish or undo Before each change was backed up, so you can publish the change or completely undo it.

About this feature: AI Access (MCP)BASIC

AI Access (MCP)

Security and documentation for IT and agency

When you connect an AI assistant to your own website, you naturally want to know what this access can do and where its limits are. That's why everything about the AI Access is available on a public page: how to connect Claude, what tools are available, what each can do and where the limits are. This documentation is available in German and English, so you can also pass it on to your IT department or agency if they want to check in advance how the access is secured.

The connection itself runs without keys to copy and without configuration files: you click "Connect", sign in to the webentwickler.io CRM, select your website and permissions and confirm. Content changes are possible, technical interventions are not – and every change is backed up before execution and can be undone. This interplay of clearly documented permissions, secured changes and drafts instead of immediate publication makes the AI Access understandable and usable even for websites with multiple stakeholders.

About this feature: AI Access (MCP)BASIC

Frequently asked questions

Frequently asked questions about the AI Access and internal links

Is it safe to connect Claude to my website?

Content yes, technology never: every change is backed up before execution, and everything can be undone.

Are links and other changes visible immediately?

No, changes are initially saved as drafts, including changes to service pages made from blocks. You publish only when it's right.

Can I have a set link removed again?

Yes, just as with setting, you can ask the assistant to remove a link.

How do I connect Claude to my website?

You register the AI Access in claude.ai or Claude Desktop as a connector, click "Connect", sign in to the webentwickler.io CRM and select your website and permissions – without keys or configuration files.

Is there documentation for my IT or agency?

Yes, everything about the AI Access is available on a public page in German and English, including the tools and their limits.

Can the AI also change the structure of my pages?

Yes, the AI assistant can switch heading levels, create lists, and add, remove or move cards, with the same rules and safeguards as in the tool.

Personal, no obligation

See the CRM on your own website.

In 30 minutes we show you how to maintain your website yourself and what it achieves. No technical jargon. Our team speaks German and English.

Arrange a call Message us on WhatsApp +49 151 290 471 52info@webentwickler.io

← All blog articles