Our published technical audit lists “broken internal links” next to crawl errors and missing schema, which is where most audits put the things nobody expects to be the problem. It is on that list because on a site with sound architecture and no crawl faults, the link layer is still doing work: Google uses links as a signal for relevance and to find new pages, and its own guidance is that every page you care about should have a link from at least one other page on your site.
Below: what we change, what we leave alone, and where the work stops.
What we actually find
Most link layers are not a strategy. They are a sediment. The related-posts widget someone switched on and never revisited. The nine footer links that exist because the template had nine slots. The “click here” a writer added because the brief said add an internal link. None of it was wrong on the day it happened, and together it produces a structure where the pages that make money are the hardest ones to reach.
The recurring failures:
Pages nobody links to. Your best service page exists, ranks for nothing, and has one link pointing at it from a sitemap. Orphans are easy to miss because nothing on the page looks broken. Sometimes one link resolves it. Sometimes the page is orphaned because the navigation, the template, or the page’s own reason for existing is the actual problem, and the fix depends on which.
Links that fire from the wrong place. A link in the footer and the same link in the third paragraph of a relevant article do different jobs. We treat the first as navigation and the second as a claim about what the target page is for, and we place them accordingly.
Anchors that describe the click instead of the destination. “Learn more” describes the click. The anchor is the one place you get to say, in your own words, what is on the other side, and spending it on two generic words is a decision even when nobody made it deliberately.
Links that survived the content that justified them. A page gets rewritten, the link stays, and now a paragraph about pricing points at an article about neighborhoods. Nobody notices because nobody re-reads their own links.
Broken links and structural concerns can surface during the free technical audit, which is where the published scope puts them. A page-level internal-link review, meaning the orphan list, the source-to-target recommendations, the anchor changes and the implementation order, is included when the written scope names it. Our team works the same way on the UX layer: the audit says which findings sit inside the offering and which sit outside it, before anyone starts work.
Where linking sits, and what it cannot fix
This is the part that decides whether link work is worth buying, so we would rather put it above the sales pitch than below it.
Internal linking sits on top of your information architecture. Architecture is the structural layer: hierarchy, URL paths, navigation, whether the system survives the next hundred pages. Links are the decisions you make inside that structure about what connects to what.
The order matters commercially. If your hierarchy buries service pages four levels deep, contextual links from relevant pages can shorten the discovery path. They do not repair the hierarchy that created the problem. Rebuilding the architecture is a different engagement than optimizing links inside a sound one, and you should know which one you are buying before you buy it, which is why we name it in the audit rather than in the invoice.
The same boundary applies downward. If Google cannot crawl or properly process the page, internal linking cannot remove that technical barrier, which is why technical fixes come first in our audit sequence rather than after.
So the honest scope of link work is smaller than the sales version: it can improve discovery paths, clarify how your existing pages relate to each other, and reinforce which ones the site itself treats as priorities. It cannot make a weak page valuable or repair an architecture that is wrong underneath. That is worth real money. It is not worth what someone will charge you for it if they let you believe it is the whole job.
The Nashville-specific part
Our SEO practice is built on the premise that Nashville neighborhoods do not behave like one market. For linking, that premise has a specific consequence.
A Nashville business with both a service dimension and a place dimension faces an obvious temptation: link everything to everything, every neighborhood page to every service page, on the theory that more connections mean more relevance. What that produces is a site where every page claims to be about everything, which is functionally the same as claiming to be about nothing.
The decision we make instead: nothing links to everything by default. The map follows the services actually offered at that location, the paths customers actually take, the intent behind the query, and whatever geographic demand data your business can support. A Green Hills page may link to another location when a reader has a real reason to compare the two. It should not do so to make the link graph denser.
That means we have to know which industries cluster where before we build the map. That knowledge is why our SEO work is organized around neighborhoods instead of a single city keyword, and it is the part a national agency cannot reconstruct from a spreadsheet.
The lines we hold on link work
No link counts. Google puts it plainly: there is no magical ideal number of links a page should contain. A quoted number per page is a deliverable that is easy to invoice and unrelated to whether the right pages get found.
No forced reciprocity. Pairing every page with its mirror to make a diagram look symmetrical is decoration. Two pages point at each other when a reader on either one would want the other, and not because a diagram looked lopsided.
We will not stuff the footer. Footer links are navigation. Treating them as a ranking instrument is how sites end up with two hundred links on every page and no page that clearly means anything.
When implementation and measurement are in scope, we document the source page, the target, the anchor, the date, and whatever metrics the scope requires us to watch afterward. That record shows what changed and what followed. It does not pretend one link was the only cause.
Where this ends up
The link layer is often less disruptive to change than hierarchy or template architecture, which is what makes it worth evaluating early when the structure underneath is already sound. Many contextual fixes need no rebuild and no new content. Navigation, footer, breadcrumb, and template problems are different: when the link problem originates there, the scope has to include the structural layer rather than pretending body-copy edits will reach it.
When internal-link work is included, the proposal states whether we are auditing the structure, implementing the changes, or coordinating with your existing developer, and its timing depends on whether crawlability, architecture, or another constraint has to be resolved first. If the audit finds the architecture is the real constraint, the recommendation becomes the rebuild, even though linking is the cheaper sale. Nick Rizkalla makes those calls himself, month to month.
Send us the URL. The free audit can flag whether broken links, weak page discovery, or site structure deserves deeper investigation. If a page-level internal-link map turns out to be what you need, the scope will name which pages, which link types, and how much implementation it covers. Or call him at (615) 988-1309.
Rank Nashville, 615 Main Street, Suite 123, Nashville, TN 37206, (615) 988-1309