Add a WordPress Blog to an Existing Website: 4 Routes, Honestly

You can add a WordPress blog to an existing website four ways, and none of them means rebuilding the site you already have. Install WordPress in a /blog folder on the same server. Run it on blog.yoursite.com. Host it anywhere and proxy yoursite.com/blog to it. Or run it headless and build the blog pages yourself inside your current app.

All four work. All four hand you a PHP application, a database and a plugin list that you own from launch day onward.

This guide covers what each route actually takes: the hosting, the theme work, the URL configuration and the maintenance. Then it covers the route most people who search this are really after, which keeps the /blog URL and drops the WordPress stack entirely. If your question is broader than WordPress, start with how to add a blog to an existing website and come back here.

Ways to add a WordPress blog to an existing website, and the one that skips WordPress

The first question is not which route is nicest. It is which route your existing hosting permits. A site on Vercel, Webflow, Framer or Shopify cannot execute PHP, so the subdirectory install is off the table before the conversation starts.

Route 1: WordPress in a /blog folder on the same server

This is the classic setup and the one WP Engine and the WordPress docs describe. Your existing site and WordPress share a server, and WordPress owns everything under /blog.

You need hosting that runs PHP and a database. As of September 2026, WordPress recommends PHP 8.3 or greater and MariaDB 10.11+ or MySQL 8.0+, on Apache or Nginx. Older stacks run WordPress, but the project warns that legacy versions may expose your site to security vulnerabilities.

The manual install is five steps. Create a database and a database user with all privileges. Rename the unzipped wordpress directory to blog and upload it inside your web root. Put the database credentials and the authentication salts into wp-config.php. Load yoursite.com/blog/wp-admin/install.php. Pick a theme.

That last step is where the work actually lives. WordPress does not inherit your existing design. Your header, navigation, footer, type scale and colors all have to be rebuilt inside a theme or a block template, and rebuilt again every time the marketing site changes. Two codebases now have to agree on what your brand looks like.

Suits: teams already running their own server, with someone who is comfortable in a terminal and willing to own updates.

Route 2: WordPress on blog.yoursite.com

The fastest route. Point a DNS record at any WordPress host, install, and you are publishing the same afternoon. Nothing on your existing site has to change.

The cost is structural. blog.yoursite.com is a separate host, so every link the blog earns lands on a property that search engines evaluate on its own footing, not on the domain your product pages sit on. Consolidating later means a redirect map and a waiting period. Our full comparison is in subdomain vs subdirectory for blogs.

This is also the only shape WordPress.com offers. Its own documentation is explicit: "On WordPress.com, you cannot create a subdirectory, where a URL like yourgroovysite.com/blog would display a separate site or WordPress installation from the site on yourgroovysite.com" (WordPress.com support, checked September 2026). As of September 2026, WordPress.com lists Personal at $9 per month billed monthly or $4 per month billed yearly, Premium at $18 or $8, and Business at $40 or $25 (WordPress.com pricing).

Suits: teams who need a blog live this week and accept that the URL is a separate address.

Route 3: WordPress somewhere else, proxied into /blog

Here WordPress runs on its own hosting, and a layer in front of your existing site rewrites requests for /blog/* to it. Readers and crawlers see one domain. This is the only way to get a yoursite.com/blog WordPress blog when your main site is on a platform that cannot run PHP.

Two things have to be configured, not one. The proxy comes first: an Nginx proxy_pass block, a Cloudflare Worker, a Next.js rewrite, or your platform's equivalent. Then WordPress itself has to print the right URLs. WP_HOME is "the address you want people to type in their browser to reach your WordPress blog" and WP_SITEURL is "the address where your WordPress core files reside", per the wp-config documentation. Get those wrong and you get asset URLs on the wrong host, redirect loops, and canonical tags quietly pointing at the origin instead of the public path.

The demand for this is real enough that it has its own products. A Shopify app called Proxy WordPress Blog exists purely to put a WordPress blog into a store's subfolder, priced at $25 per month with a 7-day trial as of September 2026 (Shopify App Store).

Suits: teams who want the subdirectory URL, already run WordPress, and have someone who can own both the proxy config and the CMS.

Route 4: Headless WordPress with a frontend you build

Keep wp-admin as the writing tool, pull content through the REST API or WPGraphQL, and render blog pages inside your existing React, Next.js or Astro app. The blog then lives at whatever route your app defines, and it looks exactly like your site because it is your site.

Understand what this route does and does not remove. It removes the theme layer. It does not remove the WordPress install, the database, the hosting bill, the plugin updates or the security patching, because the API still has to run somewhere. It also hands you every SEO output that a theme used to generate. Article and FAQ schema, the XML sitemap, canonical tags, Open Graph tags, hreflang and llms.txt are now code you write and maintain.

So you are running two stacks, two deploy pipelines and two on-call surfaces to publish blog posts. Before committing, read what the same integration looks like without a CMS to babysit in the Next.js blog guide.

Suits: product teams with frontend engineers to spare and a specific reason the blog must render inside the app.

The bill that arrives after launch

Every route above shares the same running cost, and it is not the hosting line item.

Plugins are where the risk concentrates. Patchstack's State of WordPress Security in 2026 report counted 11,334 new vulnerabilities across the WordPress ecosystem in 2025, a 42% increase over the previous year, with 91% of them in plugins and 9% in themes. WordPress core itself accounted for six, all low priority (Patchstack). Core is not your problem. The twenty third-party plugins you install to get forms, SEO fields, caching and image optimization are.

Managed hosting buys back some of that time. As of September 2026, WP Engine's Essential plan is $336.00 for the first year billed annually, a $28 per month equivalent, limited to new customers, covering one site, 25,000 visits a month and 10 GB of storage, with additional sites at $20 per month (WP Engine). That is promotional pricing, so check current terms before you budget on it. Managed hosting still leaves you choosing plugins, approving updates and rebuilding a theme.

If the WP Engine renewal is what prompted the search, the WP Engine alternatives roundup prices the honest options.

The way out: keep the /blog URL, drop the WordPress stack

The reason people search for a WordPress blog on an existing site is almost never WordPress. It is the /blog path on the domain they already own. You can have that without any of the four routes above.

Superblog is a hosted blog that connects to the site you already run. You add one routing rule, and yoursite.com/blog serves from Superblog while your marketing site stays exactly where it is, on Next.js, Webflow, Framer, Shopify, Vercel, Nginx or plain HTML. A subdomain and a custom domain are available on every plan too, with free SSL.

Here is what replaces the maintenance work:

• Nothing to manage. No server, no PHP version to pin, no plugin queue, no patch window. Managing the blog means writing in it.

• Nothing to attack. Every post ships as a static file from an edge network of more than 200 locations. Nothing dynamic runs behind it, no database and no plugin runtime, so the surface that produced 91% of last year's WordPress vulnerabilities does not exist here.

• A writing tool your team can share. Clean editor with autosave on every plan, and more than one author on a post when you need it. Scheduled publishing and collaborative review on Pro and above, with roles for Admin, Editor and Writer. Pro includes 5 team members, Super 10, Business 25.

• SEO generated on publish. JSON-LD for Article, WebPage, Organization, ImageObject and FAQ. XML sitemaps, canonical URLs, Open Graph tags, and an IndexNow ping the moment a post goes live. Multilingual SEO with hreflang and per-language sitemaps is on Super and above.

• Readable by AI engines. Every post is server-rendered HTML at a real URL, mirrored as plain markdown at the same URL plus .md, and indexed in an llms.txt file that regenerates on each deploy. That is the stack assistants use when they cite your work.

• Research and images in the dashboard. Search volume, competition and CPC for up to 25 keywords per search from live DataForSEO data, plus AI featured and Open Graph images generated from the post at 1 credit each. Both are on the Business plan, the tier above Super.

• Analytics without a consent banner. Pirsch, cookie-free and GDPR-compliant, on Pro and above. Google Analytics works on every plan.

• Speed as a default. 90+ Lighthouse on every page, automatic WebP conversion, no caching plugin to configure.

Bringing an existing WordPress blog across is a URL, not an export file. Superblog pulls from the WordPress REST API and keeps the slug on each post, so a post that lived at /pricing-strategy-2026/ still lives at /pricing-strategy-2026/. Tags, publish dates, Yoast meta titles and descriptions, and Yoast's JSON-LD come with it. Be realistic about the gaps: authors are attributed to whoever ran the import, only the first category per post carries over, Rank Math metadata is not read, and images are re-hosted on the CDN once a paid plan is active rather than during a trial. Most imports finish in 5 to 10 minutes. The step-by-step version is in the WordPress migration guide.

Scale is the question people ask next. A finance publication with more than 15,000 posts moved off WordPress onto Superblog, 23 blogs on the platform hold 1,000 or more posts, and more than 150,000 posts are served from it in total. PrintStop moved its business blog across from WordPress, and Elephas chose Superblog instead of standing up WordPress in the first place.

Pricing runs $49 a month for Pro, which covers up to 1,000 posts and 5 team members, and $99 for Super for larger archives and multilingual SEO. You get seven days to try it without entering a card, and there is a 30-day money-back guarantee. The pricing page has the plan-by-plan detail, and the side-by-side against staying on WordPress is on the WordPress blog alternative page.

Picking a route by the stack you already run

Common questions about adding a WordPress blog

Can I install WordPress in a subfolder of a site that is not WordPress?

Yes, if the same server executes PHP and can reach a MySQL or MariaDB database. If your site is hosted on Vercel, Netlify, Webflow, Framer or Shopify, it cannot, and you need a reverse proxy instead.

Is a WordPress blog better on a subdomain or a subdirectory?

Subdirectory, for a business blog. yoursite.com/blog keeps the blog inside the site whose authority you have already built, while blog.yoursite.com starts as a separate property. Use a subdomain when the subdirectory is genuinely impossible.

Do I need WordPress at all to add a blog to my website?

No. A hosted blog platform gives you the same /blog URL with no PHP, no database and no plugin updates. Avoid JavaScript widgets that inject posts into a page after load, for the reasons set out in embedding a blog on your website.

What does a WordPress blog cost to run next to an existing site?

Hosting is the small part. As of September 2026 WP Engine's Essential plan starts at $28.00 a month billed annually for one site and 25,000 visits, and that is first-year pricing. Add theme work, plugin licenses and the hours someone spends on updates.

Can I move an existing WordPress blog to /blog without losing rankings?

Yes. Superblog imports directly from your WordPress REST API and keeps each post's original slug and publish date, so existing URLs survive the move. Anything that does change, you 301 from the old path in the dashboard's redirects settings.

Your next move

If you have a server, a spare afternoon and someone who wants to own WordPress, route 1 is a fine choice and this guide gives you the shape of it.

If what you actually wanted was posts at yoursite.com/blog and nothing else on your plate, start a blog on the trial, publish one post, and add the routing rule for your platform. The /blog URL is the same either way. Only the maintenance is different.