Redirects

Add redirects for previous domains (helpx.adobe.com or marketing.adobe.com or docs.adobe.com) or for new locations within experienceleague.adobe.com.

We support the following redirects:

  • Global (dispatcher) redirects from docs.adobe.com to experienceleague.adobe.com link
  • Individual (user-defined) redirects from docs.adobe.com to experienceleague.adobe.com link
  • Redirects from marketing.adobe.com link
  • Redirects from helpx.adobe.com link

Adding redirects within experienceleague.adobe.com

When you change a URL by renaming the file or moving a file to a different location in the TOC, you can use the redirects.csv file in your repo to specify the old URL and the new URL.

  1. Copy a redirects.csv into the root level of your repo.

    The template.en repo includes a blank redirects.csv file.

  2. Open the redirects.csv file in an editor such as Microsoft Excel.

  3. On each line, add the old URL in column A and the new URL in column B.

    user redirects file

  4. Save the file.

After you commit these changes to master, if validation passes, the redirects go live once a day at the following times.

Time Zone Schedule
PST 20:05
MST 21:05
EST 23:05
GMT 04:05*
CET 05:05*
EET 06:06*
IST 09:35*

*Next day

NOTE

The schedule is based on PST. Therefore when the US begins/ends DST (second Sunday of March/fist Sunday of November), this schedule will shift for the rest of the world that observes DST later/earlier and for those that do not observe DST at all.

  • These redirects work only for experienceleague.adobe.com URLs. Redirects from other domains such as helpx.adobe.com or docs.adobe.com will be invalid. (See the note below for adding docs.adobe.com redirects.)

  • The redirects can include the full URL or start with /docs/<path>.

  • Blank lines and comment lines (lines that start with #) are ignored.

  • Used only to redirect individual pages, not a whole guide with wildcards. See the next section about global redirects for wildcards.

  • The redirects.csv is tested for validation:

    • The destination URL must be live.
    • No duplicate source URLs: A to B, A to C
    • No chains: A to B, B to C, C to D (change to A to D, B to D, C to D)
    • No loops: A to B, B to A
NOTE

If you need to redirect an article from docs.adobe.com, edit the URL to its EXL equivalent, and use that URL as the source. This redirects the global redirect. For example, https://docs.adobe.com/content/help/en/audience-manager.html becomes https://experienceleague.adobe.com/docs/audience-manager.html.

Adding global redirects for experienceleague.adobe.com

Global redirects are useful if you change the repo name or anchor URL of an entire guide, or you change the URLs of a large section of a guide. We can add wildcard syntax to the dispatcher file to redirect files from the old location to the new location.

If you want to create a global or bulk set of redirects, file a UGP JIRA ticket, and assign it to Bob Bringhurst.

Once implemented, these redirects go live once a day at the following times.

Time Zone Schedule
PST 20:05
MST 21:05
EST 23:05
GMT 04:05*
CET 05:05*
EET 06:06*
IST 09:35*

*Next day

NOTE

The schedule is based on PST. Therefore when the US begins/ends DST (second Sunday of March/fist Sunday of November), this schedule will shift for the rest of the world that observes DST later/earlier and for those that do not observe DST at all.

Redirects for previous domains

You can add redirects to a previous location: helpx.adobe.com or marketing.adobe.com or docs.adobe.com.

When providing redirects, make sure that you provide those redirects in the correct format. The marketing.adobe.com (.txt), helpx.adobe.com (.xls), and docs.adobe.com (.txt) redirects require different formats. Please create separate files and tickets for different redirect targets. See the following sections below for details:

Requesting redirects for previous domains

When requesting redirects, please open a jira issue in the project SSECD with the Component called Redirects.These jira issues are automatically assigned to an SSE team member.

Adding redirects for marketing.adobe.com

If you discover missing redirects or make changes that result in different URLs for the docs.adobe.com articles, follow these steps.

  1. Work with the SSE team (usually Bob) to create a .txt that includes the old URL followed by a space, and then the new URL. Example:

    Redirects text file

    In this text file, we need to remove the domain from the old URL so that the redirects work for both marketing.adobe.com and experience.adobe.com. Feel free to remove the domain if you like, or let the SSE team do it.

  2. Log a JIRA ticket with the SSE - Collaborative Documentation team. Select Redirects as the Component. Attach the text file.

(SSE Team only) Adding redirects for marketing.adobe.com

We work with Balvinder Singh Rawat (barawat@adobe.com) to submit pull requests for redirects. PG, Bob, and Alva have rights to make these pull requests. If one of us is out, contact Barawat and follow these instructions. (Alva recorded a video of this process in bluejeans and forwarded it.)

  1. Go to https://git.corp.adobe.com/MCPS/excui-saltstack/tree/stage/salt/global/files/etc/haproxy-macui.

    Do not edit these files directly. Instead, create a fork.

  2. Create a fork for the excui-saltstack repo.

  3. Open the haproxy-macui directory in the forked repo.

    There is one redirects file (resources_redirects.map) for all English redirects. The redirects are organized by solution. There is a separate redirects file for each language (such as resources_redirects_de.map) for each language. Ignore the “stage_beta” map files; we don’t use those.

  4. Edit the file or files.

    If I’m just adding or editing English redirects, I just edit the resources_redirects.map file directly in the github browser. If I’m copying redirects from the English map file to the language map files, I clone the repo and work in Visual Studio Code.

  5. When you’re done editing the file, commit the changes to the stage branch in your fork.

  6. Create a pull request from your fork to the main MCPS repo. If you have rights, include Balvinder (@barawat) as a reviewer. Otherwise, reach out to him directly for help.

    Before submitting the next set of redirects, delete/re-create the fork, or sync it with the base repo.

Adding redirects for helpx.adobe.com

  1. Work with the SSE team (usually Alva) to generate a list of redirects in an xls file. Use absolute links from helpx to absolute links to docs.adobe.com.
  2. Submit an xls file that includes the old URL and the new URL. In the header of the xls file please add SourceURL and DestinationURL to the top header.

(SSE Team only) Adding redirects for helpx.adobe.com

We work with helpx’s webops team. To submit your redirects, go to https://ccp.corp.adobe.com/redirects.php and add the redirects - either an xls file formatted with SourceURL and DestinationURL in the header; or you can submit individual URLs (good for smaller jobs).

Some items you can determine in the request form are the date (Releases are always on Thursdays). If you need a date outside of their release schedule, make sure to request it. You can also indicate that something is an urgent request. Generally, the team asks for 2 weeks for redirects.

After the redirect request is submitted, the system generates a jira issue that can be followed (in the WPS project for example https://jira.corp.adobe.com/browse/WPS-7571).

On this page

Adobe Summit Banner

A virtual event April 27-28.

Expand your skills and get inspired.

Register for free
Adobe Summit Banner

A virtual event April 27-28.

Expand your skills and get inspired.

Register for free