#community-help

Setting Canonical Links in Typesense Documentation

TLDR Jeremy suggested setting the default version to latest in typeSense. Dima proposed canonicalization and Jason confirmed its deployment.

4mo

Join the chat

Aug 09, 2023 (4 months ago)

Photo of md5-f19f9935c88f60757ce1890a15ee20ac

Jeremy

07:37 PM

Would be nice to have it default to the latest version of typesense

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:40 PM

We do want users to be able to access docs for older versions… so redirecting to latest version would prevent access to older versions.

We’ve tried setting page priority in sitemaps, but google doesn’t seem to care about these 😞

Jeremy

07:47 PM

Hah bummer. Having old documentation is very helpful, it just seems random which version google decides to send me to 😄

Photo of md5-1b62114a658b760944aa7d2b4c274460

Dima

08:13 PM

Maybe it’s a good idea to set up canonicalization for the latest version:
https://developers.google.com/search/docs/crawling-indexing/canonicalization

Jason

08:15 PM

I see, interesting! Thanks Dima. Will set this up

11:16

Jason

11:16 PM

Just deployed these canonical links 🤞

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3011 threads (79% resolved)

Join Our Community

Similar Threads

Suggested Improvement for Typesense 'Documents' Page

TJ suggested modification in Typesense documentation where clicking an updated version redirects to the same page, not the release page. Jason agreed and asked for a GitHub issue to track it.

4mo

Typesense version update leading to non-functional docs links

Jon reported an issue with the Typesense version update causing doc links to fail. Kishore Nallan clarified that docs are only published for GA releases, not RC versions.

17mo

Troubleshooting 400 Error When Upgrading Typesense Firestore Extension

Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.

14mo