Publishing

When you approve an article, Seovyn delivers it to the place your website lives. You set that up once, on the Publishing page.

Choose where your website lives

Under Delivery, choose the platform your site runs on. Seovyn reads your homepage and usually knows already: a card at the top says Your site runs on WordPress (or Shopify, Webflow, Next.js and so on) with the one to connect, and that tile is marked Your site. For a Next.js site it suggests your GitHub repo; on the App Router, Seovyn adds the pages that render articles itself. Each guide lists exactly what to paste and where to find it; most take one key or token and a minute.

• WordPressAn application password. Live posts or drafts.
• ShopifyYour store's blog, through a custom app.
• WebflowA CMS collection, with your fields mapped.
• FramerYour Framer CMS, with an API key.
• WixYour Wix blog, with an API key and site ID.
• NotionA database that powers your blog.
• GhostAn Admin API key from a custom integration.
• GitHubPull requests on your content repo. Ideal for Next.js.
• WebhookA signed request to your own backend.
• Seovyn-hosted siteNo website yet? Seovyn builds and hosts one.

Live or draft

On WordPress and the other website builders, you choose what "approved" means:

• Publish live. The article goes live as soon as you approve it. Approving is the review.
• Save as a draft. The article arrives in your CMS unpublished, for a last look there.

You can change it at any time. A GitHub repo gets a pull request (which can merge itself), a webhook is told to publish, and a Seovyn-hosted site adds the article at once.

Spread articles out

By default an approved article is delivered the moment you approve it. To release them evenly instead, open Publish pacing, turn on Spread out publishing and choose up to how many articles a day, from 1 to 36. Seovyn then publishes one article at a time, spaced evenly through the day: at 6 a day, one every 4 hours.

The publishing queue on Overview lists approved articles in the order they'll go out, with the time of the next one. A steady rhythm looks natural to readers and search engines, and stops a burst of approvals from putting a dozen new pages on your site in the same minute.

What gets delivered

The article in your platform's format with its title, meta description, slug and tags, a cover image where one can be made, and whatever else the platform supports: a Shopify search listing, Ghost's tags and excerpt, Webflow fields you mapped. A webhook carries everything: the Markdown body, tags, the sources the article cited, your byline and ready-made structured data. See Webhook reference.

If a delivery fails

A delivery that fails for a reason that can pass (your site is down, a timeout, a rate limit) is tried again after 10 minutes, 30 minutes, 2, 6 and 12 hours: six attempts over about a day. One that can't succeed on its own, such as a wrong key or a refused signature, isn't retried: fix it, and the next delivery uses the new settings.

Failed deliveries show under Needs attention on the Publishing page with the reason, and you get an email. See Troubleshooting.

Is it really live?

"Delivered" and "live" are different facts. A pull request can wait to be merged; a static site can take minutes to build. So after delivering, Seovyn loads the page's real address to confirm it's there. If it isn't yet, it checks again over the next day and a half before marking the article Not found and telling you.

Only pages confirmed live get links from your other articles, and only they are sent to search engines.

Search engines

When a page is confirmed live, Seovyn tells the search engines that support IndexNow (Bing, Yandex, Seznam and Naver) so they crawl it in minutes. Google finds pages through your sitemap and Search Console. See Search engine indexing.

Settings every article follows

The rest of the Publishing page holds the settings that apply wherever you publish: Brand voice, Site knowledge, Publish pacing, Search Console and indexing.