Publish Kopage website and fix typical issues

After you have created and checked your website with the classic Kopage website builder, you can publish it and make it accessible to visitors.

Before publishing, however, you should not only check the design. Navigation, links, forms, images, downloads, and the mobile display should also work.

In this guide, we will show you what to check before publishing a Kopage website and how you can systematically isolate typical problems.

Briefly explained: A website is not finished just because it looks good in the editor. What matters is the published version that your visitors can actually access and use in their browser.

Check the website completely before publication #

Before making a new website publicly available, you should walk through it once from a visitor's perspective.

Start on the home page and then check the most important subpages.

A sensible sequence is:

Check homepage
↓
Test navigation
↓
Open important subpages
↓
Check texts and images
↓
Test links
↓
Test forms
↓
Check mobile display
↓
Publish website
↓
Check public version again

Review content before publication #

Check whether all texts are complete and up to date.

Pay special attention to content that was initially inserted as a placeholder during creation.

Typical examples are:

Sample texts
incomplete headings
provisional prices
test images
old contact details
unfinished subpages
test buttons
notes for internal processing

Such content should not remain accidentally visible on the published website.

Check page names and navigation #

Open all important menu items and check whether they lead to the correct page.

Also check existing submenus.

A page can be completely finished and still remain difficult for visitors to find if it has been placed incorrectly in the navigation.

We cover the page structure in detail under Managing pages, navigation, and submenus in Kopage.

Test internal links #

In addition to the main navigation, links to other pages can be present within your texts, buttons, and other content areas.

Test important internal links and check whether they actually lead to the intended destination.

This is especially important if you renamed, moved, or removed pages during creation.

Practical Tip: Click through the website before publication. A link can look completely correct visually and still point to the wrong destination.

Check external links #

When you link to external websites or services, you should also test these links.

Check in particular whether the target page still exists and whether you are actually linking to the desired address.

For social media profiles, for example, not only the platform itself but also the correct company or personal profile should be linked.

Review images #

Check if all images are loaded correctly and match the respective content.

Also make sure that no provisional images or test graphics are left over.

If images are blurry, distorted, or unnecessarily large, you should optimize them before publishing.

You can find further information at Creating images, photo galleries, and sliders in Kopage.

Really submit forms #

For contact forms, a visual inspection is not sufficient.

Fill out the form yourself and send a test message.

Then check whether the expected confirmation appears and the message arrives at the intended destination.

We explain how to set up and test forms at Create forms and contact forms with Kopage.

Important: Always test a contact form completely before launch. A form that looks good but does not deliver messages fails to serve its purpose.

Test downloads #

If you offer PDF files or other documents, open the corresponding download links yourself.

Check whether the correct and current file is provided.

Especially after exchanging or deleting files, older links can lead to dead ends.

We cover file management under Manage files and offer downloads on the website.

Fully control multilingual website #

For a multilingual website, you should not only check the main language.

Switch to every active language and check at least the most important pages, navigation elements, buttons, and forms.

Pay special attention to ensuring that there are no untranslated or outdated contents.

You can find further information at Create a multilingual website with Kopage.

Test online shop before launch #

If your Jimdo website includes an online store, checking the product pages is not enough.

Test the intended ordering process as thoroughly as possible.

Depending on your shop configuration, this includes, for example, products, the shopping cart, customer data, shipping and payment options, and subsequent order management.

We explain the basic shop setup at Create an online store with Kopage and manage products.

Check website on smartphone #

Before publishing, you should open the website on at least one real smartphone.

Check navigation, headings, images, buttons, forms, and external content in particular.

You can find a detailed guide at Responsive Design: Optimizing Kopage website for smartphones and tablets.

Check SEO settings #

For important pages, you should also check the available SEO settings before publishing.

Pay particular attention to meaningful page titles, sensible descriptions, and understandable page content.

We cover the basics under SEO with Kopage: Page titles, metadata, URLs, and search engine optimization.

Do not forget the legal content #

Depending on the type of your website, your business, the services you offer, and your target markets, legal information obligations may apply.

This may include, for example, details about the website operator and information on data privacy.

Additional requirements may arise in an online shop.

Important: The website builder provides the technical platform. It does not automatically check whether your website contains all the legal content required for your specific use case.

Publish Kopage website #

Once your content and functions have been checked, you can publish the website using the publishing function provided in the classic Kopage website builder.

Execute the publication process completely and wait for Kopage to finish the process.

Then open your domain directly in a new browser window and check the public website.

Important: Do not judge the success of the publication solely based on the view in the editor. Always open the actual website via its public address afterwards.

Check again after publication #

After publishing, you should recheck at least the most important features.

Access domain
        ↓
Check home page
        ↓
Test navigation
        ↓
Open important subpage
        ↓
Test form
        ↓
Check smartphone

For a shop or other mission-critical functions, the control should be correspondingly more extensive.

Publishing changes to an existing website #

Even after the initial launch, you can continue to edit your Kopage website.

If you change texts, images, or other content, check the published version afterwards.

In the case of major changes, you should also test the affected links, forms, or other functions.

Change is not visible on the website #

If you have made a change but cannot see it on the public website, you should first check whether the corresponding publication or update process has been fully completed.

Then check whether you have actually opened the correct page and the correct domain.

If the old display still appears, the browser cache may also play a role.

Test website in a private browser window #

A private or incognito browser window can be helpful for troubleshooting because it does not use the same existing browser session.

Open your website there again and check if the current version appears.

Alternatively, you can open the page on a second device or in another browser.

Practical Tip: Before you undo extensive changes because you supposedly still see the old website, check the page first in a private browser window or on a second device.

Website is not accessible after publication #

If the website is not accessible at all, you should first determine whether the problem affects the website itself or the domain being used.

Try opening the domain in a standard browser and note the error message displayed.

For a new or recently changed domain, DNS settings, for example, can be relevant.

We explain how DNS works fundamentally at DNS simply explained: How the Domain Name System works.

New domain is not working yet #

If a new domain or a recently configured domain is not reachable, you should check the domain and DNS configuration.

Detailed troubleshooting can be found under New domain not working: Causes and solutions.

Do not change DNS records randomly if you do not yet know the cause.

Domain with another provider #

The domain does not necessarily have to be registered with the same provider as the hosting.

If your domain is managed by another registrar, it must be technically connected correctly to CURIAWEB hosting.

We explain the procedure under Connect domain with another provider to CURIAWEB hosting.

Homepage works, but subpage does not #

If the homepage is accessible, but a specific subpage is not, there is likely no general issue with the entire domain.

First, check whether the page in question still exists and is correctly published.

Then check the link or the navigation through which it is accessed.

If the address of the page was changed previously, an old link can also still be used.

A menu item leads to the wrong page #

In this case, check the page and navigation structure.

Check whether the menu item is actually linked to the desired page and whether an incorrect association was accidentally created when reorganizing the website.

Test the navigation again on the published website after the correction.

Image is not displayed #

If a single image is missing, you should first check whether the image file in question is still present and has been correctly selected within the corresponding content area.

Check also whether the problem affects only a specific image or multiple images.

If only a single file is affected, you should not immediately assume a general website issue.

Form is not working #

If a form does not work as expected, test it yourself first on the published website.

Check whether all required fields have been filled out correctly and if an error message is displayed.

If the form can be submitted successfully but no message arrives at the expected destination, also check the configured recipient address and the spam or junk folder of the recipient's mailbox.

Do not hastily change global email or spam filter settings before you have narrowed down the specific problem.

Download is not working #

If a download link leads to a dead end or opens the wrong file, first check whether the file is still present in the file management.

Then check whether the visible download link is actually connected to this file.

Especially after replacing or deleting files, older shortcuts may remain.

External content is not working #

With Google Maps, videos, social media content, or other external services, the cause may lie outside of Kopage.

First, check whether the external service itself is reachable and whether the integration or address used is still up to date.

We cover further basics under Embed Google Maps, YouTube, and social media into Kopage.

Issues with custom HTML, CSS, or JavaScript #

If a problem occurred immediately after an individual code change, you should investigate that change first.

Restore the previous working state if possible and check whether this resolves the problem.

We explain how to work more securely with custom code at How to use custom HTML, CSS, and JavaScript in Kopage.

Website looks incorrect on smartphone #

If the desktop version looks correct but an issue occurs on the smartphone, check the affected area first.

Especially external widgets, very wide content, long unbreakable texts, and custom-inserted code can cause mobile display issues.

If only a single element is affected, you should not immediately change the entire template or design.

Website is slow #

If a page loads unusually slowly, you should first check whether particularly large images or multiple external contents have been included.

Videos, maps, external widgets, and other third-party features may load additional resources.

Even very large image files can cause unnecessary loading time.

However, do not remove features indiscriminately. Try to find out first which area is actually problematic.

After a change, the layout is broken #

If a display issue occurred right after a change, you should first focus precisely on that change.

Was a new content block inserted? Was custom CSS changed? Was an external widget added?

The more precisely you can narrow down the time of the problem, the easier the troubleshooting will be.

Basic rule for troubleshooting: Do not change five other things at the same time. Check the most recent change first and then test again.

Problem only in one browser? #

If a website does not work properly in a browser, you should test it by opening it in a second, up-to-date browser.

If it works correctly there, the cause may be related to browser data, an extension, or a browser-specific feature, for example.

A test in a private browser window can also help narrow it down.

Issue only on one device? #

If the website works correctly on other devices, the affected device or its browser should also be considered.

Check whether the issue is reproducible and whether it affects only a single page or the entire website.

Such information is also helpful if you need support later.

Perform troubleshooting systematically #

Instead of changing settings on a whim, you should narrow down a problem step by step.

What exactly is not working?
        ↓
Since when does the problem exist?
        ↓
What was changed last?
        ↓
Does it affect one or all pages?
        ↓
Does it affect one or more browsers?
        ↓
Does it affect desktop and smartphone?
        ↓
Is an external service involved?
        ↓
Revert last change as a test
        ↓
check again

This approach allows many problems to be narrowed down much more quickly.

Do not ignore error messages #

If Kopage, your browser, or an external service displays a specific error message, you should note down its exact wording.

An error message often provides significantly more information than the general description „It doesn't work“.

If you need support, a screenshot of the error message can also be helpful.

Provide specific details for support requests #

If you cannot solve a problem yourself, accurate information makes troubleshooting much easier.

For example, the following are helpful:

affected domain
affected page
exact description of the problem
time since the problem has existed
last made change
device used
browser used
screenshot of an error message

Please also write what you have already tested yourself.

Practical Tip: Instead of „My website doesn't work,“ a description like „On the contact page, the form cannot be submitted on the iPhone in Safari; it works on the desktop“ is much more helpful for troubleshooting.

After publication on Google #

A published website does not necessarily appear immediately in Google search results.

Search engines must first discover, crawl, and process new or modified pages.

Publishing in Kopage and indexing on Google are therefore two different processes.

We cover Google, XML sitemap, and statistics functions under Google, Sitemap, Analytics and website statistics in Kopage.

Maintain website after launch #

With its publication, a website is not finished forever.

Contact information, prices, services, appointments, downloads, or other information are subject to change.

Therefore, check your website regularly and update the content if it is no longer correct.

Outdated content is also a website problem #

Even a technically flawless website can provide poor information if its content is no longer up to date.

Particularly critical are, for example:

old prices
expired events
incorrect opening hours
services no longer offered
outdated downloads
old contact information

Regular content review is therefore just as much a part of website maintenance as technical functional testing.

Pre-launch checklist #

Text complete?
        ↓
Contact info correct?
        ↓
Navigation tested?
        ↓
Internal links tested?
        ↓
External links tested?
        ↓
Images correct?
        ↓
Forms submitted?
        ↓
Downloads opened?
        ↓
Shop tested?
        ↓
Language versions checked?
        ↓
SEO settings checked?
        ↓
Legal content checked?
        ↓
Smartphone tested?
        ↓
Website published?
        ↓
Public version checked again?

Summary #

Before publishing your Jimdo website, you should thoroughly check not only its design, but also its content and functions.

Test navigation, links, images, forms, downloads, and, if applicable, your online shop. In addition, open the website on a smartphone and check the publicly accessible version after publication.

If a problem occurs, you should narrow it down systematically: check what exactly is affected, when the problem started, and what change was made last.

In case of availability issues, you should also distinguish between Jimdo, hosting, and the domain or DNS.

And even after the successful launch, the website remains an ongoing project: content, links, and functions should be checked regularly and updated as needed.

A website is successfully published when not only the editor looks „finished,“ but visitors can reliably access, understand, and use the public website.