Removing canonicalisation on a site with Gatsby and Netlify

How can we remove canonicalisation on a site? Is there any global setting for this?

Let’s keep the conversation in this thread! 🙌

I think what is getting at is that this is probably something that has to do with how Gatsby or the hosting provider (Netlify?) deals with URLs

Since server forces trailing slash, we’ll go along with that

I just want to find out how to remove canonicalisation

Could it be that the default setup of Gatsby forces non-trailing slash urls and canonicalises the ones with trailing slash?

This is a bit hard to say without knowing your implementation of Gatsby (it's not something that comes from Sanity). But my educated guess is that there is a

<link rel="canonical" ...>

tag inserted on these pages? There is plugins for Gatsby that let you control this, for example https://www.gatsbyjs.org/packages/gatsby-plugin-react-helmet-canonical-urls/

Thanks, I’ll check out the plugin

Normally, all the links have canonical element and they canonicalise to themselves by default (at least on all the other platforms/cms’es that I worked with), but for some reason, in this case they were pointing to another version of url, and that’s what I am trying to kill 🙂

were you able to get this resolved? I didn't know exactly would could be causing it but it made more sense to me that it was coming from Gatsby rather then Sanity. If you did find a fix I would love to hear more about it if possible.

Not yet, waiting for one developer to take a look into it. Will keep you posted.

Thank you so much. The other thing that could be an issue is an outdated site map. I am sure someone checked that though. I had a heck of a time with Google Tag Manager integration with Gatsby I am happy to share that fix if you would like too. Might help you down the road.

Here is the Tag Manager Integration I followed and was able to get it working. https://medium.com/nadjib-benna%C3%AF/integrate-google-tag-manager-to-a-gatsby-js-project-2dab4606749f

Thank you, we’ll look into it!

Oh last thing too. If you happen to use Netlify like we do this is how you go about it there. I saw you mention you had another host but it's worth mentioning if you are using this service for the build https://docs.netlify.com/routing/redirects/redirect-options/#http-status-codes

Yes, we do use Netlify

Thanks again, your advice is highly appreciated!