{"id":4528,"date":"2024-04-14T10:21:56","date_gmt":"2024-04-14T02:21:56","guid":{"rendered":"https:\/\/webflow.tenten.co\/?p=4528"},"modified":"2024-04-14T10:21:56","modified_gmt":"2024-04-14T02:21:56","slug":"establish-301-forwardings-for-upholding-seo-ranking","status":"publish","type":"post","link":"https:\/\/webflow.tenten.co\/en\/establish-301-forwardings-for-upholding-seo-ranking\/","title":{"rendered":"Establish 301 forwardings for upholding SEO ranking"},"content":{"rendered":"\n<div class=\"docs_rich-text w-richtext\">\n<p>Within this guide, you will understand:<\/p>\n<ol role=\"list\">\n<li>Criteria for implementing 301 forwardings<\/li>\n<li>Procedure for rerouting a page<\/li>\n<li>Technique for directing a directory<\/li>\n<li>Application of escape sequences<\/li>\n<li>Method for rerouting an entire domain<\/li>\n<\/ol>\n<h2>Criteria for implementing 301 forwardings<\/h2>\n<blockquote><p><strong>Essential:<\/strong> Although Webflow currently does not enforce a strict threshold for total forwardings, it is advisable to adhere to a maximum of 1,000. Each forwarding directive is appended to a site\u2019s manifest.json file, which furnishes site details to visitors\u2019 browsers. As the manifest file expands, more data is required to be downloaded by browsers. To optimize SEO and website performance, it is recommended to employ wildcard forwardings whenever viable, as this reduces the overall quantity of forwarding rules.\u00a0<\/p><\/blockquote>\n<p>301 forwardings serve the purpose of permanently rerouting traffic from an outdated path to a new URL \u2014 for instance, during scenarios such as:<\/p>\n<ul role=\"list\">\n<li>Revamping your URL configuration (e.g., <code>webflow.com\/mysite<\/code> to <code>webflow.com<\/code>) <\/li>\n<li>Substituting or redesigning your site resulting in fresh URLs (e.g., <code>webflow.com\/oldhomepage<\/code> to <code>webflow.com<\/code>) <\/li>\n<li>Transitioning to an entirely new domain (e.g., <code>webflowiscool.com<\/code> to <code>webflow.com<\/code>)<\/li>\n<li>Securing alternative domains to accommodate potential visitor errors (e.g., <code>webflow.net<\/code>, <code>webflow.org<\/code>, <code>webflow.io<\/code> to <code>webflow.com<\/code>) <\/li>\n<\/ul>\n<figure class=\"w-richtext-align-fullwidth w-richtext-figure-type-image\">\n<div><img decoding=\"async\" alt=\"A diagram illustrating the redirection from an old URL to a new URL. Two black squares depicted with an arrow linking them. The term 'Old URL' inscribed on the left square and 'New URL' on the right square.\" src=\"https:\/\/webflow.tenten.co\/wp-content\/uploads\/2024\/04\/64b949d95400e189a973b938_630fb031f639288790eec2cd_sgbimk5n2zdxxlncmbljedszgu95xxur1si0zznmkixhpfhgeeez6y0f0f6cgreuyg366feds36wjzgmsi-lzhkle6dlaumsumucuvj5vc9h1kimlxgh4rwq1jmahwiq9fv3sibvogesz7kryfjpmy.png\" title=\"64b949d95400e189a973b938_630fb031f639288790eec2cd_sgbimk5n2zdxxlncmbljedszgu95xxur1si0zznmkixhpfhgeeez6y0f0f6cgreuyg366feds36wjzgmsi-lzhkle6dlaumsumucuvj5vc9h1kimlxgh4rwq1jmahwiq9fv3sibvogesz7kryfjpmy\"><\/div>\n<\/figure>\n<p>Upon replacing an old URL with a new one, the previous URL may still be visible in search outcomes, referenced in blog or forum entries, bookmarked, or printed on business collateral. Visitors reaching the former URL will be directed to a 404 page by default \u2014 nonetheless, by establishing a 301 forwarding, incoming visitors to the old URL will be routed to the designated new URL.<\/p>\n<p>Over time, Google will index your updated site layout and obsolete URLs will be refreshed. Nevertheless, 301 forwardings are advised, particularly if your intention is to preserve the authority of the old URL.<\/p>\n<p>There exist various types of redirects \u2014 like 302 forwardings, indicating temporary relocations \u2014 yet, 301 forwardings are most suitable if you wish to <em>permanently<\/em> direct incoming traffic to a fresh URL.<\/p>\n<h2>Procedure for rerouting a page<\/h2>\n<p>You can permanently redirect former pages or entire page directories to novel locations within your Webflow site. To establish a 301 forwarding:<\/p>\n<ol start=\"1\" role=\"list\">\n<li>Visit <strong>Site settings <\/strong>&gt;<strong> Publishing <\/strong>&gt;<strong> 301 forwards<\/strong>\u200d<\/li>\n<li>Input the former URL in the <strong>Old path<\/strong> field (e.g., <code>\/old-url<\/code>)<\/li>\n<li>Specify the fresh URL in the <strong>Redirect to path<\/strong> field (e.g., <code>\/entirely\/new-url\/structure<\/code>)<\/li>\n<li>Click <strong>Add redirect path<\/strong><\/li>\n<li>Publish your site<\/li>\n<\/ol>\n<p>Subsequently, you can evaluate the forwarding by entering the old URL in a fresh browser tab. It should direct to the new URL. Further insights on composing redirect URLs can be explored.<\/p>\n<blockquote><p><strong>Essential:<\/strong> For redirecting an existing static page on your Webflow site to a new URL, it is imperative to eliminate or preserve the page as a draft, or amend its slug before configuring the redirection. Redirecting an existing Collection item page on your Webflow site to a new URL necessitates archiving, deletion, or unpublishing of the item, conserving it as a draft, or revising its slug before setting up the redirection.<\/p><\/blockquote>\n<h2>Technique for redirecting a directory<\/h2>\n<pTo redirect the content contained within a directory \u2014 whether redirecting to a single page or multiple pages \u2014 application of capture groups is imperative.<\/p>\n<pInitiating a basic redirection of a directory to multiple pages:<\/p>\n<ol start=\"1\" role=\"list\">\n<li>Access <strong>Site settings<\/strong> &gt;<strong> Publishing<\/strong>tab &gt;<strong> 301 forwards<\/strong>\u200d<\/li>\n<li>Include a URL incorporating a capture group <code>(.*)<\/code> within the former URL layout in the <strong>Old path<\/strong> field (e.g., <code>\/oldfolder\/(.*)<\/code>)<\/li>\n<li>Specify a URL incorporating a target path <code>%1<\/code> within the new URL layout in the <strong>Redirect to path<\/strong> field (e.g., <code>\/entirely\/new-url\/structure\/%1<\/code>)<\/li>\n<\/ol>\n<pFurther sophistication can be achieved by appending multiple capture groups to formulate intricate redirection directives. For instance, <code>\/blogs\/(.*)\/(.*)<\/code> can be rerouted to <code>\/articles\/%1\/%2<\/code>.<\/p>\n<h3>Illustrations of wildcard redirection<\/h3>\n<p>Assume you aim to redirect various pages within a directory to a single URL \u2014 for instance, directing <code>domain.com\/collections\/women<\/code>, <code>domain.com\/collections\/men<\/code>, and <code>domain.com\/collections\/children<\/code> to <code>domain.com\/collections<\/code>. Assuming <code>domain.com<\/code> is the associated domain of your Webflow site, the redirection formulation would be:<\/p>\n<ul role=\"list\">\n<li><strong>Old path:<\/strong> <code>\/collections\/(.*)<\/code><\/li>\n<li><strong>Redirect to page:<\/strong> <code>\/collections<\/code><\/li>\n<\/ul>\n<p>Alternatively, supposing you want to reroute all pages adhering to a URL configuration like <code>\/domain.com?category=food&amp;post=pie<\/code> to <code>\/blog\/food\/pie<\/code> \u2014 in essence, redirecting various pages to diverse URLs.<\/p>\n<p>You could harbor categories such as \u201cmusic,\u201d \u201ctravel,\u201d and \u201cfood,\u201d alongside posts like \u201cbeyonce,\u201d \u201clondon,\u201d and \u201cpie.\u201d These serve as your variables. In the mentioned URL, \u201cfood\u201d and \u201cpie\u201d constitute the variables. To facilitate these variable adaptations, calling out these variables with capture groups, written as <code>(.*)<\/code>, is indispensable. For instance, the redirection would be scripted as follows:<\/p>\n<ul role=\"list\">\n<li><strong>Old path:<\/strong> <code>\/%?category%=(.*)%&amp;post%=(.*)<\/code><\/li>\n<li><strong>Redirect to page:<\/strong> <code>\/blog\/%1\/%2<\/code><\/li>\n<\/ul>\n<pIn the aforementioned illustration, <code>%1<\/code> corresponds to the first capture group, while <code>%2<\/code> corresponds to the second. With this wildcard redirection method in action:<\/p>\n<ul role=\"list\">\n<li><code>\/domain.com?category=music&amp;post=beyonce<\/code> redirects to <code>\/blog\/music\/beyonce<\/code><\/li>\n<li><code>\/domain.com?category=travel&amp;post=london<\/code> redirects to <code>\/blog\/travel\/london<\/code><\/li>\n<li><code>\/domain.com?category=food&amp;post=pie<\/code> redirects to <code>\/blog\/food\/pie<\/code><\/li>\n<\/ul>\n<h2>Application of escape sequences<\/h2>\n<pIt is imperative to escape the subsequent special characters in all <strong>Old path<\/strong> URLs and URLs employing wildcards, by prefixing the<code>%<\/code> symbol before the character:<\/p>\n<ul role=\"list\">\n<li><code>%<\/code><\/li>\n<li><code>-<\/code><\/li>\n<li><code>&amp;<\/code><\/li>\n<li><code>*<\/code><\/li>\n<li><code>(<\/code><\/li>\n<li><code>)<\/code><\/li>\n<li><code>=<\/code><\/li>\n<li><code>_<\/code><\/li>\n<li><code>+<\/code><\/li>\n<li><code>?<\/code><\/li>\n<\/ul>\n<pFor instance, <code>\/old-folder\/(.*)<\/code> necessitates rendition as <code>\/old%-folder\/(.*)<\/code> to function as a redirection.<\/p>\n<pAssume you aim to redirect <code>mysite.com?category=food<\/code> to <code>mysite.com\/blog\/food<\/code>. The redirection shall be scripted as follows:<\/p>\n<ul role=\"list\">\n<li><strong>Old path:<\/strong> <code>%?category%=food<\/code><\/li>\n<li><strong>Redirect to path:<\/strong> <code>blog\/food<\/code><\/li>\n<\/ul>\n<pThe inclusion of <code>%<\/code> symbols before <code>?<\/code> and <code>=<\/code> is mandatory for the successful functioning of the redirection.<\/p>\n<h6><strong>Note:<\/strong> The necessity to escape characters is exclusive to the old path \u2014 there is no requisite for escaping characters within the new redirection path.<\/h6>\n<h2>Technique for rerouting an entire domain<\/h2>\n<pTo redirect one domain to another:<\/p>\n<ol role=\"list\">\n<li>Associate both old and new domains with your site<\/li>\n<li>Designate the new domain as the default<\/li>\n<li>Publish your site<\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"Use 301 redirects to route traffic from an old URL to a new URL.","protected":false},"author":2,"featured_media":4529,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"csco_display_header_overlay":false,"csco_singular_sidebar":"","csco_page_header_type":"","footnotes":""},"categories":[293],"tags":[],"class_list":{"0":"post-4528","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-seo","8":"cs-entry"},"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/posts\/4528","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/comments?post=4528"}],"version-history":[{"count":0,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/posts\/4528\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/media\/4529"}],"wp:attachment":[{"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/media?parent=4528"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/categories?post=4528"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webflow.tenten.co\/en\/wp-json\/wp\/v2\/tags?post=4528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}