> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/create-a-project/06-builder-publishing.md).

# 06. Spawn Studio: build and publish your page

Edit sections, preview your page and publish a free public SPAWN link.

**Open:** your project checklist → **Write your page** → **Open my page**. You need the owning SPAWN account.

## Edit the page

1. Tap or click a section in the page canvas to select it.
2. Edit its available content fields. On a phone, the editing panel opens from the bottom; choose **Done** to return to the page.
3. Choose **Add a section** to add a supported section and complete its content.
4. Use **Move up**, **Move down**, **Copy** or **Remove** to organize the selected section. Confirm removal only when intended.
5. Watch the status at the top. Wait for **Saved** before leaving.

Sections may include text, images, roadmap, tokenomics, FAQs and other blocks offered in the editor. Availability can depend on project access. A decorative or informational block does not by itself establish an external service connection.

## Search appearance and theme

Open **More options** → **How your page looks on Google** to edit search metadata. Where the project has access, **Colors and fonts** opens theme controls. Search metadata influences the information your page supplies; it does not guarantee ranking or immediate search-engine updates.

## Preview and publish

1. Choose **Preview** and inspect the page on both a narrow phone layout and a wider screen.
2. Check button destinations, social links, image cropping, spelling and token addresses.
3. Return to the builder and choose **Publish**, or use **Put your page online** from the project checklist.
4. Use **Look at it first** if you want one final preview.
5. Choose **Publish my page**.
6. Use **Copy link** or **Open my page**. The public address has the form `https://spawnmeme.com/p/your-page-slug`.

After publication, saved edits appear on the public page. Do not assume later edits remain private drafts. Review wording before applying changes to a published page.

## Costs and availability

Spawn Page publishing has no site deployment fee. Token deployment is a separate optional action with its own quote. **Custom domains are not available in the current publishing flow**; the page explicitly says that using your own web address is not available yet.

## Troubleshooting

| Problem                               | Resolution                                                                                                                                   |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Not saved**                         | Keep the editor open, copy important unsaved text somewhere safe, restore connectivity and choose **Try again**.                             |
| Changes missing publicly              | Wait for **Saved**, verify the correct project URL, then refresh the public page.                                                            |
| Page still private                    | Complete **Publish my page** and check for a public link. Preview alone does not publish.                                                    |
| Section removed accidentally          | If no undo control is offered, add the section again and restore its content. Keep a copy before destructive edits.                          |
| Colors/fonts or analytics unavailable | These controls are access-dependent; see [analytics and access](/spawnmeme-docs/feature-guides/create-a-project/07-analytics-and-access.md). |
| Page not found                        | Reopen from My Spawns under the owning account, and verify the complete public slug.                                                         |

**Success:** the public link opens your intended page, including the latest saved content, without requiring the visitor to sign in.

## Find and share your published project

Published pages appear in [Projects](/spawnmeme-docs/feature-guides/create-a-project/47-projects.md) within about a minute. Publishing a page does not launch a token. The public page footer includes **Share** for a page-specific preview and **Report** for content concerns. See [sharing](/spawnmeme-docs/feature-guides/platform-information/45-share-links.md) and [reporting](/spawnmeme-docs/feature-guides/reference-and-support/46-report.md).

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/create-a-project/06-builder-publishing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
