3 thoughts on “SEO Optimization For Tridion Based Websites: Part I

  1. Thanks for sharing, Nitesh. I like the setup and descriptive field names for editors. I’d also include in the description that this is for Web page metadata.

    Be careful, though, for multi-lingual BluePrint setups. By placing this content in the Page Metadata, it means localized pages in a translated Publication will no longer inherit shared Component Presentations. This isn’t an issue for companies without many Publications (like in the US), but can be painful for editors manage pages across dozens of languages (and secondary languages).

    Consider managing these fields in Component’s instead as we discuss in this post:

    See links to Tridion Strategist, which has some great advice on minimizing localization.


    1. Thanks Alvin for this insight. And Yes, in our case we are using that 2nd Approach , as discussed in your tridionstackexchange post, thereby localizing only when needed.

      However, most of the countries want to use their own localized / local language texts specially when sharing their pages on Facebook/Google+ and the 2nd Approach of Global content really doesn’t helps much in this case.

      my second post, Part 2 ( coming Soon ) was actually meant for all complexities like this :)


  2. Lovely and a beautiful concept illustrated so nicely. I like the way you organized the steps. It was so easy to follow and understand the concepts and technical implementation.

    keep sharing such very basics of tridion. Good Day!!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s