---
title: "Hosted blog setup"
description: "No blog yet? Rank Prompt can host a WordPress blog on a subdomain of your site or in a folder of it, styled like your website, and publish your articles to it."
url: https://help.rankprompt.com/en/articles/58-hosted-blog-setup
collection: "Integrations"
updated: 2026-11-12
language: en
---

# Hosted blog setup

No blog yet? Rank Prompt can host a WordPress blog on a subdomain of your site or in a folder of it, styled like your website, and publish your articles to it.

If your site has no blog, Rank Prompt can run one for you on a subdomain such as `blog.yourbrand.com`. Articles on your own domain build its authority, and the blog is ready for publishing from the editor as soon as it is live. Rank Prompt installs WordPress, issues the SSL certificate and keeps it running.

The hosted blog needs Starter or higher. The brand owner creates and launches it; editors can change its settings.

## Setting it up

1.  Open **Integrations > Publish content** and, on the **Hosted blog** card, click **Create new blog**
    
2.  Enter the **Blog URL**: the subdomain and your root domain
    
3.  Add the three DNS records the form shows, in your DNS provider (Cloudflare, GoDaddy, Namecheap and so on):
    
    -   **Step 1: TXT record for verification**: proves you own the domain
        
    -   **Step 2: CNAME record**: points the subdomain to the blog
        
    -   **Step 3: CNAME for SSL certificate**: lets the certificate be issued and renewed, so the blog has HTTPS
        
    
    If your DNS provider supports automatic setup (Domain Connect), the form shows **Connect with** and the provider's name above the records: click it, approve the records in the tab that opens, and come back. If not, the form names your provider and links its guide for adding records
    
4.  Click **Check**. DNS changes usually take 5 to 30 minutes to show; if a record is not found yet, the form says which one
    
5.  Click **Create managed blog**, then **Launch blog** once the card says **Ready to launch**
    

The blog takes a few minutes to set up; you can leave the page. It is styled to match your website (logo and brand color captured from your site).

> **Tip:** In Cloudflare, set every record to **DNS only** (the grey cloud). A proxied record hides the CNAME, so the blog can be neither verified nor published to.

* * *

## In a folder of your site (yourbrand.com/blog/)

The blog can also live inside your own site, at an address such as `yourbrand.com/blog/`. Every post then builds your main domain instead of a separate host. Your site's host sends that folder to Rank Prompt with one rule, so this works on Cloudflare, Vercel (Next.js), Netlify, nginx, Apache and Caddy. Shopify, Wix, Squarespace and Webflow cannot send a folder to another server: use the subdomain there.

1.  On the **Hosted blog** card, click **Set up** and choose **Folder of your site**
    
2.  Check **Your site's host** (with `www` if your site uses it) and the **Folder** (`/blog/` unless you want another), then click **Get the rule**
    
3.  Pick where your site is hosted and copy the rule into it: a Worker route on Cloudflare, `middleware.ts` on Vercel, `netlify.toml` on Netlify, or the block for your server. The rule carries your blog's own key (`X-RP-Blog-Key`): keep it private
    
4.  Click **Check and create blog**. Rank Prompt opens the folder through your site, and once the blog answers there it is created; if not, the card says what the rule gets wrong
    
5.  Click **Launch blog** once the card says **Ready to launch**
    

On a live blog in a folder, **Check proxy** in the card's menu checks the rule and the blog's login page through your site, and **Proxy rule** shows the rule again. **New key** makes a new key: the old one stops working at once, so update the rule right after. Rank Prompt checks the folder every day and the card says when your site stopped sending it.

### Send the rule to your developer

If someone else runs your site, the brand owner can hand them the rule without giving them a login. In **Proxy rule**, pick where your site is hosted and click **Send to my developer**: you get a **Link for your developer** to copy and send. It opens a page with the rule for that host, its key, the steps and a check, with no login.

-   The link works for **7 days**, until the date shown under it. **Send to my developer** again renews the same link; send it again after changing the host, so the page shows the right rule.
    
-   **Revoke link** stops it at once.
    
-   **New key** stops every link you sent, since they show the old key. The window says so; send a new link if the rule still needs setting up.
    

Anyone with the link sees your blog's key, so send it only to the person who sets up the rule.

* * *

## Statuses

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Status</p></th><th colspan="1" rowspan="1"><p>Meaning</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Ready to launch</strong></p></td><td colspan="1" rowspan="1"><p>DNS verified; the owner can launch. Until then the blog's health chip reads <strong>Needs a step</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Setting up...</strong></p></td><td colspan="1" rowspan="1"><p>The blog is being created</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Active</strong></p></td><td colspan="1" rowspan="1"><p>The blog is live</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Error</strong></p></td><td colspan="1" rowspan="1"><p>Something failed: the card says what to check, and <strong>Try again</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Offline</strong></p></td><td colspan="1" rowspan="1"><p>The account has no plan and the blog was taken offline: see <a target="_blank" rel="noopener noreferrer nofollow" class="linktype-link link" data-linktype="link" href="#if-the-plan-ends">If the plan ends</a></p></td></tr></tbody></table>

**Check DNS** on the card shows each record's state at any time.

* * *

## Once it is live

-   **View blog** opens it, **WP Admin** opens its WordPress admin
    
-   **Blog settings** (the gear) opens **Hosted site settings**: logo, favicon, font, up to 6 navigation links, a CTA button, the author shown on posts (name, title, bio, avatar, website) and the footer text, with a live preview. Leave the author's name empty and posts show no author at all: no byline, no author card, and search engines read your brand as the author. The **llms.txt** tab sets the short guide AI tools read at `/llms.txt` on your blog; left empty, the blog writes it from its published posts, never from drafts or scheduled ones
    
-   **Blog analytics** shows its traffic
    
-   **AI crawler logs: on**: the blog reports which AI crawlers read it on **AI crawlers** (`/analytics/ai-crawlers`), with nothing to connect, on the same plan as the blog. History starts the day reporting started
    

Publish to it like any other destination: open an article, publish, and pick the hosted blog. See [Publishing your content](https://help.rankprompt.com/en/articles/53-publishing-your-content.md).

* * *

## Removing the blog

The brand owner can click **Remove blog** on the hosted blog's card, once setup has finished or failed. It deletes the blog and its posts, and the domain stops serving it; it cannot be undone. Your articles stay in Rank Prompt, and the DNS records at your provider can be deleted afterwards. To use the domain again, set the blog up from the start.

* * *

## Google Search Console

Once the blog is live, the card shows **Search Console**. Click **Verify in Search Console** and Rank Prompt verifies the blog with Google and adds it to the Search Console of the Google account connected to the brand: the first time, Google asks you to allow it. No DNS record to add: Rank Prompt places Google's tag on the blog itself. See [Search Console connection](https://help.rankprompt.com/en/articles/60-search-console-connection.md#verify-a-site-in-search-console). Starter or higher.

* * *

## If the plan ends

The hosted blog is part of the paid plans. If the brand owner's account goes without one (the plan is canceled, or a payment stays unpaid), the blog keeps running for 30 days:

1.  The day it starts, the owner gets an email and a notification with the date the blog goes offline, and the blog's card says it
    
2.  After 30 days the blog goes offline: visitors and search engines get a page saying the site is not available, and the card reads **Offline**. Its posts, settings and domain are kept
    
3.  Choosing a plan at any point stops it: during the 30 days the blog simply stays online, and once offline it comes back within minutes, with everything as it was
    

A free trial of a paid plan counts as a plan. While the blog is offline nothing can be published to it.

* * *

## When the brand is deleted

Deleting the brand takes its hosted blog offline (archived) right away. **Undo** within the 48 hours brings the blog back with its posts, unless it was already offline because the account has no plan: then it comes back with the plan. If you ask us to erase your account's data, the hosted blogs on your brands are deleted with it.

* * *

## Troubleshooting

-   **DNS not detected yet**: wait up to 30 minutes, check the record type (TXT or CNAME) and the host name, then **Check DNS** again
    
-   **The card says the blog points elsewhere**: Rank Prompt checks the Step 2 record of a live blog every day, and it no longer leads to the blog. Put it back at your DNS provider, then **Check DNS**
    
-   **Blog not reachable or no HTTPS**: the Step 3 record is missing or proxied
    
-   **Already have WordPress?** Connect it instead: see [WordPress integration](https://help.rankprompt.com/en/articles/57-wordpress-integration.md)
    

* * *

## Questions?

Email [support@rankprompt.com](mailto:support@rankprompt.com) and I'll help.
