56

I'm looking for a way to modify the page title when React-Router v4+ changes locations. I used to listen for a location change action in Redux and check that route against a metaData object.

When using React-Router v4+, there's no fixed routes list. In fact, various components around the site could use Route with the same path string. That means old method I used won't work anymore.

Is there a way I can update the page title by calling actions when certain major routes are changed or is there a better a better method to update the site's metadata?

Kevin Ghadyani
  • 5,392
  • 4
  • 33
  • 50

11 Answers11

76

<Route /> components have render property. So you can modify the page title when location changes by declaring your routes like that:

<Route
  exact
  path="/"
  render={props => (
    <Page {...props} component={Index} title="Index Page" />
  )}
/>

<Route
  path="/about"
  render={props => (
    <Page {...props} component={About} title="About Page" />
  )}
/>

In Page component you can set the route title:

import React from "react"

/* 
 * Component which serves the purpose of a "root route component". 
 */
class Page extends React.Component {
  /**
   * Here, we define a react lifecycle method that gets executed each time 
   * our component is mounted to the DOM, which is exactly what we want in this case
   */
  componentDidMount() {
    document.title = this.props.title
  }
  
  /**
   * Here, we use a component prop to render 
   * a component, as specified in route configuration
   */
  render() {
    const PageComponent = this.props.component

    return (
      <PageComponent />
    )
  }
}

export default Page

Update 1 Aug 2019. This only works with react-router >= 4.x. Thanks to @supremebeing7

Updated answer using React Hooks:

You can specify the title of any route using the component below, which is built by using useEffect.

import { useEffect } from "react";

const Page = (props) => {
  useEffect(() => {
    document.title = props.title || "";
  }, [props.title]);
  return props.children;
};

export default Page;

And then use Page in the render prop of a route:

<Route
  path="/about"
  render={(props) => (
    <Page title="Index">
      <Index {...props} />
    </Page>
  )}
/>

<Route
  path="/profile"
  render={(props) => (
    <Page title="Profile">
      <Profile {...props} />
    </Page>
  )}
/>
phen0menon
  • 1,651
  • 1
  • 15
  • 34
  • 5
    This should be the accepted answer, this is much more effective and reduces the need for boilerplate code. – Raptus Mar 07 '19 at 13:44
  • @Raptus You may a simpler solution, but this one is useful yet. – JulianSoto Apr 20 '19 at 06:03
  • 1
    you could improve this answer with an example with hooks: `useEffect(() => { document.title = title; }, [])` personnally i use a custom hook if the title depends on props ` import { isFunction } from 'lodash'; import { useEffect } from 'react'; export default function useTitle(titleOrFn, ...deps) { useEffect(() => { document.title = isFunction(titleOrFn) ? titleOrFn() : titleOrFn; }, [...deps]); }; ` then simply `useTitle(()=> 'Profile of ' + userId, [userId])` – TecHunter May 17 '19 at 10:19
  • 1
    @TecHunter please, share the code on jsfiddle or some coding resource – phen0menon May 17 '19 at 12:38
  • Note: This is for react-router >= 4.x. Tried it on 3.x and it didn't work because it doesn't have a `render` prop so I had to set up a bit of a weird workaround/hack. – supremebeing7 Jun 27 '19 at 15:45
  • `props.title` should be in the dependency array for the effect since the title should be updated again if the title passed in through the props changes: ``` useEffect(() => { document.title = props.title || ""; }, [props.title]); ``` – mowwwalker Jul 03 '20 at 16:57
  • I found that you can simply at `title` as a `` like so: `` You then can access the title via props and set it. This eliminates the need for the `` wrapper. – RonE Oct 13 '20 at 15:13
  • @RonE [see](https://stackoverflow.com/a/48152635/5731003) differences between using `component` and `render` prop – phen0menon Feb 26 '21 at 12:38
54

In your componentDidMount() method do this for every page

componentDidMount() {
  document.title = 'Your page title here';
}

This will change your page title, do the above mentioned for every route.

Also if it is more then just the title part, check react-helmet It is a very neat library for this, and handles some nice edge cases as well.

Adeel Imran
  • 8,751
  • 5
  • 45
  • 71
  • I am going with react-helmet, but the other solution would work as well. – Kevin Ghadyani Sep 25 '18 at 19:59
  • 6
    This does not answer the question, even using helmet in componentDidMount() is not efficient. Is there a way to do this via the router, that is the question. – TGarrett Nov 21 '18 at 17:41
  • @TGarrett It does answer the question, that is why it is the accepted answer. Regarding your query you can use react-router life cycles hook to do the same. – Adeel Imran Nov 22 '18 at 04:50
15

Picking up from the excellent answer of phen0menon, why not extend Route instead of React.Component?

import React, { useEffect } from 'react';
import { Route } from 'react-router-dom';
import PropTypes from 'prop-types';

const Page = ({ title, ...rest }) => {
  useEffect(() => {
    document.title = title;
  });
  return <Route {...rest} />;
};

Page.propTypes = {
  title: PropTypes.string.isRequired,
};

export { Page };

This will remove overhead code as seen below:

// old:
(
  <Route
    exact
    path="/"
    render={props => (
      <Page {...props} component={Index} title="Index Page" />
    )}
  />
);

// improvement:
(
  <Page
    exact
    path="/"
    component={Index}
    title="Index Page"
  />
);

Update: another way to do it is with Hooks:

import { useEffect } from 'react';

/** Hook for changing title */
export const useTitle = title => {
  useEffect(() => {
    title && (document.title = title);
  });
};
Noelle L.
  • 25
  • 5
Thierry Prost
  • 665
  • 8
  • 19
  • 3
    React recommends composition instead of inheritance, so I wouldn't recommend this. See: https://reactjs.org/docs/composition-vs-inheritance.html – Jelle Blaauw Apr 25 '19 at 08:22
  • 1
    I prefer this answer but too sad it's not the "recommended way" – TecHunter May 17 '19 at 15:09
  • 1
    Changed to use composition as well as hooks. Happy coding – Thierry Prost Aug 06 '19 at 06:27
  • 1
    one small thing - did you mean `Page` instead of `Route` in the *improvement* block? probably just a typo – Eliran Malka Sep 03 '19 at 10:05
  • 1
    @jelle they do recommend against inheritance, _BUT_, as far as I'm aware this is to prevent people from their tendency to using sub-optimal patterns that are familiar already. I'm not aware of any actual risk or negative to using this strategy in rare cases. It can be exceptionally helpful, but it should be a last resort. To give some context, I've used it myself in one place in a thousand file project, to emphasize how rarely you should need to reach for this. If there are any real downsides to using inheritance please correct me. – Slbox Oct 08 '19 at 23:57
  • 1
    Current solution does not use any inheritance. – Thierry Prost Oct 09 '19 at 06:01
13

Using a functional component on your main routing page, you can have the title change on each route change with useEffect.

For example,

const Routes = () => {
    useEffect(() => {
      let title = history.location.pathname
      document.title = title;
    });

    return (
      <Switch>
        <Route path='/a' />
        <Route path='/b' />
        <Route path='/c' />
      </Switch>
    );
}
Jordan Daniels
  • 2,704
  • 14
  • 24
  • This works well for me, however it's `window.location.pathname` I also sliced of the slash and added a default because the home route would be blank. – Zimri Leijen Jun 19 '20 at 16:30
  • Good solution with less code. I used the `useLocation` hook and `location.pathname` instead of `history.location.pathname`. See @Tolumide answer https://stackoverflow.com/a/64509041/3559967 below. – Antony Mar 14 '21 at 06:07
  • @Antony yes, I agree. useLocation hook would be better :) – Jordan Daniels Mar 14 '21 at 23:06
7

I built a bit on Thierry Prosts solution and ended up with the following:

UPDATE January 2020: I've now updated my component to be in Typescript as well:

import React, { FunctionComponent, useEffect } from 'react';
import { Route, RouteProps } from 'react-router-dom';

interface IPageProps extends RouteProps {
  title: string;
}

const Page: FunctionComponent<IPageProps> = props => {
  useEffect(() => {
    document.title = "Website name | " + props.title;
  });

  const { title, ...rest } = props;
  return <Route {...rest} />;
};

export default Page;

UPDATE: My Page.jsx component is now a functional component and with useEffect hook:

import React, { useEffect } from 'react';
import { Route } from 'react-router-dom';

const Page = (props) => {
  useEffect(() => {    
    document.title = "Website name | " + props.title;
  });

  const { title, ...rest } = props;
  return <Route {...rest} />;
}

export default Page;

Below you can find my initial solution:

// Page.jsx
import React from 'react';
import { Route } from 'react-router-dom';

class Page extends Route {
  componentDidMount() {
    document.title = "Website name | " + this.props.title;
  }

  componentDidUpdate() {      
      document.title = "Website name | " + this.props.title;
  }

  render() {
    const { title, ...rest } = this.props;
    return <Route {...rest} />;
  }
}

export default Page;

And my Router implementation looked like this:

// App.js / Index.js
<Router>
    <App>
      <Switch>
         <Page path="/" component={Index} title="Index" />
         <PrivateRoute path="/secure" component={SecurePage} title="Secure" />
      </Switch>
    </App>    
  </Router>

Private route setup:

// PrivateRoute
function PrivateRoute({ component: Component, ...rest }) {
  return (
    <Page
      {...rest}
      render={props =>
        isAuthenticated ? (
          <Component {...props} />
        ) : (
          <Redirect
            to={{
              pathname: "/",
              state: { from: props.location }
            }}
          />
        )
      }
    />
  );
}

This enabled me to have both public areas update with a new title and private areas also update.

Hsjakobsen
  • 101
  • 1
  • 3
4

Here is my solution which is almost the same as simply setting document.title but using useEffect

/**
* Update the document title with provided string
 * @param titleOrFn can be a String or a function.
 * @param deps? if provided, the title will be updated when one of these values changes
 */
function useTitle(titleOrFn, ...deps) {
  useEffect(
    () => {
      document.title = isFunction(titleOrFn) ? titleOrFn() : titleOrFn;
    },
    [...deps]
  );
}

This has the advantage to only rerender if your provided deps change. Never rerender:

const Home = () => {
  useTitle('Home');
  return (
    <div>
      <h1>Home</h1>
      <p>This is the Home Page</p> 
    </div>
  );
}

Rerender only if my userId changes:

const UserProfile = ({ match }) => {
  const userId = match.params.userId;
  useTitle(() => `Profile of ${userId}`, [userId]);
  return (
    <div>
      <h1>User page</h1>
      <p>
        This is the user page of user <span>{userId}</span>
      </p>
    </div>
  );
};

// ... in route definitions
<Route path="/user/:userId" component={UserProfile} />
// ...

CodePen here but cannot update frame title

If you inspect the <head> of the frame you can see the change: screenshot

TecHunter
  • 5,815
  • 2
  • 24
  • 47
3

With a little help from Helmet:

import React from 'react'
import Helmet from 'react-helmet'
import { Route, BrowserRouter, Switch } from 'react-router-dom'

function RouteWithTitle({ title, ...props }) {
  return (
    <>
      <Helmet>
        <title>{title}</title>
      </Helmet>
      <Route {...props} />
    </>
  )
}

export default function Routing() {
  return (
    <BrowserRouter>
      <Switch>
        <RouteWithTitle title="Hello world" exact={true} path="/" component={Home} />
      </Switch>
    </BrowserRouter>
  )
}
Fellow Stranger
  • 25,431
  • 22
  • 134
  • 188
3

You also can go with the render method

const routes = [
 {
   path: "/main",
   component: MainPage,
   title: "Main Page",
   exact: true
 },
 {
   path: "/about",
   component: AboutPage,
   title: "About Page"
 },
 {
   path: "/titlessPage",
   component: TitlessPage
 }
];

const Routes = props => {
 return routes.map((route, idx) => {
   const { path, exact, component, title } = route;
   return (
     <Route
       path={path}
       exact={exact}
       render={() => {
         document.title = title ? title : "Unknown title";
         console.log(document.title);
         return route.component;
       }}
     />
   );
 });
};

the example at codesandbox (Open result in a new window for see title)

1

Please use react-helmet. I wanted to give the Typescript example:

import { Helmet } from 'react-helmet';

const Component1Title = 'All possible elements of the <head> can be changed using Helmet!';
const Component1Description = 'No only title, description etc. too!';

class Component1 extends React.Component<Component1Props, Component1State> {
  render () {
    return (
      <>
        <Helmet>
          <title>{ Component1Title }</title>
          <meta name="description" content={Component1Description} />

        </Helmet>
        ...
      </>
    )
  }
}

Learn more: https://github.com/nfl/react-helmet#readme

Zameer Ansari
  • 23,672
  • 19
  • 120
  • 191
1

I am answering this because I feel you could go an extra step to avoid repetitions within your components and you could just get the title updated from one place (the router's module).

I usually declare my routes as an array but you could change your implementation depending on your style. so basically something like this ==>

import {useLocation} from "react-router-dom";
const allRoutes = [
  {
        path: "/talkers",
        component: <Talkers />,
        type: "welcome",
        exact: true,
    },
    {
        path: "/signup",
        component: <SignupPage />,
        type: "onboarding",
        exact: true,
    },
  ]

const appRouter = () => {
    const theLocation = useLocation();
    const currentLocation = theLocation.pathname.split("/")[1];
    React.useEffect(() => {
        document.title = `Grade | 
        ${currentLocation[0].toUpperCase()}${currentLocation.slice(1,)}`
    }, [currentLocation])

   return (
     <Switch>
      {allRoutes.map((route, index) => 
        <Route key={route.key} path={route.path} exact={route.exact} />}
    </Switch>

   )

}

Another approach would be declaring the title already in each of the allRoutes object and having something like @Denis Skiba's solution here.

Tolumide
  • 733
  • 5
  • 10
  • I did not do much pathname processing, so the `useEffect` was simpler : ` useEffect(() => { document.title = `Grade | ${location.pathname.replace('/', '')}`; }, [location]); ` – Antony Mar 14 '21 at 09:36
0

Dan Abramov (creator of Redux and current member of the React team) created a component for setting the title which works with new versions of React Router also. It's super easy to use and you can read about it here:

https://github.com/gaearon/react-document-title

For instance:

<DocumentTitle title='My Web App'>
machineghost
  • 28,573
  • 26
  • 128
  • 197