Website content integrations
This guide is for businesses that already have a website. If you are working on Google Maps, reviews, Instagram, or a business with no website yet, start with Local ranking instead.
The idea is simple: connect the website once, then let 42flows publish and verify work through the safest path for that stack.
Best for sites that publish posts and use SEO plugins like Yoast or Rank Math.
Best for stores that want SEO articles inside a Shopify blog.
Best for GitHub-backed content sites that publish from markdown files.
Best for Next.js and custom apps that own their database, routes, and cache.
Start here
| Your website | Use this path | Helpful page |
|---|---|---|
| WordPress | Connect with a WordPress Application Password. 42flows can publish posts and work with common SEO plugins. | WordPress setup guides |
| Shopify | Connect the Shopify store and publish into a blog. Your Shopify theme handles the final page design. | Shopify publishing setup |
| Nuxt Content | Connect the GitHub repo so 42flows can add content files and let your deploy pipeline publish them. | Nuxt setup guides |
| Next.js, Astro, SvelteKit, Rails, Laravel, Django, custom CMS | Add one secure webhook endpoint. Your app saves the article and returns the final public URL. | Universal webhook integration |
For the full side-by-side view, see what each website connection can do.
What 42flows needs
42flows needs four things from any website integration:
- A safe way to send or write the content.
- A public URL where the finished page will live.
- A way to confirm the page is reachable after publishing.
- A stable rule for updates, usually the article slug or the file path.
That is why the right path depends on the website stack. A WordPress site can accept posts through WordPress. A Shopify store can accept blog articles through Shopify. A Nuxt site can publish from Git. A custom app should receive a webhook and decide how to store the article.
Docs in this section
- Website content lifecycle: what happens from connection to publish, verification, and updates.
- GitHub and Nuxt Content integration: how GitHub-backed publishing works for Nuxt Content sites.
- Universal webhook integration: the recommended path for Next.js and custom websites.
- Shopify publishing setup: how Shopify blog publishing works.
- Platform capability matrix: a plain-language comparison of all paths.
WordPress and Nuxt already have setup hubs
If the customer is on WordPress, use the WordPress setup guides and the WordPress publishing feature page.
If the customer is on Nuxt Content, use the Nuxt setup guides, especially Connect your Nuxt site via the GitHub App, and the Nuxt Content publishing feature page.
Rule of thumb for Next.js
For a normal Next.js app, use the webhook.
Use GitHub delivery for Next.js only if the app already has a file-backed content system that can render the files 42flows writes. If the app uses a database, headless CMS, ISR, or custom routing, the webhook is cleaner because the app stays in charge of storage, revalidation, and caching.
Security model
Each path uses a scoped credential:
| Website path | Credential |
|---|---|
| WordPress | WordPress Application Password for a user who can publish or edit posts. |
| Shopify | Shopify store access granted during connection. |
| GitHub/Nuxt Content | GitHub App access to the selected repository. |
| Nuxt direct receiver | Bearer token for the receiver endpoints. |
| Webhook | Bearer token for the customer-owned HTTPS endpoint. |
Webhook setup shows the token once so the customer or their developer can put it in the website environment.