Set up a VectraSEO project in six steps: (1) Profile & Audience — tell us your business, site, and who you're writing for; (2) Content & Brand — set voice, facts, and a sitemap for internal links; (3) Generation & Quality — choose your publishing quality bar; (4) Publishing — connect a CMS; (5) Search & Analytics — link Google Search Console and GA4; (6) Developer & API — generate an agent API key. Each setting is explained below.
Updated
The foundation every other feature reads from — your business, site, market, and target reader. The more specific you are, the more on-target every generated post and content-gap suggestion becomes.
Where generic AI output becomes your brand's voice. The optional Content Brief constrains both what topics get suggested and how posts are written; the Sitemap powers internal linking.
The brief works on two axes at once. It constrains which topics get suggested — content-gap discovery only proposes subjects that fit your persona and product, and skips anything on your Topics-to-Avoid list — and it constrains how each post is written — voice, the claims it may make about your product, and how titles read. A constraint you state once is applied in both places.
Topic choice isn't only a traffic decision. Every article you publish teaches search and answer engines what your business is. A high-volume keyword that files you under the wrong category works against you even when it brings clicks, so the brief biases suggestions toward topics that reinforce your real category, products, and reader — not just whatever ranks.
Product Facts is the most load-bearing field: it's the allow-list of capabilities an article may assert about your own product. List the real ones — one per line — and the writer won't invent features, integrations, or guarantees you don't offer. Supplying true facts here also helps your claims clear the truth layer and reduces posts held back for review.
Guardrails that decide what's allowed to publish. Pick a Publishing Quality Bar that matches your risk tolerance — Strict holds posts back until they clear higher word-count, sourcing, and claim-verification thresholds; Casual ships faster. See the methodology for how these checks work.
Connect where posts go live. VectraSEO publishes to seven platforms — pick one and enter its credentials. The optional Destination Capability Guard keeps generated claims inside what your destination can truthfully say. Building your own endpoint? See the Custom API guide or the integrations overview.
Close the loop between publishing and performance. Connect Google Search Console and GA4 so VectraSEO can measure rankings and traffic and optionally nudge search engines to index new posts.
For automation and integrations. Generate a per-project API key to drive VectraSEO from scripts, CI, or an AI agent, and to pull the read-only Analytics API. The full reference lives in the API field manual.
Only the Profile & Audience group — your business name, website URL, and a target audience. Content brief, CMS connection, and analytics are all optional and can be added at any time.
No. If you leave the CMS picker on 'none', VectraSEO generates and stores posts as drafts you can review or export. You only need a CMS connection if you want VectraSEO to publish to your live site.
It sets all of a project's content gates at once. 'Strict' holds posts back until they meet higher minimums for word count, H2 sections, source links, and verified claims; 'Casual' publishes faster with looser checks; 'Custom' lets you set each threshold yourself.
Seven — WordPress, Wix, Shopify, Squarespace, Blogger, Zapier, and any REST endpoint via the Custom API adapter.
A Content Brief is an optional rulebook — target persona, brand voice, product facts, topics to avoid, and title guidelines — that constrains both which topics VectraSEO suggests and how posts are written. It's optional, but filling it in makes generated content match your brand far more closely.
No — any subset works, and each field you add tightens the engine a little more. The single most valuable field is Product Facts: it is the allow-list of capabilities an article may claim about your product, so listing the real ones stops the writer inventing features you don't offer and helps your claims clear the truth layer.
Topics to Avoid is your up-front blocklist — subjects VectraSEO never suggests or writes about. Rejecting a topic is a correction after the fact: when a suggested topic is off-target, rejecting it (rather than deleting it) keeps it as a negative example so the engine stops re-suggesting the same kind of subject. Use the blocklist for boundaries you already know, and rejections to teach the engine as you go.
Open Project → Settings → Developer & API and generate an Agent API Key. It authenticates the read-only Analytics API and the agent recommendations feed via the x-api-key header, and the page includes ready-to-paste cURL and Claude Code snippets. You can rotate or revoke it anytime.
Profile and a target audience are all you need to start — everything else can be added later.
[ LOAD_RECOVERY ]
VectraSEO did not finish loading.
A stale browser bundle or interrupted network request can leave the console waiting. Refresh to fetch the current app shell.