Viewing 4 replies - 1 through 4 (of 4 total)
  • If you just want someone typing https://www.example.com to end up at https://www.example.com/content you can use .htaccess

    For example:

    RewriteEngine on
    RewriteCond %{REQUEST_URI} ^/$
    RewriteRule (.*) /mysubfolder/ [R=301]
    Thread Starter prwood

    (@prwood)

    @aestheticdesign – Thanks for the reply. I don’t want to 301 redirect the user to /content, I actually want to serve the homepage from /. All other content on the site would be served from /content/*.

    Is it important that when they are on the home page the URL is https://www.mydomain.com or just that when they type https://www.mydomain.com they get the home page even if the url is redirected to https://www.mydomain.com/content/?

    Personally, I’d structure it so that everything was in the root directory for SEO and usability purposes.

    I’m curious what your reason is for wanting the website to be in a /content subdirectory?

    Thread Starter prwood

    (@prwood)

    It’s important that users are not redirected to /content/ when they go to /. We are serving additional content outside of WordPress using other applications under other subdirectories, and so rather than putting all of WordPress right at the document root, we want to restrict WordPress to handling only requests for content under /content/, with the exception that ‘/’ should also be handled by WordPress.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Serve WordPress homepage from site root, rest of content from /content?’ is closed to new replies.