Welcome to the Q&A Forum

There are no issues with targeting two different keywords to two different pages on your site. However in this case it seems to me that they are so closely related even synonymous, that targeting two different pages with what essentially is the same search intent but with a different keyprhase that you might have better luck only optimizing one page. That way any link equity is being directed towards one page rather than split between two. All on-page content would be completely unique rather than closely related to the other page, internal links would all be directed to one landing page etc....

From a user perspective I would think that when using either search they are looking for the same thing which is a Lawyer in Allen Texas who specializes in Social Security Disability. IMO I would optimize one page to meet both searches and then 301 redirect the other page to it.

Shaqd

I have done this, although I am not familiar with the canonical method you mentioned. Social share counts are tied directly to a URL so if the structure of a URL changes at all the old count will be attributed with the shares. You can create a custom social share button that pulls the data from the old pre  url structure change. Mike King has an awesome post about how to do that here (which is what I believe you are referring to with the og: url propterty?): http://searchenginewatch.com/article/2172926/How-to-Maintain-Social-Shares-After-a-Site-Migration 

You can read a thread where he and I discussed it here: http://moz.com/community/q/preserving-social-shares-through-url-changes

His method works.

We are making significant URL changes to our website. Because the URL is changing the social sharing buttons are not showing previous shared counts. I have read several resources like the one below that is linked to in several other similar questions.

http://searchenginewatch.com/article/2172926/How-to-Maintain-Social-Shares-After-a-Site-Migration

However I would love to get some insight from someone who has done this and there thoughts on the outcome. As an ecommerce site the "Social Proof" of products that have received social shares is a big deal to us.

In Mike Kings example above the counts are being attributed to the OLD URL which is problematic over time. Our site has been up for over 12 years and has had several major changes to it, and I am certain there will be more in the future, being able to preserve the count on the current URL is ideal. While I agree with him that over time I believe social platforms will let data pass through 301 redirects, until then I need to find the best way to do this.  Also with his example and others I have seen people mention than new likes from the new url can reset the counter. If you have gone through this and have ideas pleas share them. I look forward to your thoughts thanks.

You can make the bid adjustment by going into the ad group. Then select "settings" then "devices" you should see a box below that has three lines.

desktop

mobile

tablet

Look to the right of that box and you will see "bid adj" below that in the mobile column you will either have a dash - or a percentage +or- click that and make your bid adjustment accordingly

Hopefully that helps. .

Mike,

Thanks a ton for jumping in, I really appreciate it! I may have a hybrid solution using part of your suggestion.

We have toyed with the idea of creating a custom URL for each product (easy to automate on our end) that is tied to the product number. That way if the URL changes in the future (if we did an architecture redesign which will happen again I am sure) the share count will still be connected to the unique url so it will last over time. The URL that is shared just redirects to the product page just like if I was using a URL shortner. In testing we are having issues with Twitter being able to recognize this and increase the shared count number on the product page, even though shared count is recognizing it. So if we amended our code to call from the shared count API to pull the old numbers until passed by the new numbers like you suggested I believe it would give a very accurate result. Also moving forward url changes down the line would not affect the numbers because they are unique to the product number.

What are your thoughts on this? Do you see any pitfalls?