OMCP study materials
OMCP study resources

Post-Migration Organic Traffic Loss for a Dental Group

OMCP · Put your knowledge to work in context.

All case studies

Post-Migration Organic Traffic Loss for a Dental Group

ClearSmile Dental Group has 38 locations and migrated to a new CMS three months ago. Organic sessions are down 41% versus the prior year, and organic new-patient form fills are down 33%. The migration mapped 12,000 URLs, but 2,100 now return 404s, including many former service-page URLs with tracking parameters. Location pages were consolidated from 38 to 12 regional pages. Google Search Console shows a sharp rise in "Crawled - currently not indexed" and "Duplicate, Google chose different canonical" for paginated service pages. Internal links still point to old URLs in the blog. The marketing director wants to know whether to revert the migration or fix it forward. The team has one SEO specialist and a developer available 10 hours per week.

1. Should ClearSmile revert the migration or fix it forward? Justify the decision.

Read the worked answer

Fix forward unless the new CMS has a fundamental technical defect that prevents redirects, canonical control, or indexable templates. Reverting after three months means another migration, another round of redirect churn, and more lost time. The symptoms point to fixable migration errors: 2,100 404s, parameter URLs, collapsed location pages, canonical problems on paginated pages, and stale internal links.

Reverting is justified only if key revenue templates cannot be rendered or indexed and the vendor cannot fix them quickly. Otherwise, recover by mapping every 404 with traffic or backlinks to the closest relevant live URL and applying 301s. Restore location pages or create unique city-level pages instead of 12 thin regional pages. Fix paginated canonicals so they self-reference rather than pointing to page one. Update internal links and sitemaps.

With one SEO specialist and 10 developer hours per week, sequence by revenue impact: high-value service pages and location pages first, then blog links and long-tail redirects. Set a 90-day recovery plan with weekly checks. Do not promise full recovery by a fixed date; migrations often take months.

2. Prioritize the first two weeks of fixes. What would you do first, second, and third?

Read the worked answer

First, export all 404 URLs with organic entrances, backlinks, and internal links. Map the highest-value service and location URLs to the closest live equivalent and implement 301s. Include parameter variants by using rule-based redirects, not thousands of individual rules. Validate that redirects go to relevant pages, not the homepage.

Second, fix internal links in the blog and navigation that still point to old URLs. Update the XML sitemap and remove or redirect stale URLs. Submit the sitemap and validate fixes in Search Console.

Third, address indexation and duplication. For paginated service pages, use self-referencing canonicals unless a page is truly a duplicate; do not canonicalize all pages to page one. Review the 12 consolidated regional pages and restore city-level pages where demand and capacity justify them. Add unique content for each location, not boilerplate.

With limited developer time, batch redirect rules and template fixes. Track 404 count, indexed pages, and impressions for priority URLs weekly.

3. What would you measure at 30, 60, and 90 days to know recovery is on track?

Read the worked answer

At 30 days, measure leading indicators: 404 count reduced, redirect coverage for priority URLs, internal links fixed, sitemap errors, and indexed page count. Check whether Google is selecting the intended canonical for paginated and location pages. Review crawl stats for old URLs still being discovered.

At 60 days, measure impressions, clicks, and average position for migrated service and location URLs. Compare against pre-migration benchmarks and year-over-year, not just the previous month. Track organic new-patient form fills by location. Look for early recovery in high-priority city and service queries, but expect lag.

At 90 days, measure organic sessions and form fills against the pre-migration baseline, with a recovery target such as closing half the gap rather than full recovery. Segment branded versus nonbranded traffic. Check local pack visibility and location-page conversions. Also monitor whether redirect chains or soft 404s remain.

Report leading and lagging indicators together. A rise in indexed pages without impressions or form fills means the templates are indexable but not competitive; a rise in impressions without clicks points to title and intent mismatch.