FAQ & troubleshooting
FAQ and troubleshooting
Answers to the questions we are asked most. If yours is not here, email support@vectraseo.com.
My sign-in link has not arrived. What should I do?
Sign-in links come from noreply@vectraseo.com with the subject "Your VectraSEO Login Link". Check your spam or promotions folder first. Each link works once and expires after 15 minutes. On the Check your inbox screen, click Send a new sign-in link (it becomes available after a short wait), or use a different address if you mistyped yours. If your mail server has rejected our messages before, later links can be blocked too; email support@vectraseo.com from another address and we will check.
How do passkeys work?
Sign in once with a link, then open Account and click Add passkey in the Passkeys section. Next time, enter your email and your device asks for Face ID, Touch ID, a PIN or a security key instead of sending a link. If you dismiss the prompt or it fails, choose use a magic link instead. You can rename or revoke a passkey on the same page. A browser without passkey support always uses sign-in links.
Why is my post held instead of published?
A generated post publishes only when all five quality gates pass: metadata, content quality, the truth check on factual claims, your destination's product claims, and a final scan for leftover template text. A post a gate holds stays a draft marked Needs review while automatic repair works on it. When automatic repair stops, the draft stays held until you act, for example by removing the unconfirmed claims or regenerating it. See Content pipeline for every status and action.
Publishing to my CMS failed. How do I fix it?
The post shows failed with the error your CMS sent back. Fix the cause below, then publish again. A failed republish of a live post, including a one-click fix, never takes the post out of published; the attempt is recorded on the post instead. "No CMS configured for this project" means the project has no connected CMS yet: add one in project settings.
401 or 403 means the username or application password is wrong or was revoked; create a new application password. The REST API must be reachable over HTTPS at /wp-json/wp/v2, so anything that blocks it, such as a security plugin or firewall rule, fails the publish. If the featured image cannot be uploaded, the post still publishes without it.Blog → Posts read/write permission and the site ID is right. Wix updates carry only the title and excerpt, so a body change cannot be republished there.2xx from your webhook URL fails the publish. Check the Zap is on and the webhook URL in project settings is current.5xx, 408, 429 or connection error is retried up to 3 times and reported as Destination unavailable. Any other 4xx fails at once as Destination rejected publish, with your endpoint's message. When the rejection lists the claims it refused, VectraSEO repairs a never-published post and retries on its own, a limited number of times. A 404 or 405 on an update means your endpoint has no PUT route. See Custom API.A fix says "skipped: live_unreadable". What does that mean?
A fix for a published post patches your live page, not a stored copy. live_unreadable means the live page could not be read (it was down, returned 404 or blocked us), so VectraSEO did not overwrite it from an older copy. Check the page is publicly reachable, then run the fix again. extract_low_confidence means the editable content could not be isolated on the page; destination_no_update_route means your Custom API endpoint has no update route; body_update_unsupported means your CMS (Wix) cannot take a body change. A fix reported unverified was accepted by your CMS but the live page did not change, which usually means a static site that does not rebuild on update. See every skip reason and one-click fixes.
Search Console asks me to reconnect. Why?
The project's Search Console connection cannot submit to Google, because it was made with read-only access or Google revoked the stored permission. The API reports this as needs_reconsent: true. Open the project's Settings, find Search Console, click Reconnect and approve write access on Google's screen. Your stored Search Console data is kept. See Search Console.
I got a "subscription_limit" error or an upgrade message.
The action is beyond your plan. The API answers 403 with code: "subscription_limit" and a detail message that names the limit and the plan that lifts it. Plans cap the number of projects, posts per month and competitors per project. The free plan cannot connect a CMS, automated scheduling needs Growth or above, and anything that calls an AI model (post generation, AI visibility monitors and scans, AI-written fixes, the Analytics API) needs a paid plan or an active trial. Your plan and this month's usage are on the Billing page (also GET /billing/plan). Archived posts stop counting toward the monthly post allowance. Compare plans on the pricing page.
Can I get a refund for Local Scout?
Yes, within 30 days of starting your Local Scout subscription. The refund returns your latest payment and cancels the subscription at once, so access ends immediately rather than at the end of the period. It is not available for an already-canceled subscription, or after 30 days; in that case, or if we cannot confirm your start date, email support@vectraseo.com. Signed in, GET /billing/local-scout/refund-eligibility reports eligible, the reason and days_left, and POST /billing/local-scout/refund claims it.
Can't find what
you're looking for?
Reach out to the team. We answer every email and we read every bug report.