WordPress.org

Ready to get started?Download WordPress

Forums

Multi-site setup & content filtering question (4 posts)

  1. ThatPaull
    Member
    Posted 2 years ago #

    Having sifted through the various posts related to multi-site setups, I'm still not 100% sure what the best approach for my scenario is. I just want to make sure I'm following best-practices and not setting myself up for trouble.

    The task at hand is setting up a multi-site for 2 different domains, one that contains content that is not-safe-for-work (NSFW), and one that has no NSFW content. All other content is identical. I see 2 different ways to do this...

    example 1:
    myDomain.xxx contains all content. myDomain.com has all NSFW content filtered out.

    or,

    example 2:
    myDomain.com has all the basic content, but myDomain.xxx has additional NSFW content added.

    My questions are: is there any reason to choose one example over the other? If we want to have links for the NSFW content on the .com site that would click-through (after a warning alert or age prompt), would that change anything? Is there an easy way (via categories or tags, etc...) to filter content out, or is it just easier to add the NSFW content only on the .xxx domain, and pull all the other .com content over. Furthermore, is there any reason to choose either the .com or .xxx domain to be the MS install location, or does it not really matter? Are there any other pitfalls I should be aware of?

    TIA for any suggestions/advice.

  2. Either way, you don't actually want to duplicate your data.

    If there are just two domains, I'd probably grab the WordPress MU sitewide tags plugin and do this:

    1) domain.xxx as the MAIN domain. Activate it as the 'tags' site in sitewide tags. Have it collect all the posts.

    2) domain.com as a sub site.

    Any posts that are SFW will be posted on both xxx and com, BUT will link back to .com (to avoid tanking your SEO).

  3. ThatPaull
    Member
    Posted 2 years ago #

    Thanks for the quick reply.

    Correct, the whole idea is to avoid any content duplication.

    Your suggestion seems pretty straightforward. It also begs the question, what happens when they want to include other (targeted) .xxx domains? I can see that as being a likely scenario...

    e.g.
    domain(sfw).com & domain(all NSFW content).xxx + domain2(straight).xxx + domain3(gay).xxx + domain4(lesbian).xxx etc...

    Apologies for all the .xxx references, etc... but this is an actual project I have to deal with.

  4. S'okay :) I've worked in the industry before, a job is what it is.

    domain.xxx would ... curate all the content. Gay, straight, safe for work, nsfw. But the specialized content would remain on the specialized domain.

    There wouldn't be links back to domain.com, obviously, but if you're going to be running domain2gay.xxx and domain2gay.com, you may want to use a MultiNETWORK plugin as well.

    So domain.xxx pulls posts from domain.com, and then domain2gay.xxx pulls from domain2gay.com and so on.

Topic Closed

This topic has been closed to new replies.

About this Topic