SEO

Especially for publicly accessible map projects, it can be important to be found in search engines such as Google. Not only the map name and the nodes should be found, but also the contents of your map. In addition, the search results should lead to the correct URLs of the published live map. KontextMaps are optimised for search engines for this reason. On the one hand with automatic processes, and on the other hand with manual setting options. 

 

Basically, search engine optimisation works best with live maps that are published via the original URL, a KontextMaps subdomain or a CNAME domain transfer. If your map is embedded on a website via IFrame or via a div tag, search engines cannot always reliably assign the content to the pages in which the map is embedded.



Automatic SEO optimisation

 

  • Optimised indexing: For the search engines, all map contents, such as the content boxes, receive their own static page. This content can thus be indexed directly by the search engines. This means that not only the map is found in a web search, but particularly the content. The search result then leads to the content with a direct link.
  • Optimisation for ranking: Limit the number of characters in the page title and the description meta tag to prevent a negative search engine ranking.
  • Optimisation for search result preview: OpenGraph meta tags are provided for all content so that it can be better displayed and formatted by search engines and social networks.
  • Optimisation for embedded maps: Use the canonical meta tag to link static content, such as a web page, to the dynamic map content embedded there. If the dynamic content is located on a different domain, this is taken into account when linking.
  • Optimisation for embedded maps: Automatic integration of the SEO description as alternative content for the map if it is embedded as an IFrame or image in another page that has no SEO information stored.



Manual SEO optimisation in SEO settings

 

  • Individual description: Optionally, an SEO description can be added, which is displayed in search results (relevant for all subsequent scenarios of map publication).
  • Individual description for each item: Optionally, you can add an individual SEO description for the article for all node contents in the extended content form.
  • Manual optimisation for embedded maps: Optional specification of the page URL in which the map is included to optimally ensure Canonical meta tag redirection (see scenario 2).
  • An optional CNAME setting allows the use of a CNAME forwarding, or a separate (sub)domain on which the map is displayed.

Description

Enter a concise description of your map here. The description should not be longer than 120-160 characters.

 

Map URL

Enter the final URL of your map here. If you have embedded the map on a website, enter the URL of this subpage here.

 

SEO optimisation for various publication scenarios

 

  • Scenario 1: Your map is published on a KontextMaps URL
  • If you publish your map on one of the KontextMaps domains (the default domain app.kontextmaps.com or your individual subdomain of kontextmaps), your content will be indexed together with this domain or subdomain. This means that the search results for your content will always link to a correct URL of your map. Optionally, you can save a short description of your project in the SEO settings, which will be displayed in the search results.

  • Scenario 2: Your map is embedded on an external page

  • There are two options for this: Integration via iFrame or via Div-Embed-Code. In both cases, the search engines will find the contents of the map, but not all search engines will reliably index the search results together with the domain of the page on which the map is embedded. In this case, it can happen that the search results nodeto the original KontextMaps domain of the map, because the map is then recognised as a separate page. 

     

    To ensure that the web search also works correctly with embedded maps, there are settings in the KontextMaps editor to support search engines: Firstly, the KontextMaps system creates a canonical meta tag for redirecting the indexed search results to the domain with the embedded map. Secondly, you can enter an individual description in the SEO form. In the form field for the URL of the included map, you can enter the domain of the external page. This creates a so-called canonical URL that enables forwarding from the original URL of the map to the URL of the embedded map. This means that static contents of the embedding page are linked with the dynamic map contents. If the dynamic content is located on a different domain, this is taken into account when linking.

  • Scenario 3: Map is transferred to your own (sub-)domain via CNAME
  • If you publish your map via CNAME on an external domain, the search engine optimisation works the same way as with a KontextMaps domain. Unlike a map integration on an external site, a CNAME forwarding forwards the complete map and all its content to the external (sub)domain. Thus, the KontextMaps URL of the map no longer appears. The indexing by the search engines is thus no longer done with the KontextMaps URL, but directly with the external (sub)domain. If your map is not to be published on a KontextMaps URL, CNAME forwarding is the most ideal configuration for optimal indexing by search engines.

Whoops! Your browser unfortunately does not support all the necessary technical parts needed to display this map. This happens if your browser is outdated or if JavaScript is turned off. Almost all latest browsers support the knowledge map system. Please use a newer version of your web browser to ensure a delightful experience. The newer browsers are also more secure. Thank you!