SEOVentra
Documentation

Introduction

SEOVentra is a full-stack SEO operations platform for developers, agencies, and growth teams. It combines URL indexing automation, technical site audits, AI discoverability scoring, and analytics — all in a single workspace running on Cloudflare's global edge.

URL Indexing
Submit to Google & Bing
SEO Audits
Crawl, score, fix
AI Visibility
GEO / AEO / E-E-A-T
Analytics
Velocity & regressions
Alerts
Email, webhook, Telegram
REST API
Full programmatic access

Quick start

Get your first URL indexed in under 5 minutes.

01
Create your account
Sign up at seoventra.com — no credit card required. A free workspace is created instantly.
02
Add a website
Go to Websites → Add Website. Enter your domain (e.g. example.com). Choose DNS TXT, HTML tag, or file verification.
03
Verify ownership
Follow the instructions for your chosen method and click "Verify now". HTML methods verify in seconds; DNS can take up to 24 hours.
04
Connect Google Search Console
Navigate to Indexing → Connect GSC. Authorise SEOVentra to read and submit to your GSC property. Required for Google-specific features.
05
Submit your first URLs
Go to Indexing → Submit URLs. Paste one URL per line (max 200). Select provider (GSC for Google, IndexNow for Bing + others). Hit Submit.
06
Track progress
URLs appear in the Queue tab with live status. Use URL Lifecycle to see the full discovery → crawled → indexed journey per URL.

How it works

SEOVentra runs entirely on Cloudflare's edge network — no traditional servers. Here's how the stack fits together:

▣Next.jsFrontend⚙WorkersCompute▤D1Database◆KVSessions▥R2StorageGoogle GSCIndexNowClaude APIRazorpayCloudflare Edge Network
Cloudflare Workers
All API routes and background jobs run as serverless edge functions. Zero cold starts, global distribution.
Cloudflare D1
SQLite at the edge. Primary database for accounts, domains, jobs, audits, AI scores, and metrics.
Cloudflare KV
Session tokens, rate limit counters, and short-lived cache values.
Cloudflare R2
Audit report artifacts and data exports. S3-compatible object storage at the edge.

Plans & limits

Free has no API access — API keys require Pro Lite or above. Limits reset monthly on your billing date.

PLAN SCALE COMPARISONURL Submissions2001,0005,000UnlimitedSEO Audits52050UnlimitedFree-model Scores1005001,5003,000FreePro LiteProBusiness
FeatureFreePro LiteProBusiness
Domains125Unlimited
URL submissions / mo2001,0005,000Unlimited
SEO audits / mo52050Unlimited runs
Free-model page scores / mo1005001,5003,000
Paid-model page scores / mo—35100350
Audit history7 days30 days90 days1 year
API access—
API keys—1210
Webhook alerts—
AI Visibility Monitor——
Priority support———
Exceeding a monthly limit returns a 4xx error asking you to upgrade — requests are rejected outright, not queued or throttled. Check your usage any time from the API Keys dashboard before you hit the ceiling.

Websites & verification

Before indexing or auditing, you must verify domain ownership. This links the domain to your organisation and enables GSC integration, IndexNow key generation, and crawling.

Verification methods

DNS TXTRecommended
Add a TXT record: seoventra-verify={token}. Up to 24h propagation. Survives site rebuilds — recommended for most setups.
HTML Meta Tag
Add <meta name="seoventra-site-verification" content="{token}"> to your <head>. Instant. Breaks if you redeploy without the tag.
HTML File
Upload {token}.txt to your site root containing only the token. Accessible at https://yourdomain.com/{token}.txt.

Domain statuses

  • pending — domain added, awaiting verification
  • verified — ownership confirmed, all features active
  • failed — check failed; fix your DNS/tag and retry

URL indexing

The indexing engine submits URLs to search engines and tracks status over time through a job queue with automatic retries and exponential backoff.

queuedsubmitteddiscoveredcrawledindexed✓ GoalURL INDEXING JOURNEY

Providers

Google (GSC)

Uses Google Search Console URL Inspection API. Requires GSC to be connected. Accurate but rate-limited by Google (~200 req/day per property).

IndexNow (Bing + others)

Pings Bing, Yandex, Seznam, and api.indexnow.org in parallel. No user setup needed. Fast, free, no hard limits.

Job statuses

queuedWaiting to be processed by the next worker run.
retryingAttempt failed; scheduled for retry with exponential backoff (5m → 15m → 1h → 6h → 24h).
submittedSubmitted to IndexNow. Awaiting search engine processing (usually 24–72h).
crawledGoogle crawled the URL but hasn't decided to index it yet (often thin or duplicate content).
discoveredGoogle found the URL but hasn't crawled it (crawl budget issue). Add internal links.
indexedConfirmed in Google's index. Final successful state.
failedMax retries reached. Check for server errors, noindex tags, or blocked robots.txt.
blockedBlocked by robots.txt, noindex directive, or canonical mismatch.

Sitemap management

When you add a sitemap, SEOVentra submits it to both Google Search Console and all IndexNow-compatible engines simultaneously — no separate steps needed.

  • Add a sitemap URL in Indexing → Sitemaps. Bing, Yandex, and api.indexnow.org are pinged immediately.
  • If GSC is connected, the sitemap is submitted to your GSC property in the same operation.
  • Submission results are recorded per-endpoint so you can see which engines accepted it.
  • Sitemaps can be removed at any time. Removal from SEOVentra does not delete from search engines.
Submit both /sitemap.xml and /sitemap-index.xml separately if your site uses a sitemap index file.

URL lifecycle

The URL Lifecycle tab visualises the full state history of each URL from first submission to indexing. Click any URL to see every status transition, the provider used, and failure explanations with actionable fixes.

Discovered
Crawled
Submitted
Indexed

URLs don't always progress linearly — some skip directly to indexed, others stall at crawled. The lifecycle tracker shows exactly where each URL is stuck and why, with per-status fix recommendations.

SEO audits

The audit engine crawls your verified domain and produces a comprehensive technical SEO report with an overall score, six category sub-scores, a prioritised issue list, and AI-generated fix recommendations.

Technical82On-page68Performance71Structured Data55Accessibility88Mobile7974SCORE

Score dimensions

Technical — Crawlability, status codes, redirects, robots.txt
On-page — Titles, meta descriptions, headings, content quality
Performance — Core Web Vitals signals, page speed indicators
Structured Data — Schema.org markup completeness and validity
Accessibility — Alt text, ARIA labels, heading hierarchy
Mobile — Viewport, responsive design signals

Issue severity levels

Critical
Directly harms indexing or rankings. Fix immediately.
Warning
Reduces SEO effectiveness. Fix in next sprint.
Info
Best practice violations. Fix when convenient.

AI visibility scoring

AI Visibility measures how likely your content is to be cited by AI-powered search engines — ChatGPT, Google AI Overviews, Perplexity, Claude, Bing Copilot, and You.com.

AI ENGINE CITATION PROBABILITYChatGPT72%CITEDGoogle AIO68%CITEDPerplexity65%CITEDClaude61%MAYBEBing55%MAYBEYou.com44%MAYBE

Scoring dimensions

GEOGenerative Engine Optimisation
How well your content is structured for AI extraction. Scores clarity, completeness, factual density, and answer-first writing style.
AEOAnswer Engine Optimisation
Likelihood of appearing in direct-answer results. Evaluates FAQ structure, structured data, and featured snippet signals.
EEATExperience · Expertise · Authoritativeness · Trust
Google's quality rater framework as a score. Evaluates author signals, citations, credentials, and site trust.
AI scores consume monthly quota. Check Settings → Billing for your limit.

Fix Packs

A Fix Pack turns selected audit findings into an implementation-ready package: the evidence is locked at creation, one master prompt is generated for AI coding agents, and a fresh crawl verifies whether each finding was actually resolved.

Lifecycle

  • Draft — select findings from a completed audit, manually or via the recommended (high-confidence) selection. Editable while in this state.
  • Locked — evidence, current values, and recommendations are snapshotted. A locked Fix Pack cannot be edited, only re-created. This is also when the master prompt, issue briefs, and Markdown export are generated.
  • Verification — re-run against a fresh crawl. Each finding resolves to implemented, still_present, or not_verified.
A locked Fix Pack is immutable by design — what you handed to your coding agent is exactly what verification checks against, even if a later audit changes the underlying finding.

Verification states

implemented
The finding is no longer observed under the verification rule.
still_present
The fresh crawl still shows the original issue.
not_verified
The page could not be re-checked (fetch error, URL removed, etc).
A verified fix means the technical finding is gone — not that rankings improved, traffic increased, or Google re-indexed the page. Those are separate, measured signals, not implied by verification.

Analytics & metrics

The Analytics page shows indexing velocity, URL status snapshots, quota usage, and monthly activity trends — all derived from server-side event logs with no client-side trackers.

  • Indexing velocity — daily indexed URL count for the last 14 days. Red bars = ≥5% drop (regression alert).
  • Regression detection — flags days where indexed count dropped by 5%+ and shows absolute URLs lost.
  • URL status snapshot — current distribution of all URL statuses for a domain.
  • Monthly quota usage — progress bars for URL submissions, audits, and AI scores vs plan limit.
  • Monthly activity chart — stacked bars of all platform events grouped by month.
  • Metrics snapshots stored up to 90 days for trend analysis.

Google Search Console

GSC integration enables URL inspection and sitemap submission to Google. It is optional but required for Google-specific indexing features.

Connecting GSC

From the Indexing page header, click "Connect GSC". You'll be redirected to Google's OAuth consent screen. We request two scopes only:

  • webmasters.readonly — to inspect URL indexing status
  • webmasters — to submit URLs and sitemaps
  • We do NOT access search performance data, keyword rankings, clicks, or impressions
Each domain needs its own GSC connection. If you have multiple verified domains, connect GSC for each one separately from the Indexing page.

Token security

OAuth tokens are encrypted with AES-256 before storage. They are decrypted only at API call time and are never logged or exposed in plaintext. Revoke access any time from Google Account settings or from the SEOVentra dashboard — tokens are deleted immediately on revocation.

IndexNow & Bing

IndexNow is a free, open protocol supported by Bing, Yandex, and others. SEOVentra uses it automatically — no Bing account or API key required from you.

Your IndexNow key

Every verified domain gets a unique IndexNow key derived from its verification token via a one-way hash. The key is stable and available in Indexing → Indexing Key.

For best results, host your key file at {your-key}.txt — this lets Bing independently verify domain ownership.

Submission endpoints

On every URL and sitemap submission, SEOVentra pings all four endpoints in parallel:

  • www.bing.com/indexnow
  • api.indexnow.org/indexnow
  • yandex.com/indexnow
  • search.seznam.cz/indexnow

Alerts & webhooks

Configure alerts in Settings → Alerts. Each rule pairs an event type with a delivery channel.

Event firese.g. URL indexedAlert rulematches event typeSEOVentrasends one POSTYour endpointprocesses payloadSingle best-effort POST · no signature · no retry

Event types

  • indexing_failed — a job reached max retries
  • indexing_success — a URL confirmed indexed
  • audit_complete — audit finished
  • domain_verified — domain passed verification
  • quota_warning — 80% of a monthly limit reached
  • regression_detected — indexed count dropped ≥5%

Channels

Email
Valid email address — comma-separate for multiple recipients.
Webhook
HTTPS endpoint. POST with JSON payload. Must respond 200 within 10s.
Discord
Discord webhook URL from Server Settings → Integrations.
Telegram
Your Telegram chat ID. Use @userinfobot to get yours.

Webhook payload

json
{
  "event": "indexing_failed",
  "org_id": "org_abc123",
  "domain": "example.com",
  "url": "https://example.com/page",
  "data": {
    "job_id": "job_xyz",
    "attempts": 5,
    "last_error": "GSC inspection returned no result"
  },
  "timestamp": "2026-05-23T10:30:00Z"
}

SEOVentra MCP

SEOVentra MCP is a Model Context Protocol server that lets AI clients — Claude, ChatGPT, Cursor, and Codex — query your Fix Packs, AI-visibility data, and Search Console performance directly, using the same API key you already use for the REST API.

SEOVentra is not yet listed in any client's built-in connector directory. It will not appear if you search for it by name inside Claude, ChatGPT, or Cursor — add it as a custom MCP connector instead (see below).

Connecting

  • Get an API key from Settings → API Keys (available on every paid plan).
  • In your AI client’s connector or MCP settings, add a custom server at the endpoint below.
  • Paste your API key as the connector’s credential.
text
https://api.seoventra.com/api/v1/mcp

Available tools

All 9 tools are currently read-only. None of them trigger a new crawl, a new AI-visibility scan, or a Search Console write — those stay behind their existing, explicitly-triggered dashboard actions.

project.list
Your domains, with verification and GSC connection status.
project.get
One project by id.
fixpack.list
Fix Packs for a domain or the whole org.
fixpack.get
One Fix Pack: findings and, if locked, the master prompt.
geo.visibility
Latest AI-visibility snapshot.
geo.history
Snapshot trend over a date range (max 90 days).
geo.competitors
Tracked AI-visibility competitors.
gsc.performance
Search Console queries/pages for a date range. Requires GSC connected.
gsc.inspect_url
Index status for one URL. Requires GSC connected.
Every call is resolved to your organisation from your API key, server-side — an AI client can never see or query another organisation's data. See the api-mcp reference below for the request/response shape.

API — Authentication

The SEOVentra REST API uses bearer token authentication. Generate keys from Settings → API Keys.

bash
curl https://api.seoventra.com/api/v1/orgs \
  -H "Authorization: Bearer sv_live_your_api_key_here" \
  -H "Content-Type: application/json"

Key scopes

  • read — GET endpoints only; cannot create, update, or delete
  • write — full access to all org endpoints
  • admin — write + admin panel endpoints (internal use)
Never commit API keys to source control. Keys are shown only once — if lost, revoke and regenerate.

Base URL

https://api.seoventra.com

All endpoints are prefixed with /api/v1. All requests and responses use JSON.

Domains API

GET/api/v1/orgs/:orgId/domainsauth▾
POST/api/v1/orgs/:orgId/domainsauth▾
POST/api/v1/orgs/:orgId/domains/:id/verifyauth▾
DELETE/api/v1/orgs/:orgId/domains/:idauth▾

Example: add a domain

bash
curl -X POST https://api.seoventra.com/api/v1/orgs/org_abc/domains \
  -H "Authorization: Bearer sv_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "example.com",
    "projectId": "proj_xyz",
    "verificationMethod": "dns_txt"
  }'
json
{
  "success": true,
  "data": {
    "id": "dom_abc123",
    "verificationToken": "seoventra-verify-9f2c0d41b7e84a6d8c5e1f3a7b2d9046",
    "verificationMethod": "dns_txt",
    "instructions": {
      "type": "DNS TXT Record",
      "name": "@",
      "value": "seoventra-verify-9f2c0d41b7e84a6d8c5e1f3a7b2d9046",
      "instruction": "Add a TXT record to your DNS with name \"@\" and value \"seoventra-verify-9f2c0d41b7e84a6d8c5e1f3a7b2d9046\""
    }
  }
}

Indexing API

POST/api/v1/orgs/:orgId/indexing/submitauth▾
GET/api/v1/orgs/:orgId/indexing/jobsauth▾
GET/api/v1/orgs/:orgId/indexing/statsauth▾
POST/api/v1/orgs/:orgId/indexing/inspectauth▾
POST/api/v1/orgs/:orgId/indexing/processauth▾
GET/api/v1/orgs/:orgId/indexing/historyauth▾
GET/api/v1/orgs/:orgId/indexing/lifecycleauth▾
GET/api/v1/orgs/:orgId/indexing/metricsauth▾
GET/api/v1/orgs/:orgId/indexing/indexnow-keyauth▾
POST/api/v1/orgs/:orgId/indexing/indexnow/sitemapauth▾
POST/api/v1/orgs/:orgId/sitemapsauth▾
GET/api/v1/orgs/:orgId/sitemapsauth▾
DELETE/api/v1/orgs/:orgId/sitemaps/:sitemapIdauth▾

Example: submit URLs

bash
curl -X POST https://api.seoventra.com/api/v1/orgs/org_abc/indexing/submit \
  -H "Authorization: Bearer sv_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "domainId": "dom_abc123",
    "provider": "indexnow",
    "priority": 8,
    "urls": [
      "https://example.com/new-post",
      "https://example.com/updated-page"
    ]
  }'
json
{
  "success": true,
  "data": { "queued": 2, "skipped": 0, "skippedUrls": [] }
}
ParameterTypeRequiredDescription
urlsstring[]YesAbsolute URLs to submit. Max 200. Must belong to the domainId.
domainIdstringYesID of the verified domain the URLs belong to.
providerstringNogsc_inspect (default; Google, needs GSC) or indexnow (Bing + others, no setup). The API also accepts google and bing.
prioritynumberNoJob priority 1–10. Higher = processed first. Default: 5.

Audits API

POST/api/v1/orgs/:orgId/auditsauth▾
GET/api/v1/orgs/:orgId/auditsauth▾
GET/api/v1/orgs/:orgId/audits/:auditIdauth▾
GET/api/v1/orgs/:orgId/audits/:auditId/issuesauth▾
GET/api/v1/orgs/:orgId/audits/:auditId/recommendationsauth▾

Response structure

Abridged response for GET /audits/:auditId. issueStats has one row per severity and category, and aiScore holds the most recent AI score row for the domain.

json
{
  "success": true,
  "data": {
    "id": "audit_abc",
    "domain_id": "dom_abc123",
    "status": "completed",
    "urls_crawled": 148,
    "issues_found": 39,
    "seo_score": 74,
    "speed_score": 71,
    "health_score": 72,
    "started_at": "2026-05-23 10:00:12",
    "completed_at": "2026-05-23 10:04:33",
    "issueStats": [
      { "severity": "critical", "category": "meta", "count": 3 },
      { "severity": "warning",  "category": "og",   "count": 12 }
    ],
    "progress": { "totalPages": 148, "aiPagesScored": 20, "aiPagesPerAudit": 20 }
  }
}

Fix Packs API

POST/api/v1/orgs/:orgId/fix-packsauth▾
GET/api/v1/orgs/:orgId/fix-packsauth▾
GET/api/v1/orgs/:orgId/fix-packs/:packIdauth▾
POST/api/v1/orgs/:orgId/fix-packs/:packId/lockauth▾
GET/api/v1/orgs/:orgId/fix-packs/:packId/artifacts/:typeauth▾
DELETE/api/v1/orgs/:orgId/fix-packs/:packIdauth▾

Verification

POST/api/v1/orgs/:orgId/fix-packs/:packId/verificationsauth▾
GET/api/v1/orgs/:orgId/fix-packs/:packId/verificationsauth▾
GET/api/v1/orgs/:orgId/fix-packs/:packId/verifications/latestauth▾
GET/api/v1/orgs/:orgId/fix-packs/:packId/verifications/:verificationIdauth▾
Verification requires the domain to already be verified. It's also cooldown-limited, and capped per pack and per org per day — the response includes a Retry-After header and the wait time when you hit either limit.
Fix Packs are available on every paid plan. On Free, GET /fix-packs/preview shows what a Fix Pack would contain, without creating one (rate-limited separately).

AI scores API

GET/api/v1/orgs/:orgId/audits/:auditId/ai-scoresauth▾
GET/api/v1/orgs/:orgId/domains/:domainId/ai-monitor/latestauth▾
GET/api/v1/orgs/:orgId/domains/:domainId/ai-monitor/snapshotsauth▾
The per-engine values in engine_scores are model-generated estimates, not measured citations. In a visibility snapshot, visibility_score is the percentage of answered query–engine pairs that mentioned your brand, where each pair is one of the domain's monitoring queries sent to one AI engine. Checks that fail (an engine error or an empty answer) are left out of both total_queries and the score. Read those queries with GET, and replace the whole list (up to 5) with PUT, on /ai-monitor/queries.

Example: latest visibility snapshot

json
{
  "success": true,
  "data": {
    "snapshot_date": "2026-09-19",
    "visibility_score": 40,
    "total_queries": 10,
    "total_mentions": 4,
    "gemini_mentions": 2,
    "groq_mentions": 2,
    "chatgpt_mentions": 0,
    "claude_mentions": 0,
    "perplexity_mentions": 0,
    "gemini_sentiment": 50,
    "query_results": [
      { "query": "best SEO audit tools", "engine": "gemini", "mentioned": true, "sentiment": 0.5, "excerpt": "..." }
    ]
  }
}

URL check API

POST/api/v1/orgs/:orgId/url-checkauth▾

Reuses the same page-level checks as a full audit (meta, schema, headings, links) on a single page, with nothing stored — no domain, audit, or issue rows are created. Counts toward your monthly API call quota, plus its own limit of 10 requests per minute per user.

json
{
  "success": true,
  "data": {
    "url": "https://example.com/pricing",
    "status": 200,
    "score": 78,
    "breakdown": { "meta": 20, "headings": 15, "schema": 18, "links": 25 },
    "issues": [
      { "category": "meta", "severity": "warning", "code": "missing_meta_description", "title": "..." }
    ]
  }
}
Only http/https URLs to a public hostname are accepted — localhost and private/link-local addresses are rejected before any request is made.

MCP endpoint

One endpoint, speaking Model Context Protocol over JSON-RPC 2.0, for connecting SEOVentra to an AI client. See Integrations → SEOVentra MCP above for what it's for and how to connect a client; this section covers the raw request/response shape.

POST/api/v1/mcp▾
Auth is only checked on tools/call — initialize and tools/list respond without a key, matching how MCP clients discover a server's capabilities before a user has necessarily supplied credentials. Send your key as Authorization: Bearer sv_live_... on every tools/call request.

Methods

  • initialize — capability handshake. No auth required.
  • tools/list — returns all 9 tool definitions with their JSON schemas. No auth required.
  • tools/call — invokes one tool by name with arguments. Requires Authorization: Bearer.

Example: tools/call

json
// Request
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "fixpack.list",
    "arguments": { "domainId": "dom_abc123" }
  }
}

// Response
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "isError": false,
    "content": [{
      "type": "text",
      "text": "{\"ok\":true,\"data\":{\"fixPacks\":[...]}}"
    }]
  }
}

The text content is always the tool's structured result — { ok: true, data: {...} } on success, or { ok: false, error: { code, message } } on failure — never prose the caller has to parse.

Webhooks

Configure a webhook endpoint in Settings → Alerts using the "webhook" channel. Alert rules deliver a single POST request with a JSON body to your URL when the rule fires.

Alert rules currently fire for three events: indexing_failed, url_blocked and audit_score_drop. The subject begins with a short status symbol. Example payload for audit_score_drop:

json
{
  "subject": "SEO score dropped — example.com",
  "body": "SEO score for example.com dropped from 82 to 71.\n\nThis may indicate new issues. Run a new audit to see details.\n\nDashboard: https://app.seoventra.com/dashboard/audits",
  "source": "seoventra",
  "timestamp": "2026-09-06T12:00:00.000Z"
}
There is currently no signature header or retry mechanism — delivery is a single best-effort POST with Content-Type: application/json, and a non-2xx or failed response is not retried. If your endpoint needs to verify the sender, restrict it to Cloudflare's egress IP ranges, or treat inbound alert payloads as untrusted input and validate the shape rather than the origin.

Error codes

json
{ "success": false, "error": "Human-readable message", "code": "MACHINE_CODE" }
400Bad RequestInvalid parameters or validation failure. Check the error message.
401UnauthorizedMissing or invalid API key. Include Authorization: Bearer header.
402Plan LimitA plan or monthly quota limit was reached (API calls, audits, URL submissions, domains or API keys). The body has code PLAN_LIMIT_EXCEEDED, and most limit errors also include used, limit and plan.
403ForbiddenValid credentials but insufficient permissions for this resource.
404Not FoundResource doesn't exist or doesn't belong to your organisation.
429Rate LimitedToo many requests. Wait before retrying. Some routes include a Retry-After header (seconds); others do not.
500Server ErrorUnexpected internal error. Retry, or contact support if it persists.
502Bad GatewayUpstream API error (Google, Bing). Usually transient — retry shortly.

Billing & plans

Manage your subscription from Settings → Billing. Payments via Razorpay.

  • Upgrade takes effect immediately with prorated billing.
  • Downgrade takes effect at end of current billing period.
  • Cancellation keeps account active until period end.
  • Usage limits reset on your billing date, not the calendar month.

API keys

Create and manage API keys from Settings → API Keys. Keys are shown only once — store them securely in an environment variable. Revoke compromised keys immediately.

Alert rules

Create rules in Settings → Alerts. Each rule pairs an event type with a channel. Use the "Test" button to verify delivery before relying on it. Rules can be disabled without deletion.

Questions not covered here?
Email support@seoventra.com — we respond in plain language.
System statusView pricing →