Search for a command to run...
Crafting seamless user experiences with a passion for headless CMS, Vercel deployments, and Cloudflare optimization. I'm a Full Stack Developer with expertise in building modern web applications that are blazing fast, secure, and scalable. Let's connect and discuss how I can help you elevate your next project!
No comments yet. Be the first to comment.
Muse Spark 1.2 returned Meta to frontier-model competition on August 5, 2026. The more consequential move was launching Muse Code and training the model around its agent runtime. Artificial Analysis s
The part of a CC Switch guide that ages fastest is not the install command. It is the decision about which provider needs a local proxy. As of August 5, 2026, CC Switch 3.19.1 lets Codex connect direc
QM agent is Y Combinator's July 2026 multiplayer harness for work; by August 4, its GitHub repository had about 9,700 stars. It gives each employee and project a scoped workspace, memory, keychain vie
A Codex long-running agent workflow succeeds when responsibility, state, wake conditions, acceptance criteria, and stopping boundaries remain visible and reviewable. OpenAI developer experience lead J
The Codex–ChatGPT Pro dual-agent workflow separates implementation from acceptance; it does not prove that one AI system is the strongest coding agent. Codex can hold the repository, requirements, per
Learn how to add a subdomain for your WordPress backend, separating it from your main site URL for enhanced security.
To add a separate subdomain URL for accessing your WordPress backend while keeping the default site URL for the frontend, you need to configure your server and WordPress settings accordingly. This setup allows you to access the WordPress admin dashboard through a subdomain like admin.example.com, while your site remains accessible at example.com. Below are the detailed steps to achieve this:
a. Access Your Hosting Control Panel:
b. Navigate to Subdomain Management:
c. Create a New Subdomain:
Enter the name of the subdomain (e.g., admin).
Ensure it points to the same document root as your main site (usually public_html or the directory where WordPress is installed).
Click Create.
Note: If your hosting control panel allows you to specify the document root, set it to your WordPress installation directory.
a. Access DNS Zone Editor:
b. Add an 'A' Record:
Create a new A Record for admin.example.com pointing to your server's IP address.
If your hosting uses automatic DNS management, this step might be done automatically when you create the subdomain.
c. Propagate DNS Changes:
For Apache Users:
a. Edit Virtual Host Configuration:
Access your server via SSH or use your hosting control panel's file manager.
Navigate to your Apache configuration files (usually in /etc/httpd/conf.d/ or /etc/apache2/sites-available/).
b. Add a ServerAlias:
<VirtualHost *:80>
ServerName example.com
ServerAlias www.example.com admin.example.com
DocumentRoot /path/to/wordpress
...
</VirtualHost>
c. Restart Apache:
sudo service httpd restart or sudo service apache2 restart.For Nginx Users:
a. Edit Server Block Configuration:
/etc/nginx/sites-available/).b. Add the Subdomain to server_name:
server {
listen 80;
server_name example.com www.example.com admin.example.com;
root /path/to/wordpress;
...
}
c. Restart Nginx:
sudo service nginx restart.a. Backup wp-config.php:
b. Edit wp-config.php:
Locate your wp-config.php file in the root of your WordPress installation.
Add the following code above the line that says /* That's all, stop editing! Happy blogging. */:
if (strpos($_SERVER['HTTP_HOST'], 'admin.example.com') !== false) {
define('WP_SITEURL', 'https://admin.example.com');
define('WP_HOME', 'https://example.com');
} else {
define('WP_SITEURL', 'https://example.com');
define('WP_HOME', 'https://example.com');
}
Explanation:
When you access your site via admin.example.com, WordPress will use admin.example.com as the WP_SITEURL, which affects admin URLs.
The WP_HOME remains example.com, so the frontend URLs are consistent.
For Apache Users:
a. Ensure .htaccess Exists:
.htaccess file should be in your WordPress root directory.b. Default WordPress .htaccess Rules:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^admin\.example\.com$ [NC]
RewriteRule ^(wp-(admin|login\.php).*)$ $1 [L]
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
For Nginx Users:
a. Update Server Block:
try_files directive:location / {
try_files $uri $uri/ /index.php?$args;
}
a. Obtain SSL Certificates:
example.com and admin.example.com.b. Configure SSL in Web Server:
a. Access the Admin Subdomain:
Navigate to https://admin.example.com/wp-admin/.
Log in with your WordPress admin credentials.
b. Verify Frontend Access:
https://example.com and navigate through your site to ensure everything works.c. Check for Mixed Content Errors:
a. Plugins and Themes Compatibility:
Some plugins or themes might have hardcoded URLs or may not function correctly with this setup.
Test all critical functionalities of your site.
b. Search Engine Indexing:
Use robots.txt to prevent search engines from indexing the admin subdomain.
Add the following to your robots.txt file:
User-agent: *
Disallow: /wp-admin/
c. Update Sitemap and SEO Settings:
If you prefer not to manually configure these settings, you can use a plugin to handle domain mapping.
a. Install a Domain Mapping Plugin:
b. Configure the Plugin:
admin.example.com to your WordPress backend.White Screen or Redirect Loops: This may occur due to incorrect settings in wp-config.php or server configurations.
Clear Browser Cache: After making changes, clear your browser cache to ensure you're loading the latest configurations.
Check Error Logs: Review your server's error logs for any issues that can guide you in troubleshooting.
By following these steps, you can successfully add a subdomain for WordPress backend access, separating it from your default site URL. This setup enhances security by obscuring the admin login URL and can also help in organizing site management.