Welcome to the Q&A Forum

This is not rich snippet. This is title manipulation.

If you look their HTML code their title is as:
<title>Bitstamp - buy and sell bitcoins</title>

But if you load page you will see:
($price)Bitstamp...

In javascript they have codes as:
var page_title = 'Bitstamp - buy and sell bitcoins';
$('head title').html('($'+loc_num($('span.live_price').attr('price'))+') '+page_title);
this code is responsible for updating price in title. Seems that Google index this and store modified title in their index.

Here is official documentation of Rich Snippets:
https://developers.google.com/structured-data/rich-snippets/
and there isn't anything closer to you. Probably you can use only reviews.

Could be AppAnnie, SensorTower, AppMind, Apptamin. But they're not free.

I think that free tool doesn't exist because tracking require servers, special infrastructure and reporting.

I report this last night to mods and in Twitter. Before 12 hours...

@EGOL - check whois of both domains and you will see that same person hold both domains.

Poor man linkbuilding...

I understand your fears completely because WP + themes + plugins can be HUGE mess.

Why? Because some of devs don't know technical and on-page SEO. I have seen themes where they put text "Comments" within H1 tag. At same time post title was encapsulated with H3. Things as hidden text, messy HTML codes, bloatware HTML are countless. You also can get server overloading, slow SQL queries and some issues. Can be performance issues, PHP issues, hosting issues. Running WP mean that you will get 10 CSS files and 10 JS libraries. And this is "best case scenario". Just imagine what is worst. Now add "upgrading" procedure where everything can be broken (or changed!) with just one click. Ah, and mine favorite - security exploits and hacking. Sound like "perfect storm". Isn't?

Now i know that this sound scary. That's why you should see and review HTML code of WP before migration. Probably you will see potential for improvements. And this changes need to be patched over original files (i'm talking about theme or plugins). For theme is OK - you can make child theme based on original. But for plugins - you need to "fork" original plugin and make your own custom version. Then on each update you should "diff" your version and original to keep your patches and new code. This mean very strong backup solution plus local dev environment and extra work on each update.

Also - it's year of 2016. Why you don't around for alternatives? I can give you suggestion - static site generators:
https://www.smashingmagazine.com/2015/11/modern-static-website-generators-next-big-thing/
https://www.smashingmagazine.com/2015/11/static-website-generators-jekyll-middleman-roots-hugo-review/

As you can see i'm not giving answer Yes or No. I'm just giving you few extra points to think about. Just put cards on the table.

PS: May sound negative little bit because i have some theme and plugins in past. One wrong choice and all SEO efforts can be ruined. Such is life...

Glossary:
"fork" - process of creating different version of something existing with some changes that doesn't exist in original. You can hear that devs are forking projects too. In your case - since you can apply your patches but on next update everything will be gone back to original. That's why you need to fork them.
"diff" - process for checking difference between files/project and extracting/showing only difference between them.

Yes.

Disavow needed for each site (http/https).

You can use Google PageSpeed Insights:
https://developers.google.com/speed/pagespeed/insights/

And if your site is on WordPress then you can install this plugin:
https://wordpress.org/plugins/google-pagespeed-insights/

You also can use WebPageTest, GTMetrix, Pingdom Tools. Even one simply *nix tool as wget can make local mirror to site where you can see filesizes (command is wget -r -m http://m.domain.com/au ).

Alternative you can use desktop crawlers (like mine SEOSpyder) where you can see also images size in bytes.

If they are not your - it's better to disavow them. If they are spammy - disavow them.

Those links may hurt your ranking.

Skeleton have JS to NOT include sticky menu on mobile. But was nice example about mine idea and first that i remember quick during writing this comment.

Second idea is sticky menu with "Hamburger_icon Gallery Partners Price" for mobile and normal (just as now) for desktop. This probably can skip confusing users about menu and hierarchical structure of your website.

But as i said - A/B testing is needed.

Dirk, Q&A section is missing but they (Mods + community dept + Moz staff) actively track all activity here.

Same here. I reading Moz since 2007 but, make mine account somewhere in 2011 and start contributing here in 2015. So all mine points was in last year.

I'm preparing now small script for tracking all activity in 2016 in Top 1000 users maybe

And this is the point where you clearly can see that RWD (responsive web design) isn't "one-size-fit-all" solution.

You have few choices but all are weird - double menu, hamburger + kebap menu, sticky menu on left, etc. But as i said this is weird. And only A/B test can show how they works.

I think that best in your case is to try sticky menu on top. One of best example is here:
http://getskeleton.com/
but you need to watch this on desktop. When you scroll down you can see that "Intro Code Examples More" is sticky on top. In your site you need to make changes to "Gallery Partners Pricing". This menu can be sticky even for desktop. This will bring more size in width for main content.

As i said - only A/B test can show who's right. Because all double menus have better navigation but in reality confuses user with "paradox of choice".

301 can take weeks or months dependent how large is your website. With site move this happen for days. And site move have "undo" function.

If your "bad" link is like http://OURDOMAIN/flibzy/foto-bugil-di-kelas.html then your .htaccess should be:
Redirect 410 /flibzy/foto-bugil-di-kelas.html
that's all.

Yes - you should do this for ALL 1205 URLs. Don't do this on legal pages (before hacking), just on hacked pages. I say "gone" with 410 redirect. It's amazing. In your case gone for good. Time for identify that 1205 URLs and paste them into .htaccess is let's say X hours. Time for identify that 1205 URLs and temporary remove them is Y hours. Since "temporary removal" is up to 30 days this make same job each month. In total for one year you have X in first case and 12*Y in second case. You can see difference, right?

Also today Barry Adams release story about hacking:
http://www.stateofdigital.com/website-hacked-manual-penalty-google/
and it's amazing that site was hacked just for 4 hours but Google notice this. You can see there traffic drop and removal from SERP. Ok, i'm not trying to "fear sells", but keeping bad pages with 404 will take long time. In Jan-Feb 2012 i have new temporary site on mine site within /us/ folder and even today Jan 2016 i still receiving bots crawling this folder. That's why i nuke it with 410. This save the day!

On your case it's same. Bot is wasting time and resources to crawl 404 pages over and over but crawling less your important pages. That's why it's good to nuke them. ONLY them. This will save bot crawling budget on your website. So bot can focus on your pages.

The best is to keep them 404. But fast is to 410 them.

All you need is to place this topmost somewhere of .htaccess:
Redirect 410 /dir/url1/
Redirect 410 /dir/url2/
Redirect 410 /dir1/url3/
Redirect 410 /dir1/url4/

But this won't help you if your URLs have parameters somewhere like index.php?spamword1-blah-blah. For this you need extended version like this:
RewriteEngine on
#RewriteBase /
RewriteCond %{QUERY_STRING} spamword
RewriteRule ^(.)$ /404.html? [R=410,L]
RewriteCond %{QUERY_STRING} spamword1
RewriteRule ^(.)$ /404.html? [R=410,L]
RewriteCond %{QUERY_STRING} spamword2
RewriteRule ^(.*)$ /404.html? [R=410,L]

So why 410? 410 act much faster than 404 but it's DANGEROUS! If you sent 410 to normal URL this is effective nuking it. I found that with 410 bot visit this url 1-2-3 times, but with 404 bot keep visiting over and over eating your crawling budget. URL removal in SearchConsole is OK, but it's fast but works only for 30 days. And will eat almost same time as building list for 404/410s. Hint: You can speedup crawling if you do "fetch and render" then submit to index.

You can redirect non-www to www or vice versa with .htaccess.

#Force www:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301,NC]

or

#Force non-www:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.example.com [NC]
RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

BUT - you are using Sucuri that make JS redirector against Bots. This is killing for SEO/SMM efforts.

Yes - there is bug in your robots.txt. You should wrote some as:
Disallow: /?display=table
or:
Disallow: /?display=*

Hey - i just found that we can "scrape" historical MozPoints using their profile pages:
https://moz.com/community/users/397332
if you view source this you can see "var mozpoints_data" with JSON inside.

I can scrape all historical points for Top1000 for example starting from 2015-11-01 so you can built even better sheet.

You are using Sucuri for protecting your WordPress. And they using JavaScript redirectors as you can see it.

IT's much better to disable such redirectors because they simply kill all your SEO/SMM efforts.

Google released "core update" on 8 and 15:
http://mozcast.com/
https://algoroo.com/
http://serp.watch/

Lot of SEO (including in Moz) trying to catch what's changed. This isn't Panda or Penguin.

Yes - there is turbulence now in SERP:
http://mozcast.com/
https://algoroo.com/
http://serp.watch/

According to Google this was "core update".