Onsite SEO

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 and a matching icon rail switch between five areas, the panel for the current area sits on the left, and a live preview of the blog fills the rest of the screen.

AreaWhat you do there
ContentThree sub-tabs: Posts, Topics and Authors. Write and organise the articles.
DesignLayout, columns, card style, colours and fonts for the blog.
ResultsTraffic, search performance and conversions for the blog.
SetupHow the blog presents itself: general, homepage, breadcrumbs, article page, contact card and related products.
DomainWhere the blog is served publicly, plus search indexing status.

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.

Publishing changes and the embed code

A toolbar sits above every area with two buttons that stay in place as you move between tabs. Publish saves the current settings and applies them to the live blog. Embed opens the snippet you can paste into an existing page, along with the public blog address. While edits are pending, an Unsaved marker appears next to the buttons, and the preview refreshes on its own a moment after each change.

Writing an article

  1. 1

    Start from a keyword

    Open Posts and start a new article from a keyword or cluster in Keywords.ai, or enter your own. The generator reads the client profile and AI Training knowledge base for facts and tone.

  2. 2

    Generate the draft

    You get a full article: title, structured body, meta description, slug and a featured image.

  3. 3

    Edit

    The rich editor handles headings, links, images, embeds, callouts and internal links.

  4. 4

    Check the SEO score

    Live scoring covers keyword coverage, readability, structure, internal linking and metadata completeness.

  5. 5

    Publish or schedule

    Publish immediately or queue it for a later date.

The Posts list carries a search box and three filters with counts: All, Public and Internal. Public covers published articles, Internal covers drafts that are not served yet. Each row shows a thumbnail, and a preview button loads that single article in the preview pane. The list collapses to a narrow strip when you want the preview to take the full width.

What a good SEO score looks like

SignalWhat "good" means
Keyword coveragePrimary keyword and close variants appear in the title, an early heading, and naturally through the body without stuffing.
ReadabilityShort paragraphs, varied sentence length, and headings every few hundred words.
StructureA clear H2/H3 hierarchy that matches how the topic breaks into subtopics, not a wall of H2s with no H3s underneath.
Internal linkingAt least a couple of links to relevant service or pillar pages, not just to other blog posts.
MetadataTitle 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.

Topics and authors

  • Topics is the category list. Add, rename and remove topics, and the address slug is derived from the name for you.
  • Authors holds a name, a short bio and an avatar image per writer, shown on articles when the article page is set to display the author.

Design

Design controls how the blog index and the article cards look. Every change shows in the live preview before you publish.

ControlOptions
LayoutGrid, List, Masonry or Featured.
ColumnsOne, two or three columns for grid layouts.
Card stylePreset card looks such as Classic and Minimal, each shown as a small preview.
Colours and fontsAccent colour, text and background colours, and the font used across the blog.
Elements shownWhich parts of a card appear: image, date, author, topic and excerpt.

A match-the-website option reads the client's existing site and fills in the closest colours and font so the blog matches their brand without manual picking. Anything you set by hand afterwards stays as you left it.

Setup sections

SectionWhat it controls
GeneralBlog name used internally, and whether an article opens as a full page or in a modal.
HomepageThe blog index: heading, intro and how posts are listed.
BreadcrumbsWhether breadcrumbs show, and the label used for the blog.
Article PageWhat appears on a single post: dates, author, sharing, table of contents.
Contact CardBusiness name, address, phone and website shown on the blog, defaulting to the client record.
Related ProductsShow items from Inventory alongside articles.

Setup also holds the page template and the header and footer used around the blog. Header and 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.

Domain

The Domain area opens full width and holds two cards: Blog address, which decides where visitors and search engines find the blog, and the indexing panel, which shows what has been submitted to search engines. There are three address choices.

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.

Setting up the subdomain

  1. 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. 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. 3

    Watch the setup steps

    A short checklist shows progress as the hostname is registered and the certificate is issued.

  4. 4

    Check status

    Press Check status to re-test. The badge next to the subdomain reads Pending DNS until the records resolve, then Live.

Search setup, which covers ownership verification, the sitemap and search engine notifications, runs by itself as soon as the blog address goes live. The Publish button on this card re-runs it on demand, for example after a large batch of posts or a DNS change.

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.

Sitemaps, robots rules and structured data are generated and kept current automatically for whichever address the blog is served from.

Results

Results opens full width with a date-range selector at the top. It reports the traffic trend over the selected range, views and visitors, top performing posts, where readers arrived from, search impressions and clicks, average time on page, and conversions such as form submissions, phone clicks and button clicks attributed to each published article.

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, and articles stay as Internal drafts until they are reviewed 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 in Domain. Some providers take a few hours to publish changes.

The blog loads but the branding is wrong

Open Setup and press the option to read the client's website again for the header and footer. 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.

Design changes are not showing on the live blog

Press Publish in the toolbar. An Unsaved marker next to the buttons means the edits exist in the builder and the preview only. The live blog updates once the settings are published.

Articles are live but not appearing in search

Confirm the blog address in Domain 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.

Was this page helpful?