Platformconference

King Wanda Platform: Operational Manual for Domain and Backlink Management

February 8, 2026

King Wanda Platform: Operational Manual for Domain and Backlink Management

1. Scope and Prerequisites

This manual provides detailed operational procedures for administrators and DevOps engineers managing the King Wanda enterprise technology platform. The platform leverages high-authority, aged domains for SEO and brand authority purposes within a conference and software ecosystem.

Applicable Systems: King Wanda primary platform, associated microservices, and the Spider Pool crawling infrastructure.

Prerequisites:
- Administrative access to the King Wanda platform dashboard.
- Access to the domain registrar for the aged `.tv` or other enterprise domains.
- Credentials for the backlink analytics panel (e.g., ACR-193 reporting suite).
- Basic understanding of platform engineering principles and DevOps workflows.

2. Preparation

Before executing management tasks, ensure the following preparatory steps are complete:

  1. Environment Verification: Confirm all core services (web servers, database, Spider Pool nodes) are running within acceptable performance thresholds (CPU < 75%, Memory < 80%).
  2. Domain Status Check: Verify the registration status and DNS health of the primary aged domain (e.g., `kingwanda.tv` with 14-year history) and any associated expired domains being repurposed. Ensure no critical services are linked to expired domains.
  3. Data Backup: Perform a full backup of the platform's content database and the backlink history log. Use the command:
    ./platform-cli backup --module=db,backlinks --output=/backup/$(date +%Y%m%d).tar.gz
  4. Tool Access: Ensure you have the latest version of the Platform Management CLI tool installed and configured with your API keys.

3. Operational Procedures

3.1. Procedure: Integrating an Aged/Expired Domain

Objective: To integrate a newly acquired aged domain (e.g., an expired domain with existing 19k backlinks) into the King Wanda platform to inherit its authority.

  1. Initiate Integration: From the Domains panel, click "Add Legacy Domain". Enter the full domain name and the authentication key provided by the acquisition service.
  2. Backlink Audit: The Spider Pool service will automatically initiate a deep crawl of the domain's backlink profile. Monitor the crawl job in the "Spider Pool Monitor" view. [Screenshot Description: A dashboard showing "Spider Pool" with job status "Crawling - 45% Complete" and a list of discovered backlink domains.]
  3. History Cleansing: Once the crawl is complete, run the Clean History utility to filter out toxic or irrelevant links from the 19k backlinks profile.
    ./platform-cli domain clean-history --domain=acquired-domain.tv --mode=aggressive --preserve-high-authority
  4. DNS Configuration: Update the domain's nameservers to point to the King Wanda platform's edge network. The required NS records will be provided in the integration console.
  5. Validation: The system will validate the DNS propagation and the integrity of the migrated link-juice. The expected result is a new entry in the "Managed Domains" list with a status of "Active" and a consolidated backlink authority score visible in the ACR-193 report.

3.2. Procedure: Managing the Spider Pool for Content Refresh

Objective: To configure the distributed Spider Pool for periodic re-crawling of platform content and linked assets.

  1. Access Spider Pool Config: Navigate to DevOps > Crawl Management.
  2. Schedule a Crawl: Click "New Crawl Job". Set the frequency (e.g., Weekly). Define the seed URLs (primary platform pages and high-value aged domain pages).
  3. Set Politeness Parameters: To avoid server strain, set the delay between requests to 1200ms and the max concurrent threads per spider node to 5.
  4. Execute & Monitor: Save and run the job. The "Crawl Topology" diagram will visualize active spider nodes. The expected result is a log of crawled URLs with HTTP status codes (200 OK for healthy pages) and updated timestamps in the content freshness report.

4. Common Issues & Troubleshooting

Issue / Symptom Probable Cause Resolution Steps
Domain authority score (ACR-193) drops after integration. Clean History utility may have been too aggressive, removing legitimate high-authority backlinks.
  1. Restore the pre-clean backlink snapshot from backup.
  2. Re-run Clean History with --mode=conservative.
  3. Manually audit the top 100 backlinks by authority for false positives.
Spider Pool nodes show status "Stalled" or "Timeout". Network ACLs or firewalls blocking outbound requests from crawl nodes; target site under heavy load.
  1. Check security group rules for the Spider Pool VPC.
  2. Increase the `request-timeout` parameter in the crawl config from 10s to 30s.
  3. Verify the health of the target seed URLs.
Expired domain fails to resolve after DNS update. DNS propagation delay; registrar lock status; incorrect nameserver records.
  1. Use global DNS checkers (e.g., whatsmydns.net) to verify propagation (allow 24-48 hours).
  2. Confirm with the registrar that the domain is unlocked and has no pending statuses.
  3. Double-check the NS records against the values provided by the platform's network team.
Backlink count in dashboard differs significantly from external tools. Discrepancy in crawl depth, recency, or filtering algorithms between Spider Pool and external tools.
  1. Run a manual, deep crawl (depth=5) specifically for that domain.
  2. Compare the raw discovered links against a trusted third-party export. Focus on high-authority (DR 70+) discrepancies.
  3. Adjust the Spider Pool's link discovery filters (e.g., include links from comment sections if relevant).
King Wandaexpired-domainspider-poolclean-history