Skip to content

SEO: canonical docs links in guides (42DM audit) - #218

Open
eyalb181 wants to merge 3 commits into
guidesfrom
seo/guides-doc-links
Open

eyalb181 wants to merge 3 commits into
guidesfrom
seo/guides-doc-links

Conversation

@eyalb181

Copy link
Copy Markdown
Member

Guide pages linked to old docs URLs that 301-redirect (overview/quick-start → getting-started/quick-start, overview/teams → getting-started/what-is-mirrord#mirrord-for-teams, using-mirrord/queue-splitting → sharing-the-cluster/queue-splitting, installing-mirrord/cli → getting-started/installing-mirrord/cli, + trailing-slash strips). Rewrote to canonical paths (query/fragment preserved). 14 files. (42DM audit — internal 3xx.)

🤖 Generated with Claude Code

The language/queue guides linked to pre-restructure docs URLs that now
301-redirect (overview/quick-start, overview/teams, using-mirrord/
queue-splitting, installing-mirrord/cli, plus trailing-slash variants).
Rewrite to the current canonical paths; query strings and #fragments
preserved.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>


If you want to steal traffic from a multipod deployment, you can learn more about [mirrord for Teams](https://metalbear.com/mirrord/docs/overview/teams/) which provides this feature. Right now, we only have one pod in this deployment, and mirrord's OSS features should work perfectly for us.
If you want to steal traffic from a multipod deployment, you can learn more about [mirrord for Teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now, we only have one pod in this deployment, and mirrord's OSS features should work perfectly for us.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

nit: Linking to the teams section specifically

Suggested change
If you want to steal traffic from a multipod deployment, you can learn more about [mirrord for Teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now, we only have one pod in this deployment, and mirrord's OSS features should work perfectly for us.
If you want to steal traffic from a multipod deployment, you can learn more about [mirrord for Teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord#mirrord-for-teams) which provides this feature. Right now, we only have one pod in this deployment, and mirrord's OSS features should work perfectly for us.

```

If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams [/mirrord/docs/overview/teams/](https://metalbear.com/mirrord/docs/overview/teams/) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams [/mirrord/docs/overview/teams/](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams [/mirrord/docs/overview/teams/](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord#mirrord-for-teams) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.

![alt text](how-to-debug-a-go-microservice/screenshot-2024-12-20-at-08-14-59-1.png)

If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the reference here [/mirrord/docs/reference/architecture/#mirrord-agent](https://metalbear.com/mirrord/docs/reference/architecture/#mirrord-agent).
If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the reference here [/mirrord/docs/reference/architecture/#mirrord-agent](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the reference here [/mirrord/docs/reference/architecture/#mirrord-agent](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).
If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the [reference here](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).

2. **Installing mirrord**

Install the mirrord CLI tool and run Guestbook with the required Kubernetes context. Follow the installation guide for mirrord here [/mirrord/docs/overview/quick-start/#installation](https://metalbear.com/mirrord/docs/overview/quick-start/#installation) and run the below command.
Install the mirrord CLI tool and run Guestbook with the required Kubernetes context. Follow the installation guide for mirrord here [/mirrord/docs/overview/quick-start/#installation](https://metalbear.com/mirrord/docs/getting-started/quick-start#installation) and run the below command.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Install the mirrord CLI tool and run Guestbook with the required Kubernetes context. Follow the installation guide for mirrord here [/mirrord/docs/overview/quick-start/#installation](https://metalbear.com/mirrord/docs/getting-started/quick-start#installation) and run the below command.
Install the mirrord CLI tool and run Guestbook with the required Kubernetes context. Follow the installation guide for [mirrord here](https://metalbear.com/mirrord/docs/getting-started/quick-start#installation) and run the command below.

```

If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams [/mirrord/docs/overview/teams/](https://metalbear.com/mirrord/docs/overview/teams/) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams [/mirrord/docs/overview/teams/](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams [/mirrord/docs/overview/teams/](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord#mirrord-for-teams) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.



If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the reference here /mirrord/docs/reference/architecture/#mirrord-agent.
If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the reference here /mirrord/docs/reference/architecture#mirrord-agent.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the reference here /mirrord/docs/reference/architecture#mirrord-agent.
If you would like to learn more about how the mirrord-agent in the above architecture works, go check out the [reference here](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).



If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams /mirrord/docs/overview/teams/ which provides this feature. Right now, we only have one pod in this deployment, and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams /mirrord/docs/getting-started/what-is-mirrord which provides this feature. Right now, we only have one pod in this deployment, and mirrord’s OSS features should work perfectly for us.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you want to mirror traffic from a multipod deployment, you can learn more about mirrord for teams /mirrord/docs/getting-started/what-is-mirrord which provides this feature. Right now, we only have one pod in this deployment, and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord#mirrord-for-teams) which provides this feature. Right now, we only have one pod in this deployment, and mirrord’s OSS features should work perfectly for us.

```

If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams]( /mirrord/docs/overview/teams/) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams]( /mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams]( /mirrord/docs/getting-started/what-is-mirrord) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.
If you want to mirror traffic from a multipod deployment, you can learn more about [mirrord for teams](https://metalbear.com/mirrord/docs/getting-started/what-is-mirrord#mirrord-for-teams) which provides this feature. Right now we only have one pod in this deployment and mirrord’s OSS features should work perfectly for us.

#### Installing mirrord

Let’s install mirrord CLI tool and run knote with the required Kubernetes context. Follow the installation guide for mirrord here [/mirrord/docs/overview/quick-start/#installation](https://metalbear.com/mirrord/docs/overview/quick-start/#installation) and run the below command.
Let’s install mirrord CLI tool and run knote with the required Kubernetes context. Follow the installation guide for mirrord here [/mirrord/docs/overview/quick-start/#installation](https://metalbear.com/mirrord/docs/getting-started/quick-start#installation) and run the below command.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Let’s install mirrord CLI tool and run knote with the required Kubernetes context. Follow the installation guide for mirrord here [/mirrord/docs/overview/quick-start/#installation](https://metalbear.com/mirrord/docs/getting-started/quick-start#installation) and run the below command.
Let’s install mirrord CLI tool and run knote with the required Kubernetes context. Follow the installation guide for mirrord [here](https://metalbear.com/mirrord/docs/getting-started/quick-start#installation) and run the below command.

![alt text](how-to-debug-a-java-microservice/screenshot-2024-12-03-at-08-43-53-1.png)

If you would like to learn more about how the mirrord-agent in the above architecture works, go checkout the reference here [/mirrord/docs/reference/architecture/#mirrord-agent](https://metalbear.com/mirrord/docs/reference/architecture/#mirrord-agent).
If you would like to learn more about how the mirrord-agent in the above architecture works, go checkout the reference here [/mirrord/docs/reference/architecture/#mirrord-agent](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you would like to learn more about how the mirrord-agent in the above architecture works, go checkout the reference here [/mirrord/docs/reference/architecture/#mirrord-agent](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).
If you would like to learn more about how the mirrord-agent in the above architecture works, go checkout the reference [here](https://metalbear.com/mirrord/docs/reference/architecture#mirrord-agent).

@trawler

trawler commented Aug 6, 2026

Copy link
Copy Markdown
Member

@eyalb181 do we still need this merged?

eyalb181 and others added 2 commits September 15, 2026 23:33
Point the links at the specific section rather than the page top where one
exists, and drop the UTM parameters that were preventing the fragment from
being honored.

Two anchors did not resolve against the current docs and are corrected here:
the quick start section is `install`, not `installation`, and the copy-target
section was renamed to "Replacing a Whole Workload Using `scale_down`". Every
anchored link in the guides now points at a heading that exists within the
H1-H3 range GitBook generates anchors for.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.

3 participants