Content of this page
Rendering and JavaScript SEOSeverity: Medium

Canonical is set by JavaScript

Critical SEO signals should be present in the initial HTML.

Short version

Critical SEO signals should be present in the initial HTML The error should never be evaluated in isolation. What matters is which URL group is affected and whether it creates a crawling, indexing, snippet, performance or quality problem.

Compare Initial and Rendered Canonical

A script can complement a canonical or overwrite an already existing value. It becomes particularly problematic if the start page appears as the target when a subpage is called directly. Therefore, compare HTML response and DOM after processing has been completed.

Example: Recognizing the Result

Illustrative example: In the server HTML, the canonical points to the start page, after the app navigation to the detail page. The direct entry and the rendered state contradict each other.

Limit cause and implement correction

If possible, have the intended value delivered correctly and avoid conflicting later changes. In addition, test a client-side page change and the direct reloading of the same URL. Both paths must yield the same canonical intent. A functioning navigation within the app alone does not control the direct search engine entry.

What makes you recognize a suitable correction

Provide the desired URL as consistently as possible in the original response. Check direct call, navigation within the app and reloading separately.

Classification and boundaries

When is this indication not a clear error?

Not every subsequent addition is automatically ineffective. However, conflicting baselines and unnecessary changes should be avoided.

Canonical is set by JavaScript according to CMS and cause

Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are linked only where canonical is set via JavaScript has a clearly own cause or fixed route in the respective system.

For this error, there is currently no own CMS deepening, because the correction is usually not sufficiently system-specific. Take advantage of the general causes and checks on this page.

Frequent causes of this error

Related SEO Errors

Appropriate Seitenreport checks

This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.