Answers.Body: <p>That would probably be the Propagation Method setting in the channel´s settings. There you can choose "Only save entries to the site they were created in" (among other options). The thing is not your template path, but that the entry is stored to both sites (which is useful for, say, two sites that are just different language versions of the same site, and should have the same content).</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-12T13:09:47.007Z
Answers.Text: Yes the channels are not an issue, the singles are
Answers.UserDisplayName: Lukigi
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-15T00:00:09.473Z
Answers.Text: There’s the site settings on the single, isn’t it? With radio buttons for which sites it should be available in?
Answers.UserDisplayName: KSP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-20T14:36:59.523Z
Answers.Text: There is but, I can still get to the singles by using template name, which for me is usually the same as the page slug. Going through all singles and prefixing their template names with "_"  solved this, but I would still expect the routing to ignore templates from other site folders.
Answers.UserDisplayName: Lukigi
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-20T16:31:36.930Z
Answers.Text: Ah, okay. Then I'm a bit at a loss, I totally agree that a single that isn't available for a certain site shouldn't be available (unless specifically fetched programmatically or similar)
Answers.UserDisplayName: KSP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-11T19:32:31.490Z
Answers.LastActivityDate: 2020-01-11T19:32:31.490Z
Answers.UserDisplayName: KSP
Body: <p>I have just crated a multi site according to the instructions on Crafts page.
  Lets just say I have:</p>
  
  <ul>
  <li>siteone.com with template forlder templates/siteone </li>
  <li>sitetwo.com with template forlder templates/sittwo</li>
  </ul>
  
  <p>It all works fine however all templates from templates/siteone can also be accessed on sitetwo by simply going to sitetwo.com/siteone/site-one-only-template</p>
  
  <p>Is there a way to prevent that?</p>
  
  <hr>
  
  <p>I've went through all the pages and added "_" to the template filename, then updated template paths of each single to reflect that. This now works as expected, however what's the point of site specific template folder if it's still routed to by other sites?</p>
  
Tags: <multi-site><multi-domain>
Title: Is there a way to avoid content duplication on multi site setup?
ThreadText: # Is there a way to avoid content duplication on multi site setup?
  
  (Asked by: username_0 on 2020-01-10)
  
  I have just crated a multi site according to the instructions on Crafts page.
  Lets just say I have:
  
  * siteone.com with template forlder templates/siteone
  * sitetwo.com with template forlder templates/sittwo
  
  It all works fine however all templates from templates/siteone can also be accessed on sitetwo by simply going to sitetwo.com/siteone/site-one-only-template
  
  Is there a way to prevent that?
  
  ---
  
  I've went through all the pages and added "\_" to the template filename, then updated template paths of each single to reflect that. This now works as expected, however what's the point of site specific template folder if it's still routed to by other sites?
  
  **Tags:** multi-site, multi-domain
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-01-11. Score: 1
  
  That would probably be the Propagation Method setting in the channel´s settings. There you can choose "Only save entries to the site they were created in" (among other options). The thing is not your template path, but that the entry is stored to both sites (which is useful for, say, two sites that are just different language versions of the same site, and should have the same content).
  
  > **Comments:**
  > **username_0**: Yes the channels are not an issue, the singles are  
  > **username_1**: There’s the site settings on the single, isn’t it? With radio buttons for which sites it should be available in?  
  > **username_0**: There is but, I can still get to the singles by using template name, which for me is usually the same as the page slug. Going through all singles and prefixing their template names with "_"  solved this, but I would still expect the routing to ignore templates from other site folders.  
  > **username_1**: Ah, okay. Then I'm a bit at a loss, I totally agree that a single that isn't available for a certain site shouldn't be available (unless specifically fetched programmatically or similar)  
  
  ---
  
  