DT 1.5 audits a public storefront, keeps the supporting evidence, drafts only supported fixes, waits for merchant approval, and verifies eligible Shopify writes against the public result.
DT separates what it observed, what it recommends, what a merchant approved, what a provider accepted, and what the public storefront shows afterward.
The audit reads reachable HTML, titles, descriptions, headings, canonical URLs, social metadata, structured data, robots.txt, crawler rules, and sitemap signals. It records the URL and scan time. It is not Googlebot and cannot see a search engine's private systems.
Storefront observations, connected-provider data, merchant-confirmed facts, inferred context, and unknown values stay separate. An inference cannot silently replace a merchant-confirmed fact.
A recommendation becomes an executable draft only when its target, current value, proposed value, destination, and supported write surface are known. Everything else remains guidance or a review-ready patch.
Passing a technical check means that specific implementation is present. It does not prove rankings, traffic, AI citations, sales, or future crawler behavior.
Read the current public store and save the evidence.
Prepare a bounded fix from known store facts.
Lock the exact before and proposed after state.
Match the audited hostname to one authorized store.
Recheck authority and current state before the write.
Read the affected public surface and record the result.
Technical access, entity clarity, and structured content can be checked. Search engines and AI providers still decide what they crawl, index, rank, quote, or cite. Connected AI-answer scans are directional snapshots, not guaranteed consumer-app results.
The current automated executor is limited to eligible homepage metadata and complete sitewide Organization or WebSite data on the exact connected store. Catalog-scale and unsupported changes remain review-ready patches.
Planning, account preflight, policy checks, and paused creation depend on the connected provider, permissions, tracking, business facts, and safety limits. Sending a request is not treated as a completed provider action; read-back is required where supported.
MGO Data will publish research only after the collection date, sample, method, definitions, limitations, findings, and update history are ready. Planned topics are not results, and client data is not public evidence without permission.
Run one live, read-only scan before creating an account or connecting Shopify.
Audit my Shopify store