> ## Documentation Index
> Fetch the complete documentation index at: https://cloro.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Discussions and forums schema

> Schema for the threads of Google's Discussions and forums block returned by the Google Search endpoint: title, link, source, the line under it and the answers shown when a thread is opened.

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) returns the threads of Google's "Discussions and forums" block (Reddit, Quora, Facebook groups and other forums) as `result.discussionsAndForums`, on desktop and mobile, with no flag and at no extra cost. `discussionsAndForums` is omitted when the SERP has no Discussions and forums block.

![Discussions and forums in Google Search](https://mintcdn.com/cloro/evVAQXmFf6gSfz60/images/google/search-discussions-and-forums.webp?fit=max\&auto=format\&n=evVAQXmFf6gSfz60\&q=85\&s=ad97e2fff9f8af3f6f2d054a2de7989b)

Discussions and forums in Google Search

Each thread carries the answers Google shows when the thread is opened, for open and closed threads alike. Google opens only the first thread; `expanded` says which one is open.

The block's "See more" link opens Google's Forums tab, a separate search, and is not followed. Google can cite the same post in the "What people are saying" block too; it is then in both `result.peopleAreSaying` and `result.discussionsAndForums`.

## Discussions and forums structure

| Field | Type | Description |
| - | - | - |
| `items` | array | The threads, in page order. See below |

### Thread

`position`, `title`, `link` and `expanded` are always present. `source`, `extensions`, `answers` and `redirectLink` are included only when Google shows them.

| Field | Type | Description |
| - | - | - |
| `position` | number | Position within the block (1-indexed) |
| `title` | string | Title of the thread as shown |
| `link` | string | URL of the thread |
| `source` | string | Site of the thread as shown ("Reddit", "Quora", "Facebook") |
| `extensions` | string\[] | The line under the source, as shown, in page order. See below |
| `expanded` | boolean | Whether the page shows the thread open |
| `answers` | array | What Google shows when the thread is opened, in page order. See [Answer](#answer) |
| `redirectLink` | string | Google's `/goto` redirect for `link`. See [Redirect links](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto.md). |

### Extensions

The line under the source usually holds the community, the number of comments or answers and the date (`["r/reactjs", "120+ comments", "3 years ago"]`). Google leaves out each item it has no value for, and the page does not label them, so an item's place in the list does not tell what it is: `["30+ answers", "2 years ago"]`, `["r/smartphone_specs_edu", "1 year ago"]` and `["2 months ago"]` are all possible. The items keep the language and the format of the SERP (`"3y"` on mobile).

### Answer

Google shows the top answers of the thread, or, when it has none to show, one excerpt of the thread. Google cuts long text with "...".

| Field | Type | Description |
| - | - | - |
| `snippet` | string | The text of the answer, or the excerpt of the thread, as shown |
| `topAnswer` | boolean | `true` when Google labels the answer "Top answer". Omitted otherwise |
| `extensions` | string\[] | The line under the answer, as shown (`["236 votes", "3 years ago"]`). Omitted when there is none |

## Response example

A response to `react vs vue`, on desktop:

```json theme={null}
{
  "success": true,
  "result": {
    "discussionsAndForums": {
      "items": [
        {
          "position": 1,
          "title": "What does React do better than Vue innately (excluding things like ...",
          "link": "https://www.reddit.com/r/reactjs/comments/10u17c7/what_does_react_do_better_than_vue_innately/",
          "source": "Reddit",
          "extensions": ["r/reactjs", "120+ comments", "3 years ago"],
          "expanded": true,
          "answers": [
            {
              "snippet": "Vastly superior TypeScript support Much smaller API surface No native event emitting makes ...",
              "topAnswer": true,
              "extensions": ["236 votes", "3 years ago"]
            },
            {
              "snippet": "It’s more likely to get you a job",
              "extensions": ["46 votes", "3 years ago"]
            },
            {
              "snippet": "Job market is mostly React. React has much more active community and user, as a result libraries ...",
              "extensions": ["40 votes", "3 years ago"]
            }
          ]
        },
        {
          "position": 2,
          "title": "Why do people use Vue.js instead of React.js?",
          "link": "https://www.quora.com/Why-do-people-use-Vue-js-instead-of-React-js",
          "source": "Quora",
          "extensions": ["30+ answers", "2 years ago"],
          "expanded": false,
          "answers": [
            {
              "snippet": "Vue.js is formatted like Angular.js and it has an amazing components system, good data management and is faster than React Web. It's perfect for ..."
            }
          ]
        }
      ]
    }
  }
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.