Use permanent server-side redirects (301 or 308) for moved URLs, straight to the final URL

Google trusts redirects very much when it clusters duplicates, and whether a redirect is permanent or temporary decides which URL becomes canonical: with a temporary redirect Google keeps showing the source URL. Google's crawlers follow up to 10 redirect hops, and long chains hurt crawling. Google follows JavaScript redirects only after rendering and may never see one if rendering fails; said at Search Central Live, even Google's own site consolidation used JavaScript only because it was the only option available to the person doing it, a fallback rather than a pattern to copy.

Answer every moved, merged or renamed URL with one 301 or 308 to the final URL, and collapse old chains in the redirect map into single hops. Update internal links, canonicals, hreflang and sitemaps to the new URL. Use 302 or 307 only for genuinely temporary moves, and avoid meta refresh and JavaScript redirects for permanent ones.

Entschieden aus einer URL.

Ein Audit liest die Antwort, die Header, das HTML, robots.txt, die Sitemaps und die Structured Data, und der Befund zeigt, was es gesehen hat.

So funktionieren die UrteileWas Sie verbinden