Writing a blog

Writing a blog

Choosing Blog as the post type gives you a longer body with headings. What follows are the practical points that decide whether the piece gets read.

Put the answer in the heading

Headings like "Introduction" and "Summary" tell a reader nothing when the article appears in a list. Write what the section establishes, as the heading.

The review before publishing

When visibility is Public, an AI reads the body before it goes live. It is not a spellcheck. It looks at three things:

• Whether contact details are written directly in the body
• Whether the piece contains images or text of unclear origin
• Whether any definite claims could mislead a reader

What comes back is a suggestion. Adjust the text, run the review again, and publish.

The original and the English version

For blogs, two versions are prepared from what you write: the original language and English. At publishing time you choose which one is the body.

The version you did not choose is saved alongside it. Switching the published language later does not mean rewriting anything.

How the language changes for readers

On this site, lang and content_lang in the URL do different jobs.

An article that has an English version shows it when opened with content_lang=en. You can set both, which allows something like keeping the interface in Japanese while reading the body in English. The help centre follows the same rule.

The language used when sharing to social

Blogs have a separate setting for the language used when sharing to social networks. You can keep the body in Japanese and push English to X, for example. For how the sharing itself works, see Sharing to several networks at once.

Tags

Separate tags with commas or spaces, whichever you prefer. More tags does not mean more readers, so five is a sensible ceiling. Choose words people actually search for — "contract translation" rather than "English translation".