> ## Documentation Index > Fetch the complete documentation index at: https://docs.weelkit.com/llms.txt > Use this file to discover all available pages before exploring further. # Checks and publishing > Fill in an article's metadata, work through its SEO and AEO readiness and its fixes, send it to your CMS, and follow its status. These tools are for articles. Writings don't have metadata, checks or fixes, and can't be sent to a CMS. ## Metadata and featured image Choose **SEO & Metadata** in the editor's top bar, then the **Metadata** tab. * **Fields:** the fields your organization's articles carry, such as **Meta title**, **Category** and **Tags**, plus any custom fields. They come from your CMS mapping, or from your organization's [Article fields](https://docs.weelkit.com/settings/organization.md#article-fields) when no CMS is connected. Custom fields that every article needs are marked **Required**. * **Categories and tags** come from your connected CMS. A value that isn't in the CMS's list is flagged, for example "This category is not in the synced CMS list." * **Featured image:** when your fields include one, choose **Choose from Library**, or **Browse Files** to upload a PNG, JPG or WEBP. Then fill in the image details your CMS takes, such as **Alternative text**, **Caption**, **Image title** and **Description**. Required ones are marked with \*. **Remove image** takes it off. * **Article info:** created and updated dates, author, CMS, status, categories, tags and word count. * **Publish history:** the latest send to your CMS, with its result (**Succeeded**, **Failed** or **Partial success**) and links to **Open in CMS** and **Edit in CMS**. Length counters use the active field contract's limits. SEO fields do not share a fixed universal title or description limit. ## Readiness checks The **SEO** and **AEO** tabs of **SEO & Metadata** check the article while you work on it. Weelkit checks again after every save, and the editor saves as you type, so the checks keep up with your edits. Each tab's label counts what needs fixing, for example **SEO (3)**. A new article is checked once it's saved. ### SEO The **SEO** tab shows how many checks pass, for example "18 of 22 passed", with the failed checks first. Each check shows **Passed**, **Failed**, **Suggestion** or **Not checked**. Checks that can only run on the live page are grouped under **Checked after publishing**. Open a failed check to see what to do. Choose **Fix with AI** to put a ready-made request for the fix in the chat box; review it, then send it. The SEO tab also covers your organization's editorial rules. The AEO tab's AI check judges them, so when the article has changed since, they show **Out of date**. Choose **Check again**. ### AEO The **AEO** tab shows how ready the article is for AI answers: * **AEO readiness:** a score out of 100 and the AEO checklist. Like the SEO checks, it updates as you edit. * **AI check:** an AI review of how AI engines are likely to see the article. It shows the **Main question** the article answers, **Competing coverage** (pages already answering that question, rated **Good chance**, **Some chance**, **Hard to win** or **Unknown**), and what to fix. It runs by itself when someone who can edit the article opens the panel and there's no current result, and takes up to a minute. When the article changes, the result shows **Out of date**: choose **Run again**. If it hasn't run yet, choose **Run check**. Only people who can edit the article can run the AI check. ## To fix Choose **To fix** in the top bar to see what's left to do on the article. The badge counts the open items. Each item is one of: * **Failed check:** an SEO or AEO check that fails. * **Suggestion:** a check that could be better. * **Opportunity:** something the published article's results point to, such as a search query that ranks just off page one, or readers who leave quickly. For each item: * Choose **Fix with AI** to put a request for the fix in the chat box. * To set an item aside, open its **⋯** menu and choose **Dismiss**. Dismissing hides it for everyone, and it stays dismissed. Dismissed items are listed under **Dismissed**. You need edit access to dismiss. An item closes by itself once its check passes. There's nothing to assign or schedule. The same fixes appear on the article's pages in [Performance](https://docs.weelkit.com/metrics/performance.md#fixes) (SEO) and [AEO & GEO](https://docs.weelkit.com/metrics/aeo-and-geo.md#articles) (AEO). There, **Fix in editor** opens the article with that item showing in **To fix**. ## Send to your CMS The CMS button is at the right of the editor's top bar. Its label follows the **Default status** an admin chose in [CMS settings](https://docs.weelkit.com/settings/organization.md#cms): | Default status | Button | What happens | | - | - | - | | **Draft** | **Send draft to CMS** | Weelkit sends the article to your CMS as a draft straight away. | | **Published** | **Publish to CMS** | Weelkit asks you to confirm, then publishes the article live. Choose **Publish article live**. | A line under the top bar repeats the default, for example "Saved CMS default: Draft (unpublished)." Weelkit saves your latest edits before it sends. The result shows under the button, with a link to the item in your CMS, and in **Publish history**. An article over the [body size limits](https://docs.weelkit.com/integrations/semantic-html.md#article-size) stays **Not saved** and cannot be sent. Your previous saved version stays available. The first send creates the article in your CMS. What later sends do depends on the CMS setting **When the article already exists**: **Always update existing** updates the same item, and **Always create a new item** creates another one. With **Ask before updating**, a later send opens **Update CMS article** and asks, "This article is already in your CMS. Update it?" Choose **Open existing CMS item** to inspect it when the link is available, then **Update article** to send the saved version prepared for this request. Edits made after that request need another send. **Cancel** leaves the CMS item unchanged. The result says **Updating…** while the confirmed update is being sent, and **Updated** only after the CMS update succeeds. A failed send or an unconfirmed outcome stays visible; it isn't shown as **Updated**. An update result is separate from the article's **Draft** or **Published** status below. When the button is greyed out, point at it to see why: * **CMS not connected**: no CMS is connected, or its setup isn't finished. An admin connects it in [Organization settings → CMS](https://docs.weelkit.com/settings/organization.md#cms); the [Integrations](https://docs.weelkit.com/integrations/overview.md) tab of these docs explains each destination. * **Edit access required**: you can't edit the article, or you're viewing an older version. * **Choose Draft or Published in CMS settings**, **Save the article first** or **Sign in again**: do what it says. If Weelkit can't confirm whether your CMS received a send, it says so and offers **Check original CMS send**. Check before you send again, so the article isn't created twice. When **Retry saved CMS send** is available, it retries that original request rather than starting another send. ## Article status An article's status shows next to its title in the editor, and in the Library: | Status | Means | | - | - | | **Published** | The article is live on your CMS. | | **Draft** | The article isn't live on your CMS: it hasn't been sent, or it's a draft, scheduled, pending review, private or in the trash there. | | **Archived** | You archived it in Weelkit. Your CMS never changes this status. When you restore the article, it takes its status from your CMS again. See [Archive and restore](https://docs.weelkit.com/library-and-knowledge/library.md#archive-and-restore). | The status follows your CMS. You publish, schedule or unpublish in your CMS, and Weelkit picks up the change: * When you open an article, Weelkit checks it with your CMS. Point at the status to see when it was checked, for example "Checked just now". * In the background, Weelkit keeps checking every article it sent: every few minutes right after a send, then less often as the article gets older. A scheduled post is checked again when it's due to go live. * If your CMS can't be reached, the status stays as it was, and the status says so. There's no button to refresh the status. Once an article is **Published**, it appears in [Performance](https://docs.weelkit.com/metrics/performance.md) and in [AEO & GEO](https://docs.weelkit.com/metrics/aeo-and-geo.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.