Everything Joornal does for you

What your market really searches for

Your Search Console is connected to the platform. Topics come out of the queries that already bring you visitors, the ones where you are within striking distance (bottom of page one, where nobody clicks on you yet), and the ones you miss entirely.

Your data, kept beyond Google

You connect your own Google account, or Joornal manages the property for you. Either way, performance is synchronized daily and kept: you hold the history while Google wipes it after sixteen months.

Topics proposed, and you decide

Joornal proposes in batches. You accept, you refuse, you reword. An accepted suggestion becomes a piece to produce without you writing a brief.

Every batch shows its state plainly: running, paused, finished with nothing found, failed. Nothing disappears quietly.

Grouped into clusters, around a reference page

Content groups by topic: a reference page and its satellites, what the trade calls a cluster. The platform proposes those groupings from real queries, names the page that should carry the reference, and flags orphan topics that attach to nothing.

That structure is what builds authority, and it is what a blog fed one post at a time never gets.

A calendar that runs without you

You set a cadence, Joornal spreads the publications over time and knows the public holidays in your country. You do not decide every week what goes out.

Need to shift everything? Rescheduling happens in bulk, with a preview of the new calendar before you confirm.

Knowing whether the drop is you or Google

When your curves fall, the first question is whether it is you or the search engine. Joornal tracks the incidents Google declares on its status dashboard and lines them up against your drops. That spares a few crisis meetings.

The platform learns from your corrections

Joornal records every version of an article and separates what the machine wrote from what your reviewer changed before publication. Those differences are put to use: they update the writing instructions and your knowledge base.

A turn of phrase you strike out every time stops appearing. A figure you correct twice becomes the reference. You configure nothing and write no instructions: you correct as you normally would, and the next articles take account of it.

80% machine, 20% human. Then 90/10.

The first hundred articles need real corrections: that is the period when the knowledge base gets tuned. Past that point, the working split settles around 90% automated and 10% checking and light retouching.

Put plainly, your review load is heaviest at the start and drops afterwards.

A list that shows only your decisions

A piece moves through successive states, from drafting to going live. You do not open a dashboard to hunt for what to do: the home screen shows what is waiting on a decision from you, and nothing else.

Pieces to review, suggestions to settle, comments to moderate, publications running late. If there is nothing, it says there is nothing.

Author, reviewer, expert: three distinct roles

The author, the reviewer and the expert who signs off are three separate people, each with their own record: name, photograph, role, biography, qualifications. The expert who puts their reputation on the line is not necessarily the one who wrote.

In sectors where a practitioner's endorsement is the norm, that distinction is not cosmetic.

A signature that protects you

Human review under named editorial responsibility is what turns generated text into published work you can stand behind: for your readers, for search engines, and for regulators. The EU AI Act is one example, its article 50 exempting content that has undergone human review or editorial control, where a person holds editorial responsibility for the publication, from carrying an "AI-generated" label. Whatever the regime where you publish, Joornal keeps the review and signature trail.

The same step does three jobs: quality, authority in Google's eyes, and a record you can produce.

A history you can produce

Every version carries its date, its reason and its origin. When a claim is challenged six months later, you know who wrote what, who approved it, and from which source. And you can go back to any earlier state.

Internal linking handles itself

Links between your pieces are computed on closeness of meaning rather than on menus, and are placed in the body of the articles. Pages covering the same subject reinforce each other instead of stealing each other's place.

Twin pieces get spotted

Two pages saying the same thing are grouped into a family, with the shared passages highlighted. You consolidate, or you dismiss the flag with a reason. At two hundred articles, nobody catches this by eye.

And the ones cannibalizing each other

When two of your pages compete for the same search, the platform sees it and figures out which one to fold in. And when folding would destroy more clicks than it would win, it says so and explains why it holds back.

An analysis that declines to act tells you so explicitly.

What slips gets picked up, on its own

Eight levers run continuously across your portfolio:

• Refresh content that is losing ground
• Rewrite title and meta description
• Push pages within striking distance
• Strengthen internal linking
• Consolidate twin pieces
• Handle two pages in competition
• Attach an orphan topic
• Differentiate two pieces that overlap

You set how far it goes without you

Each lever is configurable: propose and wait for your approval, or act alone. Guard rails frame the whole thing: a minimum delay before touching the same page again, a ceiling on actions per pass, a refusal to act on a piece already being processed.

And every action is measured afterwards, before and after, to say whether it paid off. Whatever produced nothing is identified as such, and is undone.

A sitemap search engines actually find

Sitemaps generated on every publication and submitted to Google through the channel meant for it. A dedicated check verifies that discovery genuinely works: that the file is declared where search engines read it, that it responds, and that it holds what you publish.

Plenty of sites have a perfect sitemap nobody finds. That is the kind of detail a monthly report never shows.

What Google does with it, in plain terms

For each page: has Google seen it, kept it, set it aside, and why. The distinction matters, because a page set aside by a technical tag is not a page judged poor, and it is not fixed the same way.

The verdicts are dated: an opinion several weeks old describes a state Google may have revisited since, and that is stated.

And what the AIs do with it

Ranking well on Google and being quoted by an AI do not go through the same robots. Joornal records your site's access logs and works them natively, hour by hour: no log analyzer to buy, no export to request from a host, no data to hand to a third party.

63 robots tracked, 16 of them AI, with a check on their real identity (a fake Googlebot is caught). You see which ones come to read your pages, which pages they read, and which ones have stopped coming.

And above all, what it brings in

Inquiries arriving through the media property are recorded with the page that produced them. So you are not only measuring visits and positions: you see which pieces bring you contacts and conversions, and which ones bring only traffic.

It is the one number that settles the argument in a board meeting.

Proof before signature

Before you commit to anything, we start from your site and your competitors: what Google does with your pages, what the AIs quote instead of you, where your editorial gaps are, which topics are worth the effort. We hand you that analysis, with the data.

It is a real audit, not a sales deck. You judge our level before paying anything.

Fully managed

You touch nothing. We run the media property: knowledge base, clusters, calendar, production, publication, upkeep, measurement. You receive what there is to review and sign, and the account of what it returns.

It is the default mode, and the one chosen by teams with nobody to put on it.

Working alongside you

Your team keeps whatever it wants to keep: the angle, the final approval, certain subjects it insists on writing itself. The rest runs without them.

Access is set per person and per site, so everyone sees their own scope and you do not open everything to everyone.

The platform in your hands

Agencies, multi-brand groups, marketing teams with their own tooling: you take the controls, your knowledge bases, your portfolio, with our support and our training. The API is there to wire in the rest of your systems.

You keep the client relationship and the editorial call. Joornal carries the volume.