@Boulter and HubSpot Dev team: This is really troubling. HubSpot took major steps forward in accommodating SEOs in the last two years, fixing speed, SSL, editing of XML sitemap, etc. but rolling HubDB out without accounting for meta description is not merely a little oversight, it's borderline incompetence.
Google will use the meta description provided in 90% of cases, in our experience. Google seeks clean, unique, structured data (just like Open Graph and Schema.org) Failure to account for this really needs to be addressed ASAP.
Moz has this to say on the matter:
"Meta descriptions can however impact a page's CTR (click-through-rate) on Google which can positively impact a page's ability to rank. For that reason, among others, it's important to put some effort into meta descriptions."
What you've effectively done here -- by not accounting for meta description -- is create a system that encourages DUPLICATE META DESCRIPTIONS by forcing one meta description PER TEMPLATE -- and not descriptions that are unique to the individual pages HubDB is so adept at creating -- and he's what Moz says about that issue:
" Avoid duplicate meta description tags
As with title tags, it's important that meta descriptions on each page be unique. Otherwise, you'll end up with SERP results that look like (repetitive and not helpful)... One way to combat duplicate meta descriptions is to implement a dynamic and programmatic way to create unique meta descriptions for automated pages. If possible, though, there's no substitute for an original description that you write for each page."
Please address this ASAP.
-David Carpenter for Connection Model