> For the complete documentation index, see [llms.txt](https://support.duplifyapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.duplifyapp.com/using-duplify/exporting-data/pages.md). # Pages Learn how to export Shopify pages with Duplify. Duplify exports all pages from your source store to your destination stores, including their content, layout, and SEO settings. This ensures your store pages, such as About, Contact, or FAQ, are fully replicated without needing to rebuild them manually. *** ## Exporting pages When you select the **Pages** option in Duplify: * All pages from your source store are exported to your destination stores. * Each export includes the page’s complete content, including markup, text formatting, images, videos, and SEO information. #### Example If your store includes an “About Us” page with formatted text, embedded videos, and optimized SEO, exporting pages with Duplify copies all of this content to your destination stores. *** ## Export events Duplify tracks export events to determine the size of your store’s export. Each event represents one data item or file. Your plan provides a specific number of monthly export events. #### Page export events * Each page exported counts as one export event, regardless of content length or media. For more details on export events across Duplify, see our [Export events reference guide](/using-duplify/export-events.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://support.duplifyapp.com/using-duplify/exporting-data/pages.md?ask=&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.