Welcome to the Q&A Forum

Hello! Were you able to fix it? To sum up the other answers, this could be a few things: a redirect in your .htaccess file a redirect in a plugin (yoast, or a separate redirects plugin - some plugins even create redirects automatically) or autogenerated by your theme/wordpress I would work in that order looking for it,

There's a really easy way to find out.  Type e-gig into google and then if the results have ecig in bold in the meta descriptions then google considers it to be the same word. This is HUGE for my niche which is dentistry.  I recently made an article about dental crowns and wondered should I call them dental 'caps' because it says in another of the tools I use that more people search for dental 'caps' than dental 'crowns'.  In fact they are slightly different things but lo and behold, google sees them as the same thing because there's caps in bold when I type crowns and crowns in bold when I type caps. Rankbrain is getting smarter and smarter and Gary from google I think released a video about punctuation and compound words.  So 'six year old', 'six-year-old' and '6 year-old' and '6-year old' are good ones to test it out on.  You can see what google thinks are the same.  Likewise using TM and R after words doesn't matter. So if you write an article for E-cig and then another for Ecig they are going to cannibalise or internally compete with one another.  I had the same problem with '6 month smiles' and 'six month smiles'.  The best solution is to use the words interchangeably and write at the level of your audience and write NATURALLY.  Google is getting really smart and you need to forget the semantics and get down to writing detailed and really readable content that people want to spend time reading. There are some great tools like 'Answer the public' and 'LSI graph' that can also help you find other words people are using.  they scrape from google so all the results are just what rankbrain and google is thinking right now.

IF they are sending considerable traffic that leads to conversions then there is a case for keeping them. I would however, also look into why your other domains are considered Spammy and try to rectify this also, that way you can still benefit from greater volumes of traffic, improve all your sites and hopefully grow stronger all around.

Thanks for your thoughts...I played it safe and changed it back to About with a 301.

It obviously depends on budget and needs. When you're a customer, you want options so you can make an informed decision.

The problem with removing these URLs is Google/Webmaster Tools doesn't read anything beyond the hash. Specifically - requesting that https://playon.co/#/?affiliate_token=04d234f75b1d74 be hidden removed from the index + cache is then processed simply as https://playon.co being removed. Again - https://playon.co is just a redirect, it is not the actual homepage. But will no-indexing https://playon.co prevent https://playon.co/en from ranking, which is the URL we need to be recognized as the homepage?

No problem - If you found this useful, I'd appreciate it if you could mark my answer as a 'Good Answer'

WooHoo I got it! I installed the custom post type plug in. Made a custom post type of personal injury Changed the custom post type slug to have dashes instead of underscores made a dummy post with the name whip its nitrous oxide

Hi CarlLSweet, I'm not sure what you are asking. We'd love to help you out, so please provide us with clarification. Thanks! Christy

Good news is that after I did the same tedious process myself, my SEO results went up!

The majority of the configuration needs to happen on the server hosting the main website, Alex. Because essentailly, the visitor isn't even going to be aware of the existence of/URL for the other infrastructure. They're going to go to example.com/blog, and example.com's server configuration is going to deliver them the content from someotherserver.com which hosts the WordPress install. In addition to the proxy configurations, you may need to deal with cookies, SSL configurations and potentially other server header information that needs to be maintained between the requests passing back and forth between the different servers as well. This is a pretty common requirement in enterprise configurations though - to keep the software running the blog from potentially interfering with or compromising the security of the main site infrastructure. So like I said - eminently do-able, but not trivial to implement. Does that answer your question? Paul

Thanks Andy - that was my first instinct. I've had a look around at some large sites such as Amazon etc for a little inspiration. As it wasn't something I've implemented before I wasn't sure if it would be bad practice.

Thanks for the follow up! There was also some indexing issues going on with google last week (pages were taking hours to get indexed, even using the fetch and render tool) so maybe this was somehow related. Glad it's resolved for now!

Hi Anthony, There's unfortunately no setting in Google Webmaster Tools for this. Your best bet is to use IP detection logic to either totally block (return an error status code and no content) or serve a simple "our content is not available in your country" error page to all requests from IP addresses in the UK. You can do this by building your own reference database or using a service - there's also some freeware). (FYI: anyone on a proxy network can get around this.) Google does use "locale-aware" crawling, including appearing to crawl from other countries than the US (most likely through a distributed computing network), and the UK is likely high on the priority list for that. Google should pick up on this over time and stop including your pages in search results. But it may not be immediate. Best, Mike