AISEO SiteFROM CHECKS TO RECORDS TO VERIFICATION
Trace every SEO action
back to its evidence.
Search data shows where to investigate. Page checks provide another kind of evidence. The workspace keeps both alongside human judgment, separating changes, delivery and later observations.
Open the SEO operations workspace →A complete evidence, action and verification workflow
- Read a final window from a permitted property. Save its scope and original data; use exact-page or joint dimensions to connect pages and queries.
- Check page responses, canonical, language or content sources. Save the check and human review.
- Turn a specific finding into a candidate issue. Record evidence level, priority, assignee and actual changes.
- Verify delivery, Google’s saved index version and later search performance separately. Keep unknown states when evidence is missing.
Working capabilities and boundaries
| Task | How to use it | What it does not establish |
|---|---|---|
| Search evidence | Save snapshots, exact pages, joint query/country/device/date scopes and rule candidates. | Hidden queries may be omitted; changes do not prove causes. |
| Technical checks | Check HTTPS redirects, XML, static canonical, meta, hreflang, JSON-LD and bounded internal-link crawls. | No JavaScript rendering; not a full-site or Google crawl. |
| Content and intent | Register existing pages, real sources, page/query exports, human topics and revision history. | No bulk SEO generation or publishing. |
| International SEO | Map actual equivalent language versions and missing/draft/published states; check static groups. | Country is not language; missing versions are not filled automatically. |
| AI search records | Save verifiable answers, models, timestamps, scopes and citations; connect GA4 referrals separately. | Human samples are not platform rankings; referrals are not answer appearances. |
| Teams and reports | Invite editors/viewers by workspace and site, record tasks, generate weekly/monthly reports and branded print PDFs. | Invites do not transfer Google tokens; report generation does not imply fresh reads. |
| Business jobs | Queueing, idempotency, claims, recovery, backoff, cancellation and in-app reminders. | Schedules require the worker; in-app notification does not establish email delivery. |
Start with access and data
Signing in does not charge you; payment requires explicit Stripe confirmation. The current plan remains USD 9/month, daily email covers one selected site and AI retains its existing allowance. Workspaces, tools and jobs do not automatically create a new plan or charge. Separate engineering budgets apply; availability follows actual access in the interface.
Owners manage sites and invitations, editors work on assigned sites and viewers read only. Administrator inspection does not grant team membership. Client reports, samples, snapshots and temporary checks remain private: excluded from sitemap and public visitor analytics.
Read data and security →When should a result stay unknown?
- When property access, GA4 permission or an external service is unavailable, do not substitute demo values.
- A crawl budget stop is partial; an old inspected index version does not prove that the latest revision is indexed.
- After a recent edit or with small samples, do not interpret short-term movement as confirmed impact or guarantee rankings, conversion or indexing.