Internal Link Suggestions

We send your draft + your candidate pages to M3 with a structured prompt asking it to identify the strongest topical matches. For each match, it generates a short natural anchor (2-5 words) that fits the draft, explains why the page is relevant, and points to the specific paragraph where the link fits. We then sanity-check the response: any suggestion whose target URL wasn't in your input list is discarded, and we cap the results at the maxSuggestions you set.

Three formats work: (1) Plain URL list — one URL per line, the simplest. (2) Sitemap XML — paste the raw output of your-sitemap.xml and we'll extract every <loc>URL</loc> entry. (3) CSV — one row per page with 'url,title' columns, useful if you want to use your real page titles as labels. For URL-only and XML formats, we infer a title from the URL slug (e.g. '/blog/json-ld-tutorial' becomes 'Json Ld Tutorial').

Modern SEO consensus is 3-5 contextual internal links per 1000 words of content, plus 1-2 navigational links (header, footer, related-posts widget). Going above 8-10 contextual links per 1000 words starts to look spammy and dilutes PageRank distribution. The AI's maxSuggestions setting defaults to 5 — which is the right number for a typical 1500-2000 word blog post.

Two rules: (1) the anchor should be a natural phrase that fits the sentence, never the exact page title, and (2) it should be specific enough to signal the linked page's topic. Vague anchors like 'click here' or 'read more' are wasted link equity. Over-optimized anchors like 'best SEO agency in Austin Texas' look spammy to Google. The sweet spot is 2-5 words that describe what the linked page is about — e.g. 'structured data guide' or 'JSON-LD tutorial'. Our AI follows this rule by default.

Free, yes — 10 generations per hour per IP, no signup, no daily limit. Privacy, mostly: your draft and sitemap are sent to our API endpoint to call M3, but the model is (in-house) and we don't log request bodies or use them for training. We do keep an in-memory rate-limit counter (resets on cold start). If you want zero-server internal linking, run our tool on a self-hosted M3 endpoint. Open DevTools → Network while you use it: only the analysis call leaves your browser.