LogoLogo
Nimble HomeLoginCreate an Account
  • Home
  • Quick Start Tutorials
    • Tutorial Library
      • Track SEO and SEM Ranking
      • Reddit as a Guerilla Marketing Strategy
  • Nimble Platform
    • Nimble Platform Overview
    • Online Pipelines
      • Supermarkets
        • ASDA
        • Tesco Groceries
        • Sainsbury’s
        • Morrisons
      • eCommerce
      • Restaurants
        • Yelp
        • Tabelog
        • Uber Eats Japan
        • Demaecan
        • Uber Eats US
      • Real Estate
        • Zillow
  • Nimble SDK
    • SDK Overview
    • Web API
      • Web API Overview
      • API Product Specs
      • Nimble Web API Quick Start Guide
        • Introduction
        • Nimble APIs Authentication
        • Real-time URL request
        • Delivery methods
        • Batch processing
        • Response codes
        • FAQs
      • Nimble Web API Functions
        • Realtime, Async & Batch Request
        • Geo Location Targeting
        • Javascript Rendering
        • Page Interaction
          • Wait (delay)
          • Wait for Selector
          • Wait and Click
          • Wait and Type
          • Scroll
          • Scroll to
          • Infinite Scrolling
          • Capturing Screenshots
          • Collecting Cookies
          • Executing HTTP Requests
          • Operation Reference
        • Network Capture
          • Filter by URL Matching
          • Filter By Resource Type
            • Real World Demo: Capturing Ajax Requests
          • Wait for Requests
          • Capturing XHR without Rendering
          • Operation Reference
        • Data Parsing
          • Parsing Templates
          • Merge Dynamic Parser
        • Custom Headers & Cookies
        • General Params
      • Vertical Endpoints
        • SERP API
          • Real-time search request
          • Getting local data
          • Browsing SERP pagination
          • Delivery methods
          • Batch Processing
          • Endpoints and Response Codes
        • Maps API
          • Searching for places
          • Getting information about a place
          • Collecting reviews
          • Delivery methods
          • Batch processing
          • Endpoints and Response Codes
    • Web Retrieval API
      • Web Retrieval API Overview
    • Proxy API
      • Nimble IP Overview
      • Nimble IP Quick Start Guide
        • Send a request
        • Nimble IP Autentication
        • Geotargeting and session control
        • Response codes
        • FAQs
      • Nimble IP Functions
        • Country/state/city geotargeting
        • Controlling IP rotation
        • Geo-sessions: longer, stickier, more accurate sessions
        • Using IPv6 Proxies
        • Response Codes
      • Integration Guides
        • Incogniton
        • Kameleo
        • VMLogin
        • AdsPower
        • FoxyProxy
        • Android
        • Multilogin
        • iOS
        • SwitchyOmega
        • Windows
        • macOS
        • Proxifier
        • MuLogin
        • Puppeteer
        • Selenium
        • Scrapy
    • Client Libraries
      • Installation
      • Quick Start
    • LangChain Integration
  • Technologies
    • Browserless Drivers
      • API Driver-Based Pricing
    • IP Optimization Models
    • AI Parsing Skills
  • Management Tools
    • Nimble Dashboard
      • Exploring the User Dashboard
      • Managing Pipelines
      • Reporting and Analytics
      • Account Settings
      • Experimenting with the Playground
      • Billing and history
    • Nimble Admin API
      • Admin API basics
      • Admin API reference
  • General
    • Onboarding Guide
      • Getting started with Nimble's User Dashboard
      • Nimble IP Basics
      • Nimble API Basics
      • Helpful Resources
    • FAQs
      • Account Settings and Security
      • Billing and Pricing
      • Tools and Integrations
      • Nimble API
      • Nimble IP
    • Deprecated APIs
      • E-commerce API
        • E-commerce API Authentication
        • Real-time product request
        • Real-time product search request
        • Delivery methods
        • Batch Processing
        • Endpoints and Response Codes
      • Unlocker Proxy Overview
        • Unlocker Proxy Quick Start Guide
          • Real-time request
          • FAQs
        • Unlocker Proxy FAQ
Powered by GitBook
On this page
  • Explore new markets using SERP API
  • Reddit as a guerrilla marketing strategy
  • How To: Leverage Nimble’s SERP API for finding relevant search results
  1. Quick Start Tutorials
  2. Tutorial Library

Reddit as a Guerilla Marketing Strategy

PreviousTrack SEO and SEM RankingNextNimble Platform Overview

Last updated 7 months ago

Explore new markets using SERP API

Search is the biggest software business in the world. Online businesses rely on Search Engines Results Page for discoverability and community building, fighting over the prime real estate which is above-the-fold (or at least on the first page) of a given search result.

In the past year, in their search results which created an enormous opportunity for businesses and marketers in reaching potential customers by tapping into popular, high visibility threads.

Reddit as a guerrilla marketing strategy

Reddit with its endless lists of sub-reddits has always been a home to passionate communities and can be a powerful tool for niche marketing. In this post we’ll try to build a simple marketing play, harnessing Reddit’s existing SEO prowess in Google search results.

Here’s how this strategy works:

  1. Search Google for your business’ relevant keywords

  2. Find the top Reddit posts in Google search results

  3. Interact with those posts (i.e., comment with your product/service, find relevant leads, etc.)

In short, leveraging Reddit’s existing SEO for relevant posts to boost your product without the legwork of trying to reach the top results page with your original content.

Nimble’s SERP API can help with automating this process and quickly churn out top Reddit posts with the highest impact.

Read ahead for the gory details of how to leverage SERP API for automatic, localised search results:

How To: Leverage Nimble’s SERP API for finding relevant search results

The SERP API expects a couple of parameters:

query - this is the keyword or term you’d like to track

search_engine - the engine you’d like to test in. For obvious reasons, we’ll go with google_search but Bing and Yandex are also available for the search engines purists

A big advantage of the SERP API being built on top of the extensive Nimble proxy network is the option to specify a country and locale for keywords that target only specific markets.

As an example, let’s go with searching for recommendations for a calendar app.

The SERP API parameters:

query: calendar app recommendations

country: US

locale: en

curl -X POST '<https://api.webit.live/api/v1/realtime/serp>' \\
-H 'Authorization: Basic <auth_credentials>' \\
-H 'Content-Type: application/json' \\
--data-raw '{
"parse": true,
"query": "calendar app recommendation",
"search_engine": "google_search",
"format": "json",
"render": true,
"country": "US",
"locale": "en"
}'

Result: An active Reddit post came up 3rd in the OrganicResult API response.

There are also several other related posts from other sub-reddits the API returns which we can capture and visit.

Top Reddit result:

Other related results

Google has been promoting Reddit pages
more aggressively
https://www.reddit.com/r/ios/comments/197kwxt/whats_everyones_preferred_calendar_app/
https://www.reddit.com/r/productivity/comments/10999vx/whats_your_favourite_app_that_can_work_as_a/
https://www.reddit.com/r/productivity/comments/10v4d3w/best_calendartodo_app/
https://www.reddit.com/r/androidapps/comments/16n7dba/what_you_consider_to_be_the_best_calendar_app/
https://www.reddit.com/r/mac/comments/1aw14ff/recommendations_for_a_better_calendar_app/