You could always setup a multi-site installation of WordPress and use the following plugin.

http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping

This should do what you're after, if it doesn't let me know and I can have a think about how we can sort this out for you.

You could always force a trailing slash using .htaccess even if someone visits the page without the end slash. Something like this might work, if it doesn't, let me know and I'll get something working for you.

<code>RewriteEngine  On  # Assuming you're running at domain root.  Change to working directory if needed.  RewriteBase  /   # www check  # If you're running in a subdirectory, then you'll need to add that in  # to the redirected url (http://www.mydomain.com/subdirectory/$1  RewriteCond  %{HTTP_HOST}  !^www\.  [NC]  RewriteRule  ^(.*)$ http://www.mydomain.com/$1 [R=301,L]  #  # Trailing slash check  # Don't fix direct file links  RewriteCond  %{REQUEST_FILENAME}  !-f RewriteCond  %{REQUEST_URI}  !(.*)/$ RewriteRule  ^(.*)$ $1/  [L,R=301]    # Finally, forward everything to your front-controller (index.php)  RewriteCond  %{REQUEST_FILENAME}  !-f RewriteCond  %{REQUEST_FILENAME}  !-d RewriteRule  .* index.php [QSA,L]</code>

Try using this instead:

<code>RewriteBase /</code> 

<code># remove .php; use THE_REQUEST to prevent infinite loops
RewriteCond %{HTTP_HOST} ^www.domain.com
RewriteCond %{THE_REQUEST} ^GET\ (.).php\ HTTP
RewriteRule (.).php$ $1 [R=301]

remove index

RewriteRule (.*)index$ $1 [R=301]

remove slash if not directory

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} /$
RewriteRule (.*)/ $1 [R=301]

add .php to access file, but don't redirect

RewriteCond %{REQUEST_FILENAME}.php -f
RewriteCond %{REQUEST_URI} !/$
RewriteRule (.*) $1.php [L]</code>

Just tried this on my development server and it worked fine:

RewriteBase / RewriteEngine on RewriteCond %{HTTP_HOST} ^test.local RewriteCond %{THE_REQUEST} ^GET\ (.).php\ HTTP RewriteRule (.).php$ $1 [R=301]

remove index RewriteRule (.*)index$ $1 [R=301]

remove slash if not directory RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_URI} /$ RewriteRule (.)/ $1 [R=301] # add .php to access file, but don't redirect RewriteCond %{REQUEST_FILENAME}.php -f RewriteCond %{REQUEST_URI} !/$RewriteRule (.) $1.php [L]

The dev URL is test.local so you would want to change this to www.yourdomain.co.ukI had a page called about.php if I entered http://test.local/about.php or http://test.local/about it would show http://test.local/about in the address bar

For you to use Site A as its own entity again I would suggest cancelling the 301 redirect as you've said, creating all the pages for Site A, making sure they're optimised on-page with good internal links to the other pages,

Once that's been done, generate an XML sitemap and submit that to Google, Bing, Yahoo etc

Then its just a waiting game for the search engines to update their index with the new pages on Site A.

Hi Cyrus,

Maybe I wasn't very clear in my previous comment; I know using website templates on multiple domains won't cause you to get a penalised by Google, but the article that was linked to said, Google has changed the algorithm to look at the layout of a web page and this didn't make sense to me.

This is why I mentioned changing your on-page optimisation to ensure you at least have different content on different domains that use the same template.

Slightly off topic, but I wanted to say that I thought your White Board Friday was really good (http://www.seomoz.org/blog/stop-optimizing-and-start-creating-whiteboard-friday), you covered a good topic and explained it really well.