-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't find old documentation pages about using private registries #2025
Comments
Sadly all google search results are broken, too. The content at #847 seems to be gone from the site. |
Thanks for surfacing the 404s from search results. To combat these SEO challenges, we need to add those URLs into the destination/target file. This covers at a high-level, how to add the |
Re: #847 That content uses Knative Build, which was deprecated. To view that file, you can view the past doc versions in the GitHub repo (along with the deprecated Knative Build content): |
Good news is that I'm not able to get those same search results (likely since our site index was updated and scraped between now and when this issue was opened): The new version of "how to ... private registry" file (from #2027) now shows at the top so im going to close this and also ensure that we are more strict about using "redirects". Thanks @ahmetb! |
Maybe a chrome history "thing" so I see recently visited pages that match the search query? I was trying to replicate that query from your screenshot so that I could obtain those URLs that result in 404s and then add them as aliases in the new file. Feel free to pass along any other bad URLs that you come across and i'll happily add them to the frontmatter of current source files. |
These pages showing up on site search results for keyword "private" seem to be gone and redirect to the homepage :( (why can't we set up redirect while shuffling files like this in Netlify?)
There's nothing under
Serving Component
on the sidebar that helps me find where this content has gone to.The text was updated successfully, but these errors were encountered: