Answers.Body: <p>Another way you could do this - that wouldn't be sustainable to expand later - is to create two landing pages as singles in Craft CMS.</p>
  <p>Then, create a new template for wherever you keep your header info (layout.twig usually) with all of the correct hreflang etc. in the header and include that layout template with the associated entry templates.</p>
  <p>Give these two templates a route such as domain.com/es/slug (you should be able to do this directly in the singles setup page within the CMS).</p>
  <p>This will create the effect you want, but without committing to a full multi-site. I emphasize again that this method does not scale well. But for an interim it should work fine. Remember to make your SEO values for these entries in the correct language. Best of luck!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-02T03:58:51.897Z
Answers.LastActivityDate: 2023-03-02T04:49:12.113Z
Answers.LastEditDate: 2023-03-02T04:49:12.113Z
Answers.UserDisplayName: cherrykoda
Answers.Body: <p>I would still recommend to create an additional site with a different language setting in Craft (Settings &gt; Sites).</p>
  <p>I recommend sharing one section between the 2 sites (pages?). Make sure, the propagation method is set to not automatically propagation entries to all sites. Make sure the fields that need to be translated are enabled for translations and that they are not automatically enabled.</p>
  <p>Then create the entries for your additional site/language by either creating new/standalone entries or create translations of existing entries.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-01T14:36:43.180Z
Answers.Text: Thanks for the response. This makes sense but also sounds like too much for something that may not last e.g. we try it then determine not to maintain it. So I know the tradeoffs, what would be the downside of creating a separate page, inserting hreflang (via an HTML field) and just keeping the language attribute as english?
Answers.UserDisplayName: Lee
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-02T14:44:03.457Z
Answers.Text: Nothing. Craft is flexible, so it would work. But what I described is a matter of minutes, so why go the wrong way…
Answers.UserDisplayName: Matthias Redl-Mann
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-02-28T07:22:24.793Z
Answers.LastActivityDate: 2023-02-28T07:22:24.793Z
Answers.UserDisplayName: Matthias Redl-Mann
Body: <p>Our team want to create one or two landing pages that are translated and localized e.g. Spanish and Portuguese</p>
  <p>This won't be a full site translation, so it doesn't deserve a subdomain or subfolder, just two pages.</p>
  <p>Looking at <a href="https://developers.google.com/search/docs/specialty/international/localized-versions" rel="nofollow noreferrer">best practices from Google</a>, and wondering are there Craft implementation best practices for:</p>
  <ol>
  <li>Defining hreflang</li>
  <li>Changing the HTML language attribute (so not lang=&quot;en&quot;)</li>
  </ol>
  <p>We are using SEOmatic in case that is useful info.</p>
  
Tags: <localization><language><plugin-seomatic><seo>
Title: How to handle a single page that is a different language?
ThreadText: # How to handle a single page that is a different language?
  
  (Asked by: username_0 on 2023-02-27)
  
  Our team want to create one or two landing pages that are translated and localized e.g. Spanish and Portuguese
  
  This won't be a full site translation, so it doesn't deserve a subdomain or subfolder, just two pages.
  
  Looking at [best practices from Google](https://developers.google.com/search/docs/specialty/international/localized-versions), and wondering are there Craft implementation best practices for:
  
  1. Defining hreflang
  2. Changing the HTML language attribute (so not lang="en")
  
  We are using SEOmatic in case that is useful info.
  
  **Tags:** localization, language, plugin-seomatic, seo
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2023-03-02. Score: 5
  
  Another way you could do this - that wouldn't be sustainable to expand later - is to create two landing pages as singles in Craft CMS.
  
  Then, create a new template for wherever you keep your header info (layout.twig usually) with all of the correct hreflang etc. in the header and include that layout template with the associated entry templates.
  
  Give these two templates a route such as domain.com/es/slug (you should be able to do this directly in the singles setup page within the CMS).
  
  This will create the effect you want, but without committing to a full multi-site. I emphasize again that this method does not scale well. But for an interim it should work fine. Remember to make your SEO values for these entries in the correct language. Best of luck!
  
  
  ---
  
  ### Answer by username_2 on 2023-02-28. Score: 1
  
  I would still recommend to create an additional site with a different language setting in Craft (Settings > Sites).
  
  I recommend sharing one section between the 2 sites (pages?). Make sure, the propagation method is set to not automatically propagation entries to all sites. Make sure the fields that need to be translated are enabled for translations and that they are not automatically enabled.
  
  Then create the entries for your additional site/language by either creating new/standalone entries or create translations of existing entries.
  
  > **Comments:**
  > **username_0**: Thanks for the response. This makes sense but also sounds like too much for something that may not last e.g. we try it then determine not to maintain it. So I know the tradeoffs, what would be the downside of creating a separate page, inserting hreflang (via an HTML field) and just keeping the language attribute as english?  
  > **username_2**: Nothing. Craft is flexible, so it would work. But what I described is a matter of minutes, so why go the wrong way…  
  
  ---
  
  