SEO audit model
Yasnora SEO audits public HTTPS sites and stores timestamped runs, affected pages, findings and recommendations. Use it to prioritize evidence-backed technical fixes.
Projects, runs and evidence
Yasnora SEO audits public HTTPS sites and stores timestamped runs, affected pages, findings and recommendations. Use it to prioritize evidence-backed technical fixes.
Only public HTTPS targets are allowed; private and metadata destinations are blocked, including after redirects. Search submission requests crawling and never guarantees indexing, ranking or traffic. Current allowances are in Plan & Usage.
Allowance and eligibility
Plans define eligible capabilities and usage allowances. Role, workspace policy and available runtimes still apply even when a feature is included in your plan.
Guest, Free, Pro, Business and Enterprise describe different access levels. Exact prices and quotas belong to the live catalog; this guide is not a contractual offer. WICSAI_*_QUOTA_* indicates a plan or policy limit.
Professional portfolio and reports
The Professional tab compares authorized sites using coverage-qualified saved evidence. Owners may grant viewer, contributor or approver access only to an active account in the same tenant. Sharing an SEO project does not grant repository access, publication or search-submission authority.
Client reports freeze the evidence, date, limitations, work state, verified outcomes and next actions. Schedules begin inactive and deliver to the private Yasnora feed. Personal billing and quota never pool through sharing. Optional capability cards distinguish available, ready-to-connect, foundation-ready and authorization/license-required states. Search connections are read-only and property-scoped. Performance diagnostics require consent and bounded usage. Isolated rendering is available to paid audits for up to three pages and keeps source/rendered evidence separate. Licensed rank/competitor data, measured AI visibility and conversion/revenue analytics remain unavailable until their separate data, attribution and budget gates are complete.
AEO, GEO and measured AI visibility
AEO and GEO inspect bounded, versioned source-HTML evidence from saved audits. Each check shows an observation, excerpt or count, partial coverage and review guidance. Old snapshots without collected evidence show N/A; a new audit uses the existing plan allowance.
A question heading or paragraph does not prove a supported answer. Author/date markers and source links do not prove freshness, factual truth or independent authority. Unsupported semantic and cross-page checks remain N/A. No combined readiness score is provided.
Save review candidates to existing opportunities, then prepare private Content revisions and use the existing approval workflow. Manual completion is not proof of improvement; no website is published automatically.
Measured AI visibility is separate: mentions, citations and sample size stay N/A without an authorized reproducible response sample. Crawling, schema and web-search results do not measure AI inclusion. Readiness supports editorial review; it does not certify semantic truth or guarantee search outcomes.
Versioned source evidence
Readiness uses source-readiness.2026-10-19.v1 separately from the technical html-v3 evaluator. It stores bounded excerpts, counts, a source-text hash and coverage alongside the selected audit. Old, failed, redirected or truncated evidence does not acquire readiness. Historical views keep their original audit; absent evidence never falls back to a newer run.
Literal observations are not semantic truth, independent authority or translation equivalence. Those judgments require an editor. Missing compatible data and measured AI-visibility samples stay N/A; no combined readiness score is generated.
Crawler, queue and provider boundaries
Public-network validation applies to DNS answers, redirects and renderer subrequests. Private and metadata destinations, oversized bodies and unbounded runs are blocked. Crawled text, structured data and provider output are untrusted evidence and cannot issue tool instructions or expand permissions.
Durable jobs revalidate tenant, project, property and allowance, fence workers and settle recorded usage atomically. Cancellation and retry preserve partial or unknown outcomes. An uncertain external write must not be replayed automatically.
Search imports use the adapter’s minimal read scopes and exact permitted property. Submissions require separate write consent. Revocation, disabled adapters and operator kill switches prevent new actions; a provider connection is not a license for paid rank, competitor or AI-visibility data. Retained reports remain historical evidence.