Proposal · RFP v2.1
12. Mandatory SEO/GEO migration
Chrysal Website 2027 · Extended draft · 19 October 2026
RFP-hoofdstuk 12
Protecting existing value
Migration begins with an inventory and baseline measurement and ends with verified redirects and intensive monitoring.
Our response & approach
Baseline measurement before migration
The migration has its own workstream and acceptance criteria. Before making changes, we establish a baseline measurement of organic traffic, important search queries, performance by country and language, backlinks where available and the fifty GEO questions. For seasonal demand, we compare with appropriate earlier periods. This allows us to distinguish a technical migration error from normal market fluctuations.
Taking inventory of content and URLs
We then inventory URLs and content through a crawl, CMS export, sitemaps, analytics and Search Console. Documents, images, language variants and important referring links are also included. Each content unit receives a decision: retain, merge, rewrite or remove. Pages with valuable traffic or important documentation are not automatically removed because they show few recent conversions.
Carefully testing appropriate redirects
We create a redirect file from old URLs to new URLs with appropriate content, retaining existing addresses where this makes sense. Removed content without an alternative receives an appropriate status. We avoid mass redirects to the homepage and test for loops, unnecessary chains, error codes and incorrect language destinations. Important downloads also receive a migration destination. Metadata, canonicals, hreflang, internal links, structured data and sitemaps are checked.
Preparing rehearsal and go-live
A dress rehearsal in the acceptance environment validates the import and mapping. Just before launch, we establish a content freeze and process the final differences. The launch check covers, among other things, robots settings, removal of test noindex, indexability, redirects, analytics, consent and contact routes. A backup, fallback procedure and decision-maker for a possible rollback are in place beforehand.
Monitoring after go-live
After launch, we check the main errors, traffic and indexing daily in week one and at least twice a week in weeks two through four. We repeat the fixed GEO sample weekly, using the same recording agreements. An incorrect redirect or blocked important page is addressed immediately according to its severity. A longer-term visibility trend receives additional investigation; ranking recovery or AI mention has no enforceable recovery time.
Migration decisions and handover
The deliverables are the inventory, decision list, redirect mapping, check reports and a handover report after two weeks. After that, technical maintenance support remains available through the SLA; further SEO/GEO growth is a separate optimization retainer. An example: a frequently visited care page receives a different position in the new structure. We retain the content value and language relationships and explicitly test the old link before the platform goes live.
Save this page as PDF
The print version is formatted as a document, without buttons or navigation. Choose “Save as PDF” in the print dialog.