## 🗂️ Overview

When creating content in Search Atlas, two settings often raise questions: **Article/Content Length** and **metadata description fields** such as the OG Description. This article defines each content length option, helps you choose the right one for your site, and explains how to work with Open Graph and other social metadata fields — including how to generate descriptions using AI.



## 📏 What Each Content Length Option Means

Search Atlas offers three content length settings. Each targets a different word-count range and suits a different content goal.

- **Short** — Approximately 300–600 words. Best for simple, focused pages where brevity is the priority: FAQs, product descriptions, landing page copy, or local service pages where users need a quick answer. Use *Short* when you want lean content that loads fast and stays on-point without padding.
- **Optimized (Medium)** — Approximately 800–1,200 words. The most versatile setting. It balances depth with readability and suits most standard blog posts, service pages, and informational articles. Choose *Optimized* when you need solid topical coverage without committing to a long-form piece.
- **Long-Form** — Approximately 1,500–2,500+ words. Designed for comprehensive guides, pillar pages, in-depth comparisons, and topics where search engines reward thorough coverage. Use *Long-Form* when your target keyword is competitive and depth is a ranking factor.

## 🎯 Choosing a Content Length for Your Site (Galserv Example)

The right content length depends on three things: the intent behind the target keyword, the competitive landscape, and the purpose of the page.

For a site like **Galserv** — a local or service-based business — the following guidance applies:

- If the page targets a **local service keyword** (e.g., "galvanising services in Manchester"), start with **Short** or **Optimized**. Local searchers want quick answers, and thin but precise content often outperforms padded long-form for local intent.
- If the page is a **service explainer or comparison** (e.g., "hot-dip galvanising vs. electroplating"), choose **Optimized** to give enough depth to answer the question fully.
- If the page is a **pillar resource or industry guide**, use **Long-Form** to compete with established informational content.

When in doubt, check the top-ranking pages for your target keyword and match their average content depth. Search Atlas Rank Tracker and Keyword Magic tools (accessible via **Left sidebar → Site Metrics → Rank Tracker** or **Left sidebar → Keywords → Keyword Magic**) can help you assess competition before choosing a length.



## 🌐 What Is an OG Description?

An **OG Description** (Open Graph Description) is a metadata field that controls how your page appears when shared on social platforms such as Facebook, LinkedIn, and WhatsApp. It is part of the **Open Graph protocol** — a set of HTML meta tags that social networks read to generate link previews.

Specifically, it maps to the `og:description` meta tag in your page's HTML. When someone shares your URL, the platform pulls this field to display a short summary beneath the page title in the preview card.

- **Recommended length:** 120–160 characters.
- **Purpose:** Increase click-through from social shares by displaying a compelling, relevant summary.
- **Note:** The OG Description is separate from your SEO meta description, though the two are often similar in content.

## 🐦 What Is twitter:site?

The **twitter:site** field is a Twitter/X Card meta tag that identifies the Twitter handle of the website or publisher associated with the page (for example, **@YourBrandHandle**). It appears in Twitter link previews and helps attribute shared content to your account. This field is optional but recommended if your brand is active on Twitter/X.



## 🤖 Where OTTO Auto-Generates Metadata vs. Manual Entry

Search Atlas's AI agent **OTTO** can automatically generate and deploy certain metadata fields as part of its on-page optimisation tasks. Here is how coverage is split:

- **Auto-generated by OTTO:** SEO meta title, SEO meta description, and in many cases the `og:title` field. OTTO applies these when running an optimisation task on a connected page.
- **Requires manual entry or AI-assisted generation:** The **OG Description** (`og:description`), **twitter:site**, and other extended social metadata fields. These are not automatically populated by OTTO and need to be added through the content or metadata editor.

## ✨ How to Add AI-Generated Descriptions

You can use Search Atlas's built-in AI writing tools to generate OG Descriptions and other metadata copy without writing from scratch. Follow these steps:

1. Open the page or article you are working on inside Search Atlas.
2. Navigate to the **Metadata** or **SEO Settings** section of the editor (the exact label depends on your workspace configuration).
3. Locate the **OG Description** field.
4. Click the **AI Generate** button (wand or sparkle icon) next to the field. If no button is visible, click inside the field and look for an inline AI prompt option.
5. Review the AI-generated text. The output will be based on your page title, target keyword, and existing content.
6. Edit the generated copy if needed to match your brand tone, then click **Save** or **Apply**.
7. Repeat for the **twitter:site** field if required, entering your Twitter handle manually (AI generation does not apply to handle fields).

Always review AI-generated metadata before publishing. Ensure the OG Description is between 120–160 characters and accurately reflects the page content.



## 💡 Quick Reference: Content Length Cheat Sheet

- **Short (300–600 words):** FAQs, product pages, local landing pages, quick answers.
- **Optimized / Medium (800–1,200 words):** Blog posts, standard service pages, how-to articles.
- **Long-Form (1,500–2,500+ words):** Pillar guides, in-depth comparisons, competitive informational topics.

## 🆘 Need More Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.