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

# WordPress publishing

> Review a prepared change, publish it to your site, and undo it if you need to.

> [!NOTE]
>
> WordPress publishing is on the Growth plan. It needs the [Sightline WordPress plugin](https://docs.asksightline.com/integrations/wordpress-plugin.md), version 1.2.0 or later.

Content gaps, page fixes, site health and wrong-fact recommendations have an **On your site** section. From there, Sightline can prepare the exact change, let you review and edit it, and publish it to WordPress. Nothing goes live without your approval, and every push can be undone.

## Publishing a change

**1. Prepare the change**

Click **Prepare the change**. Sightline writes the exact edit:

* **New content**: title, URL slug, page text, SEO title and description, and an FAQ.
* **An existing page**: SEO title and description, a short direct answer shown at the top, and an FAQ.

**2. Review and edit**

Edit anything you like. Before it can go out, the change is checked: no unfilled placeholders, title and description lengths within limits, the page must be on your own domain, and new content needs real text.

**3. Publish**

Click **Publish on the site**. The plugin publishes it in the style your site already uses.

## How it fits your site

The plugin looks at your theme and the page builder you already use (Bricks, Elementor, Divi, Gutenberg or your theme's normal content area) and publishes to match:

* **A site with a blog** gets a post.
* **A site built from pages** gets a page, added to the menu under the section that fits, or to the main menu if it's still short.
* **Page fixes and wrong facts** edit the existing page.

SEO titles and descriptions go into Yoast, Rank Math or SEOPress when one is installed. Otherwise the plugin outputs them itself.

> [!WARNING]
>
> Some page builders (Bricks, Elementor, Divi) don't use the normal page content, so the summary and FAQ text may not show on pages built with them. The title, description and FAQ structured data still apply, and Sightline tells you when it detects this. You can [hand the visible part off to a coding agent](https://docs.asksightline.com/action/coding-agents.md) instead.

## Undo

Each push records what the page held before. **Undo** puts it back, or moves a new page to the trash and removes its menu item. Pushing again replaces your earlier push rather than stacking changes. The history is kept on each recommendation.

## Turning it off

On the plugin's settings page in WordPress, untick **Allow changes from the dashboard**. Sightline will show that the site isn't accepting changes.

## Security

Changes are only accepted from Sightline. Every request is signed with a secret derived from your site key, is refused if it's more than five minutes old, and is only sent to the secure (https) address your plugin reported.

## Checking the connection

**Settings → Integrations → Agent traffic** shows whether a site is ready for publishing. **Test** checks the connection. The site must have reported in at least once, which you can trigger with **Send test event** on the plugin's settings page.


## Related topics

- [WordPress plugin](https://docs.asksightline.com/integrations/wordpress-plugin.md)
- [Plans](https://docs.asksightline.com/plans.md)
- [How Sightline works](https://docs.asksightline.com/how-it-works.md)
- [Claude Code and Cursor handoffs](https://docs.asksightline.com/action/coding-agents.md)
- [Cloudflare Worker](https://docs.asksightline.com/integrations/cloudflare-worker.md)


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