Content inventory
6
Pages, posts, categories, and services for iranb.net.
Tenant command center · iranb.net
Operate exactly one website without crossing tenant boundaries.
This dashboard resolves the current admin host to one Sanity site record, then scopes content, commerce, customers, services, SEO, graph, autoblogging, settings, and tenant-safe AI automation to that tenant only. Missing tenant context is shown as configuration work, not network data.
Tenant isolatedDraft-by-defaultShopify read-onlyMeasured vs inferred SEOAudit-aware
Customer pipeline
0
Newsletter subscribers plus lead/contact submissions, with consent metadata.
Commerce controls
1
Tenant product visibility rules; Shopify remains read-only.
SEO intelligence
gated
GSC/GA metrics, backlink recommendations, graph overlays, and reports.
Tenant operating cockpit
From demo panels to a governed website operations OS.
This layer turns the tenant dashboard into an action-led cockpit: provider readiness, editor reality, commerce safety, SEO evidence, and customer posture are visible before operators drill into workstreams.
Operator promise
One tenant, one truth model, no fake zeros, no secret leakage, and no Shopify mutations. If a provider is missing, the UI says so plainly and routes the operator to the next safe step.
Tenant resolver
locked
Host admin.iranb.net resolves to iranb.net.
Provider posture
80% ready
Composite of tenant mapping, Sanity, Shopify, SEO connectors, and published content presence. It is a readiness indicator, not fabricated traffic data.
Commerce safety
read-only live
Storefront source can feed cached products while Shopify writes remain policy-rejected.
SEO evidence
inferred only
Graph and SEO views must label recommendations as inferred until Google connectors are configured.
Edit and preview content
ready pathOpen the embedded Studio/Visual Editing path, verify draft mode, and keep WYSIWYG editor identity inside Sanity instead of leaking tokens to the browser.
Open workspace →
Merchandise without Shopify writes
operationalUse tenant visibility rules, product action modes, enrichment, and catalog freshness while Shopify remains the read-only commerce system of record.
Open workspace →
Grow with measured/inferred labels
honest fallbackSEO QA, internal graph context, and opportunities stay useful while explicitly separating provider metrics from modeled guidance.
Open workspace →
Capture customers safely
scopedSubscribers, leads, service inquiries, and redacted Shopify customer sync policies remain tenant-scoped with consent/source metadata.
Open workspace →
Sanity tokens vs Studio login
Server tokens can operate content; Studio still needs editor identity.
What tokens are for
Authenticated admin APIs can read, create drafts, run diagnostics, seed content, and perform audited server-side Sanity operations without exposing secrets to the browser.
Why Studio login remains
Sanity Studio is a browser editor. It requires a Sanity user session for identity, role permissions, audit attribution, and CORS-safe Visual Editing. A server token must not be used as a browser login substitute.
Best enterprise pattern: keep Studio login for human WYSIWYG editing, and build custom dashboard actions for repeatable server-token workflows like launch seeding, draft generation, diagnostics, and governed bulk updates.
Enterprise implementation blueprint
How this tenant should be improved and operated
Resolve tenant and provider truth
Every module first proves which site and credentials it is allowed to use.
Operate through human workspaces
Users land on action centers, editors, builders, and live tables rather than raw protected API links.
Use Studio where WYSIWYG matters
Sanity user auth remains the correct browser editor model; dashboard tokens remain server-side.
Promote only after QA evidence
Content, SEO, commerce, launch, and production verification signals stay visible before publication.
SDD-005 operating surface
Tenant feature workstreams
Each panel maps to an admin responsibility and opens a human workspace with live state, action controls, guardrails, and the technical contracts behind it. Provider-dependent areas stay clearly marked as needs-configuration or policy-gated.
content
Content studio + Visual Editing
Operate home page, pages, posts, categories, authors, media references, redirects, navigation, and reusable page-builder blocks.
6 content/service records
/api/site-content/api/draft-mode/enable/studioGuardrail: Draft/preview/publish workflows must preserve Sanity source of truth.
Open content workspace →
commerce
Read-only commerce + enrichment
Browse Shopify snapshot data, manage Sanity enrichment, SEO copy, related content, display templates, and sync preferences.
6 enrichments · 1 visibility rules
/api/site-products/api/admin/shopify/visibilityGuardrail: No Shopify product/order/customer mutations from this platform.
Open commerce workspace →
customers
Customers, leads, subscribers
Manage newsletter subscribers, service inquiries, lead status, source attribution, consent metadata, and export readiness.
0 customer-intake records
/api/newsletterleadSubmission schemaGuardrail: Consent/source metadata must remain attached to every record.
Open customer workspace →
services
Services and local business layer
Operate service pages, pricing/CTA strategy, service areas, local metadata, related products/posts/services, and schema fields.
0 services
/api/site-content?type=serviceGuardrail: Service claims must be backed by editable content and accurate schema.
Open services workspace →
seo
SEO analytics and page QA
Track page-level indexing, metadata, canonical, schema, sitemap, CTR, average position, keyword opportunities, and analytics warnings.
0 SEO reports
/api/admin/seo/api/admin/diagnostics/seoGuardrail: Measured GSC/GA signals must be separated from inferred scores.
Open SEO workspace →
graph
Tenant SEO graph intelligence
Visualize pages, posts, products, services, categories, keywords, backlinks, internal links, semantic affinity, and competitor pressure.
0 backlink recommendations
/api/admin/relationships/api/admin/seoGuardrail: Every edge labels impact direction, strength, and evidence type.
Open graph workspace →
content ops
Autoblogging editorial queue
Manage topic clusters, editorial calendar, draft generation queue, duplicate-risk checks, canonical guidance, and refresh recommendations.
0 draft records
/api/admin/autoblog/draftautoblogDraft schemaGuardrail: Draft-by-default; publish requires human approval and final SEO checks.
Open autoblogging workspace →
settings
Settings, routing, feature gates
Control theme tokens, navigation, Visual Editing, URL patterns, shop route mode, and tenant-permitted integration switches.
/api/admin/diagnostics/sanity/api/healthGuardrail: Tenant settings cannot exceed superadmin guardrails.
Open settings workspace →
ai governance
Tenant AI automation controls
Manage allowed agent clients, tenant-scoped tokens, approved workflows, draft-only permissions, and automation logs.
0 clients · 0 logs
/api/agent/gatewayintegrationClient schemaGuardrail: Deny-by-default, scoped credentials, rate limits, and audit trails.
Open AI governance workspace →
Tenant SEO graph intelligence
Graph model for pages, posts, services, products, categories, keyword clusters, internal links, approved cross-site links, backlinks, and competitor pressure. The UI explicitly distinguishes provider-measured signals from inferred influence estimates.
MeasuredInferred
page
Home / money page
mixed
service
Service cluster
inferred
commerce
Product set
mixed
keyword
Priority query
inferred
backlink
Referrer domain
measured
post
Blog support
inferred
Impact semantics
- Positive/negative/neutral impact direction per relationship edge.
- Normalized impact strength for link authority or topical reinforcement.
- Evidence type labels: measured provider metrics vs inferred model scores.
- Time-window drill-down for migrations, campaigns, and content refreshes.
When GSC/GA/backlink providers are not connected, the panel stays honest: it shows the graph contract and configuration gaps instead of pretending measured traffic exists.
Tenant command queue
P0okOwner: platform
Configure Sanity project/environment in Vercel
The dashboard will show real content, lead, SEO, agent, and audit counts as soon as Sanity env vars are present in production.
P0readyOwner: commerce
Connect Shopify read-only source and central snapshots
Required for storefront product feed, product visibility rules, enrichment conflict indicators, and cache freshness panels.
P1missing credentialsOwner: seo
Connect GSC/GA for measured SEO overlays
Until connected, graph panels clearly label opportunities as contract/inferred rather than measured performance data.
P1workspace queuedOwner: admin
Create tenant launch checklist records
Launch readiness should cover content QA, SEO, redirects, domain DNS, visual editing, privacy, monetization eligibility, and verification probes.
Provider truth
Diagnostics and degraded states
These cards are still here, but no longer pretending to be the whole product. They explain exactly why a feature is live, empty, gated, degraded, or missing configuration.
Sanity content
OKRead access to the tenant's published + draft content.
Shopify (read-only)
OKStorefront API snapshot. Writes are policy-rejected (SDD-007).
Google Search Console
Missing credentialsTop queries / indexing health pulled when service account credentials are provided.
- GSC service account credentials not configured
Google Analytics 4
Missing credentialsTraffic and engagement metrics from the GA4 Data API.
- GA4 service account credentials not configured
Products preview
OKLatest 4 Storefront products. Sanity-side enrichment overrides product copy on the storefront.
AreaTenant controlSuperadmin controlStatus
ShopifyVisibility and Sanity enrichmentRead-only source, snapshots, allowed product setslive
AutobloggingBriefs, draft queue, approvalsPrompt policy, duplicate limits, canonical rulespolicy gated
AI agentsDraft-safe tenant workflowsPolicy tiers, kill-switch, budgetspolicy gated
URL modesTenant custom patterns when allowedGlobal presets and ecommerce route modesoperator workspace