Internal links: connect useful pages without inventing orphan findings

Internal links should help someone take the next useful step. They also give crawlers routes between pages. Begin with a real navigation problem, not a target number of links or an unsupported orphan-page warning.

Find a journey that breaks down

A useful starting point is a guide that describes a service but never links to its booking page, or a product category whose important products are reachable only through a search form. Write down the visitor’s current question, the destination that helps answer it and the page where the link would naturally belong.

Leave links alone when they already provide a clear, working route. Do not add every service to every paragraph. A sparse help page can be appropriate; a large footer repeated everywhere is not automatically better navigation.

Use a real destination and meaningful text

Google’s link guidance centres on anchor elements with href attributes. A clickable card implemented only as a script event is not equivalent to a normal link. JavaScript can generate usable anchors, but inspect what is delivered or rendered instead of assuming that a click handler provides a crawlable route.

Anchor text should explain the destination in its surrounding context. “See our workshop assessment process” is more useful than an isolated “Click here.” Avoid a list of keyword variants masquerading as a sentence. Link only where the next page earns its place in the reader’s journey.

Make one contextual connection

The following fictional maintenance guide helps a reader decide whether to seek an inspection. The link label names the next step; it does not promise a price or service outcome that has not been established.

<p>
  If the wheel still rubs after the checks above,
  read our <a href="/services/wheel-assessment/">wheel assessment process</a>
  before booking a workshop visit.
</p>

The target should contain the assessment process, not a generic homepage. Check the final address after redirects and prefer the intended canonical URL when linking. Keep ordinary navigation available to keyboard users; do not require hovering or a mouse-only interaction to expose important destinations.

Build a small link plan you can review

  1. Inventory important destinations. Use your CMS catalogue, published-page list and sitemap as starting points. Exclude private or retired pages that should not be promoted.
  2. Choose relevant source pages. Find existing explanations, product groups or service pages where the destination answers a natural follow-up question.
  3. Record the proposed connection. Note source URL, destination URL, anchor wording and why a reader would need it.
  4. Add the smallest useful change. A contextual sentence may be sufficient. Update a menu only if the destination belongs in that broader navigation.
  5. Verify the result. Open the link, inspect the destination and check the source markup before repeating the approach elsewhere.

An illustrative plan might connect a “Why bicycle wheels rub” guide to “Wheel assessment,” and the service page to a preparation checklist. Those are distinct reader needs; neither connection requires adding a site-wide link to every article.

Use the right editing layer

WordPress: use the documented Link control in supported blocks, selecting meaningful text and the intended destination. Navigation editing depends on the theme and editor in use. Preview the published page rather than relying on how the editing canvas behaves.

Shopify: the rich text editor supports links in appropriate content fields. Use the store’s menu tools for navigation links to products, collections and pages. If a theme’s dropdown heading only expands a menu, ensure a separate working link exists for any category page visitors need.

Custom HTML: use an anchor with a valid href for navigation. A button should perform an action rather than simulate a link. If routing is handled by a framework, confirm that its link component produces a real anchor and that opening the URL directly works.

Verify, record and roll back

Test the source page and destination on phone and desktop. Use the keyboard, check that the label makes sense, and confirm that redirects do not lead to an unrelated page. Inspect delivered HTML for the anchor; use appropriate rendered inspection when JavaScript supplies it.

Record the changed source pages, previous wording and release date. If navigation breaks, restore the prior content or menu configuration, or revert the relevant template commit. Recheck the destination and another unaffected page. Avoid changing URL paths simply to repair a missing contextual link.

Do not infer an orphan page from a small sample

An orphan page has no discoverable internal path within the scope being assessed. Establishing that requires a sufficiently complete site inventory and link graph, including a deliberate scope definition. Not finding a link in four sampled pages does not prove that no link exists elsewhere.

SingCompare inspects a bounded sample, not the entire site. Its observed links and page evidence can suggest questions to investigate; they do not establish a complete crawl, site-wide orphan status or guaranteed discovery. Repeated anchor text is not automatically a defect, and adding links does not guarantee indexing or a ranking improvement. Use crawl and indexing evidence to investigate those separate questions.

Sources and review date

Official documentation reviewed on 17 November 2026. Platform controls and search policies can change. Examples are fictional; implementation and prioritisation advice is SingCompare’s own.

  1. Google: Crawlable links and anchor-text practices
  2. Google: SEO Starter Guide
  3. WordPress: Link control
  4. Shopify: Using the rich text editor
  5. Shopify: Understanding menus
  6. Shopify: Dropdown menus and category destinations

Continue reading

Match each page to a useful search questionCheck the right crawl and indexing controls

Check the evidence on your page.

Run a free SEO and GEO readiness diagnostic, inspect its sources and keep the report before making changes. No sign-in required.

Run free diagnostic