Broken Links and What to Fix — Rebuilding Project

Date: 2026-06-06 Type: Audit / action list only. Nothing was changed, no git, no edits to any page. Scope: (1) Our deliverables dashboard detail pages on annettethompson.com, and (2) dead/wrong links on Bob's live rebuildingseminars.com site (from the prior link-check audit).

Executive summary (3 lines)

1. Part 1 (our deliverables dashboard): 0 broken detail pages. All 22 renderable deliverable detail pages currently serve real content (all 5 PDFs resolve as real PDFs; all 17 markdown/multifile pages render real document text). The "not available in the current build" notice does not appear on any of them. Two low-priority housekeeping notes only (1 privacy leak on the icp page, 3 renderable pages not surfaced on the dashboard).
2. Part 2 (Bob's live rebuildingseminars.com): 6 link fixes across 3 pages. 4 dead 404s on the parenting-support page (each maps to one of Bob's 4 new internal articles, which are on HOLD pending his proofread), 1 redirected legal/financial link to update, and 1 mis-typed Facebook link on the audited resource page (plus 1 cosmetic email-decode 404, low priority).
3. Net: the dashboard is healthy; the actionable fixes all live on Bob's owned site, and 4 of the 6 are gated on the new articles being proofread and published first.

Part 1 — Our deliverables dashboard (annettethompson.com/rebuilding/deliverables/)

Dashboard: https://annettethompson.com/rebuilding/deliverables/ Detail template: C:\Users\annet\ClaudeProjects\AnnetteThompson\src\pages\rebuilding\deliverables\[slug].astro Dashboard source: C:\Users\annet\ClaudeProjects\AnnetteThompson\src\pages\rebuilding\deliverables\index.astro

Method

• Enumerated every slug [slug].astro can render (the DOC_ENTRIES array, 22 slugs).
• Fetched every live detail URL https://annettethompson.com/rebuilding/deliverables/<slug>/ (curl, UA Mozilla/5.0) and checked each for the literal "This document is not available in the current build environment" notice vs. a real pdf-embed iframe or a populated doc-body.
• For the 5 PDF pages, additionally HEAD-checked the underlying publicPath PDF (/rebuilding/docs/*.pdf) to confirm the embedded file actually resolves (an iframe pointing at a missing PDF would still be broken for the reader).
• Spot-extracted the rendered text of several markdown pages to confirm it is the real document, not an empty shell.
• Cross-referenced the dashboard's link list against the renderable slug list to find orphans or links pointing at non-renderable slugs.

Key finding (changes the premise)

The premise that "most slugs show the not-available notice" is no longer true as of this check. The external docs folder content is present in the live build: every markdown page renders real text and every PDF resolves. The site-audit slug (recently fixed by inlining its content) is OK, and so is every other slug. Nothing needs the "inline it like site-audit" treatment right now.

How each slug gets its content (from [slug].astro)

• 5 PDF slugs (available = does the file exist in the docs dir; the page embeds publicPath from /rebuilding/docs/): audit-report, brand-voice, combined-for-bob, social-starter-pack, email-sequence-review.
• 1 inlined-HTML slug (content hard-coded in the page, build-independent): site-audit.
• 15 markdown/multifile slugs (read from the external RebuildingDocs folder via REBUILDING_DOCS_DIR, falling back to ../RebuildingDocs; if the file is missing they would show the notice): cover-email, gap-analysis, proofreading-log, trademark-evidence, icp, master-strategy, local-seo-strategy, phase-2-backlog, gbp-categories, wikipedia-strategy, podcast-pitch-list, cities-data, firsthand-account, voice-signature, ahrefs-audit, and the email-sequence multifile (8 emails + README).
  • (That is 14 single-markdown + 1 multifile = the 15 non-PDF, non-inlined entries.)

Live status table (every renderable detail page)

Dashboard links that are NOT deliverable detail pages

All of these resolve (HTTP 200) and are fine. Checked because the dashboard links to them:

Dashboard links pointing to a slug that cannot render: NONE. Every /rebuilding/deliverables/<slug>/ link on the dashboard maps to a real renderable slug.

Housekeeping notes (low priority, not broken links)

1. icp page leaks a privacy banner publicly. The live page renders the source frontmatter, including sensitivity: PRIVATE — Bob context and "PRIVATE, do not share publicly." The dashboard itself calls ICP "Internal reference; not for external use." It is sitting on a public, ungated URL. Consider gating, redacting, or removing this from the public build. (Not a broken link; a disclosure concern.)
2. trademark-evidence is public but marked "never public." The dashboard card says "For trademark counsel review only, never public," yet the detail page is reachable at a public URL with full content. Same recommendation as ICP: gate or pull from the public build.
3. 3 orphan renderable pages. gap-analysis, proofreading-log, and phase-2-backlog all render real content at their URLs but have no card on the dashboard. Either add cards (if they should be discoverable) or leave them as deep-link-only. No breakage either way.

Part 2 — Bob's live site (rebuildingseminars.com)

Source: C:\Users\annet\ClaudeProjects\Rebuilding\audit\link-check-divorce-recovery-resource-links-2026-06-06.md Below, the audit's findings are reorganized by which live page Bob needs to edit, with the current/broken value and the exact corrected value.

Reminder from that audit: rebuildingseminars.com serves a soft-200 catch-all (unknown internal paths return the homepage with HTTP 200), so a status crawl cannot certify internal pages. All breakage below is on external links (true status codes) or mis-authored hrefs, which are real regardless.

Page A — parenting-support-resource-links (4 dead links, all 404)

All four 404 (the destination sites are alive; the specific pages are gone). The replacement for each is one of Bob's 4 new internal articles. Those articles are currently HOLD / draft, gated on Bob's proofread, so these swaps can only go live after the articles are proofread and published.

• Action: on the parenting-support-resource-links page, repoint these 4 anchors from the dead external URLs to Bob's own articles (keeps visitors on his site and feeds internal links to the new content).
• Gating: do not publish these swaps until the 4 articles are proofread by Bob and live. Until then the external links stay dead, so a sensible interim option is to remove/disable the 4 dead links now and add the internal ones when the articles ship. (Confirm the exact published URL slugs/paths once the articles are live; the URLs above assume they publish at the site root, matching the existing resource-page link style.)

Page B — legal-financial-resource-links (1 link to update: redirect)

• Action: on the legal-financial-resource-links page, change the Barkus Law anchor's href to https://sustainablefamilysolutions.com/. (Also consider updating the visible anchor text if it still reads "Barkus Law.")
• Note: the prior audit flagged barkuslaw.com as a possible bot-block 403; the operative fact here is the redirect, so updating to the final destination resolves both.

Page C — divorce-recovery-resource-links-2 (the audited page: 1 real fix + 1 cosmetic)

• Action (real fix): on divorce-recovery-resource-links-2, add the https:// scheme to the Facebook link so it points to https://www.facebook.com/RebuildingSeminars.
• Action (cosmetic, optional): fix the obfuscated email link (see above). Low priority.

Consolidated fix checklist (Part 2 only, the actionable items on Bob's site)

Immediately actionable on Bob's site (no gating): 2 (Barkus redirect, Facebook scheme) +1 cosmetic (email decode). Gated on the 4 new articles being proofread and published: 4 (the parenting-support swaps).