Build a SERP Content Gap Report with Rankings and Missing Topics

#api #python #automation #seo

A content gap report is more useful when it shows what is missing, where the evidence came from, and which URLs are already ranking.

A keyword list alone cannot do that. A ranking position alone cannot do that either. To make the report actionable, you need the SERP context around the query: titles, URLs, snippets, domains, and the topics competitors appear to cover.

This walkthrough shows a small pattern for building a SERP content gap report with TalorData SERP API.

What the report should answer

The first version should answer five questions:

Which pages rank for the query?
Which domains appear repeatedly?
What topics are visible in titles and snippets?
What topics are missing from our target page?
Which gaps are worth reviewing for a content update?

This is not a full content strategy platform. It is a structured research output that can support a human review.

Request the SERP data

Use the SERP API endpoint with a safe token placeholder in examples:

curl -X POST 'https://serpapi.talordata.net/serp/v1/request' \
  -H 'Authorization: Bearer <TALORDATA_TOKEN>' \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d 'engine=google' \
  -d 'q=serp api content gap analysis' \
  -d 'num=10' \
  -d 'json=2'

The first field to inspect is organic.

Normalize organic results

A compact result row is easier to compare than a full response.

from urllib.parse import urlparse


def domain_from_url(url: str | None) -> str | None:
    if not url:
        return None
    return urlparse(url).netloc.replace("www.", "")


def normalize_organic(query: str, data: dict) -> list[dict]:
    rows = []

    for item in data.get("organic", []):
        link = item.get("link")
        rows.append(
            {
                "query": query,
                "position": item.get("position"),
                "title": item.get("title"),
                "url": link,
                "domain": domain_from_url(link),
                "snippet": item.get("description"),
            }
        )

    return rows

This gives the report a consistent base.

Add simple topic extraction

You do not need a complex NLP system for the first pass. Start with a controlled list of expected topics.

TOPICS = [
    "pricing",
    "api documentation",
    "integration",
    "examples",
    "accuracy",
    "locations",
    "ai overview",
    "people also ask",
]


def covered_topics(text: str) -> list[str]:
    lower = text.lower()
    return [topic for topic in TOPICS if topic in lower]

Apply it to the title and snippet:

def add_topic_coverage(rows: list[dict]) -> list[dict]:
    enriched = []

    for row in rows:
        text = f"{row.get('title') or ''} {row.get('snippet') or ''}"
        enriched.append(
            {
                **row,
                "visible_topics": covered_topics(text),
            }
        )

    return enriched

This is intentionally simple. It creates a reviewable first report instead of a black-box score.

Compare against your target page

The report becomes useful when you compare SERP patterns with your own page.

Create a target page record:

target_page = {
    "url": "https://example.com/serp-api",
    "covered_topics": ["pricing", "api documentation", "examples"],
}

Then compute missing topics:

def report_missing_topics(rows: list[dict], target_topics: list[str]) -> list[str]:
    serp_topics = set()

    for row in rows:
        serp_topics.update(row.get("visible_topics", []))

    return sorted(serp_topics - set(target_topics))

This creates a concrete review item: topics competitors visibly cover that your target page may not.

Create the report rows

A minimal report can include:

query
position
domain
url
title
visible_topics
gap_note

Example row:

{
  "query": "serp api content gap analysis",
  "position": 3,
  "domain": "example.com",
  "url": "https://example.com/page",
  "title": "SERP API Guide",
  "visible_topics": ["pricing", "examples"],
  "gap_note": "Competitor page visibly covers examples. Review whether target page covers this clearly."
}