With the blog function of the classic Kopage Website Builder, you can regularly publish new posts, news, and other current content on your website.<\/p>\n\n\n\n
A blog is suitable, for example, for company news, club announcements, events, expert articles, tips, or current information. Unlike regular static pages, a blog is designed to continuously publish new posts.<\/p>\n\n\n\n
In this guide, we will explain the basic structure of a blog, how to create posts, and what you should keep in mind regarding headings, texts, images, and ongoing maintenance.<\/p>\n\n\n\n
\nBriefly explained:<\/strong> Standard pages are suitable for permanently valid content such as \u201eAbout us,\u201c \u201eServices,\u201c or \u201eContact.\u201c A blog is suitable for content to which new posts are regularly added.<\/p>\n<\/blockquote>\n\n\n\n
What is the blog feature in Kopage?<\/h2>\n\n\n\n
The blog function is a dedicated section for continuously published content.<\/p>\n\n\n\n
Instead of creating a regular website page for every piece of news and then manually linking it in an overview, you can manage posts within the blog section.<\/p>\n\n\n\n
This creates a continuous collection of articles or news posts.<\/p>\n\n\n\n
For example, a blog can be structured like this:<\/p>\n\n\n\n
Blog \/ News\n\u251c\u2500\u2500 New location opened\n\u251c\u2500\u2500 Review of our event\n\u251c\u2500\u2500 Tips related to our field of expertise\n\u2514\u2500\u2500 New service introduced<\/code><\/pre>\n\n\n\nWhen is a blog useful?<\/h2>\n\n\n\n
A blog makes sense if you actually want to publish new content regularly.<\/p>\n\n\n\n
Typical areas of application include, for example:<\/p>\n\n\n\n
\n
- Company news,<\/li>\n\n\n\n
- Club reports,<\/li>\n\n\n\n
- Specialist articles and guidebooks,<\/li>\n\n\n\n
- Project reports,<\/li>\n\n\n\n
- Event reports,<\/li>\n\n\n\n
- Product or service news,<\/li>\n\n\n\n
- or other current information.<\/li>\n<\/ul>\n\n\n\n
If your website, on the other hand, rarely changes and all important information is permanently on regular pages, you do not necessarily need a blog.<\/p>\n\n\n\n
\nPractical Tip:<\/strong> A blog should not be set up just because websites often have a blog. It is especially useful if you also want to publish content for it in the future.<\/p>\n<\/blockquote>\n\n\n\n
What is the difference between a page and a blog post?<\/h2>\n\n\n\n
Regular pages and blog posts can both contain text and images, but they serve different purposes.<\/p>\n\n\n\n
A normal page usually covers a permanently relevant area of your website.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
About us\nServices\nContact\nLocation<\/code><\/pre>\n\n\n\nBlog posts, on the other hand, are individual publications within a continuous section.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
10 Tips for ...\nNews from ...\nLooking back at ...\nOur new project ...\nChanges as of January ...<\/code><\/pre>\n\n\n\nIf you want to edit the basic page structure of your website, you can find the appropriate instructions at Managing pages, navigation, and submenus in Kopage<\/a>.<\/p>\n\n\n\n
Add a blog to a Kujabi website<\/h2>\n\n\n\n
If your website doesn't have a blog yet, open the corresponding blog function or the designated module in the Kopage editor and add the blog to the desired location on your website.<\/p>\n\n\n\n
You can then manage your posts and publish new content within this area.<\/p>\n\n\n\n
Depending on the structure of your website, the blog can be accessed via its own menu item such as \u201eBlog\u201c, \u201eNews\u201c, \u201eCurrent\u201c, or \u201eWhat's New\u201c, for example.<\/p>\n\n\n\n
What should the blog be called?<\/h2>\n\n\n\n
The name should match your website and the content published there.<\/p>\n\n\n\n
A company that primarily publishes specialist articles can use \u201eBlog\u201c or \u201eGuide\u201c, for example.<\/p>\n\n\n\n
For an association or organization, on the other hand, \u201eAktuelles\u201c or \u201eNews\u201c may be more appropriate.<\/p>\n\n\n\n
What is crucial is that visitors understand what to expect in this area.<\/p>\n\n\n\n
Create a new blog post<\/h2>\n\n\n\n
Open the management of your posts within the blog function and create a new entry.<\/p>\n\n\n\n
A post first needs a meaningful title and the actual content.<\/p>\n\n\n\n
Depending on the post, images and other available elements can also be used.<\/p>\n\n\n\n
Before you publish the post, you should check it completely.<\/p>\n\n\n\n
How to write a good post title<\/h2>\n\n\n\n
The title should describe as clearly as possible what the post is about.<\/p>\n\n\n\n
A title like:<\/p>\n\n\n\n
News<\/code><\/p>\n\n\n\nis very general.<\/p>\n\n\n\n
For example, more meaningful would be:<\/p>\n\n\n\n
New opening hours effective September 1st<\/code><\/p>\n\n\n\nor:<\/p>\n\n\n\n
Looking back at our 2026 summer festival<\/code><\/p>\n\n\n\nThis allows the visitor to see from the title alone whether the post is relevant to them.<\/p>\n\n\n\n
\nPractical Tip:<\/strong> Avoid titles that are only understandable in the context of the publication time. \u201eImportant news\u201c tells a visitor who finds the article six months later almost nothing about the content.<\/p>\n<\/blockquote>\n\n\n\n
Structure a blog post logically<\/h2>\n\n\n\n
A blog post shouldn't consist of a single long wall of text either.<\/p>\n\n\n\n
For more extensive articles, paragraphs and subheadings help to structure the content clearly.<\/p>\n\n\n\n
A simple structure could look like this, for example:<\/p>\n\n\n\n
Title\n \u2193\nshort introduction\n \u2193\nfirst topic section\n \u2193\nsecond topic section\n \u2193\nimage or example\n \u2193\nfurther information\n \u2193\nconclusion<\/code><\/pre>\n\n\n\nThe exact structure naturally depends on the respective topic.<\/p>\n\n\n\n
State the most important information early<\/h2>\n\n\n\n
With news articles, you shouldn't unnecessarily delay important information.<\/p>\n\n\n\n
For example, if opening hours change, visitors should find out as quickly as possible what is changing and when the change takes effect.<\/p>\n\n\n\n
A long introduction before the actual information appears makes it harder to use the post.<\/p>\n\n\n\n
Use images in blog posts<\/h2>\n\n\n\n
Images can make a post more vivid and visually break up longer content.<\/p>\n\n\n\n
Use images only if they match the topic.<\/p>\n\n\n\n
For a project report, for example, photos of the project can be useful. For a short organizational notice, on the other hand, a decorative stock photo is not strictly necessary.<\/p>\n\n\n\n
You can find further instructions on the use and preparation of images under Creating images, photo galleries, and sliders in Kopage<\/a>.<\/p>\n\n\n\n
Pay attention to the file size of images<\/h2>\n\n\n\n
Even with blog posts, you should not use unnecessarily large image files.<\/p>\n\n\n\n
When new posts with several large original photos are published regularly, the amount of data transferred by a page can quickly increase.<\/p>\n\n\n\n
Therefore, prepare images appropriately for use on the web and pay attention to a reasonable balance between image quality and file size.<\/p>\n\n\n\n
Review blog posts before publication<\/h2>\n\n\n\n
Read a new post completely one more time before publishing.<\/p>\n\n\n\n
Check in particular:<\/p>\n\n\n\n
Is the title understandable?\nIs the text complete?\nAre names and dates correct?\nAre links correct?\nAre the right images included?\nAre there still placeholders?\nAre there any spelling mistakes?<\/code><\/pre>\n\n\n\nWhen dealing with time-critical information, you should pay special attention to dates.<\/p>\n\n\n\n
Publish posts<\/h2>\n\n\n\n
When the post is finished and checked, you can publish it using the provided function.<\/p>\n\n\n\n
Then check the actual visitor view of your website and not just the display within the editor.<\/p>\n\n\n\n
Open both the individual post and the blog or news overview and check whether the new content appears there as expected.<\/p>\n\n\n\n
\nImportant:<\/strong> \u201eSaved in the editor\u201c and \u201ecorrectly published for visitors\u201c are not necessarily the same control. Therefore, always open the website in a regular browser after publishing as well.<\/p>\n<\/blockquote>\n\n\n\n
Edit published post<\/h2>\n\n\n\n
Previously published posts can also be updated later.<\/p>\n\n\n\n
This is useful, for example, if you want to correct an error, add additional information, or replace an image.<\/p>\n\n\n\n
Check the public display of the post again after the change.<\/p>\n\n\n\n
When should an old post be updated?<\/h2>\n\n\n\n
Not every older post needs to be regularly revised.<\/p>\n\n\n\n
An update is especially useful if the post continues to be visited by users and contains information that is no longer correct.<\/p>\n\n\n\n
In the case of a guidebook, for example, recommendations or general conditions may change.<\/p>\n\n\n\n
On the other hand, a historical event report does not need to be rewritten as if the event just happened.<\/p>\n\n\n\n
Date and temporal context<\/h2>\n\n\n\n
With current news reports, a clear temporal context is particularly important.<\/p>\n\n\n\n
Phrases such as:<\/p>\n\n\n\n
New opening hours will apply starting next week.<\/code><\/p>\n\n\n\nmay become unclear later.<\/p>\n\n\n\n
More precise, for example, is:<\/p>\n\n\n\n
New opening hours will apply from September 1, 2026.<\/code><\/p>\n\n\n\nThis ensures the post remains understandable later on.<\/p>\n\n\n\n
\nPractical Tip:<\/strong> For important time-sensitive information, use specific dates instead of exclusively terms like \u201etoday,\u201c \u201etomorrow,\u201c or \u201enext week.\u201c.<\/p>\n<\/blockquote>\n\n\n\n
Do not automatically delete old blog posts<\/h2>\n\n\n\n
An older post is not automatically worthless.<\/p>\n\n\n\n
Specialist articles, project reports, or event reviews can remain interesting long after their publication.<\/p>\n\n\n\n
Do not delete a post just because of its age.<\/p>\n\n\n\n
Instead, check whether the content is still useful, historically relevant, or accessible via other pages or search engines.<\/p>\n\n\n\n
When should a post be removed?<\/h2>\n\n\n\n
A post can be removed if it no longer serves a useful purpose or has been completely replaced by other content.<\/p>\n\n\n\n
However, for posts that have already been published for some time, you should keep in mind that their previous URL may have been indexed by search engines or linked to by other websites.<\/p>\n\n\n\n
\nAttention:<\/strong> If you delete a published post, its previous address may no longer be accessible afterwards. Therefore, before deleting, check whether a suitable redirect or updated target content is required.<\/p>\n<\/blockquote>\n\n\n\n
Maintain the blog regularly<\/h2>\n\n\n\n
A blog doesn't have to receive a new post every week.<\/p>\n\n\n\n
What is more important is that published content is useful and up to date.<\/p>\n\n\n\n
A company that publishes only four truly relevant posts per year can create more value with them than with weekly updates that have no informational value.<\/p>\n\n\n\n
Therefore, do not set a publishing schedule that you can only meet with trivial content.<\/p>\n\n\n\n
What is a neglected blog?<\/h2>\n\n\n\n
A blog becomes problematic above all when visitors get the impression that the entire website is no longer being maintained.<\/p>\n\n\n\n
A section titled \u201eNews,\u201c whose newest post is many years old, can create this impression.<\/p>\n\n\n\n
That does not mean that old posts have to be deleted. However, consider whether the name and integration of the blog section still match your actual publishing activity.<\/p>\n\n\n\n
Use blog for company news<\/h2>\n\n\n\n
A corporate blog does not have to consist exclusively of long expert articles.<\/p>\n\n\n\n
Even short, actually relevant messages can be useful.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
New employees\nNew service\nNew opening hours\nMove to a new location\nEvent\nCompany holidays\nImportant changes for customers<\/code><\/pre>\n\n\n\nWhat is crucial is that the message has informational value for the target audience.<\/p>\n\n\n\n
Use blog for expert articles and guides<\/h2>\n\n\n\n
A blog is also well suited for more detailed content in which you answer your target audience's questions or share your expertise.<\/p>\n\n\n\n
Such posts can be significantly longer than a short company announcement.<\/p>\n\n\n\n
Focusing in each case on a clearly defined topic and answering it as completely as possible.<\/p>\n\n\n\n
Avoid multiple very similar posts that essentially answer the same question.<\/p>\n\n\n\n
Use internal links in blog posts<\/h2>\n\n\n\n
If a post mentions a topic for which a detailed page of your website already exists, you can meaningfully link to it.<\/p>\n\n\n\n
For example, an article about a completed project could link to the corresponding service page.<\/p>\n\n\n\n
Internal links help visitors find further information and at the same time clarify the contextual relationships of your website.<\/p>\n\n\n\n
Only include links where they are actually helpful to the reader.<\/p>\n\n\n\n
Blog and Navigation<\/h2>\n\n\n\n
If the blog is an important part of your website, it should be easily accessible to visitors.<\/p>\n\n\n\n
Depending on the website, a main menu item like \u201eBlog\u201c, \u201eNews\u201c or \u201eUpdates\u201c may make sense for this.<\/p>\n\n\n\n
For an area that is only used occasionally, a different integration may be sufficient.<\/p>\n\n\n\n
We explain how to structure your navigation in general under Managing pages, navigation, and submenus in Kopage<\/a>.<\/p>\n\n\n\n
Blog posts and search engines<\/h2>\n\n\n\n
Publicly accessible blog posts can also be found by search engines.<\/p>\n\n\n\n
Therefore, you shouldn't write a post just for a brief moment after publication if the topic remains relevant for longer.<\/p>\n\n\n\n
A meaningful title, a clear content structure, and helpful information create a better foundation than texts artificially stuffed with search terms.<\/p>\n\n\n\n
We cover the general SEO options of the website builder under SEO with Kopage: Page titles, metadata, URLs, and search engine optimization<\/a>.<\/p>\n\n\n\n
Do not create a blog post for every search query<\/h2>\n\n\n\n
More posts do not automatically mean better visibility.<\/p>\n\n\n\n
When multiple articles answer nearly the same question, their content can overlap and offer visitors hardly any additional value.<\/p>\n\n\n\n
Therefore, it is better to create a substantive post on a single clear topic rather than several short posts with almost identical content.<\/p>\n\n\n\n
\nPractical Tip:<\/strong> Ask yourself before a new post: Is there already an article on my website about this? If so, updating or expanding the existing post might make more sense.<\/p>\n<\/blockquote>\n\n\n\n
Check blog on smartphone<\/h2>\n\n\n\n
Check both the blog overview and individual posts on a smartphone.<\/p>\n\n\n\n
Pay special attention to headings, images, long paragraphs, and embedded content.<\/p>\n\n\n\n
An extensive technical article should remain easily readable even on a small screen.<\/p>\n\n\n\n
You can find further information at Responsive Design: Optimizing Kopage website for smartphones and tablets<\/a>.<\/p>\n\n\n\n
Comments and discussions<\/h2>\n\n\n\n
Wenn du interaktive Funktionen oder Diskussionen auf deiner Website einsetzen m\u00f6chtest, solltest du diese bewusst planen und regelm\u00e4\u00dfig betreuen.<\/p>\n\n\n\n
\u00d6ffentliche Eingabem\u00f6glichkeiten k\u00f6nnen Moderation und gegebenenfalls Ma\u00dfnahmen gegen unerw\u00fcnschte Beitr\u00e4ge erforderlich machen.<\/p>\n\n\n\n
Zus\u00e4tzliche Funktionen des klassischen Kopage Website Builders behandeln wir gesammelt unter Using apps and modules in the Kopage website builder<\/a>.<\/p>\n\n\n\n
Blogbeitr\u00e4ge mit Social Media kombinieren<\/h2>\n\n\n\n
Wenn du auf sozialen Netzwerken aktiv bist, kannst du dort auf einen neuen Blogbeitrag aufmerksam machen und Besucher f\u00fcr den vollst\u00e4ndigen Inhalt auf deine Website f\u00fchren.<\/p>\n\n\n\n
Der eigentliche Beitrag bleibt dadurch als Inhalt auf deiner Website verf\u00fcgbar, w\u00e4hrend Social Media als zus\u00e4tzlicher Verbreitungskanal dient.<\/p>\n\n\n\n