New University Website Launch: How Not to Lose Backlinks

Launching a new university website on the same domain does not, by itself, cause a university to lose its backlinks. Links that point to the homepage keep working, because the homepage address does not change. The risk sits deeper in the site: when a new content management system, theme or information architecture changes the addresses of individual pages, every external link pointing to an old address stops reaching its content unless that address is redirected.

The protection is well documented. Google's guidance on site moves with URL changes asks site owners to map each old URL to its new equivalent, to use permanent server-side redirects such as HTTP 301 or 308, to avoid redirect chains, and to keep redirects in place for at least one year. Google also states that permanent redirects do not cause a loss of PageRank. For universities, whose pages are cited in academic papers, government portals, partner websites and news archives for many years, Webometrics recommends keeping redirects from old addresses in place indefinitely.

This guide explains which links are at risk when a university launches a new website, how to build and test a redirect map, what to do on launch day and in the months afterwards, and how to think about launch timing in relation to a ranking edition. It applies to redesigns, CMS replacements and URL restructuring that keep the same domain. Universities that are also changing their domain should read the Webometrics guide to changing a university domain without losing search visibility and backlinks.

Why a New Website Puts Backlinks at Risk

A backlink is a link from another website to a page on the university's website. Most of the links a university receives over time point not to the homepage but to specific pages: a programme page, a research centre, a faculty member's profile, a news story, an admissions guide, a policy document or a PDF report. When a new website is launched, those specific addresses frequently change, even though the domain stays the same.

Common causes of changed URLs in a university relaunch include:

• New CMS URL patterns. A page such as /index.php?option=com_content&id=123 becomes /news/new-engineering-laboratory.
• Restructured navigation. /colleges/engineering/ becomes /faculties/engineering/, or departments move under new parent sections.
• Documents and files. PDFs, prospectuses, annual reports and forms move to a new media library with different paths. These files are often among the most linked items on a university site.
• Language versions. Arabic, English or other language versions move from a parameter (?lang=ar) to a folder (/ar/), or the reverse.
• Retired subdomains. A faculty, conference, e-learning or staff-profile subdomain is merged into the main site and the old hostname is switched off.
• Archives not migrated. Older news, events and announcements are left behind, although external sites still link to them.
• Small technical differences. Changes in letter case, trailing slashes, file extensions (.html, .aspx, .php) or encoded characters produce different URLs from the server's point of view.

When any of these addresses returns a "not found" response, a visitor following a link from another website reaches an error page instead of the content. Google's documentation on HTTP status codes states that indexed URLs returning a 4xx status code are removed from the index. A carefully mapped set of permanent redirects prevents both outcomes.

What Google Says About Redirect Types

Google's documentation on redirects and Google Search distinguishes permanent redirects, which tell Google that the target should be treated as the canonical URL, from temporary redirects, which keep the original URL as the one shown in results. Google recommends server-side redirects whenever possible.

The practical rule for a university launch is simple: every old URL that has moved should return a single server-side 301 or 308 response pointing directly to the most relevant new page.

Step-by-Step: Launching a New University Website Without Losing Backlinks

1. Build a Complete Inventory of Old URLs

A redirect map can only protect the URLs it contains. Google's site-move guidance recommends building the list of old URLs from several sources, including sitemaps, server logs, analytics, CMS exports and Search Console's links report, and including images, videos, JavaScript and CSS files. For a university, the inventory should combine:

• a full export of pages and files from the current CMS;
• the current XML sitemaps;
• several months of web-server access logs, which show URLs that are actually requested, including old addresses that no longer appear in the CMS;
• landing-page reports from web analytics;
• the Top linked pages table in the Google Search Console Links report, which shows the pages with the most links from other sites;
• the backlinks report in Bing Webmaster Tools;
• URLs printed in prospectuses, posters, QR codes, email signatures and official documents.

Google's help documentation explains that the Search Console Links report is a sample rather than a complete list, that its tables are limited to 1,000 rows, and that the export from the report's landing page can contain up to 100,000 rows. It should therefore be treated as one input among several, not as the full inventory.

2. Prioritise the URLs That Carry Links and Visitors

Every URL in the inventory deserves a decision, but some deserve closer attention. The highest priority usually goes to URLs that receive external links, pages that receive search or referral traffic, documents and PDFs cited by other organisations, programme and admissions pages, research centre and researcher pages, and pages referenced by government, accreditation or partner websites.

3. Map Each Old URL to Its Closest New Equivalent

Build the redirect map as a spreadsheet with, at minimum, the old URL, the new URL, the intended status code and a notes column. Google's guidance is clear on three points:

• map each old URL to the matching new page, and do not send many pages to an unrelated destination such as the homepage;
• where several old pages have been consolidated into one, they can redirect to that single new page;
• where content has been removed and has no equivalent, return a 404 or 410 status rather than redirecting.

Redirecting everything to the homepage is the most common shortcut in university relaunches. It sends a visitor who followed a link to a specific programme or report to a page that does not contain what they were looking for, and it does not preserve the relationship between the link and the content it referred to.

Where old and new URLs follow a predictable pattern, for example /colleges/<name>/ becoming /faculties/<name>/, a pattern-based rule can handle many URLs at once. Pattern rules should still be tested against the real inventory, because exceptions are common.

4. Implement Permanent Server-Side Redirects

Implement redirects on the web server, the CMS redirect module or the content delivery network, using 301 or 308. Google advises avoiding redirect chains: links should go directly to the final destination, and where chains cannot be avoided they should be kept to about three hops and never more than five.

Universities that have redesigned before often already hold redirects from earlier sites. Those legacy redirects should be updated so that they point directly to the new final URLs, rather than to addresses from the previous site that will now redirect again.

If any subdomain is being retired, its hostname must remain active and continue to serve redirects. A switched-off hostname cannot redirect anything.

5. Prepare the New Site So It Can Be Crawled

Development and staging sites are often blocked from search engines with robots.txt rules or noindex directives. Google's site-move guidance asks site owners to plan which noindex rules will be removed at launch and to confirm the new site's robots.txt is correct. On the new site, Google also recommends self-referencing canonical tags, updated hreflang annotations for language versions and internal links that point to the new URLs directly, not through redirects. Search Console verification files or tags should be carried over to the new site so that monitoring continues without interruption.

6. Test the Redirect Map Before Launch

Before the public switch, run the full list of old URLs against the new environment with a script or crawler and check, for every URL:

• that it returns a single 301 or 308 response, or a deliberate 404 or 410;
• that the final destination returns a 200 status and is the intended page;
• that no chains or loops exist;
• that destination pages do not display "page not found" content while returning a 200 status, which Google's documentation describes as a soft 404.

Google's site-move guidance also recommends testing redirects with the URL Inspection tool in Search Console.

7. Launch Day

• Enable the redirects and confirm a sample of high-priority URLs immediately.
• Remove staging-only noindex rules and robots.txt blocks, and check canonical tags.
• Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools.
• Consider notifying participating search engines of changed URLs through IndexNow, a protocol for reporting URLs that have been added, updated or deleted.
• Check that the server has enough capacity. Google notes that Googlebot crawls more heavily after a move.

The Change of Address tool in Google Search Console is not used when the domain stays the same. Google's guidance reserves it for domain or subdomain changes.

If the relaunch also changes hosting provider, Google's guidance for hosting moves recommends lowering DNS TTL values at least a week in advance and keeping the old server running until its traffic reaches zero. A temporary drop in crawl rate after the switch is described by Google as normal.

8. Monitor and Fix Gaps in the First Weeks

No redirect map is perfect on the first day. In the weeks after launch, review "not found" errors in server logs and in Search Console's indexing reports, add redirects for old URLs that were missed, and watch the new sitemap's indexed count rise. Google states that rankings may fluctuate during a move with URL changes and that, for medium-sized sites, the transition can take weeks or longer. A helpful custom 404 page with site search and links to key sections reduces the impact of any gaps that remain.

9. Update the Links the University Controls

Redirects protect links that the university cannot change. Links that the university can change should be updated at the source, so that they point directly to the new URLs. These include the university's official social media profiles, institutional entries in national and international directories, ministry and accreditation portals where the university submits its own information, partner and consortium websites, email signatures, digital prospectuses and QR codes. Library and research teams should also check that repository, journal and researcher-profile links point to current addresses.

10. Keep Redirects for the Long Term

Google recommends keeping redirects for at least one year and notes that longer is better. University pages are cited in scholarly literature, theses, syllabi, policy documents and news archives that will never be edited. For that reason, Webometrics recommends treating redirects from old university URLs as permanent infrastructure, documented and maintained across future redesigns, rather than as a temporary launch task.

University-Specific Content That Needs Special Attention

Does Launching a New Website Affect Webometrics Results?

Universities planning a new website often ask whether the launch could affect their position in a forthcoming Webometrics edition. Webometrics publishes two editions each year, with the January edition first and the July edition second.

According to the official Webometrics methodology, Impact reflects an institution's presence and recognition across the wider web; Openness and Excellence draw on scholarly data from the UNIRANKS Open Index (OI). The methodology also states that measurement is recurring and validated over time, that historical observations may be retained to support consistency checks and to identify abnormal short-term changes, and that the absence of a measurable signal is not automatically interpreted as poor institutional performance. Webometrics does not publish data-collection dates.

On that basis, the decision a university faces is less about the calendar than about readiness. A relaunch on the same domain, with a complete and tested redirect map, crawlable pages and preserved content, keeps external links connected to the content they refer to. A relaunch with missing redirects, blocked crawling or lost content can reduce what search engines and other systems are able to find, and Google itself notes that search visibility can fluctuate for weeks or longer while a site with URL changes is reprocessed.

A practical way to make the timing decision is to ask whether the following conditions are met before launch:

• the redirect map covers every URL with external links or meaningful traffic, including files and language versions;
• the map has been tested end to end against the new environment;
• staging blocks and noindex rules have a confirmed removal step;
• retired subdomains will stay live and redirecting;
• someone is responsible for monitoring errors daily during the first weeks.

If these conditions are met, there is no technical reason in Google's guidance to delay a launch. If they are not, completing them first is the safer choice, whatever the date. Webometrics cannot guarantee any particular ranking outcome from a migration, and no implementation can guarantee search visibility or traffic.

For more on how editions work and how to compare results across them, see Webometrics Editions Explained. For an explanation of the three indicators, see What Do Impact, Openness and Excellence Mean in the Webometrics Ranking?

Common Mistakes When Launching a New University Website

Pre-Launch Checklist

1. Export every old URL from the CMS, sitemaps, server logs, analytics and webmaster tools.
2. Identify the pages and files with external links using the Search Console Links report and Bing Webmaster Tools.
3. Map each old URL to its closest new equivalent, or mark it for a deliberate 404 or 410.
4. Implement server-side 301 or 308 redirects, including legacy redirects and retired subdomains.
5. Test every mapped URL for status code, destination, chains and soft 404s.
6. Confirm canonical tags, hreflang, internal links and Search Console verification on the new site.
7. Remove staging blocks at launch and submit the new sitemap.
8. Monitor errors and indexing daily for the first weeks and fix gaps.
9. Update links the university controls at their source.
10. Document the redirect map and keep redirects in place long term.

Frequently Asked Questions

Will a new website on the same domain lose its backlinks?

Links to the homepage are unaffected. Links to individual pages are kept working only if each old page URL that changes is permanently redirected to its new equivalent.

Do 301 redirects lose link value?

Google states in its site-move documentation that permanent redirects do not cause a loss of PageRank.

How long should redirects stay in place?

Google recommends at least one year and says longer is better. For universities, whose pages are cited for many years, Webometrics recommends keeping them indefinitely.

Should the university use Google's Change of Address tool?

Not when the domain stays the same. Google's guidance reserves the Change of Address tool for moves between domains or subdomains.

Is it acceptable to redirect deleted pages to the homepage?

Google advises against sending many pages to an unrelated URL such as the homepage. Removed content with no equivalent should return a 404 or 410 status.

Should a university delay its new website until after a ranking edition?

The more important question is whether the launch is ready. A launch with a complete, tested redirect map and crawlable pages is the safer path at any time; an unprepared launch carries risk at any time. Webometrics does not publish data-collection dates and cannot guarantee ranking outcomes.

Questions about how your institution appears in Webometrics, or about improving its web presence? Contact the Webometrics team.

Sources

• Google Search Central, Site moves with URL changes.
• Google Search Central, Redirects and Google Search.
• Google Search Central, How HTTP status codes and network errors affect Google Search.
• Google Search Central, Site moves without URL changes.
• Google Search Console Help, Links report.
• IndexNow, Documentation.
• Webometrics, Methodology.

Sources accessed 9 November 2026.

Suggested Citation

Webometrics (2026). Launching a New University Website Without Losing Backlinks: A Redirect Guide. Webometrics.org, 9 November 2026. https://www.webometrics.org/insights/support/new-university-website-launch-backlinks-redirects

Webometrics is a UNIRANKS project dedicated to the development and application of webometric university evaluation and research. Webometrics.org is the project's dedicated public website and publication platform.