LaunchDarkly is hiring an analyst to tune its PLG funnel and an inbound SDR to handle "pricing requests". But the sitemap still lists three archived pricing pages, all set to "index" with their own canonical tags. Two carry the same title as the live page ("Pricing | LaunchDarkly") and show Foundation at $12 per service connection and $10 per 1k MAU; the oldest shows per-seat Starter and Pro plans, while today's page says "No per-seat pricing". A buyer, or an AI assistant answering "how much does LaunchDarkly cost", can land on the wrong price.
First action
Remove the three archive URLs from the sitemap today.
How to measure it
Pricing-page to sign-up rate
- Now
- –
- Target
- +10%
- By
- 60 days
Steps
Check contract links
Confirm whether order forms point to the archive URLs.
Legal 1 day
Remove from sitemap
All three archive URLs.
Web team 1 hour
Noindex or redirect
Noindex if referenced, otherwise 301 to /pricing/.
Web team 1 day
Add banner
"Archived pricing, see current pricing" with the date.
Web team 1 day
Ask the assistants
What Google and AI assistants quote today; repeat in 30 days.
Senior Growth Marketing Analyst 1 hour
Request recrawl
Search Console removal and recrawl.
Web team 1 day
Measure
Pricing sessions, sign-ups and pricing questions to SDRs.
Senior Growth Marketing Analyst weekly
Why it works
Take the three archive URLs out of the sitemap, set them to noindex (or redirect them to /pricing/ if no contract links to them), and add a dated banner on each: "Archived pricing from September 2025. See current pricing." Then check what Google and the main AI assistants say LaunchDarkly costs, and track pricing-page sessions and self-serve starts before and after.
Pricing is the last check before a trial or a sales call. One page with one current price removes a reason to hesitate and stops SDRs re-explaining old numbers.
Ready to use
ChecklistOld pricing cleanup
[ ] /pricing/archive-sept2025/ out of sitemap, noindex, banner [ ] /pricing/archive-apr2025/ same [ ] /pricing/archive/ same (per-seat plans) [ ] Contract and order-form links checked [ ] Search Console removals requested [ ] AI assistant price answers checked now and in 30 days [ ] Pricing-to-sign-up rate tracked
Risks and how to handle them
Existing customers need old terms
Keep the pages reachable by link, just not indexed.
Search results lag
Use Search Console removals for the two titled "Pricing | LaunchDarkly".
Evidence
- Your websiteThree old pricing pages are still live, set to "index" with self-canonical tags and listed in the sitemap: /pricing/archive-sept2025/ and /pricing/archive-apr2025/ (title "Pricing | LaunchDarkly", Foundation at "$12 per Service Connection" plus "$10 per 1k client-side MAU") and /pricing/archive/ ("LaunchDarkly - Pricing", Starter at $8.33 and Pro at $16.67 "Per seat / Per month"). Their meta description still reads "Find the right feature flag management platform price package for you needs".Source
- Your websiteCurrent pricing page: Developer is "Free to start" with "Unlimited seats" and "No per-seat pricing"; Foundation is pay as you go at "$10 per Service Connection / mo" and "$8.33 per 1k client-side MAU / mo" (billed yearly) with 5k AI runs included and "$5 per additional 1k runs"; Enterprise is custom; Guardian is a paid add-on for release monitoring and automatic rollback.Source
- HiringSenior Growth Marketing Analyst (posted September 11, 2026): "our Product-Led Growth (PLG) motion is evolving rapidly"; the analyst will "decode the digital body language of our prospects and users", distinguish "technical practitioner actions (e.g., SDK deployment) from broader enterprise intent (e.g., security evaluations)", define the "next best action" for each account, run growth experiments, and keep "proper tag/tracking setups across web properties".Source
- HiringInbound Sales Development Representative - Boston (posted October 15, 2026): "Respond rapidly to high-intent inbound inquiries, including demo requests, pricing requests, trials, contact forms, and other hand-raisers" and turn "buying signals into qualified meetings and pipeline".Source