Gerris home
Gerris

Chris Abraham: technical consulting, AI tools, and technical SEO

Home › Services › Internal Linking

Internal linking strategy and implementation

A website can have excellent pages that barely acknowledge each other. The useful explanation sits in the archive, the service lives three sections away, and the case study never reaches the person considering that service. I connect those pieces with relevant text links, understandable anchor wording, and destinations that work.

Use the material you have already paid to create

An established site contains years of work: answers to customer questions, specialist knowledge, product details, and evidence from completed projects. Linking that material thoughtfully can make the whole collection more useful. The work starts inside your existing site, with the routes you control and the pages your team already maintains.

Decide which pages should support which decisions

I identify the journeys that matter to the business. Someone researching a problem may need an explanation, then an example of the work, then the relevant service. A buyer comparing products needs clear category routes and helpful supporting information. Those paths become the starting map, and crawl data shows where the published site currently makes the journey difficult.

What the review covers

Make a change list people can use

Each recommendation identifies the source page, the destination, the proposed location, and the reason for adding the connection. Editorial links go to the content owner. Component changes go to the developer with examples and acceptance criteria. If the same issue appears across thousands of generated pages, I investigate the template or route data so the remedy can be applied consistently.

Build context around the important destination

A service page can link to evidence that helps somebody judge the offer. A technical article can point to the practical next step. A long reference page can offer a link to an exact section elsewhere, provided the target exists and remains stable. These are small edits, but they should be decisions about what the reader needs, not automatic replacements of every matching word in the database.

Evidence behind the approach

My React event platform case involved a discovery problem affecting roughly 2,000 event pages. That is a reminder to examine the links an application actually provides, alongside its visible design. On a large archive or a programmatic site, finding the missing connection can be more useful than writing another page nobody can reach.

Implementation and acceptance

I can add the agreed links where access allows, or provide a precise implementation map for your team. A new crawl checks the published connections and the pages they lead to. The verification record names the changed templates and editorial pages, while later reporting follows the search behavior of the priority destinations. Results are reported against the work observed and the question the project set out to answer.

Planning a linking project

Does the whole website need reviewing at once?

No. A useful first project can focus on a service family, a content archive, or a particular product category. The scope names the inventory and the priority destinations.

Can an agency use the plan with its own editors?

Yes. The proposed placements and destinations can be delivered as a working list, with developer changes separated from copy additions and a final check after publication.

This work fits alongside on page SEO, large site SEO, and agency support. Tell me which pages visitors should be finding and I can scope a practical starting point.

Updated