Skip to content

Restore moved URLs and prevent broken internal links - #36

Merged
cloudartisan merged 3 commits into
mainfrom
fix/legacy-redirects-link-check
Oct 4, 2026
Merged

cloudartisan merged 3 commits into
mainfrom
fix/legacy-redirects-link-check

Conversation

@cloudartisan

@cloudartisan cloudartisan commented Oct 4, 2026 •

Copy link
Copy Markdown
Owner

Search Console reports the legacy Ubuntu Maverick article as 404 even though its current article is available. Other posts also link to six retired dated routes, an incorrect Codex post date and a missing trailing-slash feed route.

Restore these paths with eight Hugo aliases and an immediate /feed/ redirect, and replace source links with relref or /feed.xml. Redirect pages use zero-second meta refresh and canonical destinations; the aliases stay out of the sitemap. Google treats immediate meta refresh as a permanent indexing signal, although GitHub Pages serves the redirect HTML with HTTP 200 rather than an arbitrary path 301/308. Search Console has no same-site old-to-new path correction tool.

Add a dependency-free rendered-site checker and twelve fixture tests to both PR validation and the pre-deployment workflow. It covers same-site HTML links, resources, srcset, canonical/refresh targets and sitemap URLs, and rejects localhost links, empty builds and trailing slashes on file destinations and non-default HTTP(S) ports. Development output is separate so drafts cannot hide missing production routes. External sites, fragments, CSS URLs and JavaScript-created URLs are outside this check.

Validation: pinned Hugo 0.160.1 configuration, development and clean production builds passed; twelve checker tests passed; 5,394 internal references passed. Before cleanup, the checker reproduced 12 existing missing references. All nine redirect pages have verified zero-second refreshes and correct canonical destinations; current articles remain self-canonical and aliases are excluded from the sitemap.

After merge and deployment, verify the live redirects, then optionally request destination indexing and validate the 404 fix. No Search Console submission, settings change or production deployment was performed. Redirects and reindex requests do not guarantee ranking improvements.

References: Google redirects, Change of Address limitations, recrawl requests, Hugo aliases.

@cloudartisan
cloudartisan marked this pull request as ready for review October 4, 2026 03:47
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-04T04:02:17.061691Z 117e47c Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0dd533af3c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/check_internal_links.py Resolved

Copy link
Copy Markdown
Owner Author

@codex review

Please review current head e45f9a6, including the fix for the trailing-slash file destination finding. The regression tests and pinned Hugo build pass, and PR validation is green.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e45f9a6fb6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/check_internal_links.py Resolved

Copy link
Copy Markdown
Owner Author

@codex review

Please review current head 117e47c, including the port-validation correction. Both findings have regression coverage; all twelve tests, the pinned Hugo production build and 5,394 internal references pass.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 117e47cbe9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@cloudartisan
cloudartisan merged commit 0425ec5 into main Oct 4, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant