WordPress serves as the foundational infrastructure for Vedfolnir’s new website. Its backend management and configuration are considerably more complex than Google Blogger. However, its abundance of plugins[1] and themes[2] is vastly superior—even if I remain somewhat skeptical about whether such a gargantuan number of plugins is truly necessary.

If what you desire is a platform that is secure, stable, straightforward, easy to use, and yet supports advanced design and control, I personally still highly recommend Blogger’s BPS blogging system. Even though Vedfolnir has migrated, we still maintain Blogger as a reliable backup site.

Over the past few days, through repeatedly working with WordPress—and reinstalling WordPress again, and again, and again[3]—I have compiled my observations and practical experience into the following working log:

Important Notice: This article may involve modifying scripts, commands, and core system files. Please ensure you know what you are doing before proceeding; always backup relevant files and databases prior to modifications, and inspect your site immediately afterward to catch any errors.

Can We Live Without SEO Plugins?

During this arduous testing phase, I experimented with both WordPress SEO by Yoast and All in One SEO Pack, the two heavyweight champions of the WordPress SEO world. Both consistently rank among the top five most popular plugins in the directory, illustrating just how fiercely contested the space is and how high webmasters’ appetite for SEO remains.

However, an online benchmark report indicated that both plugins consume nearly 0.7 MB of server memory “at least in a Controlled Environment.” In resource-constrained shared hosting environments, this overhead adds up like an army of ants. Whether you genuinely need these two plugins installed requires your own discretion.

When it comes to SEO, in my view nothing matters more than user-friendliness for human readers. Moreover, most things these heavy SEO plugins accomplish can be done via straightforward code tweaks (Blogger provides great training ground for this), and there are numerous lightweight, dedicated plugins available for specific needs, such as Google XML Sitemaps.

For standard web analytics, it is best to embed your Google Analytics tracking code directly into the header template of your theme.

Ultimately, Sitemaps and Analytics are the core features most people rely on SEO software for anyway. Choosing a well-engineered theme with clean built-in semantic markup delivers plenty of SEO value on its own.

Migrating from Blogger to WordPress

During my content migration, I opted not to use the standard Blogger migration plugin because site-to-site transfer connections proved notoriously unstable. This was not the fault of Bluehost, as most hosts suffer from identical timeout issues.

Instead, my workflow was: first export a complete backup archive from Blogger (Settings > Other > Export blog), create a fresh temporary private site on WordPress.com, and import that XML file there (Tools > Import > Blogger > Have a Blogger export file?). From WordPress.com, I exported a new clean XML file in native WordPress format (Tools > Export).

Finally, I returned to my self-hosted WordPress site backend and imported that WordPress-formatted XML file using the WordPress Importer Plugin.

Tip: If the import process gets interrupted, try importing the same file again. Most failures stem from XML files exceeding the server’s single-upload size limit; consult your host or update your php.ini configuration to increase upload_max_filesize and post_max_size.

Security and Safety

Regarding system security and management, Blogger benefits from Google acting as a vigilant digital guardian. As long as your credentials are not leaked, compromising it is exceedingly difficult (aside from indirect vectors like DNS hijacking via GoDaddy[4]).

With self-hosted WordPress, however, you are entirely on your own. I tested two renowned security plugins: Better WP Security and Wordfence Security. I ultimately chose Better WP Security, simply because its positive review count was 2,000 against Wordfence’s 1,000.

Strictly speaking, Wordfence offers flashier features. I deployed Wordfence on another experimental test site; its core file integrity monitoring and comparison capabilities are stellar, and viewing real-time visitor telemetry is fascinating (though understandably resource-intensive).

Regardless of which plugin you choose, make sure to inspect file permissions for critical files across your server directories: Read / Write / Execute. Specifically, the three foundational configuration files—.htaccess, wp-config.php, and php.ini—are best locked down to 604, 600, and 600 respectively. For detailed guidance, consult the official Codex documentation on changing file permissions[5].

For related troubleshooting, see our guide: 8 Ways to Fix WordPress HTTP 500 Internal Server Error.

Performance and Speed

The two most popular caching plugins are WP Super Cache (WPSC) and W3 Total Cache (W3TC). I opted for W3TC. I never ended up testing WPSC, as benchmark comparisons and community adoption gave me little reason to switch.

If your host allows it, I highly recommend configuring W3TC to integrate with Cloudflare CDN mode. Even on the free tier, your website will feel lightning fast.

Database Backup and Restoration

Regarding backup and restore plugins, widely recommended solutions include BackUpWordPress, UpdraftPlus, BackWPup Free, and WP-DB-Backup. I installed all of them on test servers; their core functionality is largely overlapping, which is why I experimented across the board. In the end, however, I decided not to use any backup plugins on production.

This is not because backups are unimportant, but because I prefer manual, controlled methods that consume zero persistent server resources. The official WordPress Codex provides a comprehensive guide on system backups[6].

For website file backups, simply archive the entire WordPress directory into a zip via cPanel and download it to your local machine.

As for database backups, Better WP Security conveniently includes this functionality (Backup WordPress Database), complete with scheduled automated backups, saving us the hassle of logging into phpMyAdmin manually.

Mobile and Smart Device Themes

Jetpack’s official plugin suite offers mobile theme templates, though visually they leave much to be desired.

The popular WPTouch suffered compatibility issues with W3 Total Cache (primarily because aggressive minification broke its mobile CSS and JavaScript), forcing me to discard it.

My solution was to adopt a theme built with native Responsive Web Design (RWD) from day one. This completely eliminates the need for separate mobile theme switcher plugins (though asset minification still requires careful testing).

Moving the WP-Content/Uploads Folder

uploads is the default media upload directory in WordPress, written in all lowercase (my typographic compulsions make me want to capitalize it, but resist the urge!). By default, it resides inside wp-content in the WordPress root directory.

Tip: I emphasize letter casing because it matters critically. On Linux and Unix-like servers, path casing is strictly case-sensitive.

For most users, the default path is the simplest and safest setup, which is why recent WordPress versions removed the dashboard UI setting for changing this directory.

The exception is if you plan to build an external image hosting architecture. Dedicated image hosting refers to storing media assets (especially images and photos) on a separate path or server (such as Amazon S3).

The purpose of image hosting is streamlined asset management and reducing load on the primary web server. Or, in my case, making it easier to wipe and reinstall WordPress at will (since Windows 8.x became too stable and robbed me of the joy of OS reinstalls, I had to find a new outlet!).

To change the default uploads upload path, add the following directive to wp-config.php in your WordPress root directory:

define( 'UPLOADS', 'wp-content/' . 'Vedfolnir' );

Here, 'wp-content/' refers to the directory within the WordPress root, and 'Vedfolnir' is our new upload folder. Alternatively, to place the upload folder directly under the web root:

define( 'UPLOADS', 'Vedfolnir' );

However, mapping image URLs directly to an external subdomain or URI is non-trivial. Even if WordPress permits it, standard server permissions prevent scripts from arbitrarily writing files into sibling subdomains or parent directories above the WordPress root.

This reminds me of that classic movie line: if there must be a time limit on this love, I hope it’s ten thousand years… well, what I mean is, viable solutions do exist.

Some webmasters build dedicated media subdomains and upload post images via FTP first, then insert the absolute URLs into posts (even better, Windows Live Writer natively supports uploading post images directly to an external FTP server).

Another approach requires modifying the database (wp_options table > upload_url_path). For now, I have no intention of undertaking such heavy lifting; keeping a clean folder under the WordPress directory suffices. Whenever we migrate to a dedicated CDN or media domain later, a single SQL search-and-replace will handle it all[7].

Moving the Entire WP-Content Directory

Taking it a step further: whether for organization, easier backups, or adding a layer of obscurity against automated exploit scanners, moving the entire wp-content directory to a custom path is actually quite straightforward (Better WP Security only provides folder renaming).

Simply move the entire wp-content directory to your chosen hidden location via FTP or file manager, then add the WP_CONTENT_DIR definition to wp-config.php:

define( 'WP_CONTENT_DIR', $_SERVER['DOCUMENT_ROOT'] . '/content/wp-content' );

Alternatively, specify the corresponding absolute URL using WP_CONTENT_URL:

define( 'WP_CONTENT_URL', 'https://www.Vedfolnir.com/content/wp-content' );

Caution: I do not advise beginners to alter the wp-content location. WordPress relies on numerous third-party plugins whose authors may hardcode relative paths; unexpected path mismatches can easily break your site when you least expect it :-P.

Conclusion

Having used Blogger for years, relying on functionality whose internal workings I cannot inspect always leaves me slightly uneasy.

Blogger’s single-template structure simplifies site management—how neat it is to have everything organized in one place! But WordPress’s decoupled architecture was built to empower extensibility and developer freedom, which is why the learning curve can feel steep for beginners. For a deeper look into WordPress’s architectural blueprint, refer to the classic 1.5 architecture documentation on Codex[8].

This is by no means the final word, as I continue to explore and test WordPress. As more insights and practical experiences emerge, I will update this article. Be sure to follow our fan page “Vedfolnir” for our latest updates!

Further Reading

  1. Useful WordPress Plugins Directory Guide.
  2. Curated WordPress Themes Directory Guide.
  3. WordPress Blog & Website Setup: Step-by-Step 5-Minute Installation Guide.
  4. Tech Oddities: Was GoDaddy’s Outage Linked to Google?.
  5. Codex - WordPress Backups.
  6. Codex - Function Reference/wp upload dir.
  7. WordPress - Site Architecture 1.5.
  8. Codex - Changing File Permissions.
✦ Independent Journalism · Reader Support ✦

Support Independent Perspectives & In-Depth Insights

Every thoughtful analysis and candid critique comes from our dedication to truth and quality. We choose not to follow sensational algorithms or clickbait headlines.

Sustaining independent research requires reader support. Make a one-time or monthly contribution, securely processed by Google.

Payments secured by Google · Manage or cancel anytime in your Google Account