fix: google search indexing for 404 urls#7827
Conversation
Signed-off-by: Oluwatunmise-olat <oluwatunmiseolatunbosun2001@gmail.com>
Oluwatunmise-olat
requested review from
CodexRaunak,
aabidsofi19 and
saurabhraghuvanshii
|
🚀 Preview deployment: https://layer5.io/pr-preview/pr-7827/
|
Signed-off-by: Oluwatunmise-olat <oluwatunmiseolatunbosun2001@gmail.com>
| @@ -0,0 +1 @@ | |||
| /*.html /:splat 301 | |||
There was a problem hiding this comment.
@saurabhraghuvanshii Search Console flagged a bunch of 404s for pages with .html at the end, like /blog/post.html. It looks like these are coming from old cached links and external sites that still think we're using that format. It is a wildcard redirect that strips the .html suffix and sends a permanent redirect to the clean path
|
@Oluwatunmise-olat Thank you for your contribution! Let's discuss this during the website call tomorrow at 5:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂 |
alexquincy
left a comment
alexquincy
left a comment
There was a problem hiding this comment.
I did not review each and every redirect, but of those that I did, some were good and others were atrocious and detrimental.
| toPath: "/learn/workshops" | ||
| redirectInBrowser: true | ||
| isPermanent: true | ||
| - fromPath: "/carrer" |
There was a problem hiding this comment.
No. Why would we want to support a misspelling? If it is a misspelling on a property that we own, let's fix it at the source, otherwise, there's no sense in fixing all of the world's misspellings that are pointed to us from whatever site they run or blog post they make. We can't control that and shouldn't try.
We need an enhanced error page that facilitates the reporting of issues. That would be an improvement to help handle all of the possible unknown 404s pointed our way. Will you open an issue to track this enhancement, @Oluwatunmise-olat?
There was a problem hiding this comment.
I would open an issue for this. That is a valid point
| toPath: "/community/handbook/design-with-layer5" | ||
| redirectInBrowser: true | ||
| isPermanent: true | ||
| - fromPath: "/community/handbook/community" |
There was a problem hiding this comment.
Whoa! Whoa, whoa. Read this again, @Oluwatunmise-olat. This would be disastrous.
There was a problem hiding this comment.
This was my reason for updating that specific redirect
| redirectInBrowser: true | ||
| isPermanent: true | ||
| - fromPath: "/blog/engineering" | ||
| toPath: "/blog" |
There was a problem hiding this comment.
What? I think you mean: /blog/category/engineering
| redirectInBrowser: true | ||
| isPermanent: true | ||
| - fromPath: "/community/newcomer" | ||
| toPath: "/newcomers" |
There was a problem hiding this comment.
No, this should be /community/newcomers.
Where is the source of this hyperlink? Someone or some site didn't include the "s".
There was a problem hiding this comment.
It was coming from static/mail/2026/lfx-2026.html
There was a problem hiding this comment.
Fixing the source right now
@Bhumikagarggg, @Oluwatunmise-olat is well acquainted with our calendar. Instead of offering this canned response, use that time to both learn something and to offer feedback: review the PR. |
@rishiraj38 @saurabhraghuvanshii, both of you gents gave a ✅ to this PR. Please improve the thoroughness of you reviews. Were this PR to be merged, no one would be able to visit the community handbook. Be thoughtful in your reviews, so that your reviews continue to carry weight. |
Signed-off-by: Oluwatunmise-olat <oluwatunmiseolatunbosun2001@gmail.com>
6 participants
Description
Addresses broken URLs surfaced in the audit.
This PR fixes #7826
Notes for Reviewers
Fixes 404s from the audit, source-level link corrections where an internal link was the cause, redirects for renamed URLs coming from external sources and Google's index, and a Netlify catch-all for
.html-suffixed requestsSigned commits