What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
To host three WordPress sites as site1.example.com, site2.example.com, and site3.example.com on one server, choose either a domain-based WordPress Multisite network or three independent WordPress installations. Multisite centralizes code, updates, and administration; separate installations keep databases, upgrades, and failures more isolated. In both designs, the migration must move files and databases, create DNS records, route each hostname in the web server, update URLs safely, issue HTTPS certificates, and test every site before changing DNS.
Choose the architecture before moving anything
One physical or virtual server does not require one WordPress database. The architecture determines how you back up, update, secure, and recover the sites, so decide it before creating document roots or importing data.
Domain-based WordPress Multisite
A domain-based network uses one WordPress codebase and one network database to serve multiple sites. WordPress describes this as mapping different domain names to the same installation directory. In this migration, the network could serve site1.example.com, site2.example.com, and site3.example.com as separate sites inside one installation.
- Best fit: the sites have coordinated ownership, a common administrator team, and compatible plugin and theme policies.
- Administration: network administrators manage core updates, network-wide settings, and shared extensions from one dashboard.
- Trade-off: the sites share the codebase and database environment. A faulty network-level change or incompatible plugin can affect more than one site, and restoring one site independently is more involved.
Three separate installations
With separate installations, each site has its own directory, database, database credentials, and wp-config.php. The web server still runs all three sites on one machine, but WordPress treats them as unrelated applications.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
- Best fit: the sites need independent release schedules, different PHP or plugin policies, stronger tenant isolation, or site-by-site restores.
- Administration: updates, plugins, themes, users, and backups are managed separately.
- Trade-off: routine maintenance is repeated three times, and shared infrastructure still remains a common point of failure.
| Decision factor | Multisite | Separate installations |
|---|---|---|
| WordPress code | One codebase | Three codebases |
| Database model | One network database with site-specific tables | Three independent databases |
| Plugin and theme policy | Network-controlled and shared where enabled | Independent for each site |
| Failure blast radius | A network or shared-code failure can affect multiple sites | Usually limited to the affected installation, subject to server-wide failures |
| Backup and restore granularity | Network-aware backup and selective site restoration are required | Each site can be backed up and restored as its own unit |
| Domain mapping | One installation must map all hostnames and support subdomain rewrites | Each hostname points to its own document root |
| Operational skill | Requires Multisite, network-table, and shared-plugin knowledge | Requires repeatable administration of three normal WordPress sites |
Choose Multisite for coordinated sites with shared governance. Choose separate installations when isolation, independent upgrades, or simpler per-site recovery matter more than centralized administration.
Inventory the existing sites and freeze changes
Make a written inventory for each source site before provisioning the destination. Record the current domain, PHP version, database engine and version, active plugins, themes, media volume, scheduled jobs, email forms, analytics integrations, redirects, administrator accounts, and any server-side tasks. Note whether a plugin writes absolute URLs, stores files outside wp-content, or depends on a particular PHP extension.
Decide how the new hostnames will be assigned. For example, map the first site to site1.example.com, the second to site2.example.com, and the third to site3.example.com. List every old URL and the corresponding new URL; this mapping will drive redirects, serialized-data replacement, canonical tags, sitemap checks, and email links.
Announce a content freeze or maintenance window. Editors should stop publishing, uploading media, changing menus, and modifying settings before the final export. A freeze prevents the database dump and the file copy from representing different points in time. If a full freeze is impossible, record the final synchronization procedure and the changes that must be replayed after the first export.
Create backups that can actually restore the sites
Back up each source independently before touching DNS or changing production configuration. WordPress migration guidance says to back up the WordPress directory, images, plugins, other site files, and the database. Treat that as the minimum set, not an optional precaution.
- Export the complete database for each site, including tables created by plugins.
- Copy the entire WordPress directory, with particular attention to
wp-content/uploads, installed plugins, themes, languages, and the currentwp-config.php. - Save server configuration, scheduled cron definitions, redirect rules, PHP settings, and any separate media or backup directories.
- Keep an untouched copy outside the destination server. Do not overwrite it while testing imports.
- Open the archive and inspect the database dump so you know the files are readable before the migration begins.
Keep a timestamped pre-migration backup, a destination backup after import, and a final backup immediately before cutover. A backup that has never been opened or restored is only an assumption, so verify at least one database import and representative file extraction on the destination or a staging system.
Build the destination server
For a Multisite network
Install the required PHP and database stack, then install WordPress once. Enable the network feature from the WordPress administration interface, choose the subdomain network option, and apply the generated constants to wp-config.php and the generated rewrite rules to the web server. The server must support the rewrite behavior required by Multisite: Apache normally uses the generated .htaccess rules, while Nginx needs equivalent rules in its server blocks.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Create three sites in the network with their intended subdomain names. Confirm that the network administrator can reach the network dashboard and that each new site has a distinct site ID and upload location. Install only the themes and plugins that are compatible with network operation; decide explicitly whether each extension is network-activated or enabled for individual sites.
For three independent installations
Create three document roots, three databases, and three database users with permissions limited to their own database. Install WordPress separately in each document root and give each installation its own wp-config.php. Use distinct filesystem ownership or permissions where your hosting model supports it, and keep uploads and backup paths separate so an administrator or compromised plugin cannot accidentally overwrite another site’s files.
Apply the same PHP and database versions used by the source sites first unless you have tested an upgrade. Installing a newer runtime during the migration adds a second variable and can turn a URL or file-permission problem into an application-compatibility problem.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Prepare DNS and web-server hostname routing
Create DNS records for all three subdomains, pointing them to the destination server’s address. Explicit records such as site1.example.com, site2.example.com, and site3.example.com make the allowed hostnames clear. A wildcard record such as *.example.com can cover additional subdomains, but it also sends unintended hostnames to the server; use it only when that exposure is acceptable.
Lower the DNS TTL before the cutover when practical, allowing resolvers to refresh the old address sooner. TTL reduction does not force every resolver to switch immediately, so keep the old service available during propagation.
DNS alone is insufficient. Configure the web server to recognize each hostname and route it to the Multisite installation directory or the correct independent document root. In a separate-installation design, verify that a request for site1.example.com cannot be served from site 2’s root. In Multisite, verify that all three hostnames reach the one installation and that WordPress resolves the correct site from the Host header.
Move the content using the path that matches your starting point
Moving three separate sites to three separate installations
Copy each database into its corresponding destination database and copy that site’s files into its document root. Preserve wp-content/uploads, themes, plugins, and language files. Update the destination configuration with the new database name, user, password, host, and table prefix only where necessary. Do not merge the databases or reuse one site’s wp-config.php for another.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
After the import, verify that the destination site loads with a temporary hostname or hosts-file override. Keep the old domain out of public redirects until the new site has passed testing; otherwise search engines and browsers may cache a redirect before you have confirmed the content.
Converting three separate sites into one Multisite network
Build the empty network first, then create a destination blog for each source site. Export each source with WordPress eXtended RSS (WXR), import the WXR file into the matching destination blog, copy the required themes and plugins, and map the imported authors to users in the network.
WXR is a content export, not a complete server image. Check media imports, custom fields, widgets, menus, shortcodes, plugin tables, and theme settings after each import. PHP upload and execution limits can prevent a large WXR file or media batch from completing. Increase the relevant limits for the maintenance window or split the export, then restore the normal limits afterward. Author mapping and settings that are outside standard WordPress content may require manual cleanup.
Moving an existing Multisite network
For a database-level move of an existing Multisite, import the network database and copy the complete WordPress files before changing domains. Review the wp_blogs and wp_site tables, then inspect every wp_x_options table for the home, siteurl, and fileupload_url values. The x represents each site’s numeric blog ID, so do not assume that the main site’s options are the only ones that need editing.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsConfirm that the network’s table prefix, upload paths, domain values, and site paths agree with the new hostnames. A single stale value can produce redirect loops, a blank dashboard, missing media, or a login cookie that is scoped to the wrong domain.
Change domains without corrupting serialized data
Changing from an old domain or path to a subdomain requires more than editing the visible site address. WordPress and plugins store URLs in serialized PHP arrays, JSON, option values, post content, metadata, and rewrite settings. A naïve find-and-replace across a SQL dump can change string lengths without updating serialization metadata and corrupt those values.
Use a serialized-data-safe search-and-replace process that understands the old and new URLs. Run it against a staging copy first, review the number and type of replacements, and preserve the original database until the new site passes testing. Include protocol changes, such as http:// to https://, in the planned mapping rather than performing an unrelated second replacement.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
For Multisite, manually review the network and site URL fields described above after the safe replacement. Temporary WP_HOME and WP_SITEURL definitions in wp-config.php can force recovery when the dashboard is unreachable, but they override normal dashboard editing. Remove those temporary definitions after recovery so administrators can manage URLs normally.
Do not use a blanket replacement that turns every occurrence of the parent domain into one subdomain. Each source site needs its own old-to-new mapping, and references between sites should be changed only when the business relationship requires it. Preserve external links that should continue to point to an external domain.
Issue HTTPS certificates for every hostname
Obtain certificates covering the primary domain and all three subdomains, or use a suitable wildcard certificate. WordPress domain-mapping guidance calls for SSL on the primary domain and Server Name Indication (SNI) for additional domains. Confirm that the web server presents the correct certificate for each hostname, not merely a certificate that happens to cover the first site.
Test HTTPS before enforcing redirects. Check administrator login, logout, password reset, cookies, media URLs, REST and other API requests, embedded resources, forms, and scheduled callbacks. Fix mixed-content references in the database or theme before redirecting every HTTP request to HTTPS. Once each site works over HTTPS, add the HTTP-to-HTTPS redirect and verify that it does not create a loop with a proxy or load balancer.
Test all three sites before changing public DNS
Use a temporary hosts-file override or staging DNS so your workstation resolves the new hostnames while the public records still point to the old server. Test each site independently and record the result.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Load the front page, representative posts and pages, category and tag archives, and a 404 page.
- Open images, PDFs, downloads, galleries, and media inserted into older posts.
- Run site search and submit every important contact, registration, and transactional form.
- Log in, log out, reset a password, and verify that cookies remain on the intended subdomain.
- Check scheduled publishing, backups, queue workers, and any server cron jobs.
- Call REST and other API endpoints used by the editor, mobile apps, integrations, or forms.
- Inspect canonical URLs, redirects, XML sitemaps,
robots.txt, pagination, and social metadata. - Review PHP, web-server, database, and application logs while performing the tests.
- Confirm that a request for one hostname cannot expose another site’s files, uploads, database records, or administrator session.
- Test cache behavior after purging old caches. A cached page from the wrong site is both a correctness and a security issue.
Compare page counts, media counts, recent orders or form submissions, administrator lists, and key plugin settings with the source inventory. Do not treat a successful home-page load as proof that the migration is complete.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Perform the cutover in a controlled sequence
- Take a final backup of every source database and the changed files.
- Put the old sites into maintenance or read-only mode so no content changes during the final synchronization.
- Import the final database changes and copy any files uploaded since the earlier transfer.
- Run the final serialized-safe URL replacement and verify the network or individual site URL fields.
- Confirm certificates, web-server host routing, rewrite rules, and application health on all three destinations.
- Change the DNS records to the destination address. Keep the old server online while caches and resolver records expire.
- Open each public hostname from multiple networks, then monitor logs, uptime, redirects, search-console coverage, and form delivery.
Keep the old server and untouched backups until all three sites have completed a full business cycle that includes publishing, form delivery, scheduled jobs, backups, and administrative work. Only then decommission the old service.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Use a rollback plan instead of improvising
Define rollback triggers before cutover: unrecoverable login failures, cross-site content exposure, missing media, failed forms, persistent redirect loops, database errors, or a broken scheduled job that affects business operations. If a trigger occurs, place the destination in maintenance mode, point DNS back to the old server, and restore the source to the last known-good state. Preserve destination logs and the imported database so the failure can be diagnosed rather than overwritten.
Do not roll back by merely copying an old wp-config.php over the new one. DNS, certificates, database state, uploaded files, caches, and URL replacements must all be considered. A rollback is safest when the source remained read-only and the final pre-cutover backup is intact.
Troubleshoot the failures that appear most often
A subdomain shows the wrong site or a server default page
Check the DNS answer, the web-server Host matching, and the document root. In a Multisite network, verify the site’s domain and path records. In separate installations, verify that each server block points to the intended directory and that no catch-all block wins first.
Every page redirects repeatedly
Compare the stored home and siteurl values with the requested protocol and hostname. Check whether temporary WP_HOME or WP_SITEURL constants conflict with database values, and inspect proxy headers if TLS terminates before the web server. Clear application and reverse-proxy caches after correcting the values.
The dashboard is blank or a plugin crashes
Compare PHP versions and extensions with the source inventory, then disable the suspected plugin from the database or filesystem only through a documented recovery procedure. In Multisite, determine whether the extension is network-activated. Restore the original files and database if the problem cannot be isolated safely.
Images are missing or return 404 errors
Confirm that wp-content/uploads was copied with its year and month directories, that file permissions allow the web process to read it, and that serialized attachment URLs were updated safely. For Multisite, check the upload path and fileupload_url values for the affected blog.
Recommended Free Tools
Forms or scheduled tasks do not run
Check SMTP or mail-service configuration, domain authentication, cron definitions, plugin-specific queues, and PHP error logs. Submit a real test form and verify delivery rather than relying only on a successful browser response.
WXR import stops or users are duplicated
Raise PHP upload and execution limits for the import window or split the WXR file. Review the author-mapping choices, then remove duplicate users or assign content manually where the source and destination user IDs differ. Recheck media and plugin-specific settings because WXR does not carry every site configuration.
Operate the three sites after migration
Document the final architecture, DNS records, certificate coverage, document roots, database names, backup locations, cron jobs, administrator accounts, and rollback procedure. For Multisite, document which extensions are network-enabled and who can change network settings. For separate installations, document the update order and test process for each site.
Schedule independent restore tests even when the sites share a server. A Multisite backup must support recovery of the network and, where required, an individual blog. Separate installations should have separate backup retention and restore checks. Continue monitoring error logs, uptime, redirects, search coverage, certificate expiration, disk space, and form delivery after the migration rather than stopping at the DNS change.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Final decision checklist
- Use Multisite when centralized updates, shared governance, and one codebase are deliberate requirements.
- Use separate installations when database isolation, independent plugins, independent release schedules, or site-level restoration are more important.
- Back up both databases and files, including uploads, plugins, themes, and configuration.
- Create DNS records and configure web-server hostname routing; one without the other is incomplete.
- Use serialized-data-safe URL replacement and review Multisite URL tables manually.
- Cover the primary domain and all three subdomains with HTTPS certificates and verify SNI behavior.
- Test every site’s content, authentication, forms, jobs, APIs, redirects, sitemaps, and isolation before cutover.
- Keep the old server and verified backups until the migrated sites have completed a full operating cycle.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
