Internal linking

Internal linking is now in Bloomiro.

Open a project and choose Internal linking in the sidebar. A scan reads your pages, maps the links that already exist (navigation and footer included, because Google and AI crawlers follow those too), and then suggests two kinds of change:

• Add: a useful next click from one page to another
• Drop: an existing link that is weak, off-topic, or competing with the same intent

The point is not more links for their own sake. A good suggestion should help a person take a real next step, give Google a clearer path through a topic, and help AI answer engines reach a page they can actually cite.

What a scan does

Bloomiro looks at each page in the run, how it already links out, and whether another page would be an honest next click. It is not writing copy. It is scoring the relationship between two URLs: would this link help a reader, a crawler, and an AI bot understand the site better?

You pick a size as a ceiling (up to 100, 200, or 400 pages). Billing follows how many pages were actually classified: 3 credits up to 100 pages, 5 up to 200, 10 above 200. A heavy scan on a small site bills as a light one.

You can put paths such as /blog last, so other pages fill the budget first.

When the scan finishes, Insights shows a map of the site, counts for crawled pages, add suggestions, drop suggestions, and existing links, and a page card when you select a node. One suggestion is one directed link (from this page to that page), even though two pages are involved.

Ask in Actions

Open Actions and ask in ordinary language, for example:

• Where should we add internal links?
• Which internal links should we drop?
• Start an internal linking scan, and leave /blog until last
• What does the homepage already link to, and what is missing?

Actions uses the saved scan. It starts with counts, then reads add pairs, drop pairs, or one page when the question needs that. It will not dump the whole graph into the chat.

If you ask it to start a scan, the work runs in the background. You can leave and come back. The map and the suggestion lists show in Internal linking when it finishes.

Use it through MCP

Connected MCP clients can use the same project-scoped scan.

The normal flow is:

1. Call get_project_context to select the project.
2. Start a scan with run_analysis and analysis_type=internal_links when you need a fresh one. scan_size is the page ceiling (light, medium, heavy). deprioritize_slugs are paths to use last.
3. Read results with get_internal_links. Start with view=summary for counts only.
4. Use view=suggestions for add pairs, view=drops for drop pairs, or view=page with a URL for one page.

Default lists stay small. Follow next_cursor if you need more. Summary is never the add or drop list. Do not load the graph resource when you only need those lists.

If there is no scan yet, Actions and MCP say so instead of inventing links.

What this is not

Internal linking is a crawl and understanding fix. It does not promise rankings, AI mentions, or that adding a link cannot hurt. Treat each suggestion as an experiment: change the link, then measure whether people, Google, and AI answers still find the right pages.