What internal links do for a business site
An internal link connects one page on a website to another page on that same site. It gives a visitor a route from an initial question to more detailed information, and it gives crawlers a way to discover URLs. For example, an article about domain ownership may link to a separate guide on registrar transfers when that distinction becomes relevant. The link should help the reader continue a task, not merely inflate the number of links on the page. Google describes links as discovery and relevance signals, but adding links does not guarantee indexing or a particular ranking.
Start with a page inventory
Before inserting links, list the pages that actually exist and the questions each answers. Include the home page, service descriptions, contact information and useful educational articles. Record the canonical URL, language, topic, publication status and whether the destination is still maintained. A draft article that has not been approved should not be presented as a live resource. Identify important pages that have no incoming contextual links. This inventory helps prevent links to retired offers, duplicate URLs or a placeholder that merely resembles a published page. A simple spreadsheet is often sufficient for a small site.
Connect questions in a useful sequence
A visitor learning about business email might first need to understand the difference between a mailbox and a forwarder. From that article, a link to mailbox storage planning may be useful, followed by a separate migration checklist. The sequence should follow a real decision rather than an arbitrary SEO cluster diagram. Ask what information the reader needs next and whether the destination answers it. Avoid sending someone to a sales page in the middle of a technical explanation unless that page genuinely helps with the decision. Clear routes reduce unnecessary searching around the site.
Use ordinary crawlable anchor elements
Google's link best-practice documentation says that an HTML anchor element with an href attribute is the reliable foundation for crawlable links. A clickable span controlled only by JavaScript may work for some visitors but is less dependable for crawlers and assistive technology. Use a real destination URL in the href, and confirm that it resolves correctly. A button is appropriate for an action such as opening a form, while a link is appropriate for navigation. Test keyboard focus and the destination after rendering, especially when a content management system generates the HTML automatically.
Make link text explain the destination
Text such as 'click here' or 'read more' gives little information when read alone. A phrase like 'domain transfer preparation checklist' identifies the destination more clearly. Google and MDN both recommend descriptive, reasonably concise anchor text that helps readers understand where a link goes. Do not stuff every possible keyword into a long linked sentence. The surrounding sentence should also explain why the resource is relevant. When an article has several links, distinguish their purposes: renewal policy, DNS records and registrar transfer are not interchangeable subjects. Read the anchor texts without context as a quick editorial test.
Link where the explanation calls for it
A contextual link is most useful near the sentence that raises a related question. If a hosting migration article warns about DNS propagation, link to an existing DNS explanation at that point. A giant list of unrelated links at the bottom is less helpful for understanding the current paragraph. Conversely, do not interrupt every sentence with a link. Decide whether the reader needs a definition, a deeper procedure or a commercial scope page, and select the matching destination. The link should be a meaningful optional next step rather than an obstacle to reading the current answer.
Important pages need a discoverable path
Google recommends that pages you care about have at least one link from another page on your site. A new service page may be listed in a sitemap yet remain difficult for visitors to reach if nothing in the navigation or related content points to it. Review important destinations from the home page and relevant category pages. Do not assume that submitting a sitemap replaces usable navigation. For a small business, a clear service menu and a few contextual links can be more valuable than a complicated artificial network of hundreds of cross-links.
Navigation and contextual links have different jobs
The main menu should expose stable routes such as services, resources, company information and contact details. Contextual links inside articles answer more specific follow-up questions. A footer may provide access to policies and other frequently needed information. Treat these as complementary, not interchangeable. Putting every article in the main menu makes navigation unwieldy, while hiding all services behind an article archive makes basic tasks difficult. W3C WAI recommends semantic navigation structures that remain understandable across screen sizes and assistive technologies. Test the hierarchy with real tasks rather than counting menu items alone.
Avoid orphaned educational articles
An orphaned article has no useful internal route leading to it, even if its URL is known or listed in a sitemap. Audit newly drafted content before publication and identify at least one relevant published page that can introduce it. A domain expiry guide might naturally be linked from a renewal planning article, not from an unrelated social media page. Verify the link points to the approved canonical URL. Do not publish placeholder links to articles that still fail editorial or word-count gates. Maintaining a source-to-destination register helps catch orphaning when content is renamed or retired.
Use categories as helpful pathways
A resource library can group articles by practical themes such as business email, domains, hosting, website design, security and analytics. A category page should explain what visitors can learn, not simply display a long undifferentiated list. Link from category summaries to relevant articles and from articles back to appropriate broader guidance when it helps orientation. Do not create near-identical category pages merely to target keyword variations. A useful grouping reflects the way a business owner approaches a problem. Revisit categories when new content changes the balance of topics.
Use the correct canonical destination
Websites sometimes expose similar content under trailing-slash variants, tracking parameters or old paths. Internal links should normally use the intended canonical destination instead of relying on redirects. Check the final URL and its canonical signal before adding links to a template. A redirect may be necessary for a retired path, but repeated internal links through redirects create avoidable complexity. Do not casually change the existing canonical URL scheme during editorial work. Record any discovered discrepancy for technical review, and preserve approved sitemap and hreflang relationships until a separate change is authorized and tested.
Bilingual links should respect language
On an English article, the most natural related link is usually the English version of the destination. A Bahasa Melayu article should ordinarily link to the corresponding Malay resource where it exists. If a destination is only available in another language, label that limitation rather than silently switching. Verify the destination URL and visible language, not merely the text of the anchor. The language selector and hreflang annotations serve different technical purposes from contextual editorial links. A bilingual linking audit should inspect both languages independently, including missing translations and links that accidentally cross to the wrong locale.
Links are not a substitute for full answers
A short paragraph that sends readers to five other pages without answering the current question is frustrating. Explain the essential distinction locally, then offer a link for a deeper procedure. An article about mailbox storage should define quotas and consequences before linking to a migration checklist. Similarly, avoid copying entire sections across articles just to manufacture link opportunities. Give each page a clear responsibility and use links to connect complementary explanations. This approach protects the reader from circular journeys where every page points elsewhere but none resolves the original problem.
Avoid arbitrary link-count targets
Google's documentation explicitly says there is no magical ideal number of links on a page. A short contact page may need very few, while a detailed technical comparison may naturally reference several related resources. Assess relevance, readability and whether the link destination is trustworthy. Do not insert the same service link into every paragraph or repeat identical anchors mechanically. Excessive linking can make the main explanation harder to follow. A review should ask whether each link earns its place by helping a reader, rather than whether an SEO tool's numerical target has been met.
Image links need useful alternative text
A linked image may have no visible words describing its destination. Google's link guidance notes that the image alt attribute can function as anchor text in this case. Write alt text that communicates the relevant image or action rather than repeating a generic file name. A logo linking to the home page needs a sensible accessible name, while a diagram linking to a detailed guide should communicate the guide's purpose. Decorative imagery and functional imagery have different accessibility needs. Test the link using a keyboard and an accessibility inspection tool, not only a mouse click.
Broken links and redirects require maintenance
An internal link may stop working when an article is renamed, a service is retired or a route changes. Check for 404 responses, redirect loops, unintended login pages and links to unpublished drafts. A broken-link scan can identify candidates, but inspect the intended destination before automatically replacing URLs. Some redirects are deliberate, and not every reported error is a publishing mistake. Record the affected source page, anchor text, target URL and proposed fix. Retest both English and Malay routes after changes, especially when the site generates navigation from shared templates.
JavaScript navigation needs rendered checks
Some interfaces create navigation only after JavaScript runs. Google can process many rendered pages, but its guidance still recommends ordinary anchors with href values for reliable extraction. A menu item that uses only an onclick handler may fail when scripts are delayed, blocked or unavailable. Inspect the rendered DOM, confirm that the link is focusable and try opening it in a new tab. Do not confuse a visual card with a working hyperlink. A browser test should cover mobile menus and keyboard operation, not only a successful desktop mouse click during development.
Link to authoritative external references appropriately
Internal links connect the site's own explanations; external links can support claims with primary documentation. An article about DNS may link to a related OnHypp guide and separately cite official technical references. Do not imply that an external provider endorses the business merely because its documentation is linked. Check whether the referenced material actually supports the statement. Google does not advise avoiding all external links; it recommends sensible contextual linking. Commercial, sponsored or user-generated links have separate qualification considerations, which should not be confused with ordinary internal editorial navigation.
Prioritize the paths customers actually use
A business owner may arrive on a technical article from search, then need a service-scope explanation or a contact route. Map the most important journeys: discovering a topic, comparing options, checking limitations and finding a next step. Test whether a visitor can complete each journey without guessing which menu contains the information. Avoid making every article a forced sales funnel. Some visitors need only an answer, and a helpful related guide may be the right destination. Measure navigation success through real testing rather than assuming that more links always create more enquiries.
Audit links before release
Prepare a source-to-destination table for each language, recording canonical URLs, anchor text, context, expected response and publication status. Check important pages for incoming links, verify that destinations exist, and inspect rendered HTML for usable anchors. Review accessibility, mobile navigation and any unexpected language switching. Reconcile broken links with approved redirects instead of changing URL architecture casually. An editorial link plan is not a completed live browser test, and a passing word count is not publication approval. Keep the build and release gates intact until independent content, technical and visual reviews are completed.