Publish reviewed articles to a Shopify blog
Connect a Shopify store token, choose the destination blog and author, deliver reviewed article drafts or confirm publication, and verify the storefront.
On this page
Connection and account access
Reviewed article publishing is available on current Starter, Growth, Pro plans. Effective trial, legacy and custom access can differ; check current plans and your account’s limits.
Configured Admin API token, selected blog and author. Blog articles, not products or theme edits; managed OAuth-app installation is not implemented.
This guide is public. Sign in to connect Shopify in PB; credentials, workspace articles and publishing controls stay inside your account.
What PB publishes to Shopify
Prerender Buddy delivers reviewed articles to the Shopify blog you select. It supports unpublished article drafts and explicitly confirmed publication.
This connection handles blog articles. It does not edit products, collections, checkout or theme files. It uses a configured store Admin API token; a managed one-click PB OAuth app installation is not part of this connection.
Prepare store access
Use the store's original myshopify.com domain, such as garden-journal.myshopify.com. The connection form uses that domain even when the storefront has a custom domain.
Provide a store Admin API access token with the blog-writing access accepted by PB: write_content or write_online_store_pages. The token must be able to read the available blogs and write articles. An app client secret is not a store access token.
Use Shopify's current access-token guidance for your app and store setup. Its article API reference describes the article write permissions. Token issuance and expiry depend on the Shopify app's authentication method; renew access and check the connection when needed.
Create the destination blog in Shopify first if it does not exist.
Connect the blog in PB
- Open your website in PB Sites, open Publishing and select Shopify.
- Enter the store domain and Admin API access token.
- Choose Load Shopify blogs and select the intended blog.
- Enter the article author name to display.
- Choose Save destination and Check connection.
Review the selected blog before saving. This becomes the website's publishing destination and replaces any other active destination for that PB website. Keep the token private.
Review, send a draft or publish
Open a full article from Article Generation. Check its facts, product claims, links and fit with your store before approving it.
Sending a CMS draft creates or updates an unpublished Shopify article. Explicitly confirmed publication makes the approved article public in the configured blog.
PB adds a stable article identifier to the generated handle. Check the article's actual public URL, including any redirect from the original store domain to the custom domain.
For a later release, use a separately confirmed PB publication schedule. Setting an editorial calendar date alone does not publish.
Updating a published article
Shopify does not provide a staged draft version of an already published article through this PB connection. PB therefore blocks a draft delivery that would change or unpublish a live article.
Review and reapprove the changed article, then confirm publication to update it. Check any uncertain previous delivery in Shopify before starting a new one.
Resolve store or blog disagreements
If blog discovery fails, verify the original store domain, token validity and granted blog permissions. Confirm that the selected blog belongs to the same store.
A successful connection check establishes access, not that the article is live. If the API reports publication but the storefront differs, inspect the article's published state, the blog template and the final redirected URL.
Disconnecting PB does not delete Shopify articles. Revoke or replace the app's store access separately when required.
Verify and monitor the result
After confirmed publication, open the final public URL without signing in. Check the expected article, title, links and canonical URL. A saved CMS draft is not public, and a connection check does not prove that an article is live.
Use Health and Monitoring to inspect the published response. Connect rendering only if checks establish a missing or incomplete crawler-readable response. CMS publishing does not require a DNS change by itself.
Revisit the relevant AI Visibility questions under comparable collection settings. Later mentions or citations do not establish that an article caused the change, and publication does not guarantee indexing or AI recommendations.
Read the article and publication workflow or how PB connects the steps. Compare other destinations in Integrations.