docs(error-tracking): fix dead anchor links and stale redirects

[gewenyu99]

Changes

Found while tracing links for the Error Tracking IA migration in #18932. These are all pre-existing and outside that PR's diff, so they're split out here to keep it reviewable.

Eight in-page anchor links pointed at headings that don't exist, so they landed at the top of the page instead of the relevant section. Two more links pointed at URLs that only resolve via a 301. Each is repointed at its correct target:

File	Was	Now
alerts.mdx	managing-issues#auto-assignment-rules	assigning-issues#automatic-issue-assignment
capture.mdx (×2)	issues-and-exceptions#how-are-issues-grouped	#how-exceptions-are-grouped-into-issues
fingerprints.mdx (×2)	managing-issues#merging-issues	grouping-issues#merging-separate-issues
issues-and-exceptions.mdx	managing-issues#resolving-and-suppressing-issues	#update-issue-status
issues-and-exceptions.mdx	monitoring#viewing-session-replays	managing-issues#watch-session-replays
issues-and-exceptions.mdx	grouping-issues#option-2-custom-grouping-rule	#option-1-custom-grouping-rule
troubleshooting.mdx	grouping-issues#custom-grouping-rule	#option-1-custom-grouping-rule
issues-and-exceptions.mdx	/docs/error-tracking/external-tracking (301)	/docs/error-tracking/integrations
productData/error_tracking.tsx	/docs/error-tracking/cutting-costs (301)	/docs/error-tracking/pricing

A few notes on the less obvious ones:

• Merging content lives only in grouping-issues.mdx#merging-separate-issues (that's where the _snippets/merging-issues.mdx snippet is imported), not on managing-issues.
• Session replays — monitoring.mdx has no replay section; the content is managing-issues.mdx#watch-session-replays.
• option-2 → option-1 — in grouping-issues.mdx, Option 1 is Custom grouping rule and Option 2 is Client-side fingerprint. Both call sites mean the PostHog-side rule, and the surrounding list already covers client-side fingerprints separately.
• troubleshooting.mdx already used assigning-issues#automatic-issue-assignment correctly, which is what the alerts.mdx fix now matches.

Why

Every one of these silently dropped the reader at the top of a long page rather than the section being cited, which is the kind of thing nobody notices until they're following a link mid-debug.

Not included

• /docs/model-context-protocol#manual-install is dead too — that heading no longer exists anywhere. It's linked from nine docs pages, including the error tracking one. The error tracking instance is being moved by docs(error-tracking): self driving IA for error tracking #18932, so it's flagged as a review comment there; the other eight are a separate sweep.
• start-here.mdx also has a link that resolves via a 301, but docs(error-tracking): self driving IA for error tracking #18932 edits that file, so it's a review comment there instead of a conflicting edit here.

Checklist

• I've read the docs and/or content style guides.
• Words are spelled using American English
• Use relative URLs for internal links
• I've checked the pages added or changed in the Vercel preview build
• If I moved a page, I added a redirect in vercel.json — n/a, no pages moved

Each target anchor was verified to exist by re-running a link/anchor validator over every /docs/error-tracking/* link in contents/ and src/ after the change.

---

Created with PostHog Code

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Jul 27, 2026 09:32PM

[github-actions]

Vale prose linter → found 2 errors, 18 warnings, 3 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/error-tracking/alerts.mdx — 1 errors, 5 warnings, 1 suggestions

Line	Severity	Message	Rule
2:13	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
9:55	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
9:61	warning	'tracking's' is a possible misspelling.	PostHogBase.Spelling
37:75	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
43:7	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
49:47	warning	Capitalize 'Data Pipelines' for PostHog's product. Use 'data pipelines' for the general industry concept.	PostHogBase.ProductNames
75:37	suggestion	Address the reader directly. Use 'you' instead of 'the user'.	PostHogDocs.DirectAddress

contents/docs/error-tracking/capture.mdx — 0 errors, 5 warnings, 1 suggestions

Line	Severity	Message	Rule
19:49	suggestion	Address the reader directly. Use 'you' instead of 'the user'.	PostHogDocs.DirectAddress
31:46	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
327:28	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
346:428	warning	Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept.	PostHogBase.ProductNames
583:33	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
599:101	warning	'runtime's' is a possible misspelling.	PostHogBase.Spelling

contents/docs/error-tracking/fingerprints.mdx — 0 errors, 0 warnings, 1 suggestions

Line	Severity	Message	Rule
9:68	suggestion	Address the reader directly. Use 'you' instead of 'the user'.	PostHogDocs.DirectAddress

contents/docs/error-tracking/issues-and-exceptions.mdx — 0 errors, 5 warnings, 0 suggestions

Line	Severity	Message	Rule
5:82	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
9:253	warning	Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept.	PostHogBase.ProductNames
30:206	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
38:14	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames
49:32	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept.	PostHogBase.ProductNames

contents/docs/error-tracking/troubleshooting.mdx — 1 errors, 3 warnings, 0 suggestions

Line	Severity	Message	Rule
7:4	warning	'Have a question? Ask PostHog AI' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
63:4	warning	''Non-Error promise rejection' with no stack trace' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
103:8	warning	'misconfiguration' is a possible misspelling.	PostHogBase.Spelling
131:227	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash

[github-actions]

Bundle report

Total JS (gzip)

6.76 MiB (-0.0 KiB / -0.0%)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint	Eager size	Budget	Modules
✅ app	16.27 MiB (-0.0 KiB / -0.0%)	report-only	1986

Largest modules in the app closure

Module	Size
./src/data/mcp-tools.json	935.7 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css	742.0 KiB
./src/components/Stickers/Stickers.tsx	696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js	481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules	395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js	364.8 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js	354.8 KiB
./src/hooks/useCustomers.tsx + 54 modules	354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules	351.4 KiB
./src/components/ProductComparisonTable/index.tsx + 121 modules	282.8 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js	281.9 KiB
./src/components/SearchUI/index.tsx + 87 modules	272.1 KiB
./node_modules/.pnpm/framer-motion@10.18.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/dom/motion.mjs + 109 modules	253.9 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules	247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules	240.1 KiB

---

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).