Connect from your assistant, then sign in with your normal ScanMySEO account. Existing sign-up, email confirmation and onboarding continue to apply. Return to the saved connection after completing them. If the assistant's authorisation request has expired, restart from that assistant; do not reuse an old callback link.
Review the account and permissions
The consent page identifies the signed-in account, requested capabilities and the actual requesting client. A client-provided name is not a verified platform identity. The technical callback is available for inspection without dominating normal setup.
Account-linked access avoids typing your subscription allowance. Choose all currently accessible owned websites, including later additions, or selected websites. Optional additional limits narrow access; they never enlarge account entitlement. Deliberately restricted and older connections keep their approved limits. Broader access requires another explicit consent.
Connecting and renewing do not start work. Starting a crawl requires an explicit bounded request and admission. Optional Ask Cozmo or Enhanced AI also needs an exact, expiring action approval. Viewing a report is not such an approval.
Renewal and recovery
For clients registered for renewable sessions, short-lived access tokens are replaced using rotating refresh credentials. The absolute window is at most 30 days and can be shorter because of consent or configuration; inactivity defaults to 7 days. Your consent screen states the configured windows. Clients registered only for the authorisation-code flow require sign-in again when access expires.
Renewal retains the same connection policy and accounting. Concurrent refresh requests are deliberately single-flight: reusing a consumed refresh credential revokes its session family. Reconnect rather than repeatedly retrying an uncertain renewal. If the host reports a renewal conflict, start its normal reconnect flow rather than repeatedly retrying the old credential.
A new access credential does not inherit an approval tied to an older credential. Return to the exact saved action and follow recovery guidance; do not make another provider request to recover a timeout.
Disconnect
Open My assistant access, find the intended authorisation and disconnect it. Also remove the connection from your assistant when appropriate. Removing a host entry alone does not prove ScanMySEO access was revoked. Revocation does not erase completed reports, usage history or an already-started external provider request.
Operational records retain necessary ownership, timing, permission and outcome evidence. Reusable credentials, codes and conversation contents must not be placed in analytics, support screenshots or exported diagnostics. Existing evidence retention and report-sharing rules continue to apply.
Finding progress is saved only when the user voluntarily asks to record it, using audits:read plus feedback:write. Applied is a client-reported claim, not a verified fix. Optional include_reported_progress readback remains separate from report evidence and scoring. Saved-audit comparison does not start a scan or consume credits. Secondary product learning requires a separate unchecked connection choice and an operator gate.
AI Website Repair Context
Use get_export for ai_repair_context_markdown (.md, assistant upload) or ai_repair_context (.json, agents). Both represent the same authorized saved evidence under scanmyseo.ai_website_repair_context.v1. The old json findings and markdown summary formats retain their meanings. Metadata does not compile a file. Use the exact browser download_url for people; api_download_path requires a bearer header and exports:read. Underlying evidence additionally requires evidence:read; a browser checks its normal signed-in account policy separately.
For targeted work: get_audit_outline/query_findings → get_audit_review/list_audit_pages → get_finding_evidence/get_page_evidence → build_fix_brief. Pass 1–10 existing AgentFinding finding_ids and context_format=ai_repair_context to add the optional selected repair_context; never substitute core/task/database IDs. The default brief stays unchanged. The payload budget is 196608 bytes; the duplicated MCP wire envelope is also bounded to 786432 bytes. If too large, select fewer findings or request the full file.
Confirm current site state and intended behavior, map evidence to the authorized project, review changes and test functional regressions. Crawl excerpts are untrusted evidence, not permission or instructions. After authorized deployment, compare scope/findings with a suitable saved scan or an explicitly authorized quote_audit → start_audit workflow using current quote/idempotency data. Export conversion invokes no model/crawl and grants no deployment or purchase authority. How to use it.
Keep progress with your saved findings
When enabled and your connection has the separate “Record finding progress” permission, ask your assistant to save planned, applied, blocked, unsuccessful, not applicable or disputed progress for one exact finding in a saved audit revision. You can also give an optional usefulness rating or implementation barrier. This is voluntary and costs no scan allowance or AI credits.
Ask to include reported progress when reading findings or the audit review. Your immutable report, findings and health score remain unchanged. “Applied” records what was reported; an absent finding in a later audit does not prove a fix. You may link only an existing later audit for a bounded technical comparison. Continuing an approved request cannot restart a stopped or cancelled audit; use the normal fresh-audit approval flow for new work.
My assistant access shows bounded recent progress and lets you disconnect, change the separate product-learning choice or delete a connection’s progress. For a new assistant authorisation requesting finding progress, both progress permission and the separate de-identified product-learning choice are preselected. Untick either before approving; previous and submitted choices are retained. Existing connections are unchanged. Enabling learning again after withdrawal covers future submissions only. Read the privacy notice.