Skip to content

Concepts

These are the words Bloggity uses, in the same sense the product uses them. They are grouped by mental model rather than alphabetically, because the groups are how the product fits together.

Concepts first, then tasks. If a tutorial uses a word you do not recognise, it is defined here, and tutorials link back to these entries rather than re-describing them. If a dashboard screen uses a term, it belongs on this page.

A. Ownership & accounts

User

The person who signs in.

Team

The billing and ownership boundary. A Team owns Products, and the credit balance lives here.

Product

The thing you want a blog for. A Product has exactly one Blog, one Voice, one Style System, and one CTA, and is identified by a name and a landing-page URL. A Team can own several Products.

Blog

The generated, hosted site for a Product. One Blog per Product.

Plan

Your subscription level. Free is the default (1 product). Starter is the paid plan (3 products). Agency is not available yet. The Plan sets how many credits you get each month and how many Products you can run.

Not to be confused with: A Plan grants credits; a Credit is what generation spends.

Credit

The unit of generation capacity. One credit equals one production post, or one research day. Credits are granted monthly and are shared across the Team. Unused credits roll over to the next month.

B. Turning ideas into content

Keyword

A target search term. One Keyword yields many Topics.

Topic

One article angle derived from a Keyword. Topics are what get scheduled.

Subquery

A long-tail phrase attached to a Topic. The writer weaves subqueries into the article.

Opportunity score

The system's estimate of the SEO upside for a Topic. It ranks the queue; it is not a traffic promise.

Importance

A stored day-offset on a Keyword (0 means tomorrow). Scheduling still honours it. The dashboard does not ask you to set it; keywords you add are stored at 0.

Keyword suggestions

System-proposed Keywords when the queue cannot cover the forecast window. You can confirm all, pick some, or defer to tomorrow.

Locked keyword

A Keyword your plan does not include. Its data and search analysis are kept and shown as a locked tile on the Search page; nothing is written for it until you upgrade.

Topic state

Available (queued and eligible for scheduling), Assigned (attached to a Post), or Backlog (parked, and restored to Available when you bring it back).

Not to be confused with: Post state, which describes an article, not a topic.

C. Scheduling & publishing

Post

One blog article. One Post per Topic per calendar day on the default daily cadence.

Post state

Waiting for keyword (no topic assigned yet), Ideated (a topic is assigned but content is not written), Written (content is ready and scheduled), or Posted (live on the blog, and editable or deletable).

Not to be confused with: Blog state, which describes the whole site rather than one article.

Day slot

One calendar day holds exactly one thing: a Post or a research task.

Calendar

The day-by-day plan. It is the single source of truth for what is scheduled.

TODO queue (Tasks)

The "do this next" list. It surfaces only the work needed to keep the forecast window covered.

Forecast window

How many days ahead the TODO queue plans: 3, 7, or 14. The default is 7.

Publish hour

The hour of day your posts go live.

Generation hour

A per-product hour stored on the Product (default 6). The writer does not wait for it: generation runs every hour and writes each post the day before it publishes, once the research scheduled ahead of it has finished.

Sample posts

Short product-specific articles generated at signup so you can see the blog before it is real. They are replaced by real posts once the Blog is Active.

Regeneration

Rewriting an article. The first regeneration of an article is free; later ones cost 1 credit.

D. Brand & presentation

Voice

The verbal identity — tone, register, and vocabulary — used to write your copy. It is editable.

Style System

The visual identity taken from your landing page: typefaces, colours, CTA treatment, and favicon or logo.

Brand CSS

The generated stylesheet that implements your Style System.

CSS contract

The shared set of style selectors that your Brand CSS and the blog components both use, so styles and layout agree.

Layout template

The spatial arrangement of the blog. One of nine named templates.

Call to action (CTA)

The reusable end-of-post component. Updating it updates every post without regenerating content. It comes in variants.

E. Blog lifecycle & domains

Blog state

Where the whole site is in its life: Generating, then Preview, Pending DNS, and Pending Cert when you connect a domain, then Active. A failed payment does not take the blog offline.

Blog slug

The short, unique name in the preview URL. It is generated from the product name when the blog is created, and it cannot be changed.

Custom domain

Your own hostname, such as blog.yourdomain.com, connected by a CNAME record. Optional. It is offered when custom-domain serving is switched on for your environment; until then the blog stays on its preview address.

Preview host

blogs.bloggity.io, where your blog is served before you connect a custom domain.

Caching & publishing

The blog is served from the edge with per-post caching. Publishing a post invalidates that post’s cache so changes appear immediately.

Release phases

There is no alpha/beta ladder. "Coming soon" means a feature is not available yet. A feature that is built but switched off for an environment (such as custom domains) stays off until that environment turns it on.

F. SEO & discovery

Discovery files

The files that make your blog machine-readable: robots.txt, sitemap.xml, llms.txt, llms-full.txt, RSS, and a search-engine verification key. They are generated from published posts only.

Indexation

Making your blog findable: the discovery files plus submission pings to search engines.

Agent readiness (GEO / AEO)

Being usable and citable by AI assistants, not only by search engines.

Canonical URL & structured data

rel=canonical tags and JSON-LD so search engines attribute URLs correctly.

G. Research

Research

The evidence layer. Instead of writing only from a landing-page skim, Bloggity can spend a day gathering sourced claims so posts can cite real sources.

Research task

A research unit that, once accepted and scheduled, occupies a day slot instead of a Post.

Research day

A calendar day occupied by research. It costs the same 1 credit as a Post.

Research corpus

The accumulated findings for a Product, built up day by day.

Finding

An atomic claim plus a quote and a resolvable source URL.

Source

The document behind a finding.

Relevance

Matching findings to the upcoming Topics they support, so the right evidence reaches the right article.

H. Dashboard surfaces

Overview

The cross-product "what is happening" screen: recent, today, and upcoming.

Content

The Keyword → Topic → Post library for one Product. You can mark a keyword to write about. Scheduling and writing happen on Tasks and the Calendar, not on this page.

Analytics

Traffic to your blog, cookieless: visitors, pageviews, top posts, and referrers.

Settings

Per-product Voice, Style, CTA, layout, publishing windows, logo, custom domain, and SEO preview.

Profile

Your account and team, plan, credits, and password.

Product switcher

The product list in the sidebar. Choosing a product opens that product’s page at /dashboard/p/{slug}/{page}.

I. Billing

Tiers

Free (the default, 1 product), Starter (paid, 3 products), and Agency (not available yet). An older Early access courtesy plan still exists for teams that joined then; new teams are not put on it.

Credit grant

Credits are granted monthly. Unused credits roll over: each grant is added to the balance, and the credits stay when a plan ends.

Checkout & subscription

Handled by our billing provider. A paid renewal grants credits. A failed payment leaves the blog online and stops new credit grants until the payment succeeds.

Credit-aware generation

When credits run out, automatic generation pauses and manual actions are refused with a clear message. Your live blog keeps serving.


Something here that does not match what the dashboard says? That is a bug in the docs — please tell us.