Prompt

Why is my headless CMS API returning empty fields for linked entries?

Technology / Developer Tools1 observationLast seen Oct 21, 2026

Latest observation

Oct 21, 2026OpenAI APIWeb search: off

This usually happens because the API is returning links/reference stubs, not the full linked entry data.

Common causes:

  1. You didn’t request link expansion / population

    • Many headless CMSs return linked entries as IDs or minimal link objects unless you explicitly “expand,” “include,” or “populate” them.
    • Examples:
      • Contentful: use include=1..N
      • Strapi: use populate=* or specific populate paths
      • Sanity: use GROQ projections to dereference
      • DatoCMS: query nested fields explicitly
  2. The linked entry is unpublished or not accessible

    • If the linked item isn’t published, or your token/role can’t read it, the API may omit it or return partial/empty data.
  3. The fields in the linked entry are empty or restricted

    • The entry may exist, but the linked fields you expect are blank, localized differently, or hidden by permissions.
  4. You’re hitting a depth limit

    • Some CMSs only resolve links up to a certain nesting level. Deeper linked entries may come back as empty references.
  5. Wrong query shape

    • If you’re using GraphQL or a projection-based API, you must explicitly select the fields inside the linked object. Otherwise you’ll only get the reference metadata.
  6. Localization / draft mode mismatch

    • You may be requesting a locale where the linked entry has no content, or querying draft content without the correct preview endpoint/token.

What to check

  • Inspect the raw API response: does it contain a link object, ID, or null?
  • Confirm you’re using the CMS’s expand/populate/include option.
  • Verify the linked entry is published and readable.
  • Check locale, preview, and permission settings.
  • Make sure your query explicitly asks for the nested fields.

If you tell me which CMS you’re using and paste a sample query/response, I can point to the exact fix.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.