{"id":2615,"date":"2024-08-12T09:00:42","date_gmt":"2024-08-12T13:00:42","guid":{"rendered":"http:\/\/sites.bu.edu\/marcom-team\/?page_id=2615"},"modified":"2026-02-03T12:22:22","modified_gmt":"2026-02-03T17:22:22","slug":"redirects-and-broken-links","status":"publish","type":"page","link":"https:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/helpful-id-updates-links\/redirects-and-broken-links\/","title":{"rendered":"Redirects and Broken Links"},"content":{"rendered":"<h1><a href=\"https:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/interactive-design-workflow\/site-launch\/redirects\/\"><b><\/b><\/a><\/h1>\n<p><span style=\"font-weight: 400;\">When a redesign launches, it\u2019s not unusual for the site structure to have changed significantly, which creates a significant number of broken links. Before site launches, we take several steps to catch broken link errors to the best of our ability.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<h4><strong>Broken Links<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">NOTE: To request a Broken Link Report or Full Link Report, file a help ticket with IS&amp;T.<\/span><\/p>\n<h4><strong>Broken Link Report vs Full Link Report<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">There are two types of reports you may need to be certain your site is full of successful links.<\/span><\/p>\n<h4><strong>Broken Link Report<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">A Broken Link Report is a scan of all links on the new site \u2013 inline links, menu items, buttons, etc. This allows the client to be sure that all links on the new site successfully link somewhere else before you launch.<\/span><\/p>\n<h4><strong>Full Link Report<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">The Full Link Report is a report that lists all URLs on the CURRENT site against all URLs on the NEW site. This allows the client to see where all current links will point once the new site is live. If pages\/posts have been removed, renamed, or reorganized in the navigation structure, you will need to create redirects for the links on the current site so that they point to the new location.<\/span><\/p>\n<hr \/>\n<h5><span style=\"font-weight: 400;\">Example 1<\/span><\/h5>\n<p><span style=\"font-weight: 400;\">On the CURRENT site the URL might be http:\/\/www.bu.edu\/academics\/eng\/undergraduate-policies\/academic-progress-and-graduation\/<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, on the NEW site, the URL is https:\/\/www.bu.edu\/academics\/eng\/policies\/undergraduate-policies\/academic-progress-and-graduation\/<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Using the old link without a redirect, WordPress may send you to http:\/\/www.bu.edu\/academics\/sargent\/undergraduate-policies\/academic-progress-and-graduation\/<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The reason why you get Sargent\u2019s version instead of ENG&#8217;s version is because WordPress is trying its hardest to NOT serve a 404 error. It thinks, \u201cI\u2019m looking for academic-progress-and-graduation\u2014oh, Sargent has one, I\u2019d rather give that than a 404.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With a redirect we can safely point the old page to the new page, which guarantees all search engine results, bookmarked pages, and links from other sites get updated and all point to the same new location.<\/span><\/p>\n<h5><span style=\"font-weight: 400;\">Example 2<\/span><\/h5>\n<p><span style=\"font-weight: 400;\">http:\/\/www.bu.edu\/marcom\/profile\/tom-coolguy links to a profile for Tom Coolguy, the MarCom FunTime Manager, on the current site. However, on the new site Tom Coolguy\u2019s profile has been removed because he\u2019s moved on to other cool guy things.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Using the old URL without a redirect, WordPress may send you to http:\/\/www.bu.edu\/marcom\/profile\/tom-otherdude because once again WordPress thinks it is smart enough to solve the problem and doesn\u2019t want to look bad sending you a 404. But Tom Otherdude isn\u2019t the new MarCom FunTime Manager, he\u2019s just another Tom.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With a redirect pointing to http:\/\/www.bu.edu\/marcom\/profile\/ we could be sure that the user is getting sent to the Profile Archive page and can find the new MarCom FunTime Manager on their own.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><strong>Team and Client Broken Link and Redirection Responsibilities<\/strong><\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IS&amp;T is responsible for generating a Broken Link Report 3-5 days prior to launch. The Broken Link Report looks at all links in the site content, \u201cpretends\u201d to click them, and lets you know if they are broken or not. This report is run at the time your launch request is submitted and processed; please ensure you send your request several days ahead to allow time for the team and client to fix broken links.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The lead designer and developer are responsible for reviewing the Broken Link Report for large, overarching patterns of links that are broken, fixing them using site redirects, marking the items as complete or deleting them in the report, and passing the report on to the project manager to hand off to the producer, client, or both.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The team members in charge of Information Architecture and content import are responsible for identifying section names that have changed and pages that have moved sections to the best of their ability, and notifying the developer of these changes so redirects can be created. A Broken Link Report will only catch broken links that are present in site content at the time the report is run. This step is required to identify possible broken links that are not linked to in site content and is not optional.<\/span>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">Get in front of this tedious task early \u2013 track the former slug name when you reorganize information architecture, and set up redirects during the content import.<\/span><\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The producer is responsible for repairing any broken links that were the result of issues in a GatherContent import. If you encounter a large or overarching issue with an easy-to-see pattern (for example, all links in a certain widget are wrong), loop in a developer \u2013 they may be able to help with a script and save hours of tedious work.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The client is responsible for repairing broken links in content that are not the result of a theme, IA, or content import change.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The developer is responsible for creating redirects, and the designer is responsible for verifying they work correctly.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The client is responsible for final verification that pages were properly redirected. It is normal and expected for several broken links to be discovered on launch as many clients have certain items bookmarked or in their browser history for quick access. It is very difficult to identify every single case before launch, and they are easy to find and fix as long as we\u2019re all on the lookout for them.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The client is responsible for alerting the team to any missing redirects or broken links after launch so that we can fix them.<\/span><\/li>\n<\/ul>\n<h4><strong>How to Get Full Link Report and Filtering Excel<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">To get a full list of all the links on a site, request a Full Link Report with IS&amp;T and include the name of the site you want to pull the link report from.<\/span><\/p>\n<ol>\n<li><span style=\"font-weight: 400;\"> In the Data tab, select the area you want to filter and choose Filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">A. Select the arrow on the top right of the selected area<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">B. Enter the information you want to filter by<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">If you are working on a staging site, for example, http:\/\/www-staging.bu.edu\/neidl\/, and want to know all the links that are linking to the current live site, http:\/\/www.bu.edu\/neidl\/, you may want to filter by the path to the current site: www.bu.edu\/neidl\/.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">C. Include or exclude data by checking or unchecking the boxes of the date filtered<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">D. Save your filtered spreadsheet as a new spreadsheet with these filters<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">\u00a0<\/span><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<h2><strong>Redirects<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">As of 2023, there are two methods for redirects. <\/span><a href=\"https:\/\/buweb.slack.com\/archives\/C08LCBE3D\/p1656531300034439\"><span style=\"font-weight: 400;\">See this Slack conversation for some more details.<\/span><\/a><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">\u201cNetwork\u201d Redirects. These are handled by IS&amp;T and added to the Webrouter, in GitHub: https:\/\/github.com\/bu-ist\/webrouter-prod<\/span>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">It\u2019s important to note that there are two types of redirects that can be entered. It is important to understand these and specify which we need in a ticket OR consult with IS&amp;T to help determine which is correct for your needs:<\/span>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"3\"><span style=\"font-weight: 400;\">redirect appends the incoming URL to the redirect URL. For example, \/oldsite\/some-page -&gt; \/newsite\/some-page\/<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"3\"><span style=\"font-weight: 400;\">redirect_asis takes all variations of the incoming URL and redirects them to a single new URL\u00a0<\/span><\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">Network redirects are used for \u201cmarketing URLs,\u201d to redirect an entire site when it is shut down, such as merging a site into another site.<\/span><\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Safe Redirect Manager in a site handles most other redirects and is used in conjunction with network redirects to further redirect pages and URLs<\/span><\/li>\n<\/ol>\n<h4><strong>How to Redirect a Page or Section<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Safe Redirect Manager is best for individual page redirects, or redirects of an entire section of a site. For example, \u201cthis page moved here\u201d and \u201cwe renamed X section to Y but all the page titles underneath are still the same\u201d are both examples of times when Safe Redirect Manager is the best choice.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">How? Enable the Safe Redirect Plugin and then visit Tools &gt; Safe Redirect Manager. Follow the on-page directions carefully. If you\u2019re having trouble setting up a redirect, contact a developer.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Example:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The list of all of the redirects on a single site:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Editing an individual redirect rule. Follow the on-page directions carefully:<\/span><\/p>\n<h4><strong>How Safe Redirect Manager Handles the Order of Redirects<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Safe Redirect Manager (SRM) uses the menu_order followed by the ID (post id) of the SRM posts to determine the order redirects should apply. All SRM posts when entered have a menu order of 0. There are times when you have page-specific redirects such as \/somesite\/some-page that redirects to \/somenewsite\/some-new-page as well as a \u201ccatch-all\u201d redirect for \/somesite\/* that redirects to \/somenewsite\/. To have the page-specific redirect match first, you may need to adjust the menu order.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Note: Because the menu order by default is 0, you may find that posts with a lower post id (those created first and hence older) will be superseded by newer (higher post id) SRM posts. So if you enter your catch-all redirect before page-specific redirects, that may function correctly. However, if the catch-all is added after and has a higher post id, you may find that it breaks the page-specific redirects. Confusing? Yeah\u2026hence this note being added.<\/span><\/p>\n<h4><strong>Controlling the Order<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">You can control the order redirects take effect with menu_order by changing the \u201corder\u201d field in the metabox when editing an SRM post. For a recent project, we set our catch-all redirects (\/somesite\/*) to have an order of 100 so they are matched AFTER the page-specific redirects in SRM that were left with a default menu_order of 0.<\/span><\/p>\n<h4><strong>How to Redirect an Entire Website<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">BU Network Redirects are redirects that affect the entire site. These are good for redirecting entire sites, or large sections\/patterns of a site. These are entered on a network-wide basis in the Webrouter in GitHub and are handled by IS&amp;T. For example, if you are combining several sites together in your redesign, such as migrating a separate magazine site\u2019s content into the parent school site, you may need a network redirect to point visitors to the old magazine site to the new school site\u2019s magazine section.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">How? If you suspect you\u2019ll need this kind of redirect, talk with your developer, project manager, or account manager and they\u2019ll get the conversation started.<\/span><\/p>\n<h2><strong>Important Information for Redesigns (Not Brand-New Sites)<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">All site redesigns will need to <\/span><a href=\"http:\/\/sites.bu.edu\/marcom-team\/departments\/interactive-design\/interactive-design-workflow\/site-launch\/google-search-requesting-recrawls\/\"><span style=\"font-weight: 400;\">request a recrawl<\/span><\/a><span style=\"font-weight: 400;\"> using the Google Search Console. If you do not have access, contact your developer. If your developer doesn\u2019t have access, Ashley has access as a backup.<\/span><\/p>\n<h4><span style=\"font-weight: 400;\">Note: BU Source URLs are now deprecated. Please do not use them unless the site already is using them.<\/span><\/h4>\n<p><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<h2><strong>Important Information for Deprecating Sites<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">In some cases, a project may combine one or more sites or abandon an older site, and require the deprecation of an older site and URL.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this case, there are two parts that need to be addressed: a bulk redirect of the old site that will preserve URLs (this is important when speaking with IS&amp;T), and then redirects being entered into Safe Redirect Manager (SRM). The first part will involve someone from IS&amp;T and should be planned in advance through the creation of a ServiceNow ticket. PLEASE NOTE that the bulk redirect should be put in place after the new site launches, not before. The new site should launch and have a little time to ensure that things are working before this is attempted. The redirects can be added to SRM at any point throughout the adding of content, prior to site launch, and even after launch.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a redesign launches, it\u2019s not unusual for the site structure to have changed significantly, which creates a significant number of broken links. Before site launches, we take several steps to catch broken link errors to the best of our ability. \u00a0 Broken Links NOTE: To request a Broken Link Report or Full Link Report, [&hellip;]<\/p>\n","protected":false},"author":12906,"featured_media":0,"parent":329,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/2615"}],"collection":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/users\/12906"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/comments?post=2615"}],"version-history":[{"count":18,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/2615\/revisions"}],"predecessor-version":[{"id":4247,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/2615\/revisions\/4247"}],"up":[{"embeddable":true,"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/pages\/329"}],"wp:attachment":[{"href":"https:\/\/sites.bu.edu\/marcom-team\/wp-json\/wp\/v2\/media?parent=2615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}