This page is intentionally configured with multiple canonical URL and hreflang implementation errors. It serves as a test case for SiteScan analyzer 011 (Language and Canonical Checker) to verify that all hreflang validation rules are correctly detecting issues.
The canonical tag uses a relative path /about.html instead of an absolute URL like https://test.gooux.com/about.html. Search engines require absolute URLs in canonical tags. Additionally, the canonical points to a different page entirely, which means it is not self-referencing.
| Issue Type | Severity | Description |
|---|---|---|
| Invalid language code | Error | Uses en-UK which is not valid. The correct code is en-GB (ISO 3166-1 uses GB for United Kingdom). |
| Invalid language code | Error | Uses xx which is not a valid ISO 639-1 language code. |
| Relative hreflang URL | Error | The French hreflang uses relative URL /fr/bad-canonical.html instead of absolute. |
| Duplicate language entry | Error | Italian (it) appears twice with different target URLs. |
| Missing self-reference | Error | None of the hreflang entries point back to this page URL. |
| Missing x-default | Warning | No x-default hreflang is specified for users whose language is not covered. |
| Protocol mismatch | Warning | The German hreflang uses http:// while this page is served over https://. |
When SiteScan processes this page, analyzer 011 should report all seven issues listed above. The five errors represent critical problems that would cause search engines to ignore or misinterpret the hreflang annotations entirely. The two warnings indicate best-practice recommendations that should be addressed for optimal international SEO performance.
In a production website, even a single hreflang error can cause Google to completely discard all hreflang annotations for the affected page. This makes thorough validation essential before deploying multilingual SEO implementations.
The combination of canonical and hreflang issues on this page represents a worst-case scenario that tests the full range of detection capabilities in the analyzer module. Each issue type requires different validation logic, from ISO code lookups to URL normalization and cross-reference checking between canonical and alternate language tags.