Archive the unmanaged Postgres pages - #2504
Merged
Merged
Conversation
Third of three. The pages stay reachable for Support and leave Google and the sidebar. 25 pages carry noindex: true and drop out of the navigation. The index page at /unmanaged-postgres stays listed and indexed, and links to all 25, so there is one way in that search engines and site search can both find. The shared callout now says the pages are archived and points at both Managed Postgres and the index. The four section pages were empty stubs that existed only as navigation roots. They now list their own children, so an old link to one of them lands somewhere useful rather than on a bare warning. Also archives reference/postgres-whats-next, which sat in the Fly Postgres navigation group while living outside the directory. It is unmanaged Postgres content and was missed when the pages moved in 2502. Its URL is unchanged.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third and last of the Postgres path swap, after #2502 and #2503. This is the archiving step agreed with Sam and Alex: the pages stay reachable for Support and leave Google and the sidebar.
The shape comes from Mintlify's hidden pages matrix at https://www.mintlify.com/docs/organize/hidden-pages#search-seo-and-ai-indexing. There is no combination that hides a page from the sidebar, keeps it in site search, and removes it from Google, because
searchable: trueon a hidden group restores Google along with site search. So the answer is one index page that stays listed and indexed, linking to an archived set that is neither.25 pages now carry
noindex: trueand are out of the navigation./unmanaged-postgresstays in the sidebar, stays indexed, and links to all 25, so there is exactly one way in and both Google and site search can find it. The shared callout insnippets/postgres.mdxnow says the pages are archived and points at both Managed Postgres and the index.Two additions beyond the agreed shape, both small.
The four section pages,
getting-started,connecting,managingandadvanced-guides, were empty stubs holding nothing but the warning. They existed only as navigation roots, and removing the navigation would have left them as dead ends. Each now lists its own children, so an old link lands somewhere useful.reference/postgres-whats-nextis archived too. It was sitting in the Fly Postgres navigation group while living outside thepostgres/directory, so it was not caught when the pages moved in #2502. The content is unmanaged Fly Postgres throughout,fly pg createandpostgres-flexand an explicit "this is not a managed database". I found it by diffing the navigation before and after rather than by listing the directory, which is the only reason it turned up. Its URL is unchanged, it just gainsnoindexand the callout and appears on the index.No redirects change in this PR. All 605 entries are untouched, and every URL that worked after #2503 still works.
Verified on the preview at https://fly-io-archive-unmanaged-postgres.mintlify.site
All 26 pages return 200. The
noindexflag is set on 25 of them and correctly absent from/unmanaged-postgres. The sitemap drops from 913 entries to 887, the only/unmanaged-postgrespath left in it is the index, and/reference/postgres-whats-nextis gone. The sidebar goes from 25 entries under/unmanaged-postgresto one.One limitation worth recording, because it caught me. A Mintlify preview blanket-noindexes every page it serves.
/postgresand/networking/servicesboth carry<meta name="robots" content="noindex, nofollow"/>on the preview despite having no such frontmatter, and neither carries it on the live site. So the rendered meta tag cannot be verified on a preview for any page. What is checkable is the page metadata in the payload, which does reflect the frontmatter, and that is what the numbers above come from. The rendered tag needs a re-check on docs.fly.io after this merges.