Welcome to the Q&A Forum

Before doing that I would make absolutely sure the previous owner didn't do anything that'll bite you down the road... like buying a bunch of garbage links. Do you not want to run that site or do you just want to pull all the traffic they're getting to your site? I'm also curious how you know that site gets about 500 visitors per day; have you seen their analytics?

As long as the site looks clean, and you just want to buy their traffic I don't see why you can't 301 it into your site.

Ideally just take the snippet of code from the output that's highlighted (whatever structured data you needed), and edit the code on your site. What CMS are you working with? Are you building from HTML or are you using a CMS platform like WordPress/Drupal/Joomla? Without knowing your site limitations it's hart to answer this question.

It could hurt you in the long run (Google may decide the dev site is more relevant than your live site), but this is an easy fix. No-index your dev site. Just slap a site-wide noindex meta tag across all the pages, and when you're ready to move that code to the production site you remove that instance of code.

Disallowing from the robots.txt file will help, but that's a soft request. The best way to keep the dev site from being indexed is to use the noindex tag. Since it seems like you want to QA in a live environment that would prevent search engines from indexing the site, and still allow you to test in a production-like scenario.

Like Miriam mentioned - use the real number on citation sources and major offsite areas. The only ways I would suggest using a vanity number on your site is through javascript swapping (think CallRail phone tracking), or by using it in an image with the alt text being the real (non-vanity) number.

I would A/B test with the javascript method on your site. That solution would use a find & replace function depending on the click source (organic, direct, ppc, social, forum, etc), and swap in the tracking number/Vanity number. Test that for a while and compare phone call volumes. I think if you are a local business that would hurt NAP consistency, so that would need to be monitored pretty closely as well to make sure that vanity number doesn't cause damage.

I think BOTW is a good citation source, but if you can't get it for free the best thing to do is test. If you're thinking that site will be a valuable piece to your marketing (and deserve a piece of the budget), then test with the first location to see how much traffic it drives. Set up a special segment or filter in Google Analytics to track referrals from BOTW. If you're seeing some decent traffic for what you're paying (and possible conversions), then it's definitely worth expanding to. If you're just paying for the citation source then you might be better off sinking that monthly fee into paid search or somewhere else. I agree BOTW is a good local citation to have, but that's what I would do to try and justify spending money on it.

Take a look into tools like Places Scout or BrightLocal. Those have some pretty good Local (pack) reporting features which could help you solve this problem. The monthly plans aren't too expensive, so if you have a ton of keywords to check they could be viable options for you.

You don't need to. Just let Google crawl at will. The only reason you would want to limit the crawl rate is if you're having performance issues from the server you're on (too much traffic at once). If you're not having any issues, then allow Google to crawl as many pages as they can.

Like Jono mentioned, check your referral traffic. I would recommend going into your analytics account, and segmenting by all sessions/organic/referral/direct to really see what is causing the high bounce rate. If it's referral traffic it's most likely referral spam. There are some good tools out there and filters to help get rid of that garbage and true up your numbers a bit more.

If the previous site was penalized in any way and you're trying to start with a new domain, then you don't want to redirect or note a change of domain. This is going to help them update their index to reflect the new domain for your pages. I don't know enough about the penalty, but if it was a manual action then you really should fix the penalized domain before doing this. If you're too far into the penalty box, then you almost need to start fresh.

Can you offer any more insight on your current situation? Without knowing much more, my instinct is to say to not note a change of address if you're trying to move forward from a penalized domain.

What's the thought on using a 410 server response (Gone) for products that won't be in stock on the site anymore? I've seen that strategy work to get pages out of the index. Does anyone have opposition to using that strategy? That would be assuming the page isn't linked to on the site (or other sites for that matter). I've seen that work OK for product pages buried a littler further in the site architecture.