<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>NetElixir Know How Archives - NetElixir</title>
	<atom:link href="https://stage.netelixir.com/tag/netelixir-know-how/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description></description>
	<lastBuildDate>Fri, 29 Sep 2023 05:51:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.4</generator>

<image>
	<url>https://stage.netelixir.com/wp-content/uploads/2021/05/cropped-x_icon_orange-32x32.png</url>
	<title>NetElixir Know How Archives - NetElixir</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Google&#8217;s Match Type Update Explained</title>
		<link>https://stage.netelixir.com/googles-match-type-update-explained/</link>
		
		<dc:creator><![CDATA[Phani Santhosh]]></dc:creator>
		<pubDate>Fri, 05 Feb 2021 15:58:17 +0000</pubDate>
				<category><![CDATA[Paid Search]]></category>
		<category><![CDATA[Google update]]></category>
		<category><![CDATA[Match Type]]></category>
		<category><![CDATA[NetElixir Know How]]></category>
		<guid isPermaLink="false">https://stage.netelixir.com//?p=9953</guid>

					<description><![CDATA[<p>Just yesterday, Google announced an update to the matching behavior of phrase and broad match modifier (BMM) keywords.  What The Match Type Update Means The change starts phasing out support for Broad Match Modifier. Most of the Broad Match Modifier traffic will be captured by Phrase Match going forward, while the remaining traffic will be [&#8230;]</p>
<p>The post <a href="https://stage.netelixir.com/googles-match-type-update-explained/">Google&#8217;s Match Type Update Explained</a> appeared first on <a href="https://stage.netelixir.com">NetElixir</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><span style="font-weight: 400;">Just yesterday, </span><a href="https://support.google.com/google-ads/answer/10346549"><span style="font-weight: 400;">Google</span></a><span style="font-weight: 400;"> announced an update to the matching behavior of phrase and broad match modifier (BMM) keywords. </span></p>
<h2><b>What The Match Type Update Means</b></h2>
<p><span style="font-weight: 400;">The change starts phasing out support for Broad Match Modifier. Most of the Broad Match Modifier traffic will be captured by Phrase Match going forward, while the remaining traffic will be mainly covered by Broad Match (we SEM managers sometimes call Pure Broad to keep the purpose separated from Broad Match Modifier).</span></p>
<p><span style="font-weight: 400;">Google says, “S</span><i><span style="font-weight: 400;">tarting mid-February, both phrase match and broad match modifier keywords will begin to transition to this new matching behavior. [ …] In July, once the new behavior has been rolled out globally, you’ll no longer be able to create new broad match modifier keywords.”</span></i></p>
<p><span style="font-weight: 400;">Below is a quick blurb from Google that helps us understand the change better:</span></p>
<figure id="attachment_9954" aria-describedby="caption-attachment-9954" style="width: 500px" class="wp-caption aligncenter"><img fetchpriority="high" decoding="async" class="wp-image-9954" src="https://stage.netelixir.com//wp-content/uploads/2021/02/Googles-Match-Type-Update-Explained-1024x536.png" alt="Google's Match Type Update Explained" width="500" height="262" srcset="https://stage.netelixir.com/wp-content/uploads/2021/02/Googles-Match-Type-Update-Explained-1024x536.png 1024w, https://stage.netelixir.com/wp-content/uploads/2021/02/Googles-Match-Type-Update-Explained-300x157.png 300w, https://stage.netelixir.com/wp-content/uploads/2021/02/Googles-Match-Type-Update-Explained-768x402.png 768w, https://stage.netelixir.com/wp-content/uploads/2021/02/Googles-Match-Type-Update-Explained.png 1200w" sizes="(max-width: 500px) 100vw, 500px" /><figcaption id="caption-attachment-9954" class="wp-caption-text"><em>Image from Google</em></figcaption></figure>
<p><span style="font-weight: 400;">So essentially, the order of words in the query matching a Phrase keyword will remain unchanged while some new words may find place between two subsequent words. </span></p>
<h2><b>Why Is Google Making This Change?</b></h2>
<p><span style="font-weight: 400;">The easy answer is ‘Simplicity’. According to Google, “<em>W</em></span><i><span style="font-weight: 400;">e’ve seen that phrase match and broad match modifier often serve the same use cases, and that you can reach more of the right customers through a combination of the two.”</span></i></p>
<p><span style="font-weight: 400;">The change will save time and efficiently streamline keyword management. Google has been making a lot of changes to get rid of complex account structure for a while now. Be it pushing for hybrid campaigns or using smart bidding for pure Broad, Google prefers simple campaign setups that are aligned with automated bidding solutions. </span></p>
<h2><b>“So, Why Do We Use Keywords”?</b></h2>
<p><span style="font-weight: 400;">Advertisers use keywords for reach, relevance, and performance. Based on feedback and data from past few years, Google understood that advertisers would not need multiple options to define an optimal keyword mix when smart bidding, as modern search features and audiences are taking care of better targeting. That’s why Google will now have the following keyword match types for simplicity’s sake: </span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Exact match for precision</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Broad match for reach</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Phrase match and broad match modifier for a balance of both</span></li>
</ul>
<h2><b>Customer Experience Is The Top Priority </b></h2>
<p><span style="font-weight: 400;">Google made an array of changes to all match types to prioritize the intent and semantic match over syntactic match (where words in queries have to match more closely with exact wordings in the keyword). Changes were made not just on the ads side, but on the SEO front as well, starting with Rankbrain and most recently BERT. Google cares about user experience and is the most popular search engine in the world for a reason. To continually improve a user’s experience, such changes are always in the works. Updates are purpose driven to ensure users are finding the most relevant results for their searches. </span></p>
<h2><b>Is This A Push For More Smart Bidding Coverage?</b></h2>
<p><span style="font-weight: 400;">Maybe Google wanted to reduce the liberty that advertisers had with using BMM over pure Broad. Advertisers were skeptical about pushing Pure Broad hard while keeping the targeting restricted using BMM. As a result, Google had to roll out Smart Bidding for a Broad Match. Google felt that adoption might remain low as long as advertisers have the option to use BMM over pure Broad. Smart Bidding with Broad will capture more contextual signals including Landing Page, other keywords in the ad groups, etc. to drive better returns. However, we recommend running some experiments before rolling out this bid strategy fully. </span></p>
<h2><b>Next Steps </b></h2>
<p><span style="font-weight: 400;">Google shared a host of </span><a href="https://support.google.com/google-ads/answer/10346549"><span style="font-weight: 400;">match type best practices here</span></a><span style="font-weight: 400;">. That said, NetElixir has also curated a few important next steps below:</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Stop using BMM match type for any new keyword.</span></li>
<li style="font-weight: 400;" aria-level="1"><b>Don’t</b><span style="font-weight: 400;"> change the match type of an existing keyword from BMM to Phrase. This would reset history. </span><i><span style="font-weight: 400;">Google will automatically apply the new behavior to BMM.</span></i></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Keep analyzing search queries to see what queries are now matching phrase matches over BMM. Add or negate queries accordingly. </span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Remove redundant keywords as suggested in the Recommendations tab.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Phrase matches are likely to see an increase in volume while BMM may see a drop. Adjust budgets accordingly. </span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">For tROAS/tCPA smart bidding, targets don’t need to be adjusted if your performance goals are the same. Spend may increase as the strategy drives more volume at your target CPA or ROAS. If you want to optimize within a daily budget instead, you can use Maximize Conversions or Maximize Conversion Value.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">For Max (conversions or conversion value) smart bidding strategies, increase the daily budgets to accommodate more volume if you see a spike. </span></li>
</ul>
<p><span style="font-weight: 400;">As always, NetElixir is here to help. If you have any questions about this update, please don’t hesitate to </span><a href="https://stage.netelixir.com//contactus/"><span style="font-weight: 400;">contact our experts</span></a><span style="font-weight: 400;">. </span></p>
<p>The post <a href="https://stage.netelixir.com/googles-match-type-update-explained/">Google&#8217;s Match Type Update Explained</a> appeared first on <a href="https://stage.netelixir.com">NetElixir</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
