The content calendar

Most content plans start with a blank spreadsheet and a guess. The content calendar starts with evidence you already have: the searches Google says your site appears for, and the pages you have already published. It turns that into a rolling plan of about thirty days, writes each article on the day it is due, and hands it to you to read before it goes anywhere near your blog.

What it actually does

The page describes itself in one line at the top: "A publishing plan built from the searches your site already appears for. Each article is written on its scheduled day, then you review it and send it to your CMS."

That sentence hides five separate jobs, and it is worth seeing them laid out, because you can inspect and change every one of them.

First, Rankbank finds keywords. It reads your Google Search Console queries (the actual searches that showed your site, with how many times they appeared and where they ranked), mines your own pages from the last reading of your site, and asks a model to suggest adjacent topics around clusters that are already proven. Those three sources are not treated as equal, and Where the keywords come from explains the pecking order.

Second, it scores them. Every keyword gets a number out of 100 and a list of reasons in plain English, like "Already ranking at position 8.4, close enough to move onto page one". The scoring is deterministic arithmetic on measured figures, not a model's opinion.

Third, it plans. The highest-scoring keywords get assigned to publishing days, spread across the week according to how often you say you publish. That produces the month grid.

Fourth, it writes. On the day an article is due you press Write it now, or the nightly top-up writes it for you. The draft is built from a brief containing the target query, the related Search Console queries it should answer, real internal link targets taken from your site, your style settings, and anything you told it.

Fifth, you review and publish. The draft opens in an editor next to an evidence panel showing exactly what data produced it. You edit whatever you like, then send it to a connected blog as a draft or as a live post.

Honesty about the AI part

Drafts are generated by a language model. That is worth being direct about, because the word "AI" covers a lot of very different things.

What the model is given: your real Search Console queries with their impressions and positions, real URLs from your own site to link to, your instructions, and your voice settings. What it is explicitly forbidden from doing: inventing statistics, study results, dates, prices or quotes, and using any phrase you put in the banned-phrases list. Where sourced facts are available, the prompt says those are the only figures it may state, each with its source linked.

What it does not decide: which topics matter. That comes from measured search data and arithmetic, not from the model. The model does language work: clustering, phrasing, titles, prose.

And nothing publishes on its own. An article reaches your blog only when there is a connection you set up, on a draft you opened, after you pressed Publish. If you configure a connection to post as Published rather than as a draft, that is a choice you make on the connection form and can change per article.

What it needs before it can start

Two things, only one of them required.

Your site has to have been read at least once. The plan is built from the topics your pages already cover, so that it can avoid repeating them and can link to them. Without a reading there is nothing to plan against and the build stage stays locked. See How Rankbank reads your site.

Search Console is optional but changes the result completely. Without it the plan comes from your pages alone, and the calendar says so in a panel above the grid: "This plan has no search data behind it." With it, every scheduling decision is backed by impressions and positions. Connecting Google Search Console takes a couple of minutes.

Where to find it

Blogs & Articles → Content Calendar in the sidebar opens a page listing every site you manage, each with a badge showing how many days are planned and a button reading Open calendar or Plan this site. If you manage exactly one site, Rankbank skips the list and opens that site's calendar directly.

Inside one site's calendar there are six tabs:

• Calendar is the month grid, covered in Reading the calendar.
• All articles is a plain table of everything planned or written for the site, newest first, for when the grid gets too long to page through.
• Rewrites holds pages you have already published that the site audit has since found a problem with.
• Keywords is the pool with its scoring shown.
• Style & settings is the voice, cadence and structure form.
• Where it publishes is your CMS connections.

What it deliberately does not do

The calendar is a month grid and nothing else. There is no drag-and-drop rescheduling, no filters, no bulk actions, and no way to add a day by hand. Entries come from the planning pipeline, and you remove one by pressing the bin icon on its cell, which sends its keyword back to the pool for another day.

There is no version history on a draft. When you edit an article and save, that is the article.

Rankbank never touches your live site. Publishing sends the finished article to a blog you connected, using credentials you supplied. Nothing else on your site is read or written by this module.

Where to go next

• Setting up your calendar walks through the first build.
• A month of content on autopilot, done properly does the whole loop end to end with one site.
• Topics and content ideas is where the site audit hands topics over to this module.