Home / Help Center / Write and publish a blog post

Write and publish a blog post

Create, edit, publish and delete posts on your public blog — and what has to happen before Google sees a new one.

Your blog lives at /blog and is managed from Blog in the admin sidebar. This is an admin-only screen.

Create a post

Click New post and fill in the form. Only two fields are required:

• Title — also the headline on the post page.
• Content — the body, written in Markdown (see below).

The rest are optional but worth filling in:

• URL slug — leave it blank and it is generated from the title. The grey placeholder shows what you will get.
• Category — free text, such as Strategy. It appears as a badge and groups posts on the index.
• Excerpt — shown under the title on the blog index and used as the page description in search results. Aim for one clear sentence of about 150 characters. Skipping it means search engines pick their own snippet.
• Cover image URL — a full https:// address to an image you host.
• Tags — comma separated.

Use Preview above the content box to see the formatted post while you write, then Edit to go back.

The one thing to know about publishing

Ticking Published and saving puts the post on your blog straight away — anyone who visits /blog sees it.

Search engines are different. The pages Google reads are generated when the site is built, so a new post is not visible to search engines until the next frontend build runs. Publish first, then deploy when you want it indexed. Nothing is lost in the meantime; the post is live for visitors the whole time.

Drafts

Untick Published to keep a post as a draft. Drafts show a Draft badge in the list, are not visible to anyone on the site, and are left out of the sitemap.

The eye button in the list switches any post between published and draft — useful for pulling something down quickly without deleting it. Published posts also get an arrow button that opens the live page in a new tab, so you can check how it looks.

Formatting with Markdown

The content box accepts a small, deliberate subset. These go at the start of a line:

For formatting inside a sentence, put the marker on both sides of the words:

• Two asterisks either side makes text bold.
• One asterisk either side makes it italic.
• Backticks either side make inline code.
• A link is the words in square brackets, then the address in round brackets.

Tables work too, in the style used just above.

Two limits worth remembering:

• A link address must be complete, starting with http:// or https://. A shortcut to a page on your own site, such as a bare /pricing/ path, will not become a link — write the full https://watsbizz.com/pricing/ address instead.
• Start headings at the two-hash level. The post title is already the main heading on the page, so a single hash would compete with it.

Editing and deleting

Click the pencil on any post to edit it. Saving updates the live post immediately for visitors, and search engines pick up the change after the next build.

Changing the URL slug of a published post changes its address. The old address stops working and any existing links to it break, so avoid renaming a post that has been out for a while.

The bin icon deletes a post permanently after a confirmation. There is no undo and no trash — copy the content somewhere safe first if you might want it back.

Views

Each post shows a view count in the list. It counts visits to the post page and is a rough popularity guide, not analytics.

Writing posts that bring in traffic

• Answer a question someone would actually type into Google. Post titles that read like questions or how-tos tend to do best.
• Write one post per topic. Two posts covering the same ground compete with each other rather than helping.
• Do not duplicate the Help Center. Help articles explain the product to people who already use it; blog posts explain the subject to people who have not signed up yet.
• Length matters less than usefulness, but a post under roughly 300 words rarely ranks for anything.

Back to the WatsBizz Help Center.