Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the genesis domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/darren/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/darren/public_html/wp-includes/functions.php:6114) in /home/darren/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":9412,"date":"2014-05-21T09:03:11","date_gmt":"2014-05-21T13:03:11","guid":{"rendered":"https:\/\/darrenslaughtercom.stage.site\/?p=9412"},"modified":"2014-05-21T09:03:11","modified_gmt":"2014-05-21T13:03:11","slug":"5-reasons-dont-think-contractors-use-exact-match-domain-names","status":"publish","type":"post","link":"https:\/\/darrenslaughter.com\/5-reasons-dont-think-contractors-use-exact-match-domain-names\/","title":{"rendered":"5 Reasons I Don’t Think Contractors Should Use Exact Match Domain Names"},"content":{"rendered":"

\"howIn setting up a new client, the conversation turned to domain names, and, should they register their company name or an exact match domain. If you aren’t sure what an exact match domain name is, it would look something like this:<\/p>\n

“www.philadelphiaplumber.com” or “www.bostonpaintingcontractor.com”<\/p><\/blockquote>\n

Now, back in the day you could go out and get an exact match domain name and hit the number one spot on Google for that keyword.<\/p>\n

Not anymore boys and girls!<\/strong><\/p>\n

Today, EMDs don\u2019t work unless they have other value tied to the site:<\/p>\n