We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug When NextSeo is used on a page, robotsProps from DefaultSeo is ignored.
NextSeo
robotsProps
DefaultSeo
Reproduction https://codesandbox.io/p/sandbox/garmeeh-next-seo-1134-jiv1kj
// _app.tsx import { DefaultSeo } from 'next-seo' import type { AppProps } from 'next/app' function MyApp({ Component, pageProps, router }: AppProps) { return ( <> <DefaultSeo robotsProps={{ noimageindex: true, noarchive: true, }} /> <Component {...pageProps} /> </> ) } export default MyApp
// index.tsx import type { NextPage } from 'next' import { NextSeo } from 'next-seo' const HomePage: NextPage = () => { return ( <> <NextSeo title="Home" /> <div>HomePage</div> </> ) } export default HomePage
Expected behavior
// Expected: <meta name="robots" content="index,follow,noarchive,noimageindex">
// Got: <meta name="robots" content="index,follow">
Additional context dangerouslySetAllPagesToNoIndex and dangerouslySetAllPagesToNoFollow are not affected.
dangerouslySetAllPagesToNoIndex
dangerouslySetAllPagesToNoFollow
The text was updated successfully, but these errors were encountered:
i have same problem
Sorry, something went wrong.
Same issue here as well. I've had to overwrite robotsProp at every page as the default setting isn't respected.
robotsProp
same issue
No branches or pull requests
Describe the bug
When
NextSeo
is used on a page,robotsProps
fromDefaultSeo
is ignored.Reproduction
https://codesandbox.io/p/sandbox/garmeeh-next-seo-1134-jiv1kj
Expected behavior
Additional context
dangerouslySetAllPagesToNoIndex
anddangerouslySetAllPagesToNoFollow
are not affected.The text was updated successfully, but these errors were encountered: