Assessing SEO Impact Before Website Platform Changes

If you plan to migrate your job board to a new SaaS or custom-built platform, please consult an SEO expert before you do anything. I’ve helped three job boards recover from failed migrations this year alone. There are plenty of things to consider before making the move: - Optimal Redirect Strategy: Properly setting up 301 redirects to maintain your SEO equity and prevent 404 errors. - Removing Old and Useless Pages: Cleaning up outdated content to improve site quality and crawl efficiency. - Fixing Existing Structural Issues: Addressing any current problems so they don’t carry over (those ancient, home-grown platforms often have plenty). - Google Jobs Migration: Yep, moving to a new platform has implications for your visibility on Google Jobs and requires careful planning. - Core Web Vitals Performance: Ensuring the new platform is optimized for speed and user experience. - Sitemaps: To expedite indexing, update and submit your XML sitemaps to search engines, make them dynamic to reduce Soft404s - Retaining Backlinks: Preserve your backlink profile and reach out to update critical external links. - Ensuring Crawlability and Indexability: Search engines can access and index your new site without issues and test the new site with an external scraper - Migrate Structured Data Markup: Make sure you will retain the structured data you have in the correct format. - Updating Internal Links: Reviewing and correcting internal links to improve navigation and crawl efficiency. And the list goes on. What are the risks of not doing this? You could lose much of your organic traffic—if not all of it. Recovering from a poor migration can take 3 to 12 months, depending on the severity of the issues, and you might lose between 50% and 80% of your traffic. Plan carefully! Have you suffered from a bad job board migration? Share your experience below!

Google Search Console gives you numbers. GSC Wizard gives you answers. Decades of doing data driven SEO. Every week I'd export GSC data, wrangle it in spreadsheets, try to find the story in the numbers. Then do it again for the next client. And again. So I built the tool I always wanted: GSC Wizard turns raw Search Console data into actionable intelligence. No spreadsheet gymnastics required. Here's every feature and what it actually solves: ◆ SITE RESTRUCTURING & TOPICAL MAPPING BERTopic clustering with multilingual-e5-large-instruct embeddings maps your entire site into topic clusters. Visual drag-and-drop tree hierarchy lets you redesign site architecture. Auto-generates redirect maps, internal linking plans, and content briefs for gaps. Works across languages so you can see coverage gaps per topic per market at a glance. ◆ CANNIBALIZATION DETECTION Detects when pages compete for the same keywords. Not just keyword overlap, but intent-level conflicts. Shows which URL should win and which should merge or redirect. ◆ CONTENT DECAY MONITORING Visualizes which pages are losing traffic over time with an intuitive heatmap. Spot declining content before it's too late. ◆ FORECASTING Predict future organic traffic based on historical GSC trends. Model scenarios for content investments, seasonal patterns, and growth targets. ◆ ANOMALY DETECTION Automatically flags unusual spikes or drops in clicks, impressions, CTR, and position. No more finding out a month later that something broke. ◆ MIGRATION DASHBOARDS Track performance before and after domain, folder or URL migrations across multiple GSC properties. Monitor traffic recovery, catch URL mapping gaps, and compare old vs. new property data side by side. The cross-property view is critical for enterprise migrations that nobody else handles properly. ◆ EXPERIMENT MONITORING Run A/B tests on title tags, meta descriptions, and content changes. Measure impact with statistical significance testing and group comparisons. Prove that your SEO changes actually worked. ◆ INTERNATIONAL ANALYSIS Analyze performance across countries and languages. Detect country-level cannibalization, and compare properties across markets. Cross-property analysis shows you which markets are underserved. ◆ INDEXING MONITOR Track which pages Google is picking up and which ones are quietly disappearing from the index. ◆ PAGE POACHING OPPORTUNITIES Find keywords ranking at positions 4-20 that are ripe for pushing into the top 3 with small optimizations. ◆ ON-PAGE CHECKS Check if top queries appear in titles, meta descriptions, and H1 headings. Simple but surprisingly powerful. ◆ KEYWORD CLUSTERING Group related keywords into clusters and track aggregate performance. See which topics drive the most traffic and where clusters are thin. Every report surfaces specific opportunities. Sign up for the waiting list now.

70% of the potential client websites I checked this year have recently been or are about to go through a migration. Most of those who’ve migrated, come to us with real problems: lost rankings, traffic declines, and reduced organic pipeline. Those only planning to migrate are often confident they won’t need SEO help. They assume the devs will handle the entire process, and a few new content pieces will get them back on track. The reality? Without proper tech SEO support, this second group is likely to end up facing the same problems as the first one, often within 6-9 months post-migration. Before we dive into steps you can take to ensure a smoother migration, let’s clarify what qualifies as a website migration from an SEO perspective: - redesign - relaunch - rebranding - merger/acquisition - removing a significant portion of the site - change of domain/subdomain Any of these can impact your organic performance and user experience. Here are the key things to watch out for on a website to protect the progress you’ve worked hard to build: 1. Understand what the migration is about and assess how it could affect your organic performance. 2. Run a pre-migration audit to benchmark current performance and identify critical pages and elements. 3. Brief your dev and marketing teams on what’s working well and what needs consideration during the migration. 4. Map your URL changes in the redirect map. Avoid redirecting all removed pages to the homepage. 5. Check core tech SEO elements immediately post-migration, this is a critical moment when most issues arise. 6. Monitor organic performance closely for 3-6 months post-launch. Remember: SEO isn’t your dev team’s responsibility. They can handle the technical setup to some extent, while your marketing manager is overseeing the content migration. BUT, the only person who will look under the hood of your website from the perspective of best web practices, UX, and search engines - is a dedicated SEO specialist. They’ll help you migrate smoothly and ensure organic success in the long run. Don't let your house on fire just to save a few bucks. Cutting corners here can cost you far more in the long run when things go south.

How Martech Choices Impact SEO? (And What to Do About It) In B2B marketing, the technology decisions we make can have a bigger impact on SEO than we often realize. It's not just about picking the latest tools—it's about understanding how they all fit together and affect our overall marketing goals, especially in complex environments like enterprise B2B SaaS. Imagine this scenario: A large B2B SaaS company decides to switch to Salesforce to streamline their sales processes. Sounds like a great move, right? But here’s what can happen—they might also migrate their website to a new platform that comes with Salesforce. This change seems like a win for the sales team, but can cause some unexpected problems for their SEO. The new platform can mess with the website’s URL structure and site architecture—two things that are crucial for maintaining search engine rankings. Almost overnight, their organic search traffic can take a hit. However, if the SEO team can be looped in earlier, they can flag these issues and help create a migration plan that can protect their search rankings. Involving the SEO team from the start can allow them to use their data insights to shape the new site’s architecture. They can ensure that the site is optimized not just for sales conversions but also for search visibility. This can help maintain a balance between driving sales and maintaining strong organic traffic. The Martech decisions we make don’t happen in isolation—they can ripple across the entire marketing strategy, especially when it comes to SEO.

Over the past 2 months, I've seen 2 businesses migrate their websites without SEO being involved in the planning, execution, or post-go-live considerations. One of these businesses then engaged us to fix the issues that arose. (image below) Below is a list of issues I’ve seen: - No consideration for redirecting retired pages - No consideration for overall site architecture - Staging website being indexed - Redirecting all old pages to the homepage - Not ensuring XML sitemap is updated on search console - Not initiating domain change migration in search console - Not tracking any new events/lead funnels within GA4 - Updating internal links to URL pathway avoiding mass 301s - Creating redirect chains by not reworking historical redirects - E-commerce businesses duplicating product and category pages - Going live with the noindex tag left in - Not updating Hreflang Tags - Not updating canonical URL structure - No plan around updating external links - Not updating robot.txt if new site architecture - Using 302 redirects instead of 301s - Not migrating previous title structure - Going live with ‘home’ as your homepage title tag - this one horrifies me - Not having a previous crawl & backup to refer back to - Not allowing staging site to be crawled and assessed to compare against the current site as the build progresses, to capture possible issues before launch - No consideration of site speed You’ve then got a range of post-go-live checks that are important to keep on top of: - Track keywords before & post go live to see any major changes - Monitoring search console for any errors - Using tools to push indexing (tagparrot is a good one) There are probably a lot more considerations, but the point is that if you’re investing thousands in a new website, you need to ensure SEO is involved from the start of the build. The website might look great, but if it is not visible, traffic or conversions will not increase. When done well you can improve your SEO performance through a migration. #technicalseo #websitemigration #seomistakes #seoagency #seotips #seostrategy #seoexpert

Website migrations are one of the scariest moments in SEO. Right now, I have 4 SEO clients in the middle of migrations. And every single time, the same questions come up: 🔹 Are we going to lose rankings? 🔹 Are we going to lose traffic? 🔹 Are leads going to dip? 🔹 Are we about to take 3 steps backwards before we can move forward? The honest answer? You never know with 100 percent certainty until after launch. Especially when: 🔹 Pages are being pruned 🔹 URLs are changing 🔹 Site architecture is shifting 🔹 Content is being consolidated 🔹 Platforms are being switched Migrations can create massive upside. They can also create chaos if handled poorly. The difference is preparation. This checklist is the framework we use before migrations, including: 🔹 Full URL crawl and benchmarking 🔹 Revenue page protection 🔹 301 redirect mapping 🔹 Technical QA before launch 🔹 Analytics and tracking validation 🔹 Post-launch monitoring for 30 to 60 days A migration is not just a design project. It’s not just a dev project. It’s a business risk management project. Handled correctly, it protects rankings, traffic, and revenue. Handled poorly, it can undo years of SEO progress in weeks. If you’re planning a migration in 2026, involve SEO early. Not after staging is done. #SEO #WebsiteMigration #TechnicalSEO

If you do not want to lose traffic, your SEO strategist should lead the website re-platforming and migration projects. I cannot stress this enough: without involving SEO, you are likely to miss something that may result in declining traffic. It doesn't matter what your dev team says. Even with a perfect website migration or a re-platforming project, you will likely lose 10 - 20% of your traffic temporarily before Google consolidates all signals and gives it back! If something goes awry, you are living a nightmare. Here are some of the things that can go wrong, followed by how you should ensure they don't. ❌Change in URLs, meta tags, and site structure leading to traffic drop. ❌Broken links, missing content ❌Downtime and user disruptions ❌Loss of data ❌Bad redirect setup ❌Broken images and other HTML assets ❌Allowing staging website to get indexed ❌Performance issues ✅Implement 301 redirects for old URLs, update meta tags, and submit updated sitemaps while keeping the old site map in the Google Search Console. Monitor performance before and after migration and address any issues that may arise. ✅Export internal links in a file before the migration and keep it with you to test after migration. Update internal links during the migration project. Crawl the website with screamingfrog post migration to fix any remaining broken links, including images and multimedia. Spot-check the internal links in the previously exported file to ensure everything works as intended. ✅Communicate downtime to users. Perform migration during low-traffic periods of the day. ✅Always back up everything before starting the migration. ✅Create a 1-to-1 URL redirect map, considering previous redirect rules and updating them to reflect the new changes. Keep 301 redirects in place for at least one year. ✅Try keeping image URLs and image names the same. If that's not possible, redirect non-HTML assets as you do with the rest of your site and include them in your URL map. ✅Make sure authentication is in place for a staging environment. You can still crawl it with ScreamingFrog. ✅Keep a snapshot of core web vitals performance before the migration and benchmark against post-migration metrics. Find and fix issues using the directions given inside the tools.

I’ve noticed a pattern, a lot of companies jump into “migration” without a clear picture of how it’s going to play out after launch. And that’s where this go sideways. Because migrating from WordPress (or any platform) to Webflow isn’t just a design or development project. It’s an operational + structural change. You’re not only moving pages, you’re changing how your site is organized, how your team ships updates, how content is produced, and how search engines (and AI assistants) understand what you do. So before you move, ask yourself these 5 questions: 1️⃣ Are you migrating for a nicer site or for control? If marketing still needs dev help for every change post-launch, the “new platform” won’t feel new for long. 2️⃣ Who will own the CMS and publishing rhythm after launch? A migration should unlock content velocity. If the structure is unclear, publishing becomes chaotic fast (believe me, I've seen it too many times). 3️⃣ Is your analytics + tracking setup clean today? If GA4 events, attribution, conversion tracking, and HubSpot connection are messy now, migration will amplify the mess, not fix it. 4️⃣ Are you rebuilding UX or copying old layouts? Migration is usually the only moment teams get permission to rethink flows. If you just replicate the old site, you keep the old conversion problems too. But that doesn't always require full and complete redesign, sometimes just a structural change is enough to gain velocity. 5️⃣ Do you have an actual SEO + AEO migration plan? Redirects, metadata, schema, internal linking logic, content hierarchy, and now the AI layer. If your pages aren’t structured clearly, traditional search crawlers struggle… and AI systems won’t confidently cite or recommend you either. Most companies treat migration as a design refresh, or a platform switch to make updates easier, but it’s not the point. The point is what happens after the move: how you scale content, how you position your offer, and whether Google and AI search can instantly understand what each page is about. If you’re exploring migration this year, take 30 minutes and pressure-test your answers to these questions before you talk to anyone. And if you want a deeper strategic breakdown, we documented our full Webflow migration framework in a guide you can download in the comments bellow. P.S. In the screenshot bellow you can see their traffic one month in, it's clearly still unstable, but it already shows a lot of progress.

Planning a Website Migration? Here’s Your Step-by-Step Blueprint for SEO Success 🚧 Website migrations are some of the riskiest (and most rewarding) SEO projects you can take on. Whether you’re rebranding, switching CMS platforms, or consolidating domains — your rankings and traffic depend on getting it right. Here’s a step-by-step guide to help you plan and execute a flawless migration: 1️⃣ Define Migration Objectives & Timeline Start with the “why” and “when.” 1. Are you migrating due to a rebrand, domain change, or technical need? 2. Set a realistic timeline and try to avoid launching during high-traffic periods. 2️⃣ Identify Key Stakeholders Who needs to be in the loop? Involve developers, SEOs, content managers, designers, and decision-makers early on. If it’s a live project, start booking planning meetings ASAP. 3️⃣ Benchmark Current Site Metrics Before anything changes, capture your current performance: ⚡ Page speed 🔑 Keyword rankings 📈 Organic traffic 🔗 Backlink profile These benchmarks help you track gains (or losses) post-migration. 4️⃣ Back Up the Website Always back up your entire site — files 💾 and database 🗂️. If you don’t have access, write down how you’d coordinate this with a developer or hosting provider. 5️⃣ Create a Technical SEO Spec Sheet Document both the current and new site setups for: 🧾 robots.txt 🗺️ XML sitemap(s) 🔁 Canonical tags 📝 Meta titles & descriptions 🔤 Heading structure (H1–H6) Make sure these are optimized and nothing gets lost in the move. 6️⃣ Build a URL Mapping File Map every old URL to its new destination. Label redirects as: 🔁 301 (permanent) ⚠️ 302 (temporary — only when necessary) This preserves link equity and avoids crawl errors. 7️⃣ Test Redirects in Staging Before going live: 1. Test all redirect mappings 2. Use tools like 🐸 Screaming Frog to crawl your staging site 3. Look for broken links, loops, and missing metadata Share in the comments out how you’d run this in a real-world scenario. 8️⃣ Verify or Transfer Google Search Console Ownership Make sure the new site is tracked in GSC 🔍 Submit updated sitemaps, monitor crawl status, and fix issues early 🛠️ If this is a practice run, open GSC and locate the ownership/verification panel so you're familiar with it. 💬 How are YOU doing site migrations for your clients? Share your best practices or horror stories in the comments! 🔁 Share this post with fellow SEO, marketing, and dev specialists 🔔 Don’t forget to follow for more insights on Google Ads, SEO, and Email Marketing! Let’s work smarter, not harder! 💡 #SEOMigration #WebsiteMigration #TechnicalSEO #DigitalMarketing #SearchEngineOptimization #GoogleSearchConsole #URLMapping #WebDevelopment #SEO #PageSpeed #MarketingTips #WebPerformance #GrowthMarketing #CMSMigration #ScreamingFrog

The best hack ever I did when migrating big sites to new CMS, URL Patterns, etc. is to keep old URLs as is and just change new URLs after a specific cutoff date. This eliminate a lot of work on SEO side and minimize the Google impact on the site. For example if the old URL pattern is https://lnkd.in/eYjSFQXJ, and the new URL pattern is https://lnkd.in/eREZhvhe. Determine the cutoff date and keep old existing URLs as is and just change new URLs going forward. It needs some advanced technical setup but believe me it is worth it. Remember, site wide changes take a long time to process by Google sometimes months to assess the change https://lnkd.in/eVG4FvDf I always recommend do gradual changes especially around migration - migrate a small section of the site, preferably a mid-trafficked section. Fix all bugs and issues and see how Google reacts to the change - Then migrate the rest of the site in chunks I also believe there is a "reset & revaluate" that sites go through with major changes or site-wide changes where Google resets everything they know about the site and revaluate its quality, rankings, etc.