Adding tags for SEO

[dennyabrain]

For every page or post that is published on our site, we must add relevant tags in the metadata for that post. We'll need to write some code so that gatsby puts those tags into the html head element so that search engine crawlers can index it.

The scope of this issue includes :

• Build the feature for taking tags from the markdown frontmatter and putting it in the html head element
• Add tags to all the existing content and verify if they are appearing in the published pages
• Documenting the process in the README for future contributors

[aatmanvaidya]

gatsby version 4.19.0 or higher is required to add SEO, else we will have to use plugins. - https://www.gatsbyjs.com/docs/how-to/adding-common-features/adding-seo-component/
https://www.digitalocean.com/community/tutorials/how-to-boost-seo-using-gatsby-s-seo-component-and-gatsby-react-helmet

[maanasb01]

Hello, are the tags to be included in the <meta name="keywords"> tag? I tried this issue and was able to include the tags for each blog post page in the <meta name="keywords"> tag. I created a Map for each slug and its tags and then added the keywords in the <meta name="keywords"> tag based on the page's slug. For the current page's slug, I am extracting it from the path coming from the useLocation hook (which was already being used in Seo.js ). I have done this for blog post pages only (as the path check was already being done for "/blog/", so I just extracted the slug from there for all blog posts). What other pages would require tags?

[dennyabrain]

@maanasb01 its ok to do it just for the blogs for now. Feel free to make a PR with your code.

[maanasb01]

@dennyabrain Upon further review of the code, I have determined that I wouldn't need to use the Map or the path name, as the SEO component already accepts meta props from the blog_layout component. Therefore, we only need to pass meta.tags. A similar approach can be applied to resolve the issue #26, where dynamic social cards are required. I am creating a PR for the issue. Should I include the changes for issue #26 in the same PR? Or create a separate one for that?

[dennyabrain]

One PR is good..just mention both in the PR to link them