Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property autoptimizeCompatibility::$conf is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCompatibility.php on line 18

Deprecated: Creation of dynamic property autoptimizeCriticalCSSCore::$criticalcss is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCriticalCSSCore.php on line 20

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property Smush\Core\Modules::$webp is deprecated in /home/swalsh/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 109

Deprecated: Creation of dynamic property Jetpack_Publicize::$modules is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Publicize\Publicize_UI::$in_jetpack is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 101

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/swalsh/public_html/wp-includes/Requests/Transport/cURL.php on line 345

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758
{"id":6176122015,"date":"2012-04-04T12:22:40","date_gmt":"2012-04-04T12:22:40","guid":{"rendered":"http:\/\/digital-football.com\/?p=6176122015"},"modified":"2012-04-04T12:22:40","modified_gmt":"2012-04-04T12:22:40","slug":"football-clubs-and-blogger-outreach-where-is-it","status":"publish","type":"post","link":"http:\/\/digital-football.com\/featured\/football-clubs-and-blogger-outreach-where-is-it\/","title":{"rendered":"Football Clubs and Blogger Outreach. Where is it?"},"content":{"rendered":"

Football Social Media has come a long way in the past 18 months in terms of fan engagement, player policy and stadium social media. However, one area of social media forgotten about by football clubs is blogger outreach.<\/p>\n

Blogger outreach is a tactic used by brands on social media to identify key bloggers who are influential around a certain subjects. Brands aim to build a relationship with them over time with the end product usual being a piece of content generation that shows the brand in a positive light.<\/p>\n

What is blogger outreach?<\/h3>\n

For example, imagine you own a restaurant and want to generate some social media coverage in order to build awareness. What you might do is identify bloggers who have shown interest and expertise in the food industry. Ideally, you would want a blogger who you know to be active, influential and happy to cover the event. You also would want an individual whose blog is well read so you can increase the chances of people learning about your restaurant. Once you’ve identified a number of bloggers (because more is better) then you “reach out” to them and invite them to the launch event. The blogger gets a free meal or access to something they may never have got in exchange for agreeing to write some social media content up afterwards. But be warned, if the event\/service isn’t up to their expectations – they won’t always write just nice things. Blogger outreach isn’t a bribe, it’s a chance to impress and make your mark on the social media world.<\/p>\n

Where does football fit in?<\/h3>\n

It strikes me that football clubs have loads of “events” in which bloggers would be interested in covering:<\/p>\n