-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
English Canonical URL vs. Redirect Target mismatch #44
Comments
Front Page DE / ok Front Page EN
Beides falsch und stimmt noch nicht mal überein :-( Extraseiten:https://kleiderordnung.berlin/en/imprint/ https://kleiderordnung.berlin/impressum/ All News:https://kleiderordnung.berlin/news/ Single News:https://kleiderordnung.berlin/en/all-year-vest-by-lilli-mendelssohn-and-the-sustainable-stylist-339/ |
.... und es gibt noch gar kein rel alternative meta tag in meinem custom HTML Head. Front Page URL Fix. ✅
There, it's quite straightforward to activate otion 8 (❽), the only one not shown in the polylang tutorial screenshot:
Polylang Tutorial Source:
Canonical Fix, Alternative Language Version(s)Wenn wir das in der Navi kennen, ist es für meta dasselbe; Zunächst mal pragmatisch alles hinzufügen und korrigieren, was einfach umzusetzen ist und zeitnah deployen zwecks SEO, dann manuell verifizieren und in Google Search Console ebenfalls "validate fix" anfordern. ✅ |
Google search console: Validation started |
Manually generate a robots.txt
|
Google Search Console: Validation started |
Sitemap explizit konfiguriert in Search Console.
|
Technical SEO failures reported on 27 September 2023:
Pages with intentional redirects:
Possible problems:
|
Page with redirect: Validation started: 10/12/23
Everything else should redirect to one of the canonical DE/EN versions: |
New reason preventing your pages from being indexed.
Search Console has identified that some pages on your site are not being indexed due to the following new reason:
Page with redirect
If this reason is not intentional, we recommend that you fix it in order to get affected pages indexed and appearing on Google.
The text was updated successfully, but these errors were encountered: