> For the complete documentation index, see [llms.txt](https://docs.tipo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tipo.io/settings-source-store/sync-pages-and-blogs.md).
# Sync pages and blogs
This guide explains how to allow **Destination stores** to sync content from your **Source store**, including:
* ๐ Pages
* โ๏ธ Blog posts (Articles)
* ๐๏ธ Blogs
***
### โ What this setting does
When enabled, Destination stores can pull content from the Source store so your storefront content stays consistent across stores.
Examples of content you may want to sync:
* About Us page
* Shipping / Returns pages
* Blog posts and announcements
***
### โ๏ธ **Enable sync setting in Source store**
1. Open the app in **Source** store > click **Settings**
2. Scroll down to the bottom > turn on **Pages sync** and **Blogs sync**
3. Click save
After saving, Destination stores can start syncing the selected content types (based on your connection/setup).
***
### ๐ How it works
* The app copies the selected content from the **Source store** to the **Destination store(s)**
* Synced content is usually matched by a unique identifier (such as handle) so updates can be applied correctly
* If the Destination store doesnโt have the content yet, it may be created automatically (depending on the sync rules)
#### Matching & Imports
This setting controls how pages, blogs, and articles are imported and updated between connected stores.
#### **Option 1: Create & Update**
Create new items and update existing items with matching identifiers.
Use this option when you want to:
* Sync new pages, blogs, and articles to the destination store.
* Keep previously synced items up to date.
**Example**
Source Store:
* About Us
* Contact Us
Destination Store:
* About Us
Result:
* About Us is updated.
* Contact Us is created.
#### **Option2: Update Only**
Only update existing items with matching identifiers.
Use this option when you want to:
* Update content that already exists in the destination store.
* Prevent new pages, blogs, or articles from being created.
**Example**
Source Store:
* About Us
* Contact Us
Destination Store:
* About Us
Result:
* About Us is updated.
* Contact Us is ignored because it does not already exist in the destination store.
***
#### **Create Only**
Only sync new items created after the connection setup.
Use this option when you want to:
* Automatically sync newly created pages, blogs, and articles.
* Leave existing content unchanged.
**Example**
Connection created on January 1.
Source Store:
* About Us (created before January 1)
* Summer Collection (created after January 1)
Result:
* Summer Collection is synced.
* About Us is ignored.
* Existing synced items are not updated.
***
### โ ๏ธ Important notes
* Content sync does not always include theme layout or styling, this depends on Shopify theme setup.
* If the Destination store already has a page/blog/article with the same handle, the app may update it to match Source (depending on sync settings).
* For best results, keep handles consistent across stores.
***
**๐ Still need support?**
If you still need help, please feel free to contact us at . Weโll be happy to assist you further.
---
# 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://docs.tipo.io/settings-source-store/sync-pages-and-blogs.md?ask=
```
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.