Skip to content

How to Update the Application Title based on Routing Changes in Angular

Have you tried to update the document's title of your application? Maybe you're thinking that applying interpolation should be enough:



That solution is not going to work since the <title> element is outside of the scope of the Angular application. In fact, the root component of your app is within <body> tag, and the title is part of the <header> element.

Luckily, Angular provides the Title service with the methods to read the current title of the application, and a setTitle(title) to update that value.

However, what happens if you need to update the title on routing changes? Also, you may consider updating it on certain components for Analytics purposes.

In this blog post, I'll explain step-by-step how to create a custom Title service to have full control over the title of the current HTML document for your application.

🔗Project Setup


You'll need to have installed the following tools in your local environment:

  • Node.js. Preferably the latest LTS version.
  • A package manager. You can use either NPM or Yarn. This tutorial will use NPM.

🔗Creating the Angular Project

Let's assume we'll need to build an application with the following routes as requirements:

    |- Renders a home component
    |- Renders a list of products
    |- Renders a product detail based on its Identifier

  The app redirects to /home path by default

Now, let's create the project from scratch using the Angular CLI tool.

ng new angular-update-title --routing --prefix corp --style css --skip-tests

This command will initialize a base project using some configuration options:

  • --routing. It will create a routing module.
  • --prefix corp. It defines a prefix to be applied to the selectors for created components(corp in this case). The default value is app.
  • --style css. The file extension for the styling files.
  • --skip-tests. it avoids the generations of the .spec.ts files, which are used for testing

🔗Creating the Modules and Components

Once we got the initial structure of the app, we'll continue running the following commands to create a separate module for /home and /products, which are the main paths of the project:

ng generate module home --routing
ng generate component home/home

ng generate module products --routing
ng generate component products/products
ng generate component products/product-detail
  • The --routing flag can be using also along with ng generate module to create a routing configuration file for that module.

🔗Creating the Title Service

Similar to the previous section, we will create a shared module to hold the Title service. Both can be generated with the following commands:

ng generate module shared --module app
ng generate service shared/services/title
  • The --module app flag is used to "link" the brand new module to the pre-existing app.module.ts file.

🔗The Routing Configuration

Open the app-routing.module.ts file, and create the initial routes.

// app-routing.module.ts

const routes: Routes = [
    path: '',
    pathMatch: 'full',
    redirectTo: 'home'
    path: 'home',
    component: HomeComponent,
    data: {
      pageTitle: 'Home'
    path: 'products',
    loadChildren: () => import('./products/products.module').then(m => m.ProductsModule)
  • By default, the application will redirect to the home path.
  • When the router loads the home path, a HomeComponent will be rendered.
  • The products path will be loaded using the lazy loading feature.

Pay attention to the data provided to the home path. It contains the configured title through pageTitle string.

Next, open the products-routing.module.ts file to enable an additional configuration to load the Products and the Product Detail page.

// products-routing.module.ts
const routes: Routes = [
    path: '',
    component: ProductsComponent,
    children: [
        path: ':id',
        component: ProductDetailComponent,
    data: {
      pageTitle: 'Products'
  • The router will render the ProductsComponent by default when the path matches to /products. This route also defines custom data to be rendered as titles later.
  • When the path also adds an Id on /products/:id, the router will render the ProductDetailComponent.

🔗The Title Service Implementation

It's time to implement the custom Title Service for our application.

// title.service.ts

import { Injectable } from '@angular/core';
import { Title } from '@angular/platform-browser';
import { ActivatedRoute, NavigationEnd, Router } from '@angular/router';
import { BehaviorSubject, merge, Observable } from 'rxjs';
import { filter, map, tap } from 'rxjs/operators';

const DEFAULT_TITLE = 'Corp';

@Injectable({ providedIn: 'root' })
export class TitleService {
  title$ = new BehaviorSubject<string>(DEFAULT_TITLE);

  private titleRoute$: Observable<string | undefined> =
      filter((event) => event instanceof NavigationEnd),
      map(() => this.getPageTitle(this.activatedRoute.firstChild))

  private titleState$ = merge(this.title$, this.titleRoute$).pipe(
    filter((title) => title !== undefined),
    tap((title) => {
      this.titleService.setTitle(`${DEFAULT_TITLE} - ${title}`);

    private router: Router,
    private activatedRoute: ActivatedRoute,
    private titleService: Title
  ) {

  private getPageTitle(
    activatedRoute: ActivatedRoute | null
  ): string | undefined {
    while (activatedRoute) {
      if (activatedRoute.firstChild) {
        activatedRoute = activatedRoute.firstChild;
      } else if ( &&['pageTitle']
      ) {
        return['pageTitle'] as string;
      } else {
        return undefined;
    return undefined;

The above service implementation could be understood in just a few steps.

  • First, we'll need to make sure to inject the Router, ActivatedRoute and Title services in the constructor.
  • The title$ attribute contains the initial value for the title("Corp"), which will be emitted through a BehaviorSubject.
  • The titleRoute$ is an Observable ready to emit any pageTitle value defined in the current route. It may use the parent's pageTitle otherwise.
  • The titleState$ is an Observable ready to listen to either title$ or titleRoute$ values. In case incoming value is defined, it will call the Angular Title service to perform the update.
  • The getPageTitle method will be in charge of obtaining the pageTitle of the current route if it is defined or the title of the parent otherwise.

🔗Injecting the Title Service

One easy way to apply the custom Title Service in the whole application is by updating the app.module.ts file and injecting it into the constructor.

// app.module.ts

export class AppModule {
  constructor(public titleService: TitleService) {}

In that way, once the default component gets rendered, the title will be displayed as Corp - Home.

Home Page Title Updated

If you click on Go to Products link, then a redirection will be performed and the Title service will be invoked again to display Corp - Products at this time.

However, we may need to render a different title according to the product detail. In this case, we'll show Corp - Product Detail - :id where the Id matches with the current route parameter.

// product-detail.component.ts

import { Component, OnDestroy, OnInit } from '@angular/core';
import { ActivatedRoute } from '@angular/router';
import { map, Subscription, tap } from 'rxjs';
import { TitleService } from 'src/app/shared/services/title.service';

  selector: 'corp-product-detail',
  templateUrl: './product-detail.component.html',
  styleUrls: ['./product-detail.component.css'],
export class ProductDetailComponent implements OnInit, OnDestroy {
  protected subscription = new Subscription();

  productId$ = this.route.params.pipe(map((params) => params['id']));

    private route: ActivatedRoute,
    private titleService: TitleService
  ) {}

  ngOnInit(): void {
    const productIdSubscription = this.productId$
        tap((id) => this.titleService.title$.next(`Product Detail - ${id}`))


  ngOnDestroy(): void {

Let's explain the implementation of this component:

  • The constructor injects the ActivatedRoute and the custom TitleService.
  • The productId$ is the Observable which is going to emit the Id parameter every time it changes in the URL.
  • Once the component gets initialized, we'll need to subscribe to the productId$ Observable and then emit a new value for the title after creating a new string using the id. That's possible through the titleService.title$.next() method.
  • When the component gets destroyed, we'll need to unsubscribe from the productIdSubscription.

We're ready to go! Every time you select a product, the ProductDetail component will be rendered, and the title will be updated accordingly.

Title updated on Products Detail Page

🔗Live Demo and Source Code

Want to play around with the final application? Just open the following link in your browser:

Find the complete angular project in this GitHub repository: angular-update-title-service. Do not forget to give it a star ⭐️, and play around with the code.

Feel free to reach out on Twitter if you have any questions. Follow me on GitHub to see more about my work.

This Dot Labs is a development consultancy focused on providing staff augmentation, architectural guidance, and consulting to companies.

We help implement and teach modern web best practices with technologies such as React, Angular, Vue, Web Components, GraphQL, Node, and more.

You might also like


Internationalization (I18N) in Angular with Transloco


Angular v10 released!


Make it Accessible: Better Layout with HTML


Make it Accessible: Accessible Alphabet Board with Angular and RxJs