If you want to sell worldwide, I wouldn't use .london extension. This extension specifically tells Google (and buyers) that you are local to London. Sometimes I understand why Aussies or Americans would order from .co.uk but usually only if it's our last choice, honestly. So why would we order from a .london if there's ANY other choice?

You could run a .com or .net as your main domain and then run .london geotargeted to your UK audience. I think it's a mistake to use it globally.

You may want to try:

Quora

Reddit

And FaqFox, which does exactly what you asked for.

I don't do a ton of Bing ad work so this may be incorrect but the way I understand it is that you're selling the total number of ads that appeared (impressions.)

So if one search for wills returns 4 ads on the side, that's 1 search, 4 impressions.

Yours shows about 1 search per 3.1 impressions. That sounds like my understanding of this would be correct but again, this is my understanding. I'm not 100% sure.

Let's put it this way, if I owned Wordpress (or a smaller blog company) and it had two sites and one was going to get a penalty and the sites were:

http://mysite.wordpress.com

http://www.wordpress.com/mysite

I would want the subdomain penalised.  I don't think it's going to pass through to my main domain. I am nearly certain the subfolder will in 95% of cases.

@Patrick - I do agree with you but Wordpress is a very public example of tons & tons & TONS of spammy subdomains ranking just fine. I think the size of the subdomains is in proportion to their links so if a million subdomains are penalised, even on Wordpress.com, I think you'd see effect if there was going to be one.

While I do agree it's possible for them to affect you, I want you to think about an example.

Take the keyword "blog."  By itself, it's very, very competitive.

Somehow Wordpress.com ranks #3 for blog.

They do not rank for "create a free website" which is in their homepage title but they do rank for "create a free blog" #1.

Their results are all over the place. They have a huge number of spammy, low quality subdomains. Are the inconsistencies because of the difficulty of these terms? Maybe. The spammy subdomains? Maybe.

But I can't see Wordpress.com ranking for "blog" if the subdomains could pull you down.

Take this for example (Just one LITTLE piece of the spammy pie):

http://bit.ly/1O5AzDr

I know this question is answered already but my 2c based on what we've changed about our onsites.

If your brand name includes a main keyphrase, we typically don't include it on every page. You basically end up "competing" with yourself for that keyphrase. There's no point having:

Syracuse Wedding Photographers | MyCompany Photography

and using that brand bit on every single page. You're over-telling Google that the page is photo related. (Photographers in general have this issue but it applies to MyCompany Plumbing and MyCompany Iphone Repair too.)

Searching for indexed & duplicate content.  I put a line or two in quotes and Googled it.  I found most of the UTMs that way. Once you do that, it's a simple change to site:yoursite.com inurl:UTM

Strangely, browseo sees it correctly: http://www.browseo.net/?url=https%3A%2F%2Fplaceit.net%2F%3F_escaped_fragment_%3D%2Fstages%2Fsamsung-galaxy-note-friends-park

I'm not 100% sure why this is happening on your site specifically. Normally the #! isn't too big of an issue for cache but I've seen it have a few hiccups.  These pages seem to be indexed fine but they aren't generating cache.

I did find a few working but only those with UTM codes:

http://webcache.googleusercontent.com/search?q=cache:gRbYNNVyK18J:https://placeit.net/%23!/stages/office-by-the-window%3Futm_source%3Dblog%26utm_medium%3Dbanner%26utm_campaign%3Dbanner+&cd=1&hl=en&ct=clnk&gl=au

This doesn't look like it's working but view the source code - the content is actually there.  I found it by Googling the content in " marks.

Let's use a Wix example site (not a client, just a sample from their page) as my example. Say you wanted to check:

http://www.kingskolacheny.com/#!press/crr2

In the source code I see the escaped fragment URL.  This is the one you can find a cache for:

http://www.kingskolacheny.com/?escaped_fragment=press/crr2

That leads me to: http://webcache.googleusercontent.com/search?q=cache:http://www.kingskolacheny.com/?escaped_fragment=press/crr2

If your #! URLs are not setup this way, you will struggle to see it. One page websites are ... one page. But if you have escaped fragment URLs setup, you should be able to submit those and go from there.

The easiest way I know to find these is Screaming Frog, Ajax tab, Ugly URL field - try that one.

You will crawl some of the same URLs - that's why you remove duplicates at the end.  There's no way to keep it from re-crawling some of the URLs, as far as I know.

But yes, get it to recognize 600-800k URLs and then split the file.  (Export, put the links in as an html file and start over.) Let me break it down the best I can:

1. Crawl your main (seed) URL until you've recognized 800k.

2. Pause/stop and then export the results.

3. Create an html file with the URLs from the export - separated 50k to 100k at a time.

4. Recrawl those files in Xenu with the "file" option.

5. Build them back up to 800k or so recognized URLs again and repeat.

After a few (4-6) iterations of this, you'll have most URLs crawled on most sites no matter how large.  Doing it this way, I think you could expect to crawl about 2-3 million URLs a day.  If you really paid attention to it and created smaller files but ran them more frequently, you could get 4-5 million, I think.  I've crawled close to that in a day for a scrape once.

Let Xenu crawl until you have about 800k links.  Then export the file and add it back as 8 x 100k lists of URLs.  You can then run it again and repeat the process.  By the time you have split it 4-5 times, you can then export everything, put it into one file and remove duplicates.

Xenu, done this way, with 100 threads, is probably the fastest way to do the whole thing. I think you could get the 5M results in under 1 day of work this way.