How to set html tag title from a route #1056

giacomorebonato · 2024-01-22T10:46:58Z

giacomorebonato
Jan 22, 2024

I can't see this from the examples, I am looking for a way to set HTML page title from a route definition.

<!DOCTYPE html>
<html>
<head>
  <title><!-- this title --></title>
</head>
<body>

This is challenging because the <head /> element is defined in the root component __root.tsx and other routes don't have access to it.
At the moment I am relying on rendering an hidden HTML element that I copy to the page head, before sending the code to the browser.

Which works well, until I want to find a way to apply the streaming technique and then I am lost!

giacomorebonato · 2024-01-22T11:40:54Z

giacomorebonato
Jan 22, 2024
Author

Another option that I am considering is to extract the __root.tsx component into a re-usable one, where I can pass the title as prop.

0 replies

dohomi · 2024-01-24T01:35:55Z

dohomi
Jan 24, 2024

Following this diccussion, I've seen https://tanstack.com/router/v1/docs/guide/router-context#processing-accumulated-route-context but not sure how to adjust Vite config to be able to have the <head/> section inside of __root.tsx

1 reply

thinhbg2812 Jan 24, 2025

Link is dead boss

tannerlinsley · 2024-01-24T03:28:54Z

tannerlinsley
Jan 24, 2024
Maintainer

I’m working on a first class solution for title tags.

…

On Jan 23, 2024 at 6:36 PM -0700, Dominic Garms ***@***.***>, wrote: Following this diccussion, I've seen https://tanstack.com/router/v1/docs/guide/router-context#processing-accumulated-route-context but not sure how to adjust Vite config to be able to have the <head/> section inside of __root.tsx — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

8 replies

kyxec Nov 27, 2024

Up

thinhbg2812 Jan 24, 2025

up

ilarramendi Jan 28, 2025

Up

nicoandreoli2000 Feb 25, 2025

Updates?

BrendanC23 Feb 25, 2025

This has been implemented. Here are the docs. Also, see the new posts at the bottom of this discussion.

benweier · 2024-01-24T08:14:28Z

benweier
Jan 24, 2024

I'd be keen for a first-class solution too. I had to adapt this solution from my previous React Router version...

For the moment I have a Meta component that gets all the matched routes which have a meta function on the route context from beforeload, and rendered as high up in my route tree as possible

The meta function accepts a t function from i18next as well as the loader data so that I can use translations and dynamic data in the meta tags if needed. I didn't want to enforce the t usage inside Meta, opting to pass it as an argument instead, and awaiting deferred data in meta turned out to be a terrible experience so I simply enforce that any route data used by the meta functions must never be deferred.

It's not perfect and there's actually no type-safety between my route data and the meta data argument, but it does the job pretty well - I just have to be very mindful of the loader data and manually provide the types to meta when required. A cool pattern I've used in another project is being able to render Meta components further down the route tree to effectively "override" the top level Meta if, for example, it needed a different titleTemplate pattern.

0 replies

matclayton · 2024-03-07T14:10:10Z

matclayton
Mar 7, 2024

@tannerlinsley any update when a first class solution might land, we're evaluating swapping to TanStack Router and this is one of the core pieces we're considering, especially when combined with Streaming responses. I noted the code/examples cover the Meta data, (except I couldn't find an example which loads in data for the tags), and wondered if this was the final API, or if it was a matter of just adding docs?

0 replies

shakibhasan09 · 2024-03-09T21:44:00Z

shakibhasan09
Mar 9, 2024

@tannerlinsley thanks for the wonderful library, looking forward to use the title tag feature in TanStack Router

0 replies

mutewinter · 2024-03-10T17:52:57Z

mutewinter
Mar 10, 2024

For now, here's an example using accumulated route context:

interface RootContext {
  getTitle?: () => string | Promise<string>;
}

function Root() {
  const matches = useMatches();

  useEffect(() => {
    // Set document title based on lowest matching route with a title
    const breadcrumbPromises = [...matches]
      .reverse()
      .map((match, index) => {
        if (!('getTitle' in match.routeContext)) {
          if (index === 0 && import.meta.env.DEV) {
            // eslint-disable-next-line no-console
            console.warn('no getTitle', match.pathname, match);
          }
          return undefined;
        }
        const { routeContext } = match;
        return routeContext.getTitle();
      })
      .filter(Boolean);
    void Promise.all(breadcrumbPromises).then((titles) => {
      document.title = titles.join(' · ');
      return titles;
    });
  }, [matches]);

  return <Outlet />;
}

export const Route = createRootRouteWithContext<RootContext>()({
  beforeLoad: () => ({ getTitle: () => 'App Name' }),
  component: Root,
});

// In another route file:

export const Route = createFileRoute('/test/')({
  beforeLoad: () => ({ getTitle: () => 'Test' }),
  component: () => <Test />,
});

This results in title like:

/: App Name
/test/: Test · App Name

And supports further nesting.

4 replies

barrenechea May 13, 2024

I wonder how to make it work with LazyFileRoute

bruceharrison1984 May 16, 2024

@barrenechea See this issue for how to make this work with Lazy routes. I just ran a quick POC and it works.

#1209 (comment)

barrenechea May 20, 2024

That was it! Thank you very much @bruceharrison1984 🚀

thinhbg2812 Jan 24, 2025

It's work for me :(
in my case it's nested routed

no getTitle /order/

giacomorebonato · 2024-03-11T07:24:01Z

giacomorebonato
Mar 11, 2024
Author

I am now relying on react-helmet-async for head markup in my fastrat React + Fastify starter kit.
I will update it if in the future there will be cleaner option, but I don't miss anything at the moment.

0 replies

Rendez · 2024-08-08T12:38:27Z

Rendez
Aug 8, 2024

I've opted for a much simpler solution relying on the meta property, so it's future-proof:

const TITLE = 'Your Company';

export const Route = createRootRouteWithContext<RootRouteContext>()({
  meta: () => [
    {
      title: TITLE,
    },
  ],
  component: RootComponent,
});

function Meta({ children }: { children: ReactNode }) {
  const matches = useMatches();
  const meta = matches.at(-1)?.meta?.find((meta) => meta.title);

  useEffect(() => {
    document.title = [meta?.title, TITLE].filter(Boolean).join(' · ');
  }, [meta]);

  return children;
}

function RootComponent() {
  return (
    <Meta>
      <Outlet />
    </Meta>
  );
}

0 replies

bruceharrison1984 · 2024-08-20T14:30:01Z

bruceharrison1984
Aug 20, 2024

To build on @Rendez solution, I wrote a simple hook that gathers up all the titles, and exposes them via prop. You can easily combine this with the Meta resource in Rendez's answer to nicely split apart all the logic from breadcrumbs.

import { useMatches } from "@tanstack/react-router";
import {
  createContext,
  PropsWithChildren,
  useContext,
  useEffect,
  useState,
} from "react";

const BreadcrumbContext = createContext<
  | {
      breadcrumbs: string[];
      getBreadcrumbString: (separator?: string) => string;
    }
  | undefined
>(undefined);

export const BreadcrumbProvider = ({ children }: PropsWithChildren) => {
  const [breadcrumbs, setBreadcrumbs] = useState<string[]>([]);

  const matches = useMatches();

  useEffect(() => {
    const meta = matches
      .map((x) => x.meta?.find((meta) => meta.title)?.title)
      .filter((x) => x !== undefined);
    setBreadcrumbs(meta);
  }, [matches]);

  const getBreadcrumbString = (separator = " > ") => {
    if (!breadcrumbs) return "";
    return breadcrumbs?.join(separator);
  };

  return (
    <BreadcrumbContext.Provider value={{ breadcrumbs, getBreadcrumbString }}>
      {children}
    </BreadcrumbContext.Provider>
  );
};

export const useBreadcrumbs = () => {
  const breadcrumbs = useContext(BreadcrumbContext);
  if (!breadcrumbs)
    throw new Error("useBreadcrumbs must be used within BreadcrumbProvider");
  return breadcrumbs;
};

/// access breadcrumb data from any where via
/// const { breadcrumbs, getBreadcrumbString } = useBreadcrumbs();

Adjust your root module to be similar to the following:

function RootComponent() {
  return (
      <BreadcrumbProvider>
        <Meta>
          <Outlet />
        </Meta>
      </BreadcrumbProvider>
  );
}

0 replies

gnllucena · 2024-09-22T03:42:26Z

gnllucena
Sep 22, 2024

hey @tannerlinsley , I’ve seen the meta function in some examples in the tanstack/router repo:

import { createFileRoute } from "@tanstack/react-router";

export const Route = createFileRoute("/(identity)/sign-up")({
  meta: () => [
    {
      title: "New title",
    },
    {
      charSet: "UTF-8",
    },
    {
      name: "viewport",
      content: "width=device-width, initial-scale=1.0",
    },
  ],
});

but I don't see my page title changing... is this API still experimental?

4 replies

chrism1996 Sep 26, 2024

hey @tannerlinsley , I’ve seen the meta function in some examples in the tanstack/router repo:
import { createFileRoute } from "@tanstack/react-router";

export const Route = createFileRoute("/(identity)/sign-up")({
  meta: () => [
    {
      title: "New title",
    },
    {
      charSet: "UTF-8",
    },
    {
      name: "viewport",
      content: "width=device-width, initial-scale=1.0",
    },
  ],
});
but I don't see my page title changing... is this API still experimental?

Same. Trying to build a reusable Seo component to update title, description etc. I have seen the meta property in createFileRoute but i dont see it in the docs, is that experimental @tannerlinsley ?

vKongv Sep 30, 2024

Seen that too, seems to be under "start" documentation based on the URL. Doesn't work in router yet.

rahulvils Mar 9, 2025

If you have index.html that contains title tag then remove it and add HeadContent in the __root file

maelp Sep 2, 2025

Same here... I don't have <title> in my index.html, and I've added HeadContent and Scripts

fitimbytyqi · 2024-10-11T16:51:08Z

fitimbytyqi
Oct 11, 2024

Has this been fixed ?

I just tried setting a meta attribute inside createFileRoute and it seemd to work!

export const Route = createFileRoute("/")({
  component: Home,
  loader: async () => await getCount(),
  meta: () => [
    {
      title: "This is working!",
    },
  ],
});

7 replies

fitimbytyqi Oct 28, 2024

@nemeseri I am sorry, as mentioned, my example comes from Start.

thinhbg2812 Jan 24, 2025

i dont see any option for meta in tanRouter thou

maelp Sep 2, 2025

Still not working on Tanstack Router

divyeshio Sep 3, 2025

@maelp Try this :

export const Route = createFileRoute("/")({
  component: Home,
  loader: async () => await getCount(),
  head: () => ({
    meta: [
      {
        title: "This is working!",
      },
    ],
  }),
});

maelp Sep 3, 2025

@divyeshio indeed this works, I guess the doc needs to be updated to use this pattern

nanaaikinson · 2024-10-20T04:13:48Z

nanaaikinson
Oct 20, 2024

This is what I currently use and works well. You can add more features to it.

import { useEffect } from "react";

interface HelmetProps {
  title?: string;
  description?: string;
  keywords?: string;
}

const Helmet: React.FC<HelmetProps> = ({ title, description, keywords }) => {
  useEffect(() => {
    // Set document title if provided
    if (title) {
      document.title = title;
    }

    // Set meta description if provided
    if (description) {
      let metaDescription = document.querySelector('meta[name="description"]');

      if (!metaDescription) {
        metaDescription = document.createElement("meta");

        (metaDescription as HTMLMetaElement).name = "description";

        document.head.appendChild(metaDescription);
      }
      (metaDescription as HTMLMetaElement).content = description;
    }

    // Set meta keywords if provided
    if (keywords) {
      let metaKeywords = document.querySelector('meta[name="keywords"]');

      if (!metaKeywords) {
        metaKeywords = document.createElement("meta");

        (metaKeywords as HTMLMetaElement).name = "keywords";

        document.head.appendChild(metaKeywords);
      }
      (metaKeywords as HTMLMetaElement).content = keywords;
    }
  }, [title, description, keywords]);

  return null; // This component does not render any visible UI
};

export { Helmet };

0 replies

BrendanC23 · 2025-02-20T21:08:46Z

BrendanC23
Feb 20, 2025

The docs are slightly outdated currently, but they describe a new way to set the title tag (that works with or without Start). They currently suggest doing

export const Route = createRootRoute()({
  head: () => ({
    title: 'My App',
})

but the actual syntax is

export const Route = createRootRoute()({
    head: (ctx) => {
        return {
            meta: [
                {
                    title: "My App",
                },
            ],
        };
    },
})

You also need to render a <HeadContent /> tag. If you are using TanStack Start, this goes inside <head>. If not, it should just go before <Outlet>. Note that for the latter, I also had to get rid of <title> tag within my <head> in index.html. Otherwise, that was used instead of the route's title.

3 replies

dohomi Feb 21, 2025

I am using it with the router and this is the output of my HTML based on follwoing __root.tsx. Shouldnt the content be part of <head> instead of <body>?

abrahimzaman360 Feb 21, 2025

Look at my answer below:

rhuanbarreto Jun 18, 2025

@tannerlinsley I added a PR for adding this important info for SPAs: #4457

abrahimzaman360 · 2025-02-21T06:59:18Z

abrahimzaman360
Feb 21, 2025

The way I have done suggested by @BrendanC23:

task:
Remove <title> tag from Index.html

• Do it once, In the Root Route file:

export const Route = createRootRoute({
  component: () => (
    <>
      <HeadContent />
      <RootComponent />
    </>
  ),
  head: () => ({
    meta: [
      {
        title: "My App",
      },
      { name: "description", content: "Learn more about MyApp" },
    ],
  }),
});

then,
• In File Route or Virtual Route:

import { createFileRoute } from "@tanstack/react-router";

export const Route = createFileRoute("/")({
  component: HomeComponent,
  head: (ctx) => {
    return {
      meta: [
        {
          title: "Index Page",
        },
        {
          name: "description",
          content: "Super Content",
        },
      ],
    };
  },
});

function HomeComponent() {
  return <h1>Hello Index</h1>;
}

1 reply

henggana Mar 25, 2025

Nice! ctx have loaderData property which contains data returned from the route loader.

alexy4744 · 2025-02-24T23:06:34Z

alexy4744
Feb 24, 2025

For SPAs, you can render the <HeadContent /> inside the <head> of the document by using a portal, so that it isn't rendered inside of your <body>:

import { createPortal } from "react-dom";

export const Route = createRootRoute({
  component: () => (
    <>
      {createPortal(<HeadContent />, document.querySelector("head")!)}

      <Outlet />
    </>
  ),
  head: () => ({
    meta: [
      { title: "My App" },
      { name: "description", content: "Learn more about MyApp" },
    ],
  }),
});

8 replies

maxime-forveille Feb 25, 2025

The benefit would be to take advantage of the dedup.
Right now, either you don't put the title inside the index.html but you will have those default route path titles or you put the title inside the <body> in your index.html and use the portal to allow us to override it inside routes.

Example of the lack of a title in the index.html, we should only see Admin App then Liste des organisations:

title-flicker.mp4

tannerlinsley Feb 25, 2025
Maintainer

When would you not have the flicker though (even if it’s empty, you’ll see a flicker from nothing or the default title)? It’s too late in the document lifecycle no matter how you slice it. Not sure what else could be done here other than full document control + SSR

maxime-forveille Feb 25, 2025

I was assuming that if my index.html has a defaut title in the head tag and I set the same at the index route, there will be no flicker.

cfmano Mar 5, 2025

The problem with this approach is that if you only use portal for SPAs, the HeadContent component doesn't update existing title (and other head related elements), but only adds them into head. If you need default title (inside e.g. index.html), this approach will never work. You either need to remove original <title> manually or fully replace <head> with <HeadContent />. Neither of them is comfortable.

maxime-forveille Mar 5, 2025

I understand that you don't want to parse the index.html in SPA mode. But the documentation could state it in a clearer way.
First I was expecting a behavior like react-helmet-async where I can put a title inside my index.html and then overwrite it in components.

binhonglee · 2025-03-12T05:40:56Z

binhonglee
Mar 12, 2025

Not an answer (more like a followup question), is there a way to dynamically set the title based on an async request response for SSR? Currently it seems to be possible to set html tags based per route but I'd like to send a separate network request to (another lol) server to get information to render the body (which can be done with use()) as well as <title /> and other meta tags. Basically, for SEO and link preview purposes, I'd like the page to render dynamically with info received from another server.

1 reply

binhonglee Jun 16, 2025

btw i figured this out a while ago. I did something like this for my use case. Hope this helps!

export const Route = createFileRoute('/obj/view/$id')({
  loader: async ({ params: { id }, context }) => {
    return await context.queryClient.ensureQueryData(
      objQueryOptions(id),
    )
  },
  head: ({ loaderData }) => ({
    meta: seo({
      title: loaderData.name,
      description: loaderData.description,
  }),
  component: YourComponent,
})

function YourComponent() {
  ...
}

with objQueryOptions living in a separate util file (using @tanstack/react-query) something like this:

export const fetchObj = createServerFn({ method: 'GET' })
  .validator((d: string) => d)
  .handler(async ({ data }) => {
    return await axios
      .get<Obj>(`https://yourwebsite.com/api/${data}`)
      .then((r) => r.data)
      .catch((err) => {
        console.error(err)
        if (err.status === 404) {
          throw notFound()
        }
        throw err
      })
  })

export const objQueryOptions = (id: string) =>
  queryOptions({
    queryKey: ['post', id],
    queryFn: () => fetchObj({ data: id }),
  })

amalkurbanbaev · 2025-06-14T18:47:36Z

amalkurbanbaev
Jun 14, 2025

I couldn't find a solution that I could use without "as unknown as"

export const Route = createFileRoute("/_protected/publications/$id/")({
  component: PublicationView,
  head: (ctx) => {
    const publication =
      ctx.loaderData as unknown as PublicationRetrieveSchemaReadable

    return {
      meta: [
        {
          title: `Publications / ${publication?.title}`,
        },
      ],
    }
  },
  loader: async ({ params, context }) => {
    const publication = await context.queryClient.ensureQueryData(
      publicationApiGetPublicationOptions({
        path: { publication_id: params.id },
      }),
    )

    return publication
  },
})

2 replies

schiller-manuel Jun 14, 2025
Maintainer

your property order is incorrect. see https://tanstack.com/router/latest/docs/eslint/create-route-property-order

amalkurbanbaev Jun 14, 2025

wow, I didn't know about this ordering rule (I use Biome)... now the type inference works and i removed "as unknown as"

chanithecat · 2025-08-18T04:52:41Z

chanithecat
Aug 18, 2025

I found a way to achieve this by using staticData

i set an optional static data title to the module declaration

declare module "@tanstack/react-router" {
	interface Register {
		router: ReturnType<typeof createRouter>;
	}
  interface StaticDataRouteOption {
    title?: string
  }
}

then we add this to the __root.tsx's title

export const Route = createRootRoute({
	head: (ctx) => ({
		meta: [
			{// other meta tags... }
			{
				title: ctx.matches[ctx.matches.length - 1].staticData.title
					? `${import.meta.env.VITE_APP_NAME} - ${ctx.matches[ctx.matches.length - 1].staticData.title}`
					: `${import.meta.env.VITE_APP_NAME}`,
			},
		],
		{// other head tags... }
	}),
	{// other options ... }
});

this checks if the deepest matched route has a title static data
if it exists we set it like My App - Title
else its just My App

then we just set the title to the child routes

// signup.tsx
export const Route = createFileRoute("/signup")({
	staticData: {
		title: "Sign Up",
	},
	component: SignupPage,
});

we get this

added bonus if i dont want the app name in there i could just simply override this by adding a head to the child as well like this

export const Route = createFileRoute("/demo/start/api-request")({
	head: () => ({
		meta: [
			{
				title: "API Request Example",
			},
		],
	}),
	component: Home,
});

so far its working for me but i havent tested this in all cases.
is this correct guys? what do u guys think did i miss anything?

edit: added images

1 reply

DamianoMagrini Sep 9, 2025

Using staticData here limits this approach to the cases when the title is available synchronously. If a route's title relies on its loader data or other async ops, context can be used instead and should cover all cases.

maelp · 2025-09-02T22:44:27Z

maelp
Sep 2, 2025

I'm trying to follow https://tanstack.com/router/latest/docs/framework/react/guide/document-head-management but setting the head({ title}) in a route does not seem to work... I've included and , not sure what I'm missing?

2 replies

rhuanbarreto Sep 3, 2025

From docs:

First, remove the <title> tag from the the index.html if you have set any.

Did you do this?

michalmilek Sep 3, 2025

From docs:

First, remove the <title> tag from the the index.html if you have set any.

Did you do this?

no need propably(?), i had the same problem - you have to add HeadContent from tanstack router into RouterProvider

mirus-ua · 2025-09-04T13:30:10Z

mirus-ua
Sep 4, 2025

Hello
On the docs page https://tanstack.com/router/latest/docs/framework/react/guide/document-head-management#deduping I see a paragraph with this text

title tags defined in nested routes will override a title tag defined in a parent route (but you can compose them together, which is covered in a future section of this guide)

But not in that article or in the documentation, I can't find how to compose titles. Can you point me in the right direction? Or is this part not ready yet?

6 replies

mirus-ua Sep 4, 2025

Yes, but I want to compose the parent and child titles and not override

divyeshio Sep 4, 2025

@mirus-ua I suppose you may want to do this for breadcrumbs. Here's how you can do it:

const matches = useMatches();

  const breadcrumbs = matches
    .map((m) => ({
      title: m.meta?.at(0)?.name ?? m.meta?.at(0)?.title,
      link: m.pathname,
    }))
    .filter((x) => x.title);

Uh oh!

How to set html tag title from a route #1056

Uh oh!

Replies: 21 comments · 48 replies

Uh oh!

giacomorebonato Jan 22, 2024 Author

Uh oh!

Uh oh!

Uh oh!

tannerlinsley Jan 24, 2024 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

giacomorebonato Mar 11, 2024 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Replies: 21 comments 48 replies

giacomorebonato
Jan 22, 2024
Author

tannerlinsley
Jan 24, 2024
Maintainer

giacomorebonato
Mar 11, 2024
Author