Segmentation for Meta Tags on Landing Pages

[Anonymous]

You can segment landing pages with language for example. However this is not possible for the meta title. This poses some issue for us. It would be great to have this option too.

[Anonymous]

This would be so so helpful. Has anybody found any workarounds?

[SanfordWhiteman]

Is your goal to change the <TITLE> tag (not actually a meta tag) for human-facing purposes, i.e. after visiting the page? Or for SEO, i.e. crawling the page?

[Anonymous]

Hi. We have landing pages segmented by language. Goal is to change the <TITLE> and <META> data including OG markup for SEO and social, i.e. this need to be what the search engine or social media platform scrapes.

[SanfordWhiteman]

OK. First, I think there's some misunderstanding about how segmented LPs look to crawlers.

• Standard auto-segmented pages have exactly the same URL and change their displayed elements based on the lead associated with the current Munchkin cookie.  Crawlers will not generate associated Munchkin cookies so they would not generate the non-default segments. Nor would you want to (from the crawler's perspective) completely swap out content at the same URL.
• Tokenized LPs links (with mkt_tok) are self-associating but are only present in personalized emails. And you do not want them anywhere else, ever!
• Hard-segmented pages have the segment coded in the URL, like http://landing.example.com/lp1.html?lang=en-us.  This functionality is not used in most cases but certainly can be.

So it's only the third option that has any applicability to SEO.  As explained here the Googlebot wants to see <LINK hreflang=> meta tags on all your localized pages pointing to other localized variants.  You can segment these parts of your page using a Guided LP Template.

[Anonymous]

Thanks Sanford. Yes, it's the third option that's relevant. Here's an example landing page (in English):

http://info2.filemaker.com/state_of_the_custom_app_lp.html

And here's the same page with the language set to German:

http://info2.filemaker.com/state_of_the_custom_app_lp.html?language=de

As you can see the language is forced in the URL as is your third example but the <TITLE> and <META> data is not changed because Marketo does not allow this to be segmented. Or, are you saying this is possible through the Guided LP Template?

[SanfordWhiteman]

As you can see the language is forced in the URL as is your third example but the <TITLE> and <META> data is not changed because Marketo does not allow this to be segmented. Or, are you saying this is possible through the Guided LP Template?

Yes, that is exactly what I am saying.  And ​you should include <LINK hreflang=...> tags that point to all ​the language-specific variations (those tags don't need to be segmented, they just need to represent all the segments).