title: How to fix /wp/ redirect to /blog/ permalink
body: <p>I'm a new user and frankly, I haven't got a clue what I'm doing at this point. I'm figuring things out slowly but surely and this site has so far been a gold mine for me... So, let's see if we can make this work.</p>
  
  <p>So, my website has a WordPress installation within the root directory to allow me to have a blog; WordPress is installed solely for the blog and this is in the <code>public_html/wp</code> folder. Everything within the <code>wp</code> folder is WordPress.</p>
  
  <p>Now, when I write a post, the permalink is <code>my-website.co.uk/wp/post-title</code>.
  The <code>.htaccess</code> file rewrites this permalink to <code>my-website.co.uk/blog/post-title</code>.</p>
  
  <p>This is great, looks much better but the problem is, when WordPress auto-shares the posts, the <code>/wp/post-title</code> permalink redirects to homepage and not to the relevant blog post. This means, whenever someone clicks on the shared link, they're taken to my homepage (sorry if I sound like I'm dumbing it down).</p>
  
  <p>Now, in the <code>public_html</code> folder, I have one <code>.htaccess</code> file which is as follows</p>
  
  <pre><code>Options +FollowSymLinks -MultiViews
  RewriteEngine On
  RewriteBase /
  
  RewriteRule ^(.+?)/do-not-touch.php do-not-touch.php
  
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{DOCUMENT_ROOT}/$1.php -f
  RewriteRule ^(.+?)/?$ $1.php [L]
  
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{DOCUMENT_ROOT}/$1.htm -f
  RewriteRule ^(.+?)/?$ $1.htm [L]
  
  RewriteCond %{REQUEST_FILENAME}.php -f
  RewriteRule .*[^/]$ $0/ [L,R=301]
  
  RewriteRule ^blog/([0-9-]+)/?$ blog.php?page=$1
  RewriteRule ^blog/([A-Za-z0-9-]+)/?$ blog.php?slug=$1
  
  RedirectMatch 301 ^/tenants.htm /information-for-tenants.htm
  </code></pre>
  
  <p>Then, in the WP folder, we have another <code>.htaccess</code> file:</p>
  
  <pre><code>#+PHPVersion
  #="php70"
  AddHandler x-httpd-php70 .php
  #-PHPVersion
  
  # BEGIN WordPress
  &lt;IfModule mod_rewrite.c&gt;
  RewriteEngine On
  RewriteBase /wp/
  RewriteRule ^index\.php$ - [L]
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule . /wp/index.php [L]
  &lt;/IfModule&gt;
  
  # END WordPress
  </code></pre>
  
  <hr>
  
  <p>My theory (remember, I have no idea what I'm doing) is that the second <code>.htaccess</code> file redirects the <code>/wp/</code> permalinks up to the <code>public_html</code> file index (shown by the RewriteBase <code>/wp/ RewriteRule ^index\.php$</code> --- Not sure what the <code>\.php$</code> does) whilst the first <code>.htaccess</code> file rewrites the <code>/wp/post-title</code> to <code>/blog/post-title</code> (shown by <code>RewriteRule ^blog/([0-9-]+)/?$ blog.php?page=$1</code> and <code>RewriteRule ^blog/([A-Za-z0-9-]+)/?$ blog.php?slug=$1</code>).</p>
  
  <hr>
  
  <p><strong>Finally</strong>, in my WordPress admin permalink settings, the selected permalink is shown as <code>my-website.co.uk/wp/sample-post/</code>.
  All permalinks are <code>my-website.co.uk/wp/[customisable]</code> -- In other words, it doesn't allow me to alter the <code>/wp/</code> section of the permalink.</p>
  
  <p>I could really use some help. I need to redirect <code>wp/post-title</code> (whatever the title may be) to <code>blog/post-title</code> instead of <code>/index</code>.</p>
  
  <p>As a result of the redirect, search engines fail to crawl my blog posts (I think?).</p>
  
  <p>This is my website blog: <a href="https://www.harryalbertgroup.co.uk/blog" rel="nofollow noreferrer"><a href="https://www.harryalbertgroup.co.uk/blog" rel="nofollow noreferrer">https://www.harryalbertgroup.co.uk/blog</a> </a></p>
  
  <p>And this is the WP permalink: <a href="https://www.harryalbertgroup.co.uk/wp" rel="nofollow noreferrer"><a href="https://www.harryalbertgroup.co.uk/wp" rel="nofollow noreferrer">https://www.harryalbertgroup.co.uk/wp</a> </a> </p>
  
  <p>Thanks in advance.</p>
  
  <p>(Note: This website was built for me. I've been slowly fixing all of the issues I've faced so far. We're slowly getting there, it's really just the sharing features that I need to fix now, from what I can see)</p>