Vlogger on holiday / the SEO field guide
The 404 detour.
Follow the evidence.
To measure the impact of broken internal links, record which reader journeys fail, repair the links, then compare the same pages and metrics over comparable periods. Start with a repeat crawl. Use Search Console and GA4 to investigate what happened afterward, while keeping other changes in view.
A working link is a better route through your content. A traffic increase is a separate result that needs evidence. This guide shows how to tell those two stories clearly.
By Dawid Lisowski · SEO hobby expert, blogger and traveler
Source check for this draft: 10 October 2026 · The holiday story and
all example figures are fictional.
A holiday vlog sends a reader to a dead end
Imagine a travel creator filming a sunrise walk along the waterfront. The video description sends viewers to a weekend itinerary on the creator’s blog. Halfway down that article, a link promises a practical camera-packing checklist. The reader taps it and reaches a “page not found” screen.
The vlog did its job: it sparked interest. The itinerary did its job: it made the next question obvious. The broken link interrupted the handoff. That moment gives the investigation a useful focus: can a reader get from the itinerary to the promised checklist?
Now translate the scene into an audit. Record the source article, its exact anchor text, the destination URL and the response. Look for every other post that points to the same missing destination. One deleted checklist might create several broken link occurrences.
For the wider architecture, use the blog’s guide to internal-link structure. Here, the task is narrower: measure a specific failure and check whether the repair restores a useful route.
Keep the diagnosis precise. A 404 response means that URL was not found. It does not establish a site-wide ranking penalty. Google explains that it does not index content returned with a 4xx status; that is different from claiming one broken link damaged every page. See Google’s HTTP-status guidance.
Capture a baseline you can repeat
Before editing, export a crawl and keep the settings with it. Include the source URL, destination, anchor text, HTTP status, final URL after redirects and the date checked. Separate unique broken destinations from broken link occurrences; the two counts answer different questions.
Record your crawl’s scope. A sitemap gives you a useful URL inventory, but it is not the complete link graph and can omit older or unlisted pages. Crawl from the homepage as well, then compare the discovered URLs with the sitemap. State any limits, such as blocked pages, crawl caps or a mobile-only version.
Choose a before-period and a follow-up period that use the same length and weekday mix. For example, compare 28 days before the repair with 28 days after it, while recording deployment day separately. That is a practical reporting convention, not a guaranteed timetable for search changes. Low-traffic pages may need a longer observation period.
Keep a short change log
- Repair: the source pages, old destinations, new destinations and publication time.
- Other edits: title changes, new content, navigation updates and tracking adjustments.
- Outside context: a new holiday vlog, a promotion, seasonal travel demand or a search update.
- Measurement setup: report filters, timezone, channel grouping and event definitions.
Use the blog’s traffic and CTR reporting guide as a related discussion. Keep your actual exported reports alongside the repair log so another person can inspect the comparison.
Measure broken internal links at four levels
1. Technical repair
Count confirmed broken occurrences before and after. Check that the intended destination loads, that the final content matches the anchor, and that in-page fragments land on an existing heading.
2. Reader journey
Where tracking exists, measure visits from the itinerary to the checklist and whether readers complete a useful next step. A crawler cannot tell you how many people clicked a link.
3. Search performance
Monitor affected pages in Search Console. Compare search clicks, impressions, CTR and average position with consistent filters. These are search-result metrics, separate from on-site link clicks.
4. A meaningful outcome
Choose a reader or business goal: reaching a helpful guide, downloading a checklist or submitting an inquiry. Report the count and rate together. More page views alone do not prove that goal improved.
Use GA4 engagement and bounce rate correctly
In GA4, bounce rate is the share of sessions that were not engaged. An engaged session meets a duration, key-event or page/screen-view condition. Read Google’s GA4 engagement and bounce-rate definitions and document the settings used in your property.
A reader can find a complete answer on one page. Another reader might open several pages because the navigation is confusing. Interpret engagement with the page’s purpose rather than assuming every decrease in bounce rate is a success.
Check what your tracking actually records
Do not assume GA4 automatically counts every internal-link click. If a custom event is needed, configure and test it before the baseline, record its definition and keep it consistent. Do not send personal information in event parameters. If tracking was absent before the repair, you cannot reconstruct a reliable historical click count afterward.
Use Search Console’s Performance report documentation to distinguish search CTR from internal-link click-through rate. If you define a custom internal-link rate, specify both the numerator and denominator—for example, clicks on that link divided by measured views of its source article.
Repair the destination and the reader’s expectation
- Check the intended destination. Correct a typo, restore a useful deleted page, or replace the link with a genuinely equivalent guide. If no useful destination exists, remove the link and revise the sentence.
- Update the source link directly. A moved page may need a permanent redirect, but update your internal links to the final canonical destination too. Avoid a chain of unnecessary hops.
- Keep the promise in the anchor text. “Camera-packing checklist” must lead to a camera-packing checklist. A working link to an unrelated homepage still fails the reader.
- Repeat the crawl and the human test. Use the saved crawl settings. Open each repaired route on mobile and desktop, and check keyboard navigation and fragment targets.
The blog’s
broken-link repair workflow
covers the wider maintenance task. For the link itself, follow
Google’s guidance on crawlable links and descriptive anchors:
use a real anchor with an href and words that explain
the destination.
Prioritize failures on important reader routes rather than fixing URLs in alphabetical order. A dead link from a popular itinerary to its next-step guide deserves attention before an unused reference with a clear alternative already nearby.
Blogger note: edit the source post in HTML view and use the full destination URL. If a post moved, check Blogger’s Custom redirects settings and test the result. Keep this article’s existing permalink when refreshing its body.
Use the internal-linking mistakes checklist to look beyond status codes: vague anchors, irrelevant destinations and poor navigation can also interrupt the journey.
A worked example: the route improves, attribution stays open
Fictional teaching example: the creator finds 12 broken internal-link occurrences across five source pages. The figures below are invented to demonstrate calculations. They are not measurements of this blog or evidence of an SEO uplift.
The repeat crawl finds no remaining broken occurrences in the same audited scope.
Search clicks rose from 250 to 280. That observation alone cannot identify the cause.
| Measure | Before | After | Change |
|---|---|---|---|
| Broken internal-link occurrences | 12 | 0 | 12 repaired |
| Search impressions | 10,000 | 10,000 | No change |
| Search clicks | 250 | 280 | +30 / +12% |
| Search CTR | 2.5% | 2.8% | +0.3 percentage points |
| GA4 organic-search sessions | 400 | 420 | +20 / +5% |
| GA4 engaged organic-search sessions | 240 | 273 | +33 |
| GA4 organic-search engagement rate | 60% | 65% | +5 percentage points |
Search Console and GA4 measure different activity. Their click and session counts are not expected to match exactly. No internal-link click data is supplied in this example.
Show the arithmetic, then explain the limit
Relative change in search clicks = (280 − 250) ÷ 250 × 100 = 12%
CTR change = 2.8% − 2.5% = 0.3 percentage points
Engagement rate after = 273 ÷ 420 × 100 = 65%
The strongest finding is direct: the repaired routes work within the audited scope. Search clicks and engagement also increased in the fictional follow-up period. A new vlog, changed query mix, seasonality or unrelated edits could help explain those changes.
We cannot claim the checklist received more internal clicks because that metric was not collected here. Naming a gap in the data makes the story more useful than inventing an explanation.
Separate a verified repair from a possible SEO effect
A useful voiceover would say: “We fixed 12 broken routes and verified each destination. Search clicks were higher in the follow-up period. We are continuing to track the affected pages because that increase may have several causes.” It reports the result without giving the repair credit it has not earned.
Compare affected pages with a similar group you did not edit, where possible. Look for comparable topics, traffic levels and seasonal patterns. This provides context, but an unmatched before-and-after comparison is not a randomized experiment. Report counts and repeat observations rather than treating one small fluctuation as conclusive.
Publish evidence readers can inspect
- A redacted crawl excerpt showing source, old destination, status and repaired destination.
- A dated repair log and comparable report exports, with filters explained.
- An original screenshot of the reader’s route, with private data removed.
- A conclusion that separates observations, interpretation and unresolved questions.
These materials can demonstrate real work. Decorative trust badges, invented case studies and unsupported E-E-A-T scores cannot replace them. Google’s people-first content guidance encourages clear sourcing and identifiable authorship; it also explains that E-E-A-T itself is not a specific ranking factor.
For future publishing, the blog’s travel-camera blog audit example discusses automated checks. Treat any numerical audit score as that tool’s rubric and inspect whether each anchor actually matches its destination.
A plain-English SEO glossary
Follow a glossary link from the article to jump to a definition.
- 404 / Not found
- A server response indicating that the requested URL was not found. Confirm the HTTP response rather than relying only on the page’s visible error message.
- Canonical URL
- The preferred URL for a page when equivalent versions exist. Use a consistent destination in internal links. A canonical declaration is a signal, not a redirect.
- Link equity
- An SEO shorthand for value associated with links. It is not a currency or a directly measured GA4 metric. The blog’s link-equity explainer discusses the concept.
- Search CTR
- Search clicks divided by search impressions, expressed as a percentage. It describes a search-result interaction rather than a click between two blog posts.
- Percentage points
- The arithmetic difference between two percentage values. Moving from 60% to 65% is an increase of five percentage points, approximately an 8.3% relative increase.
- Confounder
- Another factor that could help explain a result, such as a new video release, changed tracking or seasonal demand. Record it before attributing a traffic change to your repair.
Frequently asked questions
Do broken internal links automatically lower every page’s rankings?
No. A broken destination and an interrupted reader journey need attention, but a 404 does not establish a site-wide penalty. Verify the affected routes and examine page-level data before making a ranking claim.
Which result should I verify first after fixing the links?
Repeat the crawl and manually open the repaired routes. Confirm the final response, the destination’s relevance and any fragment target. Search and engagement reports answer follow-up questions.
How long should the before-and-after comparison be?
Use comparable periods long enough to capture meaningful activity. Two 28-day windows are a practical starting point because they include the same weekday mix. Low traffic, seasonality and delayed discovery can require a longer follow-up.
Can GA4 show how often readers clicked a broken internal link?
Only if appropriate tracking captured that interaction. Check your implementation and test any custom event. Historical internal-link clicks cannot be reliably reconstructed from page views alone.
Should every missing page redirect to the homepage?
No. Restore useful content or redirect a moved page to an equivalent destination. If no relevant replacement exists, remove the broken source link and revise its context. An unrelated homepage usually fails the original promise.
Will colorful cards and a glossary improve E-E-A-T?
They can make a guide easier to read and use. Evidence comes from accurate explanations, clear sources, identifiable authorship and real documented work. Styling does not demonstrate a firsthand audit or guarantee search visibility.
Check the journey before the next vlog goes live
Open the itinerary, follow its most useful next-step links and note any mismatch between the anchor’s promise and the destination. Save a crawl, repair the failures and repeat the same check. Then monitor search and reader outcomes with the limits of your data visible.
Start with one important route and build a repeatable routine. The web-link manager essentials guide is a useful next read for organizing that maintenance. A clear path to the promised answer is a result you can verify before the next holiday upload.