How to relaunch a website without ruining SEO

How to relaunch a website without ruining SEO 🔗 **Source:** [How to relaunch a website without ruining SEO](https://www.youtube.com/watch?v=GtWz7wBahJw) > [!note]+ Document Notes > tags: [seo, wordpress, website-relaunch] > author: Tina Risse > source: WordCamp > reference: https://www.youtube.com/watch?v=GtWz7wBahJw > date created: 2024-12-19 14:30 > > # 🏷️ Title: How to relaunch a website without ruining SEO >  ## 🧰 Action Inbox - [H1] Audit current rankings and URLs before any relaunch — pre-launch planning #seo - [H2] Test all redirects and check indexability settings — launch day checklist #technical - [H3] Monitor traffic for 3-4 weeks post-launch — recovery timeline #analytics ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Google Search Console](https://search.google.com/search-console) - [Screaming Frog SEO Spider](https://www.screamingfrog.co.uk/seo-spider/) ## 📝 Summary - **What happened**: Tina Risse presented a lightning talk on preventing SEO disasters during website relaunches - **Why it matters**: Website relaunches can cause 90%+ traffic losses if not handled properly from an SEO perspective - **Key stakeholders**: WordPress developers, SEO consultants, site owners planning relaunches - **Risks and tradeoffs**: Google treats URL changes as new pages, losing historical ranking data; changes must balance innovation with SEO preservation - **Bottom line takeaway**: Follow a structured pre-launch audit, avoid URL changes when possible, and monitor carefully for 3-4 weeks post-launch ## 📖 Main Content Website relaunches create a fundamental tension between developer excitement for fresh designs and SEO concerns about traffic preservation. Google's conservative algorithm treats URL changes as completely new pages, discarding historical ranking data, backlinks, and user signals associated with the original URLs. Even when content remains identical, changed URLs must rebuild their search authority from scratch. The core challenge stems from Google's unpredictable response to simultaneous changes. While small, gradual updates signal freshness and currency, wholesale changes across content and structure trigger algorithmic uncertainty. Google essentially asks: "If this looks very different, how do we know users will still find it valuable?" This leads to temporary or permanent ranking decreases until new performance data accumulates. However, relaunches also present opportunities for long-term SEO growth through improved user experience, faster loading times, and better technical implementation—factors Google rewards in its ranking algorithms. ## 🗒️ Notes #### ⏱️ [01:30](https://www.youtube.com/watch?v=GtWz7wBahJw&t=90) — [H1] Speaker introduction and dual perspective - Key idea: Tina Risse brings both SEO consultant and WordPress developer perspectives to relaunch challenges - Evidence: "8 years ago doing SEO... now also a WordPress developer with focus on accessibility" #### ⏱️ [02:15](https://www.youtube.com/watch?v=GtWz7wBahJw&t=135) — [H2] The emotional conflict of relaunches - Key idea: Developers get excited while SEO professionals feel nervous about relaunches - Evidence: "As developer I get excited... but as SEO person when I hear relaunch I'm more like why" #### ⏱️ [02:45](https://www.youtube.com/watch?v=GtWz7wBahJw&t=165) — [H1] Massive traffic loss example - Key idea: Relaunches can cause catastrophic SEO damage when done incorrectly - Evidence: "One example of website that lost over 90% of its traffic because of relaunch gone wrong" #### ⏱️ [03:30](https://www.youtube.com/watch?v=GtWz7wBahJw&t=210) — [H1] Why Google dislikes change - Key idea: Google's algorithm is inherently conservative and treats any change as risky - Evidence: "Google is just really conservative it does not like change... known to freak out at tiniest changes" #### ⏱️ [04:00](https://www.youtube.com/watch?v=GtWz7wBahJw&t=240) — [H1] URL changes lose historical data - Key idea: Changing URLs destroys all accumulated SEO value and forces pages to restart ranking from zero - Evidence: "Google attaches everything it knows... to the URL when that URL changes... treated as completely new page" #### ⏱️ [05:00](https://www.youtube.com/watch?v=GtWz7wBahJw&t=300) — [H2] Content and structure changes trigger uncertainty - Key idea: Simultaneous large-scale changes make Google question whether users will still find the site valuable - Evidence: "When you change a lot of things all at once Google is more like... how do we know users will like it as much" #### ⏱️ [05:45](https://www.youtube.com/watch?v=GtWz7wBahJw&t=345) — [H1] Pre-launch step 1: Understand current rankings - Key idea: Use SEO tools to identify your most valuable pages that need protection during relaunch - Evidence: "Use SEO tool of your choice... Google search console... gives you traffic driving pages" #### ⏱️ [06:15](https://www.youtube.com/watch?v=GtWz7wBahJw&t=375) — [H1] Pre-launch step 2: Crawl all current URLs - Key idea: Use crawling tools to discover all existing URLs including hidden content for redirect planning - Evidence: "All websites have a lot of stuff hidden somewhere... use crawling tool... Screaming Frog" #### ⏱️ [07:00](https://www.youtube.com/watch?v=GtWz7wBahJw&t=420) — [H1] Development principle: Avoid URL changes - Key idea: The best SEO strategy is preventing URL changes entirely, as redirects offer no guarantees - Evidence: "Try to avoid URL changes... 301 redirect... Google will usually transfer ranking data... but no guarantee" #### ⏱️ [07:45](https://www.youtube.com/watch?v=GtWz7wBahJw&t=465) — [H2] Keep traffic-driving content intact - Key idea: Preserve the core content and search intent of your highest-performing pages - Evidence: "Keep traffic driving topics and pages... content stays roughly the same... search intent... still there" #### ⏱️ [08:30](https://www.youtube.com/watch?v=GtWz7wBahJw&t=510) — [H2] Navigation link importance confirmed by Google leaks - Key idea: Google's algorithm gives special weight to pages linked in site navigation - Evidence: "Recently leaked Google algorithm documents... Google gives weight to what is linked in navigation" #### ⏱️ [09:00](https://www.youtube.com/watch?v=GtWz7wBahJw&t=540) — [H2] Avoid keyword cannibalization - Key idea: Don't split content from one URL across multiple pages as it creates internal competition - Evidence: "Don't spread content across different URLs... keyword cannibalization... multiple pages competing for same keywords" #### ⏱️ [09:45](https://www.youtube.com/watch?v=GtWz7wBahJw&t=585) — [H1] Check WordPress indexability setting - Key idea: The most common post-launch disaster is forgetting to uncheck WordPress's search engine visibility blocker - Evidence: "Little checkbox... couple of clients called... our website not on Google at all... this checkbox was ticked" #### ⏱️ [10:30](https://www.youtube.com/watch?v=GtWz7wBahJw&t=630) — [H2] Post-launch monitoring timeline - Key idea: Allow 3-4 weeks for Google to process changes before judging relaunch success - Evidence: "Sit tight and monitor... for about 3 to 4 weeks... how long it might take Google to notice and process changes" #### ⏱️ [11:15](https://www.youtube.com/watch?v=GtWz7wBahJw&t=675) — [H1] Relaunches as long-term opportunity - Key idea: Despite short-term risks, relaunches can improve SEO through better user experience and technical improvements - Evidence: "Relaunch is also always a chance... to grow long term... improved user experience... load faster... things Google likes" ## 📚 References - [Google Search Console](https://search.google.com/search-console/) - [Screaming Frog SEO Spider](https://www.screamingfrog.co.uk/seo-spider/) - [WordPress SEO Settings](https://wordpress.org/support/article/search-engine-optimization/) ## 🗣️ Paraphrase - Website relaunches create inherent conflict between development innovation and SEO stability, requiring careful planning to avoid traffic disasters - Google's conservative algorithm treats URL changes as new pages, discarding historical ranking data and requiring sites to rebuild search authority from scratch - Success requires pre-launch auditing of current performance, minimizing URL changes during development, and patient monitoring for 3-4 weeks post-launch while Google processes changes ## 📰 Newsletter 🚀 **Website Relaunch Without SEO Disaster** Planning a WordPress site relaunch? SEO consultant Tina Risse shares battle-tested strategies to protect your search traffic during major site changes. **Key insight**: Google treats URL changes as completely new pages, wiping out years of ranking history. Her approach focuses on preservation over perfection. **Before you launch**: Audit current rankings with Google Search Console, crawl all existing URLs with tools like Screaming Frog, and map redirects in advance. Most importantly—avoid URL changes whenever possible. **The hidden killer**: WordPress's "Discourage search engines" checkbox. Multiple clients lost all Google visibility because developers forgot to uncheck this setting post-launch. **Timeline reality**: Allow 3-4 weeks for Google to process changes. Short-term dips are normal, but proper planning prevents permanent traffic loss. Resources: [Google Search Console](https://search.google.com/search-console), [Learn WordPress SEO](https://learn.wordpress.org/lesson-plan/search-engine-optimization/), [WP-CLI Search Replace](https://wp-cli.org/commands/search-replace/) ## ✅ Action Items #### WordPress - Core: Add relaunch checklist to WordPress admin dashboard warnings - Documentation: Create comprehensive relaunch guide linking SEO and development best practices - Community: Develop relaunch workshop curriculum for local meetups - Support: Build knowledge base articles for common post-relaunch SEO issues - Training: Create learning path connecting technical implementation with SEO outcomes ## 🧪 Hypotheses - Sites that avoid URL changes during relaunches maintain 85%+ of their organic traffic within 4 weeks - WordPress sites with the search engine visibility checkbox accidentally enabled lose 95%+ of organic traffic within 2 weeks - Relaunches that preserve navigation links to high-traffic pages recover search rankings 40% faster than those that don't - Sites using 301 redirects for unavoidable URL changes retain 70-90% of original page authority ### 📊 Methodology - Longitudinal study tracking 100 WordPress site relaunches over 6 months, measuring traffic retention - A/B testing of relaunch approaches: URL-preserving vs. URL-changing strategies - Analysis of Google Search Console data before/after relaunches to quantify ranking recovery ### ❓ Questions - How do different redirect chain lengths affect SEO authority transfer during relaunches? - What is the optimal content similarity threshold for maintaining rankings on redesigned pages? - How does relaunch timing (seasonality, algorithm updates) impact traffic recovery rates? ### 🔮 Future Research - Impact of Core Web Vitals improvements during relaunches on ranking recovery - Effectiveness of different sitemap submission strategies post-relaunch - Correlation between internal link structure changes and traffic retention ### 💡 Implications - **Practice**: Developers must integrate SEO auditing into standard relaunch workflows rather than treating it as an afterthought - **Policy**: Agencies should establish mandatory SEO checkpoints before launching client sites to prevent traffic disasters - **Security**: URL mapping and redirect planning becomes critical infrastructure requiring documentation and testing - **Education**: WordPress training programs need integrated SEO modules rather than treating development and SEO as separate disciplines - **Funding**: Relaunch budgets must account for 3-4 weeks of monitoring and potential remediation work ### 🧠 Learning Styles Assessment Reading level estimate: 10th grade #### 👀 Visual learners - Present: Traffic loss example, WordPress checkbox screenshot - Improve: Before/after ranking charts, redirect flow diagrams, crawl result visualizations #### 🔊 Aural learners - Present: Conference presentation format with spoken explanations - Improve: Podcast-style case study discussions, audio checklist narrations #### 🗣️ Verbal learners - Present: Clear definitions of technical terms, analogies about Google's conservative behavior - Improve: Story-driven case studies, comparison tables of redirect types #### 🧩 Kinesthetic learners - Present: Step-by-step checklist format, hands-on tool recommendations - Improve: Interactive crawling exercises, redirect testing workshops #### 🧠 Logical learners - Present: Clear pre/during/after timeline, cause-effect relationships - Improve: Decision trees for URL change scenarios, ROI calculations for SEO preservation #### 🧑‍🤝‍🧑 Social learners - Present: Conference community setting, invitation to share relaunch stories - Improve: Peer review groups for relaunch plans, collaborative post-mortems #### 🧘‍♀️ Solitary learners - Present: Self-contained checklist, individual audit instructions - Improve: Self-assessment rubrics, private progress tracking tools #### 🌿 Naturalistic learners - Present: Ecosystem thinking about site interconnectedness - Improve: Analogies to habitat preservation, sustainable growth metaphors ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive technical terms - Improve: More detailed alt text for any visual examples, ARIA labels for complex processes #### Keyboard navigation - Present: Standard presentation format - Improve: Ensure any interactive elements are keyboard accessible #### Contrast and readability - Present: Conference presentation likely meets basic contrast - Improve: Verify slide text meets 4.5:1 ratio, use larger fonts for technical details #### Text resizing and reflow - Present: Presentation format adaptable - Improve: Ensure content reflows properly at 200% zoom #### Media and captions - Present: Video has transcript provided - Improve: Add timestamps to transcript sections, provide downloadable checklist #### Forms and interactions - Present: Minimal interactive elements - Improve: Any future interactive tools need proper labeling #### Standards reference - Content appears to meet WCAG 2.2 AA standards for informational content ### 🌍 DEIB Assessment #### Cultural breadth - Present: Single presenter perspective, European context - Improve: Include relaunch examples from different markets, consider non-English SEO factors #### Inclusive language - Present: Gender-neutral pronouns used, technical jargon defined - Improve: Avoid assumptions about team size or budget levels #### Neurodiversity support - Present: Structured timeline approach, clear categorization - Improve: More frequent heading breaks, consistent formatting patterns #### Representation - Present: Female presenter in technical role - Improve: Include diverse case studies, acknowledge different business contexts #### Psychological safety - Present: Emphasizes that SEO losses "are not your fault",