# Blogs and AI content

Write, design and publish a client blog from one builder, served on the client's own subdomain, on their site, or embedded.

Blogs opens as a single builder for the active client. A top bar switches between four areas, a settings panel sits on the left, and a live preview of the blog fills the rest of the screen.

| Area | What you do there |
| --- | --- |
| Content | Posts, Categories and Authors, write and organise the articles. |
| Design | Pick the blog look: Magazine, Minimal or Corporate. |
| Results | Traffic and engagement for the blog. |
| Setup | Everything about how the blog is presented and where it is served. |

> **Choose the client first**: The builder always edits the blog of the client selected at the top of the app. Switch clients and the posts, design and blog address all change with it.

## Writing an article

1. **Start from a keyword**: Pick a keyword or cluster from Keywords.ai, or enter your own. The generator reads the client profile and AI Training knowledge base for facts and tone.
2. **Generate the draft**: You get a full article: title, structured body, meta description, slug and a featured image.
3. **Edit**: The rich editor handles headings, links, images, embeds, callouts and internal links.
4. **Check the SEO score**: Live scoring covers keyword coverage, readability, structure, internal linking and metadata completeness.
5. **Publish or schedule**: Publish immediately or queue it for a later date.

## What a good SEO score looks like

| Signal | What "good" means |
| --- | --- |
| Keyword coverage | Primary keyword and close variants appear in the title, an early heading, and naturally through the body without stuffing. |
| Readability | Short paragraphs, varied sentence length, and headings every few hundred words. |
| Structure | A clear H2/H3 hierarchy that matches how the topic breaks into subtopics, not a wall of H2s with no H3s underneath. |
| Internal linking | At least a couple of links to relevant service or pillar pages, not just to other blog posts. |
| Metadata | Title under about 60 characters, meta description under about 155, both distinct from every other published page. |

> **Always review before publishing**: AI drafts are strong starting points, not final copy. Check facts, prices, service areas and claims against the client's own material.

## Blog address

Under Setup, the Blog address card decides where visitors and search engines find the blog. There are three choices.

**Subdomain (recommended)**

Add one DNS record and the blog (the index and every article) is served on the client's own subdomain, fully rendered and indexable. Nothing on the client's website has to change, and the traffic still counts on their domain. This is the right default for most clients.

**Client's own site path**

Posts live under the client's website itself, at a folder such as /blog. This only works when the site actually answers at that path, usually via the SEO script or an existing CMS blog.

**Platform address**

Posts stay on the platform address. The quickest way to get a blog live and useful for previews or trials, but the traffic is not on the client domain.

## Setting up the subdomain

1. **Choose the subdomain**: The field is pre-filled with blog. in front of the client's website domain, for example blog.acmeroofing.com. Change it if the client prefers something else, then press Set up.
2. **Copy the DNS records**: The card lists the records to add (type, name and value), each with a copy button. Add them at whoever manages the client's domain.
3. **Watch the setup steps**: A short checklist shows progress as the hostname is registered and the certificate is issued.
4. **Check status**: Press Check status to re-test. The badge next to the subdomain reads Pending DNS until the records resolve, then Live.

> **DNS takes time, not effort**: Records usually resolve within minutes but can take a few hours. Nothing else is needed while you wait, press Check status again later and the blog goes live on its own.

## How the blog looks

- Design offers three ready-made looks (Magazine, Minimal and Corporate), each with a preview you can open before committing.
- Header & footer can be read straight from the client's existing website so the blog matches their brand: business name, logo, brand colour, phone, address and menu links. Anything you edit by hand is kept the next time the website is re-read.
- Categories and authors, with bios and avatars, are managed under Content.
- Sitemaps, robots rules and structured data are generated and kept current automatically.

## Setup sections

| Section | What it controls |
| --- | --- |
| General | Blog name and the basics shown across every page. |
| Homepage | The blog index: heading, intro and how posts are listed. |
| Breadcrumbs | Whether breadcrumbs show, and the label used for the blog. |
| Article Page | What appears on a single post, dates, author, sharing, table of contents. |
| Related Inventory | Show products from Inventory alongside articles. |
| Contact Card | Business name, address, phone and website shown on the blog, defaulting to the client record. |

## Sharing and embedding

- Embed code, a snippet to paste into an existing page when the blog should appear inside the client's own site.
- Blog page URL, the public address of the blog, ready to copy into a menu or a report.
- API endpoint, the address the blog reads its posts from, for a developer wiring the content in themselves.

## Publishing to WordPress instead

When the client's blog already lives on a WordPress install, connect WordPress in Client settings and articles publish straight there over the WordPress API, body, featured image, categories and metadata included, exactly as a writer would have published them. You can also copy the finished HTML when a developer owns deployment.

## Bulk production

Bulk generation drafts many articles from a keyword list or a topical map in one pass, and a recurring schedule can keep a publishing cadence running. Both route into the same review queue, nothing goes live unreviewed unless you explicitly enable auto-publishing.

A practical cadence for a small local client is 2-4 articles per month: one pillar-supporting piece from the topical map, one seasonal or news-driven piece, and one or two informational posts that answer a specific customer question. Larger, multi-location clients can sustain a daily batch feeding a review queue that staff clear each morning.

## Common problems

**The subdomain still says Pending DNS**

The records have not resolved yet. Re-check that the type, name and value were copied exactly at the domain provider, a trailing dot or an added domain suffix on the name is the usual mistake, then press Check status again. Some providers take a few hours to publish changes.

**The blog loads but the branding is wrong**

Open Header & footer and press the option to read the client's website again. If the site was recently redesigned, the old values were captured from the previous version. Fields you edited by hand are kept, so correct those manually.

**Articles are live but not appearing in search**

Confirm the blog address shows Live rather than Pending DNS, then give indexing time. Newly served subdomains are crawled within days, not hours. Submit the blog in Indexing under Offsite SEO to speed it up.

**The scheduled article did not publish**

Check the destination is still reachable: a Pending DNS subdomain or an expired WordPress application password both hold articles in the queue. The article stays queued and publishes once the connection is restored.

**The SEO score is stuck lower than expected**

Look at which sub-signal is weakest rather than the overall number. Thin internal linking is the most common gap, add two or three links to relevant service pages and rescore.

**The draft repeats facts that are wrong or outdated**

The generator is only as accurate as the AI Training knowledge base. Update or correct the source material there, then regenerate rather than hand-editing every future draft.

**Bulk-generated articles feel repetitive**

Vary the source keywords and briefs going into the batch, and mix pillar, informational and seasonal topics rather than generating ten variations of the same cluster at once.