![\"\"/](\"https://avatars2.githubusercontent.com/u/1160934?v=4?s=100\")
Ifiok Jr.
💻 📖
![\"\"/](\"https://avatars0.githubusercontent.com/u/52423?v=4?s=100\")
Harlley Oliveira
🐛
![\"\"/](\"https://avatars.githubusercontent.com/u/5944305?v=4?s=100\")
Joel Gibson
💻 📖 ⚠️
Simple Usage
\n \n);\n```\n\nBut `GatsbySeo` gives you many more options that you can add. See below for a typical example for any given gatsby layout.\n\n**Typical page example:**\n\n```tsx\nimport React, { FC } from 'react';\nimport { GatsbySeo } from 'gatsby-plugin-next-seo';\n\nconst Layout: FC = ({ children }) => (\n <>\nThis page is no indexed
\n \n);\n\n/*\n\n\n*/\n```\n\n#### dangerouslySetAllPagesToNoIndex\n\nIt has the prefix of `dangerously` because it will `noindex` all pages. As this is an SEO plugin, that is kinda dangerous action. It is **not** bad to use this, just please be sure you want to `noindex` **EVERY** page. You can still override this at a page level if you have a use case to `index` a page. This can be done by setting `noindex: false`.\n\n#### No Follow\n\nSetting this to `true` will set `index,nofollow` (to set `noindex`, please refer to [`noindex`](#noIndex)). This works on a page by page basis. This property works in tandem with the `noindex` property and together they populate the `robots` and `googlebot` meta tags.\n\n**Note:** The `noindex` and the [`nofollow`](#noFollow) properties are a little different than all the others in the sense that setting them as a default does not work as expected. This is due to the fact Gatsby SEO already has a default of `index,follow` because `gatsby-plugin-next-seo` is a SEO plugin after all. So if you want to globally these properties, please see [dangerouslySetAllPagesToNoIndex](#dangerouslySetAllPagesToNoIndex) and [dangerouslySetAllPagesToNoFollow](#dangerouslySetAllPagesToNoFollow).\n\n**Example No Follow on a single page:**\n\nIf you have a single page that you want no indexed you can achieve this by:\n\n```tsx\nimport React from 'react';\nimport { GatsbySeo } from 'gatsby-plugin-next-seo';\n\nexport default () => (\n <>\nThis page is not followed
\n \n);\n\n/*\n\n\n*/\n```\n\n#### dangerouslySetAllPagesToNoFollow\n\nIt has the prefix of `dangerously` because it will `nofollow` all pages. As this is an SEO plugin, that is kinda dangerous action. It is **not** bad to use this, just please be sure you want to `nofollow` **EVERY** page. You can still override this at a page level if you have a use case to `follow` a page. This can be done by setting `nofollow: false`.\n\n| `noindex` | `nofollow` | `meta` content of `robots`, `googlebot` |\n| --------- | ---------- | --------------------------------------- |\n| -- | -- | `index,follow` (default) |\n| false | false | `index,follow` |\n| true | -- | `noindex,follow` |\n| true | false | `noindex,follow` |\n| -- | true | `index,nofollow` |\n| false | true | `index,nofollow` |\n| true | true | `noindex,nofollow` |\n\n#### Twitter\n\nTwitter will read the `og:title`, `og:image` and `og:description` tags for their card, this is why `gatsby-plugin-next-seo` omits `twitter:title`, `twitter:image` and `twitter:description` so not to duplicate.\n\nSome tools may report this an error. See [Issue #14](https://github.com/garmeeh/gatsby-plugin-next-seo/issues/14)\n\n#### facebook\n\n```tsx\nfacebook={{\n appId: 1234567890,\n}}\n```\n\nAdd this to your SEO config to include the fb:app_id meta if you need to enable Facebook insights for your site. Information regarding this can be found in facebook's [documentation](https://developers.facebook.com/docs/sharing/webmasters/)\n\n#### Canonical URL\n\nAdd this on a page per page basis when you want to consolidate duplicate URLs.\n\n```js\ncanonical = 'https://www.canonical.ie/';\n```\n\n#### Alternate\n\nThis link relation is used to indicate a relation between a desktop and a mobile website to search engines.\n\nExample:\n\n```tsx\nmobileAlternate={{\n media: 'only screen and (max-width: 640px)',\n href: 'https://m.canonical.ie',\n}}\n```\n\n```tsx\nlanguageAlternates={[\n {\n hrefLang: 'de-AT',\n href: 'https://www.canonical.ie/de',\n },\n {\n hrefLang: 'es',\n href: 'https://www.canonical.ie/es',\n}\n]}\n```\n\n#### HTML Attributes\n\nAdd html attributes to the html tag with the `htmlAttributes` prop.\n\nExample:\n\n```tsx\nhtmlAttributes={{\n prefix: \"og: https://ogp.me/ns#\",\n}}\n```\n\n#### Meta Tags\n\nThis allows you to add any other meta tags that are not covered in the `config`.\n\n`content` is required. Then either `name` or `property`. (Only one on each)\n\nExample:\n\n```js\nmetaTags={[{\n property: 'dc:creator',\n content: 'Jane Doe'\n}, {\n name: 'application-name',\n content: 'GatsbySeo'\n}]}\n```\n\nInvalid Examples:\n\nThese are invalid as they contain `property` and `name` on the same entry.\n\n```js\nmetaTags={[{\n property: 'dc:creator',\n name: 'dc:creator',\n content: 'Jane Doe'\n}, {\n property: 'application-name',\n name: 'application-name',\n content: 'GatsbySeo'\n}]}\n```\n\n## Open Graph\n\nFor the full specification please check out [the documentation](http://ogp.me/).\n\nGatsby SEO currently supports:\n\n- [basic](#basic)\n- [video](#video)\n- [article](#article)\n- [book](#book)\n- [profile](#profile)\n\n### Open Graph Examples\n\n#### Basic Example\n\n```tsx\nimport React from 'react';\nimport { GatsbySeo } from 'gatsby-plugin-next-seo';\n\nexport default () => (\n <>\nBasic
\n \n);\n```\n\n#### Video Example\n\nFull info on [http://ogp.me/](http://ogp.me/#type_video)\n\n```tsx\nimport React from 'react';\nimport { GatsbySeo } from 'gatsby-plugin-next-seo';\n\nexport default () => (\n <>\nArticle
\n \n);\n```\n\n#### Book Example\n\n```tsx\nimport React from 'react';\nimport { GatsbySeo } from 'gatsby-plugin-next-seo';\n\nexport default () => (\n <>\nBook
\n \n);\n```\n\n#### Profile Example\n\n```tsx\nimport React from 'react';\nimport { GatsbySeo } from 'gatsby-plugin-next-seo';\n\nexport default () => (\n <>\nProfile
\n \n);\n```\n\n## JSON-LD\n\nGatsby SEO has the ability to set JSON-LD a form of structured data. Structured data is a standardised format for providing information about a page and classifying the page content.\n\nGoogle has excellent documentation on JSON-LD -> [HERE](https://developers.google.com/search/docs/data-types/article)\n\n- [Override](#override)\n- [Article](#article)\n- [News Article](#news-article)\n- [Blog Post](#blog-post)\n- [Breadcrumb](#breadcrumb)\n- [Blog](#blog)\n- [Book](#book)\n- [Speakable](#speakable)\n- [Course](#course)\n- [FAQ](#faq)\n- [Corporate Contact (Deprecated)](#corporate-contact-deprecated)\n- [Local Business](#local-business)\n- [Logo](#logo)\n- [Product](#product)\n- [Social Profile (Deprecated)](#social-profile-deprecated)\n- [JsonLd](#jsonld)\n- [Sitelinks Search Box](#sitelinks-search-box)\n\n### Override\n\nEach (non-deprecated) JSON LD component provides a set of utility props to help you in the journey of setting up your your site for Search Engine Optimization and voice assistant support. However there are times when you will need more control, and for these situations there is an `overrides` prop available which allows you to manually override the schema type.\n\nThe following example would add a `datePublished` property to the JSON LD head script produced.\n\n```tsx\nconst OverrideCourseJsonLd = () => (\nStand
\n\nEffort
\n\nPeace
\n \n);\n```\n\n| Property | Type | Description |\n| -------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------- |\n| [questions](#question-interface) |Question[] | An array of Question elements which comprise the list of answered questions that this FAQPage is about. |\n\n#### Question Interface\n\nThe questions and answers for an FAQ Page.\n\n| Property | Type | Description |\n| ------------------------------------------------------------------------------------------------------------------------------ | ------------------- | ----------------------------------------------------------------------------------------- |\n| [answer](https://github.com/ifiokjr/gatsby-plugin-next-seo/blob/master/docs/api/gatsby-plugin-next-seo.question.answer.md) | string | The answer to the question. There must be one answer per question. |\n| [question](https://github.com/ifiokjr/gatsby-plugin-next-seo/blob/master/docs/api/gatsby-plugin-next-seo.question.question.md) | string | The full text of the question. For example, \"How long does it take to process a refund?\". |\n\n### Course\n\n```tsx\nimport React from 'react';\nimport { CourseJsonLd } from 'gatsby-plugin-next-seo';\n\nexport default () => (\n <>\n Ifiok Jr. 💻 📖 | \n Harlley Oliveira 🐛 | \n Joel Gibson 💻 📖 ⚠️ | \n