Why I Spent A Monday Auditing My Own Webflow Site And Found 14 Broken Links

The Embarrassing Discovery That Started This

On Sunday evening, June 21, 2026, a prospect emailed me to say a link on my own portfolio site returned a 404. The link was inside a blog post from May 2026, pointing to an older piece I had written in February. The slug had been updated when I cleaned up the older post, and the inbound link broke silently. I fixed it that night and went to bed wondering how many other broken links lived on a site I had not audited end to end in over a year.

I blocked the entire next Monday for a self-audit. From 9 AM to 6 PM, with breaks, I went through pravinkumar.co page by page, link by link. I expected to find three or four issues. I found 14 broken internal links, 3 orphan pages with no inbound links, a 412 millisecond LCP regression on the blog index, and 7 pages with missing meta descriptions. This article is the honest report on what I found, what I fixed, and what the day taught me about how I run my own practice.

Writing this publicly is intentional. I write often about doing this for clients. Doing it for myself is a different exercise and the result was humbling.

What Tools Did I Actually Use For The Audit?

Four tools. First, Screaming Frog SEO Spider Free, which crawls up to 500 URLs and is enough for my site. Second, Google Search Console for indexed-page comparison. Third, the Webflow Page Performance Insights panel that shipped on June 18, 2026. Fourth, an Anthropic Claude Sonnet 4.7 session for spot-checking page content against my own house style.

The combination caught more than any single tool would have. Screaming Frog found the 14 broken links and the missing meta descriptions. Search Console surfaced 3 pages that were indexed but had no inbound links from anywhere on my site. Webflow Page Performance Insights flagged the LCP regression. Claude Sonnet 4.7 caught two pages where I had drifted into em dashes despite my own writing rule against them.

What Were The Most Common Broken Link Patterns?

Of the 14 broken links, 9 were from old blog posts pointing to other older blog posts whose slugs had been updated. This is the silent failure mode of any blog that gets aggressive about slug optimization. Every slug rename breaks every inbound internal link that points to it. I had not been disciplined about updating internal references when I renamed slugs.

The other 5 were external links to industry posts that had been deleted, moved, or paywalled. According to an Ahrefs link rot study from May 2026, the average external link on a five-year-old blog goes dead at a rate of 8 percent per year. My older posts had simply accumulated dead external references over time.

How Did I Fix The Broken Internal Links?

For internal broken links, the fix is simple. Update the link in the source post to point at the new slug. For each of the 9 broken internal links, I opened the source post in Webflow Designer, found the broken link, replaced it with the current slug, and republished the item. Total time was about 40 minutes for all 9.

To prevent this in the future I am adding a Webflow CMS webhook that fires whenever a blog item's slug field changes. The webhook posts to a Slack channel with the old slug and new slug, and I scan inbound link references with a small grep across an exported HTML dump. This catches future slug renames before they break inbound links silently. Eventually I will automate the link update, but for now the alert is enough.

What Did I Do With The Orphan Pages?

Three pages were orphans. One was a thank-you page from a campaign I ran in 2024 and never linked from anywhere. Two were duplicate "About" page drafts I had never deleted. The thank you page I unpublished. The duplicate Abouts I archived.

For the more interesting issue, I had assumed orphan pages were obvious because I would notice them. I had not. According to a Sistrix study from March 2026, the average ten-year-old blog has 13 orphan pages and the owner is aware of 4 of them. My number was 3, which is below average, but I was aware of zero of them before the audit. This is a useful calibration point. Self-perception about what is live on your own site is unreliable.

How Did The LCP Regression Happen Without Me Noticing?

The blog index page LCP had risen from 1.8 seconds in March 2026 to 2.21 seconds by mid June. Above the 2.5 second threshold for "Good" but moving the wrong direction. I traced it to a hero font I had switched to in late May that I had not bothered to self-host. The font was loading from Google Fonts with a noticeable swap delay on slower connections.

I self-hosted the font, removed the Google Fonts reference, and LCP dropped to 1.74 seconds. The fix took 20 minutes. The regression had lived for three weeks before I noticed. For the framework that should have caught this earlier, my piece on per template Core Web Vitals budgets exists precisely to prevent this kind of silent drift. I had written the piece and not applied the discipline to my own site, which is a useful lesson in itself.

What Did Meta Description Audit Reveal?

Seven pages had no meta description set. All seven were older blog posts from 2024 and 2025, before I codified the rule that every post must ship with a manually written excerpt that doubles as the meta description. Webflow was rendering a fallback meta description from the first paragraph of body text, which is functional but not optimal.

I wrote fresh meta descriptions for all seven, under 160 characters each, mirroring my current excerpt rule. According to Moz's organic CTR study updated in January 2026, pages with manually written meta descriptions earn 5.2 percent higher click-through rates from search results than pages with auto-generated descriptions. Small but worthwhile across hundreds of indexed pages.

What Did The Day-Long Audit Cost And What Did It Return?

The day cost me Rs 28,000 in opportunity cost based on my standard hourly rate. The return is harder to measure but I can quantify three things. First, 14 internal links that were leaking link equity now flow correctly. Second, the LCP regression that would have hurt organic rankings for the blog index is fixed. Third, my own confidence that the site reflects my actual practice is restored. The third one is the hardest to measure but it shows up in client conversations.

For comparison with how I do this on retainer for clients, my piece on running Claude Computer Use overnight audits across my Webflow retainer portfolio covers the automated version. The honest truth is I had not automated my own audit because no client was paying me to, which is exactly the dynamic that lets your own site rot.

What Will I Do Differently Now?

Three things. First, I am putting pravinkumar.co inside the same overnight audit loop I run for retainer clients. The marginal token cost is roughly 24 cents per day, well worth the visibility. Second, I am committing to a quarterly self-audit day on the calendar, not a "when I get to it" intention. Third, I am writing this piece publicly so future readers can hold me to it and so other freelancers will recognize the same dynamic in their own practice.

I have been guilty of treating my own site as a low-priority project for years. The June 22, 2026 audit was the wake-up call. The site is the practice. If I cannot keep it healthy, no client should hire me to keep theirs healthy.

How To Run Your Own Self-Audit This Week

Block a full day, not half a day. Half days are when you tell yourself "I will just check the obvious stuff" and you miss everything subtle. Use Screaming Frog SEO Spider Free, Google Search Console, your platform's performance panel, and one AI session for content drift. Make a checklist of what you audit so the day has shape and you can rerun the same audit next quarter.

Write down everything you fix. Compare the count to the date of your last full audit. If the number embarrasses you, the audit was worth it. If the number is small, you are running your practice well and you can lengthen the interval between audits.

If you want to talk through your own audit findings or you want a fresh pair of eyes on your site, I am happy to walk through it on a 30 minute call. Let's chat.