> For the complete documentation index, see [llms.txt](https://nimora.gitbook.io/nimora-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nimora.gitbook.io/nimora-docs/nimora-ai-media-and-seo-docs/features/publishing-and-approvals.md).

# Publishing and approvals

## Publishing and approvals

Nimora uses a review-first publishing model. Teams can move fast without turning AI output into uncontrolled live changes.

### Why approvals matter

Approvals protect:

* Brand voice
* SEO quality
* Product accuracy
* Compliance review
* Team accountability

### Approval queue

The approval queue keeps generated output visible before publish-back. It can include SEO batches, product media, videos, blog drafts, metadata updates, and structured data changes.

### Publish-back

Publish-back sends approved changes to the connected store. Depending on platform and permissions, this can include metadata updates, product images, blog drafts, product records, or schema payloads.

### Recommended process

1. Generate or identify an issue.
2. Review the suggested fix or asset.
3. Approve only what matches the brand and product.
4. Publish the approved change.
5. Confirm the live result.
6. Watch analytics after the update.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://nimora.gitbook.io/nimora-docs/nimora-ai-media-and-seo-docs/features/publishing-and-approvals.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.