Core concepts

Seovyn has a small vocabulary. Each term below is something you'll see in the dashboard, with a link to the page that covers it in full.

Your workspace

Organization. One website, with everything that belongs to it: its sources, articles, publishing settings and plan. If you write for several sites, each gets its own organization, and you switch between them at the foot of the sidebar. See Organizations.

Plan. How much Seovyn writes for an organization each month (4 articles on Free, 30 on Pro, 100 on Scale) and what runs without you: autopilot and refreshes of live articles are on Pro and Scale. See Plans and usage.

Where articles come from

Source. A place Seovyn watches for ideas and material: a competitor's site, a subreddit or a YouTube channel. Each source writes one kind of page. See Sources.

Keyword target. A search you want an article for, such as "best transactional email api". You add your own; Seovyn adds more from Search Console, competitors, topic clusters and Google's related searches, and labels where each came from. See Keyword targets.

Topic cluster. A pillar guide plus the articles that answer the questions inside it, all linked together. Seovyn plans clusters from your site and finishes one before starting the next. See Topic clusters.

Page type. What an article is for: a blog post (guides and how-tos), a comparison (X vs Y, alternatives) or a landing page (features and use cases). It decides the article's structure. On a Seovyn-hosted site, a GitHub repo or a webhook it also decides the address: /blog/…, /compare/… or /features/….

How articles are made

Brand voice. The briefing every article is written to: who it's for, the tone, the point of view, the call to action and the phrases to avoid. See Brand voice.

Site knowledge. What Seovyn knows first-hand about your business: facts read from your own pages, and notes your team adds. See Site knowledge.

Draft. An article Seovyn has written and checked, waiting for a decision. It carries its research, its sources and a preview of how it will look on Google.

Quality score. A score out of 100 on every draft, from two checks: automatic SEO checks and the Editor, an AI reviewer that reads the article against its sources. 85 and up is a strong draft. See Quality score.

Who decides

Review queue. The drafts waiting for you, on Overview. The Library keeps every article Seovyn has written, whatever its status. See Review and approve.

Supervised. The mode every organization starts in: each draft waits for your approval.

Clean approval. A draft you approve without editing it. Editing clears its quality score, so it no longer counts.

Autopilot. After five clean approvals in a row, of drafts that scored 70 or more, drafts that score 75 or more can approve themselves after a hold window (12 hours by default) in which you can stop them. A rejection puts you back in supervised mode. See Autopilot.

Where articles go

Destination. The place your website lives and approved articles are published: WordPress, Shopify, Webflow, Framer, Wix, Notion, Ghost, GitHub, your own site through a webhook, or a Seovyn-hosted site. One organization has one destination. See Publishing.

Publish pacing. An optional limit on how many approved articles go out a day, released evenly instead of all at once.

Live check. After delivering, Seovyn loads the page's real address to confirm it's there. "Delivered" and "live" are different facts, and only live pages get linked from other articles.

What happens after

Results. Each published article's clicks, impressions and position from Google Search Console, measured again at 30, 60 and 90 days. See Results.

Update. A refreshed version of a live article, or a new title and description for its search result, prepared by Seovyn and published only when you (or autopilot) say so. See Updates and refreshes.

Browser Agent. Tasks with no API, like submitting a sitemap or checking a page renders, carried out in your own Chrome by Pilot, Seovyn's extension. In beta. See Browser Agent.