Two numbers sum up the last few months at Lindsey Web Solutions: 73 and zero. Seventy-three published blog posts that vanished from our website and had to be recovered. Zero inbound links pointing to one of the most commercially important posts on our entire site. This is the behind-the-scenes story of how our Columbus, OH web design agency lost most of its content archive, got it back, and then audited every internal link we had — because publishing great content is only half the job. The other half is making sure Google and your readers can actually find it.
We’re sharing this publicly for a reason. Every week we talk to small business owners whose websites have the same invisible problems: posts that 404 for no obvious reason, orphaned pages no one links to, and anchor text that tells Google nothing. If it can happen to a web agency, it can happen to anyone. Here’s exactly what went wrong, what we found when we audited our own site, and the playbook we now run after every migration.
How 73 Blog Posts Went Missing (and How We Recovered Them)
The short version: during a replatforming project — moving our front end from a traditional WordPress theme to an Angular build that reads from WordPress as a headless CMS — the two systems fell out of sync. The posts were still sitting in our WordPress dashboard with a published status, but the URLs that served them returned 404 errors. Visitors and Google’s crawlers hit a dead end while the content looked perfectly healthy from the admin side. We covered the general mechanics of this failure mode in our guide on why WordPress blog posts go missing and how to recover them, and we can confirm from painful experience: it is every bit as sneaky as it sounds.
The recovery itself was a structured rebuild — re-exporting the WordPress content, regenerating the static site, and redeploying. The restore shipped with our rev23 deployment on September 26, 2026, and brought back 73 published posts. A post-restore verification pass confirmed the fix held: our XML sitemap went from listing only a handful of static routes to 98 URLs, including 65 of the 73 restored posts with correct lastmod dates — the metadata Google uses to schedule recrawls.
But getting the posts back online was step one. Step two was the question nobody wants to ask after a migration: did anything else break along the way?
What Our Internal Link Audit Found
An internal link audit maps every page on your site, counts the links pointing into and out of each one, and flags anything orphaned, broken, or misaligned. We ran ours with a crawl of the restored site, Google Search Console data, and manual spot-checks (our own WebsiteLinter tool handles the technical and crawl-error side of this). The findings were uncomfortable in exactly the way useful findings should be:
| Finding | Location | Why it mattered | Fix |
|---|---|---|---|
| Post 1022 (“What Skipping Website Maintenance Actually Costs Your Small Business”) had zero inbound links — a true orphan | /website-maintenance-costs-small-business/ |
Our best maintenance-related conversion content was invisible to Google’s link graph and unreachable from any other page | Wove it into the maintenance-costs topic cluster with descriptive anchor text from 4 sibling posts |
| Post 947 (our ADA compliance pillar) had zero correct inbound links | /ada-compliant-website-columbus-ohio/ |
A pillar page with a live legal deadline (the DOJ’s April 2027 web accessibility rule) was getting no crawl equity | Re-pointed links to the live URL immediately rather than waiting for a pending backfill post |
| Posts 946 and 962 linked to a broken “-guide” URL variant of post 947 | /ada-compliant-website-columbus-ohio-guide/ (404) |
Two ADA cluster posts funneled readers and crawlers to a dead end | Corrected anchors to the canonical post 947 URL |
| ~30 broken links across the restored archive | Restore-era slug changes (e.g., /about/ → /about-us/) |
Every 404 is a wasted crawl and a dead end for readers | Full slug-mapping pass; corrected or redirected each URL |
The pattern is the important part: none of these were content problems. Every post involved was well-researched and genuinely useful. They were architecture problems — the connective tissue had been severed during the restore while the content itself survived intact.
Why Orphaned Content Quietly Kills Organic Traffic
We’ve seen this movie before, and we have the data to prove the plot. In May 2026, before our first internal-linking sprint, our Google Search Console showed a sobering figure: 1 click from 73 impressions across 28 days — spread across dozens of published posts. We had the content library; we had zero architecture. You can read the full breakdown in our internal linking sprint case study, where we rebuilt 84 isolated posts into four connected topic clusters.
The mechanism is straightforward. Google’s crawlers discover and rank pages partly through links. An orphan post — one with zero inbound internal links — sends a signal that the site itself doesn’t consider the page important, and crawlers reach it rarely or never. PageRank enters your site through its strongest pages and flows along links; when a post has no links pointing to it, that flow stops dead. The post can sit published for months, occupying space in your CMS and contributing nothing to your traffic or your lead pipeline.
Imagine a local restaurant that publishes a beautiful catering menu page but never links to it from the homepage, the navigation, or a single blog post about holiday party planning. The page exists. It might even rank someday by fluke. But every internal signal tells Google — and every real visitor — that it doesn’t matter. That’s what an orphan post is, and that’s what post 1022 was for us: one of our most conversion-relevant articles, completely disconnected from the site built around it.
And the stakes compound when the topic is time-sensitive. Our ADA cluster was linking to a 404 while the Department of Justice’s April 2027 digital accessibility deadline is actively driving search interest. Leaving broken links in place for weeks would have wasted crawl equity on a dead URL during the exact window the topic matters most — which is why we re-pointed the live links first and scheduled deeper restructuring for after review.
The Playbook: Topic Clusters, Anchor Text, and Money-Page Bridges
Here’s the exact five-step process we now run after any migration, restore, or major content push:
- Inventory and crawl everything. Export every published URL, run a full crawl, and record inbound-link counts per post. Anything with zero inbound links gets flagged as an orphan candidate on day one — not discovered by accident three months later.
- Assign every post to a topic cluster. A cluster has a pillar page (the broad, authoritative hub) and spoke posts (specific angles). We mapped our archive into clusters like website maintenance costs — where post 1022 now anchors several spokes — and ADA website accessibility, where post 947 is the pillar. Every spoke links up to its pillar and sideways to related spokes.
- Align anchor text to the target query. “Click here” and “read more” tell Google nothing. Each link’s anchor text should describe what the destination page is about, using the language people actually search. This was a dedicated editorial pass, not an afterthought.
- Bridge every cluster to a money page. A money page is where a visitor becomes a lead. Each cluster now links contextually to a relevant conversion page — our services overview, our website maintenance plans, or our free website audit. Blog traffic that can’t convert is a missed opportunity; the bridge is what turns a reader into an inquiry.
- Re-crawl and verify. After the fixes, re-crawl to confirm zero 404s remain, regenerate the sitemap so every restored post carries a fresh lastmod date, and watch Search Console for recrawl activity over the following weeks.
None of this requires new content. It requires treating the content you already own as a system instead of a pile.
How to Run This Audit on Your Own Site
If you suspect your site has the same problems, you don’t need an agency to start. This checklist covers the core of what we did:
- Crawl your site with any SEO crawler (Screaming Frog’s free tier handles small sites) and export every URL with its response code.
- Flag every 404 and 301 chain an internal link points to — if you moved pages during a redesign, this list will be longer than you think.
- Sort pages by inbound internal links. Anything at zero is an orphan. Prioritize orphans that target your most valuable keywords.
- Group posts into clusters around your three to five most important service topics. One pillar page per cluster; spokes link up and across.
- Rewrite generic anchors (“learn more”) into descriptive ones that match the destination’s focus keyword.
- Audit anchor destinations — click every internal link on your top ten traffic pages and confirm it lands where it should.
- Add one money-page bridge per cluster, linking contextually from your highest-traffic post in that cluster to the relevant service or contact page.
- Regenerate your sitemap and confirm every published post appears with a current lastmod date, then request a recrawl in Search Console.
For a business like yours — say, a Columbus-area contractor with thirty blog posts and a contact page that barely gets internal links — this checklist typically surfaces a dozen quick wins in a single afternoon.
What We’d Do Differently Next Time
The honest post-mortem: the restore worked, but the audit should have started the day after the migration, not weeks later. Our lessons, now baked into our process:
- Build a 301 redirect map before any replatform, not after the first 404 report. Slug changes during a restore are where broken links are born.
- Crawl-diff old versus new within 48 hours of cutover. Comparing pre- and post-migration crawls catches orphaned posts and dead links while the context is fresh.
- Regenerate the sitemap as part of the deploy, not as a follow-up ticket. A sitemap that lists 8 URLs for a 90-page site tells Google to ignore 90% of your work.
- Treat internal links as a scheduled maintenance task, like plugin updates — not a one-time project. Content drifts; links rot.
That last point is really the thesis. Website maintenance isn’t just uptime and security patches — it’s keeping the architecture that lets your content work. That’s the philosophy behind our breakdown of what skipping maintenance actually costs, and it’s why post 1022 is the post we refused to leave orphaned.
Get Your Own Internal Link Audit
If your site has been through a redesign, a migration, or years of unplanned blog growth, there’s a decent chance it’s carrying the same invisible baggage ours was — orphaned pages, broken anchors, and clusters that never got connected. Contact Lindsey Web Solutions for a free consultation, or run your URL through our free website audit to see what a structured crawl turns up. We’ll show you what the 73-and-zero lesson looks like on your own site — and how to fix it before it costs you another quarter of organic traffic.