Language Check

Language Check lists drafts whose body isn't in the language it should be in, and rewrites the ones you select.

Find it in Settings → ContentForge, under Language Check. (It used to be a page of its own under ContentForge; old links lead to the new spot.)

You'll mostly need it once: to clear a backlog. Drafts written before GEOforge started checking its own output carry no record of the language they came out in, so the only way to find them is to scan. New drafts are checked as they're generated, and a draft that comes out wrong is corrected before it reaches you.

What "should be" means

The expected language comes from Content Language on your brand profile — see Brand profile settings.

If that's set to a specific language, every draft should be in it. If it's on Auto, each draft should match the language of its own topic title.

Running the check

The check doesn't run every time you open Settings, because scanning a large archive takes a while. Click Check drafts to start it.

When the Writer flags a draft as being in the wrong language, an item appears in Today's Priorities on your dashboard, for example "2 drafts were written in the wrong language". Clicking it brings you here and starts the check for you. The priority is based on the Writer's own flag, so it won't count older drafts written before the Writer checked its output. Running the check finds those too.

Reading the list

The header tells you how many drafts need attention out of how many were scanned. Each row shows:

• The draft title, which links through to the article.
• Its current stage in the pipeline.
• Written in X, should be Y — the language found in the body against the language expected.
• The word count.

If you see a note that only the most recently updated drafts were checked, the scan hit its ceiling. Clear what's listed, then run the check again to see the next batch.

Re-checking

After the first scan, Re-check runs it again. Nothing is read from a stored flag, so the list always reflects the drafts as they stand right now — including any rewrites that have finished since you last looked.

Rewriting drafts

Tick the drafts you want corrected, or use Select all, then click Rewrite. The button counts what you've selected.

The rewrite translates the existing article rather than generating a new one, so the structure, argument and citations are preserved — it's the same piece, in the right language.

Rewrites run in the background. You can leave Settings, and the drafts update as each one finishes. Run Re-check afterwards to confirm the list has cleared.

A few things worth knowing:

• Large selections are submitted in batches of 100. If something goes wrong partway through, GEOforge tells you how many rewrites were already queued — those are running regardless.
• Some drafts may be reported as skipped. That usually means the draft is in a stage where it can't be edited.
• Rewriting is generation work, so it draws on your content allowance in the same way a draft does. Selecting a long backlog all at once is a real spend — worth a look at the count before you confirm.

Why a draft might not appear

Drafts whose language can't be identified confidently are left out rather than guessed at. A very short draft often doesn't carry enough evidence to call, so it won't be listed even if it looks wrong to you.

That's deliberate. A false positive costs a rewrite of an article that was already correct, so the check abstains rather than reporting a mismatch it isn't sure about. If you know a specific draft is in the wrong language and it isn't listed here, open it and use the language prompt on the article itself.

Keeping the list empty

The backlog is a one-off, but new mismatches can appear if your setup drifts. The usual cause is a knowledge base in one language and topic titles in another, with Content Language left on Auto — the Writer has two signals pointing different ways.

Setting Content Language explicitly removes the ambiguity, and is the fix worth making if this list keeps filling up.