# Onsite Widgets (Classic)

{% hint style="warning" %}
You are reading the **Classic Widget Documentation**

Classic widgets are a previous widget version for onsite widgets created before September 23rd.

From September 23rd 2025, all new widgets created will be NextGen.

Please check your widget version on the **Widget List page** to see if it is **Classic** or **NextGen** widget.

You can read the [Nextgen widget documentation here](/ugc/guides/widgets-nextgen.md).
{% endhint %}

## Overview

Nosto's UGC widgets have been developed to provide a variety of key features that make them the best choice for displaying content on a web page. Used by 90% of clients. Serving 16 million requests a day.

## Usage

**Key Features**

* Speed & flexibility of development within the Stackla platform.
* Easy customization of CSS and JS.
* Access to a powerful internal [JavaScript API](/ugc/api-docs/javascript.md).
* Optimized responsive display.
* Built-in content freshness detection.
* Speed and robustness of content delivery.
* Produces simple and reusable HTML embed code.
* Extensible with maps and direct upload widgets.
* Dynamic content request options using filters and tags.
* Customizable content polling frequency.
* No API rate limits.
* Advanced features such as Product highlights and Likes.
* Reporting on tile and widget performance via Google Analytics.
* Tile recommendation data to help make moderation easier.

**Designed for**

* Displaying content on websites and browser-based apps.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nosto.com/ugc/guides/onsite-widgets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.