imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Check that pages can be found without a sitemap.

An internal-link review should show how someone reaches a page and why the link is useful. Start with crawlable HTML links and follow the path from hub to topic and next decision. A sitemap does not replace information architecture.

From published resource to relevant route

  1. Find

    Map actual HTML links from the site.

  2. Understand

    Assess why someone should follow the relationship.

  3. Try

    Follow the link to the right content and language.

Separate discoverability from relevance

A resource may be technically reachable through a single footer link without helping anyone understand its context. Conversely, an attractive control may lack a usable address. Review needs both technical evidence and editorial judgement.

Collect ordinary HTML links and destinations from the built website. Verify internal addresses reach the intended resources. Then start from the homepage and traverse the network. A published page found only in the sitemap needs a justified route from other content.

Sketch a small topic network

Choose a service, a commissioning guide and an implementation guide. Explain when each is useful. The service can link to preparation material, while the guide can identify help for readers who do not want to carry out the work themselves.

Do not link everything to everything automatically. A related resource should genuinely answer the next question. Too many equivalent cards can make the decision harder even when every URL is technically valid.

Link typeQuestion
Topic hubIs there an understandable route to the resource?
Contextual linkDoes the destination answer a useful follow-up?
BreadcrumbDoes it reflect a real parent structure?
Related resourceDoes it support the reader’s next decision?

Read the wording and destination together

Anchor wording should create an accurate expectation. A generic click here becomes unclear when links are read separately. Conversely, keyword-heavy wording can damage the sentence. Choose what helps the reader understand the resource.

Open the link and assess its destination. HTTP 200 can still show the wrong subject or language. Contextual links should normally use the appropriate language version. A language-selector fallback is a separate navigation decision, not a way to pretend a missing explanation exists.

Test improvements without filling the footer

Choose a resource previously hard to find and add a useful link from an existing topic. Ask a colleague to follow it and explain why the destination is the next step. Recheck the network afterwards. Keep the main navigation focused and use hubs and context rather than hundreds of footer links. Record each page’s intent; a new relationship should improve understanding, not hide two resources competing for the same task. Retain evidence of the change so later editors understand the connection.

Sources and further reading

Questions, answered

Does a sitemap make a page complete?

No. It may support discovery but cannot replace usable navigation and ordinary HTML links.

Should every page link to every other page?

No. Choose relationships around the reader’s question and avoid mechanical mass linking.

IMBAHUB

What would you like to make possible?

An internal-link review should show how someone reaches a page and why the link is useful. Start with crawlable HTML links and follow the path from hub to topic and next decision. A sitemap does not replace information architecture.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.