{"id":2302,"date":"2023-12-23T03:39:19","date_gmt":"2023-12-23T03:39:19","guid":{"rendered":"https:\/\/wpconsults.com\/?p=2302"},"modified":"2026-07-18T22:17:18","modified_gmt":"2026-07-19T03:17:18","slug":"google-warnt-vor-urls-mit-doppelten-schragstrichen-gelost","status":"publish","type":"post","link":"https:\/\/www.wpconsults.com\/de\/google-warns-against-urls-with-double-slashes-solved\/","title":{"rendered":"Google warnt vor URLs mit doppelten Schr\u00e4gstrichen (gel\u00f6st)"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Somewhere on your site, a link like <code>example.com\/\/blog\/post<\/code> is quietly creating a second copy of a page you already have. URLs with double slashes are technically valid, which is exactly why nothing errors out, and why they sit unnoticed while search engines treat each variant as a separate page.<\/p>\n\n<p class=\"wp-block-paragraph\">Google has said these URLs can confuse some crawlers, so the warning is real, just smaller than the headlines make it. I will show you what actually causes double slashes on a WordPress site, how to find them, and the clean way to fix them for good.<\/p>\n\n\n<div class=\"wp-block-group wpc-takeaways is-layout-flow wp-block-group-is-layout-flow\">\n<h3 class=\"wp-block-heading\">Key Takeaways<\/h3>\n<ul class=\"wp-block-list\"><li>The URL standard (RFC 3986) allows repeated slashes in a path, so <code>\/\/page<\/code> loads fine and nothing ever warns you about it.<\/li><li>Google&#8217;s Gary Illyes called double slashes a usability problem that may also confuse some crawlers; it is <strong>not a penalty<\/strong>, it is a duplication problem.<\/li><li><code>\/page\/<\/code> and <code>\/\/page\/<\/code> are two different URLs to a search engine, so the variant splits canonical signals and wastes crawl on pages you never meant to publish.<\/li><li>Almost every double slash comes from one of four sources: sloppy link concatenation, a trailing slash saved in a URL setting, stacked redirect rules, or migration leftovers.<\/li><li>Fix the source first, then let one site-wide 301 rule collapse whatever slips through; a canonical tag is the backstop, not the fix.<\/li><\/ul>\n<\/div>\n\n\n<style>.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-content-wrap{padding-top:var(--global-kb-spacing-sm, 1.5rem);padding-right:var(--global-kb-spacing-sm, 1.5rem);padding-bottom:var(--global-kb-spacing-sm, 1.5rem);padding-left:var(--global-kb-spacing-sm, 1.5rem);border-top:1px solid var(--global-palette10, #3182CE);border-right:1px solid var(--global-palette10, #3182CE);border-bottom:1px solid var(--global-palette10, #3182CE);border-left:1px solid var(--global-palette10, #3182CE);border-top-left-radius:5px;border-top-right-radius:5px;border-bottom-right-radius:5px;border-bottom-left-radius:5px;box-shadow:15px 15px 0px 0px rgba(160, 152, 255, 0.31);}.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-contents-title-wrap{padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;}.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-contents-title{font-weight:600;font-style:normal;}.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-content-wrap .kb-table-of-content-list{color:var(--global-palette4, #2D3748);font-weight:regular;font-style:normal;margin-top:var(--global-kb-spacing-sm, 1.5rem);margin-right:0px;margin-bottom:0px;margin-left:0px;}.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-content-wrap .kb-table-of-content-list .kb-table-of-contents__entry:hover{color:var(--global-palette1, #3182CE);}.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-content-wrap .kb-table-of-content-list .active > .kb-table-of-contents__entry{color:var(--global-palette1, #3182CE);}@media all and (max-width: 1024px){.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-content-wrap{border-top:1px solid var(--global-palette10, #3182CE);border-right:1px solid var(--global-palette10, #3182CE);border-bottom:1px solid var(--global-palette10, #3182CE);border-left:1px solid var(--global-palette10, #3182CE);}}@media all and (max-width: 767px){.kb-table-of-content-nav.kb-table-of-content-id3268_6ddb5a-74 .kb-table-of-content-wrap{border-top:1px solid var(--global-palette10, #3182CE);border-right:1px solid var(--global-palette10, #3182CE);border-bottom:1px solid var(--global-palette10, #3182CE);border-left:1px solid var(--global-palette10, #3182CE);}}<\/style>\n\n<h2 class=\"wp-block-heading\">What Google actually said about double slashes in URLs<\/h2>\n\n<p class=\"wp-block-paragraph\">In the <a href=\"https:\/\/developers.google.com\/search\/help\/office-hours\/2023\/december\" target=\"_blank\" rel=\"noopener nofollow\">December 2023 Google SEO office hours<\/a>, Google&#8217;s Gary Illyes was asked whether a double slash in a URL path, something like <code>example.com\/\/us\/shop<\/code>, has any SEO impact. His answer had two halves: technically the format is fine, because <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc3986\" target=\"_blank\" rel=\"noopener nofollow\">RFC 3986<\/a> treats the slash as a separator that may repeat in a path, but from a usability standpoint it is a bad idea and it may confuse some crawlers.<\/p>\n\n<p class=\"wp-block-paragraph\">Notice what he did not say: there is no double-slash penalty, and Google is not going to demote a page for it. <a href=\"https:\/\/www.searchenginejournal.com\/google-answers-if-double-slash-in-url-has-seo-impact\/504364\/\" target=\"_blank\" rel=\"noopener nofollow\">Search Engine Journal&#8217;s coverage<\/a> landed on the same reading. The real cost shows up indirectly, through duplication and crawl waste, which is what the rest of this post deals with.<\/p>\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"English Google SEO office-hours from December 2023\" width=\"720\" height=\"405\" src=\"https:\/\/www.youtube.com\/embed\/GAZ6j00geMk?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n<h2 class=\"wp-block-heading\">Why URLs with double slashes hurt your SEO anyway<\/h2>\n\n<p class=\"wp-block-paragraph\">To a search engine, a URL is an identifier, so <code>\/blog\/post\/<\/code> and <code>\/\/blog\/post\/<\/code> are simply two different addresses that happen to serve the same content. If both return a normal 200 page, you have shipped a duplicate: two URLs collecting links, impressions, and crawl budget for one piece of content.<\/p>\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"969\" height=\"210\" src=\"https:\/\/wpconsults.com\/wp-content\/uploads\/2023\/12\/image-27.png\" alt=\"Example of URLs with double slashes creating duplicate page addresses\" class=\"wp-image-2306\" srcset=\"https:\/\/www.wpconsults.com\/wp-content\/uploads\/2023\/12\/image-27.png 969w, https:\/\/www.wpconsults.com\/wp-content\/uploads\/2023\/12\/image-27-300x65.png 300w, https:\/\/www.wpconsults.com\/wp-content\/uploads\/2023\/12\/image-27-768x166.png 768w\" sizes=\"auto, (max-width: 969px) 100vw, 969px\" \/><\/figure>\n\n\n<p class=\"wp-block-paragraph\">On a handful of pages that is a rounding error, but double slashes rarely stay a handful, because the broken template or setting that created one creates them everywhere it renders. The result is <strong>split canonical signals, messy Search Console reports, and crawlers spending requests on variants<\/strong> instead of on the pages you want indexed faster.<\/p>\n\n<h2 class=\"wp-block-heading\">What creates double slash URLs on a WordPress site<\/h2>\n\n<p class=\"wp-block-paragraph\">Double slashes are almost never typed by hand; they are assembled by code. The classic case is concatenation: a base URL stored with a trailing slash meets a path that starts with its own slash, and <code>site.com\/<\/code> plus <code>\/page<\/code> becomes <code>site.com\/\/page<\/code>.<\/p>\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Cause<\/th><th>Where it usually hides<\/th><th>Fix<\/th><\/tr><\/thead><tbody><tr><td>Link concatenation<\/td><td>Theme templates, widgets, menus with hardcoded paths<\/td><td>Remove the doubled slash in the template or menu item<\/td><\/tr><tr><td>Trailing slash in a saved URL<\/td><td>Plugin settings, custom fields, hardcoded site URLs<\/td><td>Store the base URL without a trailing slash<\/td><\/tr><tr><td>Stacked redirect or rewrite rules<\/td><td>.htaccess, redirect plugins, CDN rules adding an extra slash<\/td><td>Audit the rules and test the redirect chain<\/td><\/tr><tr><td>Migration leftovers and old backlinks<\/td><td>Internal links imported from an old structure, external sites linking wrong<\/td><td>Update internal links; let the 301 rule below catch external ones<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\">The four common sources of double slash URLs on WordPress sites, where each hides, and how to fix it at the source.<\/figcaption><\/figure>\n\n\n<h2 class=\"wp-block-heading\">How to find double slash URLs on your site<\/h2>\n\n<p class=\"wp-block-paragraph\">Crawl your site with a tool like Screaming Frog and filter the URL list for <code>\/\/<\/code> after the protocol; that surfaces both the variant pages and, more usefully, the internal links pointing at them, which is where the source lives. Search Console helps from the other side: the Pages report lists duplicate and &#8220;crawled, currently not indexed&#8221; variants Google has already met.<\/p>\n\n<p class=\"wp-block-paragraph\">If an ugly variant is already indexed and you want it gone quickly, the Removals tool buys you time while the redirect does the permanent work; I cover that in <a href=\"https:\/\/www.wpconsults.com\/remove-urls-from-google-search-results\/\">removing URLs from Google search results<\/a>.<\/p>\n\n<h2 class=\"wp-block-heading\">How to fix URLs with double slashes for good<\/h2>\n\n<p class=\"wp-block-paragraph\">Fix the source first, because a redirect that masks a broken template is a patch, not a repair. Correct the concatenation, strip the trailing slash from the stored URL, or repair the rewrite rule, and the new double slashes stop appearing.<\/p>\n\n<p class=\"wp-block-paragraph\">Then add a site-wide rule that collapses anything that still slips through, including old external links you cannot edit. On Apache, this goes in your .htaccess:<\/p>\n\n<pre class=\"wp-block-code\"><code>RewriteEngine On\nRewriteCond %{THE_REQUEST} ^[A-Z]+\\s\/\/+(.*)\\sHTTP\/[0-9.]+$ [OR]\nRewriteCond %{THE_REQUEST} ^[A-Z]+\\s(.*\/)\/+(.*)\\sHTTP\/[0-9.]+$\nRewriteRule .* \/%1%2 [R=301,L]<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">The rule reads the raw request line (<code>THE_REQUEST<\/code>) because Apache quietly collapses repeated slashes in its other variables, then 301-redirects any doubled-slash path to its clean version. A 301 is the right tool here since the variants should never exist again; if you want the fuller reasoning on choosing redirect types, see my guides on <a href=\"https:\/\/www.wpconsults.com\/use-cases-for-301-and-302-redirects\/\">301 vs 302 use cases<\/a> and the <a href=\"https:\/\/www.wpconsults.com\/difference-between-301-302-307-410-451-redirects-seo-perspective\/\">difference between 301, 302, 307, 410, and 451 redirects<\/a>.<\/p>\n\n<p class=\"wp-block-paragraph\">Two easier paths for specific setups: Nginx merges repeated slashes by default, so Nginx users usually only need the source fix. And if you just have a few known stragglers, you can stage those one-off 301s from your WordPress dashboard with the Redirections module in <a title=\"\" class=\"aalmanual\" target=\"_blank\"  rel=\"nofollow\"   href=\"https:\/\/rankmath.com\/?ref=pixelydgroup\">Rank Math<\/a>.<\/p>\n\n<p class=\"wp-block-paragraph\">Finally, keep self-referencing canonical tags on your clean URLs. That is the backstop: if a variant ever gets crawled before the redirect catches it, the canonical still tells Google which address owns the content.<\/p>\n\n<h2 class=\"wp-block-heading\">So, do double slashes in URLs actually hurt your rankings?<\/h2>\n\n<p class=\"wp-block-paragraph\">Honestly, not in the dramatic way the warning headlines suggest; there is no penalty, and Google usually sorts the duplication out on its own eventually. I would not panic over one stray variant in a crawl report.<\/p>\n\n<p class=\"wp-block-paragraph\">But &#8220;Google usually sorts it out&#8221; is doing quiet damage while you wait: split signals, wasted crawl, and reports you cannot trust. The whole fix, source plus redirect rule, costs about an hour, and that trade is so lopsided that leaving double slashes in place is just untidiness you are choosing to keep.<\/p>\n\n\n<div class=\"wp-block-group wpc-post-cta is-layout-flow wp-block-group-is-layout-flow\">\n<h3 class=\"wp-block-heading\">Still seeing double slash URLs in your crawl?<\/h3>\n<p class=\"wp-block-paragraph\">If the variants keep coming back or the redirect rule is not behaving, feel free to <a href=\"https:\/\/www.wpconsults.com\/work-with-wpconsults\/\">contact us<\/a> or <a href=\"mailto:abdullah@wpconsults.com\">email me<\/a> and I will help you track the source down.<\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-group wpc-changelog is-layout-flow wp-block-group-is-layout-flow\" id=\"article-update-logs\">\n<h2 class=\"wp-block-heading\">Update Logs<\/h2>\n<p class=\"wp-block-paragraph\"><strong>02 Jul 2026<\/strong><\/p>\n<ul class=\"wp-block-list\"><li>Reframed the piece around Google&#8217;s actual office-hours answer (no penalty, but a crawler-confusing duplicate), added the four real WordPress causes with fixes, and a site-wide redirect rule that collapses stray double slashes.<\/li><\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>URLs mit doppelten Schr\u00e4gstrichen sind zwar technisch gesehen g\u00fcltig, f\u00fchren jedoch zu einer Aufsplitterung der Ranking-Signale und k\u00f6nnen manche Crawler verwirren. Hier erfahren Sie, was Google dazu tats\u00e4chlich gesagt hat, wodurch sie entstehen und wie man sie auf saubere Weise beheben kann.<\/p>","protected":false},"author":1,"featured_media":7437,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kb_optimizer_status":0,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","rank_math_title":"URLs With Double Slashes: What Google Says + the Fix","rank_math_description":"Google says URLs with double slashes can confuse some crawlers. What actually causes them, what it means for your SEO, and how to fix them at the source.","rank_math_focus_keyword":"urls with double slashes","_colophon_preset":"regular","_colophon_fc_on":"","_colophon_edited_on":"","_wpc_translation_mode":"keep","_wpc_translation_visited":"","_wpc_keep_translation":false,"_wpc_lastmod":"","footnotes":""},"categories":[89],"tags":[64],"class_list":["post-2302","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technical-seo","tag-without-plugin-series"],"_links":{"self":[{"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/posts\/2302","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/comments?post=2302"}],"version-history":[{"count":0,"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/posts\/2302\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/media\/7437"}],"wp:attachment":[{"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/media?parent=2302"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/categories?post=2302"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wpconsults.com\/de\/wp-json\/wp\/v2\/tags?post=2302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}