Welcome to the Q&A Forum

Nick -  Probably a dumb question but I want to confirm my understanding.   I know all search Volume metrics are estimates at best, but .... reporting a search volume from Bing as 100 searches/month is intended to represent actual searches on Bing, right?   Assuming Google gets 5-10 times more search volume depending on the keyword, in terms of actual volume a keyword If I see a kw that gets 100 searches on Bing, it might get 500+ on Google (just broadly estimating), correct? Just wanted to confirm that Moz doesn't adjust the Bing volume to account for their lower share of search, and normalize the numbers up to estimate the search volume across all search engines. Thanks! Mike

this might do it as well A flexible pattern URL mapping is a way of redirecting all URLs that match a particular pattern, to equivalent destination URLs, using a single mapping. It does this by allowing you to parse out and name portions of the requested URL to substitute into the destination URL. These types of URL mappings are useful when you are changing the structure or format of your URLs, but want to make sure you can redirect requests for pages under their old URL structure to their new URLs. An example of a flexible pattern URL is the following: /myblog/:post-year/:post-month/*rest-of-url?id=:post-id Each portion of the URL above that starts with a colon (:) creates a named component that is matched until the next delimiter character (./=&?), and any portion that starts with an asterisk (*) creates a named component that is matched until the end of the URL (up to the query string). The named components can then be used in the URL mapping's destination, with each name included inside of curly braces. For example, the named components defined in the flexible pattern URL above could be used to create the following destination: /newblog/{post-year}/{post-month}/post-{post-id}/{rest-of-url} To demonstrate how this flexible pattern URL mapping would work, let's consider the following example requested URL and where it would be redirected. The named components in the requested and destination URLs are highlighted. Requested URL: http://www.mydomain.com/myblog/2013/12/marketing/inbound-marketing-rocks?id=98765 Redirected to: http://www.mydomain.com/newblog/2013/12/post-98765/marketing/inbound-marketing-rocks With this pattern-based URL mapping we were able to retain all of the important, identifying parts of the original URL and insert them into the new URL structure. In addition, with this particular mapping, we were able to: capture the variable-length {rest-of-url} component (i.e. marketing/inbound-marketing-rocks) to be used in the destination url, by using an asterisk (*) at the beginning of that component's definition move the {post-id} component from the query string in the original URL into the middle of the URL in the destination

Thanks for your help Marie. I think I'll add the canonical tag to all the "About" pages leading to the original page like you said.