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

# How to publish a page and set its live URL

> Ship a finished piece from the article's Publishing tab and record where it went live so the rest of the workflow can see it.

Publish from inside the piece — there's no standalone publish page. Open the article at its detail
page (`content/detail/[id]`), go to the **Publishing** tab, choose the destination, publish, then
**set the live URL** on the piece (rank tracking, indexing, and reporting all key off it). If you
have the compliance guardrail on for this content type, publishing runs a real gate
that blocks failing content until it's fixed or approved — see
[Use the guardrail at publish](/platform/automate-compliance-checks).

## Steps

1. Open the piece and go to the Publishing tab.
2. Choose the destination (configured under Settings, then Platforms; see
   [2.1.5](/platform/publishing-platform-indexnow)).
3. Publish.
4. Set the live (published) URL on the piece. This one matters: rank tracking, indexing, and
   reporting all key off the recorded published URL, so a piece without its live URL set is
   effectively invisible to the rest of the workflow.
5. If IndexNow is on, publishing pings the search engines automatically; if GSC auto-queue-on-
   publish is on, the URL is queued for indexing. Verify it happened, then finish the job with
   [2.5.3 Index on GSC + sitemap](/platform/index-gsc-sitemap).

## The compliance gate

If you have the compliance guardrail enabled for this content type, publishing runs
a final check. Failing content is **blocked** until it's fixed or the exact version is approved. Each
violation comes with the offending excerpt, why it breaches, and a suggested fix. This block is real
and live today — see [Use the guardrail at publish](/platform/automate-compliance-checks) for the
full flow, and [Set up the guardrail](/platform/set-up-evaluator) to configure it.

> **Note:** the guardrail *settings copy* in the UI may still describe enforcement as "coming soon."
> That copy is stale — the publish path does block failing content. Treat the block as real.

## Publishing isn't the finish line

> A piece is "done" only after the
> [technical SEO audit](/platform/technical-seo-audit) passes and it's [submitted for indexing](/platform/index-gsc-sitemap).
> See the [Definition of Done](/theory/definition-of-done).

**Next:** [2.5.2 Technical SEO audit](/platform/technical-seo-audit) · [2.5.3 Index on GSC](/platform/index-gsc-sitemap)