4 ways to add a blog to any website, and the trade-offs of each

A subdomain, a folder behind a reverse proxy, a script or a WordPress plugin: how each way of adding a blog works and what it changes for search engines.

Plenty of websites were never built with a blog in mind, from one-page sites made in a site builder to web apps. There are four common ways to add one anyway. You can put the blog on a subdomain, serve it from a folder through a reverse proxy, embed it with a script, or, if the site runs on WordPress, add it with a plugin. They differ in how much setup they need, in what search engines receive, and in what you will have to maintain.

1. A blog on a subdomain

The blog lives at an address such as blog.example.com. You create it with one DNS record, usually a CNAME, that points the subdomain to whoever hosts the blog. Nothing changes in your main site's code or hosting, so this works whatever your site runs on, as long as you can edit your domain's DNS.

For search engines, the subdomain is a separate host. Google's crawl budget guide says its crawlers treat each hostname as a separate site with its own crawl budget. The subdomain needs its own robots.txt, because a robots.txt file applies only to the host it sits on, and usually its own sitemap. In Search Console, a Domain property covers the main site and every subdomain in one place.

What you give up is a single host. There is a second one to keep an eye on, and the blog is only as visible as the links that lead to it, so put it in your main navigation.

2. A blog in a folder, through a reverse proxy

The blog lives at example.com/blog, but it is served by another system. A rule in your CDN, web server or hosting platform forwards every request for /blog to the blog's host and returns the answer under your own domain. Cloudflare, Nginx, Vercel, Netlify and Next.js can all do this with one rule.

For search engines, the articles are ordinary pages on your main host. They share your robots.txt and your Search Console property, and Google's guide to multi-regional sites lists "low maintenance (same host)" as a plus of subdirectories.

The catch is access. Someone has to be able to edit the proxy configuration, and a mistake in that rule can break the blog or send the wrong status codes. Some site builders don't allow proxy rules at all, and then this option is off the table.

3. A script embed

You paste one line of code into a page of your site, and the script adds the articles there. It is the quickest option to set up, and it works on site builders that let you add code but not proxy rules or extra pages.

A script runs in the visitor's browser, so search engines see the articles only if they run JavaScript. Google does: its JavaScript guide says Google Search renders pages with an evergreen version of Chromium. Rendering is an extra step, though. Pages wait in a rendering queue, sometimes for a few seconds and sometimes longer, and the same guide still recommends server-side rendering or pre-rendering because not all bots can run JavaScript. Dynamic rendering, which serves bots a separate pre-rendered version, doesn't solve this for the long term: Google calls it a workaround and recommends server-side rendering, static rendering or hydration instead.

Two details decide whether a script-based blog can be indexed at all. Each article needs its own URL, because Google says not to use URL fragments, the part after a #, to load different content. And links between articles need to be ordinary HTML links with an href, since those are the links Google can generally crawl.

How much all this matters depends on how a given script works, so test it. The live test in the URL Inspection tool shows a screenshot and the rendered HTML as Google sees them.

4. A WordPress plugin

If your site already runs on WordPress, a plugin can add the blog inside it. The articles then appear in your WordPress site, on your own domain, with no DNS or proxy work. Check one article after installing: it should have its own URL, a clear title and heading, and a place in your sitemap, like any other post. The limits are plain: it works only on WordPress sites, and like any plugin it needs to be kept up to date.

The four options side by side

Subdomain Folder via proxy Script WordPress plugin
Where articles live blog.example.com example.com/blog pages of your existing site your WordPress site
What you change one DNS record one proxy rule one line of code install a plugin
Same host as your site no yes yes yes
Best fit any site where you can edit DNS sites behind a CDN or server you control site builders with no other option WordPress sites

Questions that decide it

Most sites can rule out two or three options in a minute:

  1. Is the site built on WordPress? The plugin is the natural fit.
  2. Does the site sit behind a CDN or a server where someone can add a forwarding rule? A folder keeps the blog on your main host.
  3. Can you edit your domain's DNS but nothing else? A subdomain works without touching the site.
  4. Can you only paste code into pages? That leaves the script, and the rendering checks above matter most.

One more question applies to all four: who will notice and fix it if something breaks? A proxy rule or a DNS record is set once and rarely touched again, so write down what was changed and where.

Whichever you choose

The basics are the same for all four. Every article needs its own URL that shows its full text. Link to the blog from your main navigation, and from articles to the pages of your site they mention. Keep a sitemap with every article in it. Add the site to Search Console and check a few articles with the URL Inspection tool once they are live. And if you switch setups later, remember that a change of URL means redirects, and Google's site move guide warns that rankings can fluctuate while it recrawls.

Ranketto supports all four: a subdomain with one DNS record, a folder with one rule in Cloudflare, Nginx, Vercel, Netlify or Next.js (we provide the snippet), a one-line script on any site, and a WordPress plugin. With any of them, the articles are served while your subscription or trial is active, and they disappear from the site when it ends.

Questions and answers

Which way of adding a blog is best for SEO?

Google's documentation doesn't rank these options. A subdomain and a folder both serve ordinary pages, and a folder keeps everything on one host. A script depends on JavaScript, which Google can render but not every crawler can.

Will Google index blog articles that are added with JavaScript?

Google runs JavaScript and can index what it renders, but rendering can be delayed, and other crawlers may not run JavaScript at all. The live test in Search Console's URL Inspection tool shows you what Google renders.

Can I switch to another option later?

Yes, but if the article URLs change, every old URL needs a redirect to its new address, and Google warns that rankings can fluctuate while it recrawls the site.

Sources

  1. Managing multi-regional and multilingual sites
  2. Optimize your crawl budget
  3. How Google interprets the robots.txt specification
  4. Add a website or platform property to Search Console
  5. Understand the JavaScript SEO basics
  6. Dynamic rendering as a workaround
  7. URL Inspection tool
  8. Link best practices for Google
  9. How to move a site

Read next

See it work before you pay

ranketto.com runs on Ranketto too, and its Search Console numbers are public.

Sign-ups aren't open yet. Until then, you can follow ranketto.com's own Search Console numbers.