Skip to content

fix(redirects): redirect stale /questions/topic/replay-vision to /replay-vision - #19808

Open
posthog[bot] wants to merge 2 commits into
masterfrom
posthog-self-driving/fixwebsite-redirect-stale-replay-vision-cb499c
Open

fix(redirects): redirect stale /questions/topic/replay-vision to /replay-vision#19808
posthog[bot] wants to merge 2 commits into
masterfrom
posthog-self-driving/fixwebsite-redirect-stale-replay-vision-cb499c

Conversation

@posthog

@posthog posthog Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Adds a redirect so the retired /questions/topic/replay-vision route resolves to /replay-vision instead of returning 404.
  • The old topic route hurt both people and internal navigation: direct hits (from campaign links and the live Replay Vision page) returned HTTP 404, and Gatsby prefetches of /page-data/questions/topic/replay-vision/page-data.json failed silently.
  • Repository search found no such page and no matching redirect; the replacement /replay-vision returns HTTP 200.
  • Follows the existing /questions/topic/* redirect convention (a Vercel default 308 permanent redirect).

Why: A stale topic route left over from the move to the /replay-vision marketing page caused steady website friction — visible 404s for external visitors and prefetch misses for internal navigation.

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

Created with PostHog Desktop from this inbox report.

…lay-vision

The old /questions/topic/replay-vision route returns 404 for direct visits and for Gatsby page-data prefetches. The replacement page lives at /replay-vision. Add a redirect so both the direct URL and the prefetch resolve.

Generated-By: PostHog Desktop
Task-Id: 9877db9c-7e3e-481d-9e91-9352b7f3bf2a
@posthog

posthog Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

🦔 PostHog Review reviewed this pull request

Found 0 must fix, 1 should fix, 0 consider.

Published 1 finding (view the review).

Resolved comments: 1 fixed

@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Aug 28, 2026 08:36PM

@posthog

posthog Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

PostHog Review alpha 🦔 If you find any issues helpful - please reply "valid", "invalid", etc., for evaluation purposes 🙏

@posthog posthog Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

PostHog Review

Found 1 should fix.

Comment thread vercel.json
@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

8.15 MiB (+0.0 KiB / +0.0%)

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

Entrypoint Eager size Budget Modules
app 16.91 MiB (+0.5 KiB / +0.0%) report-only 2036
Largest modules in the app closure
Module Size
./src/data/mcp-tools.json 1053.9 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 754.5 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
./src/hooks/useCustomers.tsx + 55 modules 370.0 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
./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 + 126 modules 301.7 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 273.0 KiB
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/magnifying-glass.mjs 254.7 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).

… topic

The Replay Vision page's community section built its forum URL from the
product slug (/questions/topic/replay-vision), but that topic page does not
exist — forum topic 377 is shared with Session Replay and lives at
/questions/topic/session-replay. With the new redirect in place, all three
community links (search forums, "be the first to ask", view all questions)
resolved back to /replay-vision itself, and Gatsby kept prefetching the
non-existent page-data URL.

Add an optional forumTopicSlug to the product data (defaulting to the slug)
and set it to Session Replay's slug for Replay Vision, so the links resolve
directly to the real topic and the stale prefetch stops.

Generated-By: PostHog Desktop
Task-Id: ab574683-c9e3-4695-a8d3-276208d2bcfc
@posthog
posthog Bot marked this pull request as ready for review August 28, 2026 20:25
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.

0 participants