Internal Linking Assistant

Compare a page's content with real URLs from your site. The assistant finds passages where a contextual link may help readers and explains each source-to-destination recommendation.

Find relevant link opportunities

Analysis runs in your browser. This tool does not crawl your site or verify live status codes, so provide only destination pages you know are valid.

Required when you use relative paths below.

Identifies where each suggested link would come from.

One page per line: URL | page title or main topic. More specific descriptions produce better matches.

0 words

How the assistant works

  1. Enter the source page and paste its visible content.
  2. Add real destination URLs with a short title or topic for each page.
  3. Review passages that share meaningful topic terms with a destination.
  4. Open the destination and confirm it genuinely helps the reader before adding a natural link.

The assistant compares text; it does not crawl your navigation, measure inbound link counts, detect true orphan pages, or request HTTP responses. Use the results as editorial leads rather than automatic instructions.

How to interpret a recommendation

Relevance before link count

A link should connect the current passage to a page that answers a related question or provides a useful next step. A shared keyword alone is not enough.

Natural anchor text

Describe what the reader will find. Vary wording when the surrounding sentences differ, and avoid repeatedly forcing an exact-match phrase.

Source and destination

The source is the page being edited. The destination is an existing page supplied in your candidate list; the tool never invents a destination path.

Manual verification

Confirm the destination is live, canonical, and useful. Point directly to the final page instead of an avoidable redirect whenever possible.

Practical site-structure checks

Orphan and weakly linked pages

An orphan page has no discoverable internal links pointing to it. Valuable pages usually need a meaningful path from relevant content or navigation, but some utility, campaign, or account pages may intentionally sit outside normal discovery. A full crawl or link export is needed to identify orphans reliably.

Link depth

Important pages should have sensible discovery paths from related sections of the site. Review depth in context rather than enforcing an arbitrary universal click limit.

Parent pages and supporting content

Category or parent pages define a topic area; supporting guides explain narrower questions. Links between them should clarify that relationship and help users move between overview and detail.

Broken links and redirects

Repair links to missing pages and update internal links that pass through unnecessary redirects. Direct links reduce extra requests and make the intended destination clearer.

Example: a useful contextual link

Labelled example: A guide about fixing Google indexing problems discusses HTTP response codes. A contextual link from that passage to the HTTP Status Checker can help the reader verify whether a URL returns 200, redirects, or fails. The connection is useful because the destination supports the task described in the source content.

Continue the technical review

Common questions

Does this tool crawl my whole website?

No. It privately compares pasted source content with the destination pages you provide. Use a crawler or exported link graph when you need sitewide incoming and outgoing link counts.

How many internal links should a page contain?

There is no useful universal number. Add links when they help users reach relevant information, then review dense or repetitive sections for distraction.

Can this identify orphan pages?

Not from one page's text. True orphan detection requires comparing crawlable pages, sitemaps, and the site's internal link graph.