The Wix SEO emergency checklist: what to do when something goes catastrophically wrong

Every Wix website owner dreads the moment: you check your analytics and traffic has vanished, you Google your brand name and your site is not there, or you receive a terrifying email from Google Search Console about a manual action. SEO emergencies are rare but they do happen, and the difference between a swift recovery and months of lost revenue often comes down to how quickly and methodically you respond. Panic is natural, but panic without a plan causes people to make the situation worse. This lesson gives you a complete emergency response framework, nine specific emergency scenarios with step-by-step recovery procedures, a communication plan for clients, and a disaster recovery plan you can implement before an emergency ever occurs. Print this lesson, bookmark it, and share it with your team, because when an SEO emergency strikes, you will not have time to search for answers.

When to Declare an SEO Emergency vs Normal Fluctuations

Not every ranking drop is an emergency. Search rankings fluctuate naturally due to algorithm refreshes, competitor activity, seasonal trends, and index updates. Declaring a false emergency wastes time and creates unnecessary stress. Use these thresholds to determine whether you are dealing with a genuine SEO emergency or normal search volatility.

• Normal fluctuation: Position changes of 1-5 places for individual keywords over a few days. This is completely normal and does not require action.
• Concerning but not emergency: 20-30% traffic drop over 1-2 weeks. Monitor closely, check for algorithm updates, review recent changes to your site, but do not take drastic action yet.
• Moderate emergency: 50%+ traffic drop sustained for more than 3 days with no obvious external cause (algorithm update, seasonality). Begin diagnostic procedures.
• Severe emergency: 90%+ traffic drop overnight, complete deindexation, manual penalty notification, or site compromised by hackers. Activate emergency response immediately.
• Critical context: A 50% traffic drop on a site that generates GBP 500/month from organic search has different urgency than the same drop on a site generating GBP 50,000/month. Calibrate your response intensity to the business impact.

The SEO Triage Framework: Assess, Prioritise, Act, Monitor

Regardless of the specific emergency, follow this four-stage framework to ensure a structured response that does not make things worse.

SEO triage framework

• ASSESS: Gather data before taking any action. What exactly has changed? When did it start? What is the scope (site-wide or specific pages)? Check Google Search Console, Google Analytics, and Google itself. Document your findings.
• PRIORITISE: Determine the root cause and the severity. Is this a technical issue, a penalty, an algorithm update, or an external attack? Rank the potential causes by likelihood and impact.
• ACT: Implement fixes starting with the most likely cause. Make one change at a time where possible so you can identify what resolves the issue. Document every action you take with timestamps.
• MONITOR: After implementing fixes, monitor results daily for at least 2-4 weeks. SEO recovery is rarely instant. Set up alerts so you know immediately if the situation changes.

Emergency 1: Site Completely Deindexed

Your entire website has been removed from Google search results. Searching for site:yourdomain.com returns zero results. This is the most severe SEO emergency and requires immediate action.

Step-by-step recovery from complete deindexation

• Verify the deindexation: Search for site:yourdomain.com on Google. If zero results appear, the site is deindexed. Also check Google Search Console Page Indexing report for a sudden drop to zero indexed pages.
• Check for a manual action: Log into Google Search Console > Security & Manual Actions > Manual Actions. If a manual action is listed, follow the Emergency 2 procedure below.
• Check for a site-wide noindex: View your published site's page source (Ctrl+U in Chrome) and search for "noindex". Check the robots meta tag in the HTML head. On Wix, go to Settings > SEO (Google) > Robots Meta Tags and ensure noindex is NOT enabled for your homepage or site-wide.
• Check robots.txt: Visit yourdomain.com/robots.txt. Look for "Disallow: /" which would block all crawling. On Wix, go to Settings > SEO (Google) > robots.txt Editor and verify no disallow rules are blocking the entire site.
• Check DNS and domain connectivity: Ensure your domain is properly connected to Wix. Go to your domain registrar and verify DNS records are pointing to Wix servers. If the domain expired or DNS was changed, this could cause deindexation.
• Check for hacking: Look for signs of site compromise (spam content, redirects to other sites, injected code). If hacked, follow Emergency 4 procedure.
• If none of the above apply: The site may have been deindexed due to a severe quality issue or algorithm action. Review all content for compliance with Google's spam policies. Remove any content that could violate guidelines.
• Request reindexing: After fixing the identified issue, use the URL Inspection tool to request indexing for your homepage first, then your most important pages.
• Submit your sitemap: Resubmit your sitemap in Google Search Console to prompt Google to recrawl all pages.
• Monitor: Check the Page Indexing report daily. Pages should begin reappearing in the index within 1-7 days if the underlying issue has been resolved.

Emergency 2: Manual Penalty Received

You received a notification in Google Search Console that a manual action has been applied to your Wix site. A manual action means a human reviewer at Google has determined your site violates Google's spam policies. This requires a specific, documented response and a formal reconsideration request.

Step-by-step manual penalty recovery

• Read the manual action notice carefully: Log into Google Search Console > Security & Manual Actions > Manual Actions. Note the exact type of manual action and which pages are affected (site-wide or partial).
• Understand the violation: Each manual action type corresponds to a specific spam policy violation (see the GSC errors lesson above for details on each type). Understand exactly what Google is objecting to.
• Document the current state: Take screenshots of the manual action notice, the affected pages, and any problematic content. This documentation is valuable for the reconsideration request.
• Fix the violation thoroughly: Remove all content, links, or practices that violate the policy. Be thorough, as Google will deny reconsideration requests if violations remain. For unnatural links, audit and disavow toxic backlinks. For thin content, substantially expand every flagged page. For spam, remove all spammy elements.
• Document every fix: Create a detailed record of every action taken, including: what was wrong, what you fixed, when you fixed it, and how you ensured it will not recur.
• Submit a reconsideration request: In GSC, under the Manual Actions section, click "Request Review". Write a detailed, honest explanation of what caused the issue, every step you took to fix it, and what measures you have put in place to prevent recurrence. Be transparent, do not make excuses, and demonstrate genuine effort to comply.
• Wait for Google's response: Reconsideration reviews typically take 2-6 weeks. You will receive a notification in GSC when the review is complete.
• If denied: Google will usually explain what issues remain. Fix the remaining issues, update your documentation, and resubmit. There is no limit on reconsideration requests, but each one requires genuine additional fixes.
• If approved: The manual action will be lifted. Rankings should begin recovering within days to weeks, though full recovery to pre-penalty levels may take 2-6 months.
• Post-recovery audit: After the manual action is lifted, conduct a thorough audit of your entire site to ensure no similar violations exist on other pages that were not flagged.

Emergency 3: 90%+ Traffic Drop Overnight

You wake up to find organic traffic has almost completely disappeared. This is alarming but the diagnostic process is systematic. The cause is almost always one of a few specific things.

Diagnostic steps for catastrophic traffic loss

• First, verify the data is accurate: Check your analytics tracking code is still installed on your Wix site. A broken or removed tracking code mimics a traffic drop. Open your site in an incognito window and verify the analytics script is present in the page source.
• Check Google Search Console messages: Log in and look for any new messages or alerts. Google often sends warnings before or during major issues.
• Check for manual actions: Navigate to Security & Manual Actions. This is the first diagnostic step for any severe traffic drop.
• Check the Page Indexing report: Has the number of indexed pages dropped dramatically? If yes, investigate indexing issues (noindex, robots.txt blocks, deindexation).
• Check for a Google algorithm update: Search for "Google algorithm update" along with the current date. Visit sites like Search Engine Land, Search Engine Roundtable, and the Google Search Status Dashboard. If a confirmed algorithm update occurred on the same date as your traffic drop, the two are likely related.
• Check for site changes: Did you or anyone on your team make changes to the Wix site in the days before the drop? Changes to URL structure, page deletions, noindex settings, robots.txt, redirects, site redesign, or major content changes can all cause traffic drops.
• Check domain and hosting: Is your site accessible? Can you load it in a browser? Check if the domain is expired, DNS has changed, or if there is a Wix platform outage.
• Check Core Web Vitals: Has site speed dramatically worsened? A severe speed regression can cause ranking drops.
• Check backlink profile: Use Ahrefs or Semrush to check if you have lost a significant number of backlinks recently. A major backlink loss can cause ranking drops.
• Implement the fix for the identified cause and monitor daily for 2-4 weeks.

Emergency 4: Site Hacked or Defaced

Your Wix site has been compromised: spam content appears on your pages, visitors are redirected to malicious sites, or Google Search Console shows a security issue. While Wix's platform security makes full-scale hacking rare, compromised accounts, malicious third-party apps, or injected Custom Code can create similar situations.

Security and SEO recovery from a hacked Wix site

• Change your Wix account password immediately. Use a strong, unique password and enable two-factor authentication (2FA) if not already active.
• Change passwords for all connected accounts: Google Search Console, Google Analytics, domain registrar, email accounts, and any third-party services connected to your Wix site.
• Audit and remove suspicious Custom Code: Go to Settings > Custom Code in the Wix dashboard. Review every code injection. Remove anything you did not add or do not recognise. Pay particular attention to script tags that reference unfamiliar external URLs.
• Review and remove suspicious apps: Go to your Wix App Market dashboard and review all installed apps. Remove any apps you did not install or that seem suspicious. Even legitimate apps can be compromised.
• Check Velo code: If you use Velo by Wix, review all page code, site code, and backend modules for any code you did not write. Look for fetch() calls to unfamiliar domains, base64-encoded strings, or obfuscated code.
• Review all pages for spam content: Systematically check every page of your site for injected content, hidden text, or spam links. Pay attention to footer areas, comment sections, and dynamic pages.
• Check redirects: Test your site pages to ensure they load normally and are not redirecting to external sites. Check on both desktop and mobile, and from different geographic locations.
• After cleaning up: Request a security review in Google Search Console. Navigate to Security & Manual Actions > Security Issues and click "Request a Review". Describe the issue and the steps you took to resolve it.
• Submit a sitemap resubmission to prompt Google to recrawl your clean pages.
• Monitor your site daily for 30 days after the incident to ensure the compromise does not recur.

Emergency 5: Accidental Noindex on Entire Site

Someone accidentally applied a noindex tag to the entire Wix site, causing all pages to be deindexed. This can happen through the Wix SEO settings, a Custom Code injection, or a Velo code error. It is one of the fastest emergencies to fix but one of the slowest to recover from because Google must recrawl every page.

Immediate fix for accidental site-wide noindex

• Check Wix SEO settings: Go to Settings > SEO (Google) > Robots Meta Tags. Ensure "noindex" is NOT applied at the site level.
• Check individual page settings: If the noindex was applied page by page, you need to check and update each page. In the Wix Editor, open each page's SEO settings and remove the noindex directive.
• Check Custom Code: Go to Settings > Custom Code. Look for any meta tags that include "noindex". Remove them immediately.
• Check robots.txt: Go to Settings > SEO (Google) > robots.txt Editor. Ensure there are no disallow rules blocking important pages.
• Check Velo code: If you use Velo, search for any code that programmatically sets noindex via the wixSeo API. Remove or correct the code.
• Publish the site immediately after removing all noindex directives.
• In Google Search Console, use the URL Inspection tool to request indexing for your homepage and top 10 most important pages.
• Resubmit your sitemap in Google Search Console to prompt Google to recrawl all pages.
• Monitor the Page Indexing report daily. Pages should begin returning to the index within 2-7 days, but full reindexation of a large site can take 2-4 weeks.
• Document the incident: what caused the noindex, when it was applied, when it was discovered, and when it was fixed. Use this to create a prevention checklist.

Emergency 6: Domain Expired or DNS Failure

Your domain has expired, DNS records have been incorrectly changed, or your domain registrar has suspended the domain. The result is the same: your Wix site becomes inaccessible, and Google cannot crawl it.

Recovery steps for domain and DNS issues

• Check domain status: Go to your domain registrar (GoDaddy, Namecheap, Google Domains, etc.) and check the domain status. Is it expired? Is it on hold? Are there any pending transfers?
• If expired: Renew the domain immediately. Most registrars allow renewal within a grace period (typically 30-40 days after expiration). After renewal, DNS propagation takes 24-48 hours.
• If past the grace period: The domain may be in a redemption period (additional 30 days) where renewal costs significantly more (often GBP 100-200+). Pay the redemption fee immediately, as losing the domain to a third party would be catastrophic for SEO.
• If DNS was changed: Log into your domain registrar and verify DNS records point to Wix servers. Wix requires specific DNS records (CNAME or A records) that are detailed in your Wix dashboard under Settings > Domains.
• If using Wix-purchased domain: Contact Wix support directly as they manage the domain registration. Check your Wix billing settings to ensure payment information is current.
• After restoring the domain: Verify your site loads correctly at both the root domain and www subdomain.
• Check Google Search Console: The property should reconnect automatically once the domain is live. Verify ownership is still confirmed.
• Request indexing for your homepage and key pages to accelerate Google rediscovering your site.
• Set up auto-renewal: Enable automatic domain renewal to prevent this from happening again. Set calendar reminders 30 days before expiration as a backup.
• Monitor search results for 2-4 weeks. If the domain was down for more than a few hours, some pages may have been temporarily deindexed and will need to be recrawled.

Emergency 7: Major Algorithm Update Hit

Google releases several major algorithm updates each year (core updates, helpful content updates, spam updates, etc.). If your Wix site is significantly impacted by an algorithm update, the recovery process is different from technical emergencies because there may be nothing technically wrong with your site. Instead, Google has changed what it considers high-quality content or authoritative signals.

Response strategy for algorithm update impact

• Confirm the algorithm update: Check the Google Search Status Dashboard (status.search.google.com/summary), Search Engine Land, Search Engine Roundtable, and social media for confirmed update announcements.
• Wait for the update to complete: Major algorithm updates roll out over 1-2 weeks. Do not make changes while the update is still rolling out, as rankings fluctuate significantly during the rollout period.
• Analyse the impact: After the update completes, compare your traffic and rankings data from before the update to after. Identify which pages lost rankings and which queries were affected.
• Study the update's focus: Google usually announces what the update targets. Core updates focus on overall content quality. Helpful content updates target unhelpful, low-quality content. Spam updates target manipulative practices. Align your analysis with the update's stated purpose.
• Audit affected pages against Google's quality guidelines: For each significantly impacted page, honestly assess: Does this page demonstrate Experience, Expertise, Authority, and Trustworthiness (E-E-A-T)? Is the content genuinely helpful? Would you be satisfied with this content if you were the searcher?
• Improve content quality: Rewrite and expand thin or unhelpful pages. Add original research, expert insights, personal experience, and unique value that competitors do not offer.
• Strengthen E-E-A-T signals: Add author bios with credentials, cite authoritative sources, update outdated information, and improve the overall trustworthiness of your site (privacy policy, contact information, about page).
• Remove or consolidate low-quality content: If you have many thin, duplicate, or low-value pages, consolidate them into fewer, higher-quality pages or remove them entirely.
• Be patient: Recovery from algorithm updates typically takes until the next update of the same type (often 3-6 months). There is no quick fix for algorithm-based ranking changes.
• Continue publishing high-quality content consistently. Google rewards sites that demonstrate sustained quality improvement over time.

Emergency 8: Negative SEO Attack

Negative SEO involves a competitor or malicious actor attempting to harm your rankings through external manipulation, most commonly by building thousands of spammy or toxic backlinks pointing to your Wix site. While Google claims its algorithms can largely ignore manipulative links, the risk is real enough that a response plan is warranted.

Identification and response to negative SEO

• Identify the attack: Signs include a sudden spike in backlinks from low-quality or irrelevant domains, backlinks with spammy anchor text (pharmaceutical terms, gambling keywords, adult content), or thousands of links appearing overnight from foreign-language directories.
• Audit your backlink profile: Use Ahrefs, Semrush, or Moz to export your complete backlink profile. Filter for links acquired in the timeframe of the suspected attack.
• Document the attack: Record the timeline, the volume of toxic links, the types of linking domains, and the anchor text patterns. This documentation is useful if you need to file a spam report or reconsideration request.
• Create a disavow file: In a text file, list the domains you want Google to ignore. Use the "domain:" prefix to disavow entire domains (e.g. "domain:spammysite.com"). Include all domains involved in the attack.
• Submit the disavow file: Upload it via the Google Disavow Tool (search.google.com/search-console/disavow-links). This tells Google to ignore these links when evaluating your site.
• Monitor for ongoing attacks: Negative SEO attacks are often sustained over weeks or months. Set up weekly backlink monitoring alerts in Ahrefs or Semrush to detect new toxic links quickly.
• Report the attack: If you can identify the source, file a web spam report with Google. Provide your documentation of the attack pattern.
• Strengthen your positive link profile: The best defence against negative SEO is a strong, natural backlink profile. Continue building high-quality backlinks that outweigh any toxic links.
• Consider Google's perspective: Google has become increasingly sophisticated at identifying and ignoring manipulative links. In many cases, a negative SEO attack has less impact than feared. Do not panic, but do respond systematically.

Emergency 9: Wix Platform Outage Affecting SEO

While rare, Wix platform outages can make your site temporarily inaccessible to both users and Googlebot. When Google encounters a down site, the SEO impact depends on the duration and frequency of the outage.

• Short outages (under 1 hour): Generally no SEO impact. Google expects occasional downtime and will retry crawling later.
• Medium outages (1-6 hours): Minimal long-term SEO impact but may cause temporary ranking fluctuations. Google may temporarily show cached versions of your pages.
• Extended outages (6-24+ hours): Can cause pages to be temporarily deindexed if Google crawls during the outage and receives server errors consistently. Rankings typically recover within days after the site comes back online.
• Repeated outages: If your Wix site experiences frequent downtime, Google may reduce crawl frequency and lower rankings due to poor user experience signals.

What you can do during a Wix platform outage

• Verify the outage is Wix-wide (not just your site): Check the Wix Status Page (status.wix.com), social media (search "Wix outage" on Twitter/X), and DownDetector for Wix.
• Document the outage: Record the start time, duration, and which functions are affected. This documentation is useful if you need to explain a temporary ranking drop to clients.
• Do NOT make changes to your Wix site during the outage: Changes made during instability may not save correctly or could cause additional problems.
• If you have access to Google Search Console: Check the crawl stats to see if Googlebot is encountering errors. Do not make any changes to Search Console settings during the outage.
• Communicate with stakeholders: If the outage is extended, inform clients or team members that it is a platform-wide issue outside your control, and provide the Wix Status Page link.
• After the outage resolves: Verify your site loads correctly on all pages. Check your most important pages in a browser.
• Request indexing for key pages: If the outage lasted more than a few hours, use the URL Inspection tool to request indexing for your top 10 pages to prompt Google to recrawl them with the correct content.
• Monitor rankings for 1-2 weeks: If you notice lasting ranking drops after a resolved outage, investigate further, as the outage may have coincided with other issues.

Communication Plan for Clients During SEO Emergencies

If you manage SEO for client Wix websites, how you communicate during an emergency is as important as how you fix the problem. Clients who are kept informed and reassured are far more likely to remain calm and supportive during the recovery process.

• Immediate notification (within 1 hour of discovery): Send a brief message acknowledging the issue, stating that you are investigating, and providing an estimated timeline for your first update. Do not speculate on causes yet.
• Initial assessment (within 4 hours): Provide a clear summary of what has happened, what you believe the cause is, what steps you are taking, and when you expect to have more information. Use simple language, avoiding jargon.
• Daily updates during active recovery: Send a brief daily update summarising progress, actions taken, and next steps. Include data where possible (e.g. "15 of 50 pages have been reindexed").
• Resolution notification: When the issue is resolved, send a detailed summary including: what happened, the root cause, what you did to fix it, what preventive measures you have implemented, and the expected timeline for full recovery.
• Post-mortem report (within 1 week): Provide a formal written report documenting the entire incident from detection to resolution, with lessons learned and preventive measures for the future.

Documenting and Learning from SEO Emergencies

Every SEO emergency is a learning opportunity. A structured post-mortem ensures you extract maximum value from the experience and reduce the likelihood of recurrence.

Post-mortem documentation framework

• Timeline: Document every event from the first sign of the problem to full resolution, including timestamps for: issue detected, initial assessment complete, root cause identified, fix implemented, fix verified, and full recovery confirmed.
• Root cause analysis: Identify the true underlying cause, not just the immediate trigger. Use the "5 Whys" technique: ask "why" five times to drill down from the symptom to the root cause.
• Impact assessment: Quantify the impact in terms of: pages affected, traffic lost (sessions and revenue), duration of the impact, and estimated cost to the business.
• Response evaluation: Assess how effectively you responded. What went well? What could have been faster? Were the right people notified quickly enough? Did you have the access and tools you needed?
• Preventive measures: List specific actions you will take to prevent this type of emergency from recurring. Assign each action to a specific person with a deadline.
• Update your emergency checklist: Add any new procedures or steps you discovered during this incident to your master emergency checklist.

Building an SEO Disaster Recovery Plan

The best time to prepare for an SEO emergency is before it happens. A proactive disaster recovery plan reduces response time and prevents panic-driven mistakes.

• Maintain a current backup of all critical SEO data: Export your keyword rankings monthly, save copies of important page content, document your sitemap structure, and record your backlink profile baseline.
• Create a documented list of all access credentials needed during an emergency: Google Search Console, Google Analytics, Wix dashboard, domain registrar, CDN (if any), and email hosting. Store these securely but ensure they are accessible to at least two team members.
• Set up monitoring alerts: Configure Google Search Console email notifications, set up Google Analytics alerts for traffic drops exceeding 50%, use a third-party monitoring tool (like Ahrefs or Semrush) for ranking alerts, and monitor your site uptime with a tool like UptimeRobot.
• Create a pre-approved emergency contacts list: Include your Wix support contact, domain registrar support, any third-party SEO tool support contacts, and your development team contacts.
• Document your site's SEO configuration: Record all meta tag settings, robots.txt configuration, Custom Code injections, installed apps, Velo code overview, redirect rules, and canonical tag strategy. This documentation is invaluable when diagnosing what changed.
• Test your disaster recovery plan annually: Run a tabletop exercise where you simulate an SEO emergency and walk through your response procedures. Identify gaps and update the plan accordingly.
• Keep this lesson bookmarked and accessible: When an emergency occurs, you need immediate access to step-by-step procedures, not hours of research.

The Complete Emergency Response Checklist

This is your master checklist for any SEO emergency. Follow these steps in order when something goes catastrophically wrong with your Wix site's SEO.

Master SEO emergency response checklist

• STOP: Do not make any changes to your site yet. Gather data first.
• VERIFY: Confirm the issue is real. Check analytics tracking is working. Check from multiple devices and locations. Check with multiple tools.
• ASSESS SEVERITY: Use the thresholds in this lesson to determine if this is a normal fluctuation, a moderate issue, or a severe emergency.
• CHECK MANUAL ACTIONS: Log into Google Search Console > Security & Manual Actions. If a manual action exists, follow Emergency 2 procedure.
• CHECK SECURITY ISSUES: In GSC, check for security issues. If present, follow Emergency 4 procedure.
• CHECK SITE ACCESSIBILITY: Can you load your site in a browser? If not, check domain status and Wix platform status. Follow Emergency 6 or Emergency 9 as appropriate.
• CHECK INDEXING: In GSC Page Indexing report, has the number of indexed pages changed dramatically? If pages have been deindexed, check for noindex (Emergency 5), robots.txt blocks, or complete deindexation (Emergency 1).
• CHECK FOR ALGORITHM UPDATES: Search for recent Google algorithm updates. If an update coincides with your traffic drop, follow Emergency 7 procedure.
• CHECK FOR NEGATIVE SEO: Audit your backlink profile for sudden spikes in toxic links. If detected, follow Emergency 8 procedure.
• CHECK RECENT SITE CHANGES: Review what changes were made to your Wix site in the days before the issue. Changes to site structure, content, settings, or apps are common causes of ranking drops.
• IMPLEMENT THE FIX: Based on your diagnosis, follow the specific emergency procedure from this lesson.
• DOCUMENT EVERYTHING: Record the issue, diagnosis, actions taken, and results in your incident log.
• COMMUNICATE: Notify relevant stakeholders (clients, team members) following the communication plan in this lesson.
• MONITOR: Check results daily for 2-4 weeks. Set up additional alerts to catch any recurrence.
• POST-MORTEM: After recovery, conduct a thorough post-mortem and update your disaster recovery plan.

Complete How-To Guide

Complete step-by-step guide to building and using your Wix SEO emergency response system

• Create your SEO emergency response document now, before any emergency occurs. Use a shared document (Google Docs, Notion, or similar) that is accessible to all team members from any device.
• Copy the emergency response checklist from this lesson into your document. Customise it with your specific site details, access credentials (stored securely), and team contact information.
• Set up your monitoring stack: Enable Google Search Console email notifications for all issue types. Create a Google Analytics alert for organic traffic drops exceeding 30% week-over-week. Set up a free UptimeRobot monitor for your Wix site. If budget allows, configure Ahrefs or Semrush rank tracking alerts.
• Document your current SEO configuration baseline: export your current indexed pages count from GSC, record your current average organic traffic level, document all custom code injections, list all installed Wix apps, and note your current robots.txt and sitemap configuration.
• Create your access credentials file: list every platform credential needed during an emergency (GSC, Analytics, Wix dashboard, domain registrar). Store securely using a password manager and ensure at least two team members have access.
• Set up your communication templates: pre-write email templates for initial notification, progress updates, and resolution notifications. Having templates ready saves valuable time during an actual emergency.
• Run a practice drill: simulate an SEO emergency (e.g. "Imagine your traffic dropped 90% overnight") and walk through the emergency checklist. Time yourself and note where you hesitate or need more information.
• Schedule quarterly reviews: every 3 months, review and update your emergency response document. Verify all credentials are current, monitoring alerts are functioning, and the checklist reflects any new procedures.
• When an actual emergency occurs: open your emergency response document, follow the master checklist step by step, and resist the urge to skip steps or take shortcuts.
• After each real emergency: update your response document with lessons learned. Add any new steps, tools, or contacts that proved necessary during the incident.
• Share this process with your team or clients: ensure everyone who manages a Wix site knows the emergency response procedure exists and where to find it.
• Review the nine specific emergency scenarios in this lesson annually. Familiarise yourself with the procedures so they are not completely new when you need them.