How to use DT 1.5

Start here

Your first 10 minutes

1. Create or select a store.The store shown in the sidebar controls the website, connections, reports, tasks, and approvals you see.
2. Open Connections.Add the website first. Connect Shopify if DT should apply supported changes, and Search Console if you want search-performance evidence.
3. Open Run Audit.Enter the public website address and run a read-only scan. The scan does not change the site.
4. Read the report.Confirm the evidence matches the right page before asking DT to prepare a fix.
5. Ask the Assistant for one outcome.For example: “Use this audit to draft the highest-impact supported SEO fix.”
6. Review Approvals.Compare the current value, proposed value, destination, and verification plan. Approve only when they are correct.
7. Check Task Queue and Overview.These show whether work is waiting, blocked, applied, verified, or needs your input.

Orientation

What each dashboard area does

If you manage more than one store, always check the store name in the sidebar before reviewing or approving work.

Ask for work

Use the Assistant in plain language

Tell DT the business result you want, not the name of a technical patch. It will use the selected store’s available website evidence, saved facts, connections, and prior work.

How to get a stronger answer

• Name the product, audience, country, goal, and important limits.
• Say whether DT may only analyze, may draft work, or may prepare an approval.
• Ask it to use a saved report or connected data instead of guessing.
• When the evidence is incomplete, provide the missing owner facts or ask DT to wait.

SEO and AI search

Run and read a website audit

Open Run Audit, confirm the exact public hostname, and start the scan. DT reads reachable public pages and records evidence such as titles, descriptions, headings, canonicals, structured data, robots rules, sitemap signals, and crawler access.

1. Confirm scope.Use the canonical customer-facing website, not an admin address or preview theme.
2. Check the page evidence.A summary can hide page-level differences. Open the affected URL and verify what DT found.
3. Separate missing from incorrect.An empty heading, duplicate schema block, and missing schema block require different fixes.
4. Do not guess business facts.Currency, address, phone, legal name, price, and availability must come from the owner or a trustworthy connected source.
5. Save useful evidence.Reports give later recommendations and measurements a stable starting point.

Ongoing work

Set up Continuous SEO

Continuous SEO turns a one-time scan into a monitored workflow. It checks available evidence on a schedule, keeps new findings separate from older work, drafts eligible proposals, and measures supported changes when Search Console data is available.

1. Open Continuous SEO.The setup panel shows completed, blocked, and optional dependencies.
2. Connect the needed sources.A website is required for public checks. Shopify enables supported writes. Search Console enables search-impact measurement.
3. Add visibility queries.Track real branded and buyer questions. Avoid stuffing the same phrase into website copy.
4. Review each new finding.Use its source, affected page, evidence, and proposed next action.
5. Measure after a change.Search data is delayed. DT should label results as evaluating, inconclusive, improved, declined, or invalidated rather than claiming an instant win.

Use Pause to stop scheduled checks. Pausing monitoring does not undo approved work or erase the activity record.

Human control

Review Approvals and Task Queue

Approvals contains exact changes waiting for a decision. Task Queue contains the wider work history, including blocked and completed items.

Data and permissions

Connect only what the job needs

Connected execution

Apply supported Shopify changes

Connect the permanent myshopify.com store through Connections. DT matches the audited public hostname to that authorized store before any write.

1. Audit the public storefront.This records the current value and target page.
2. Draft an eligible fix.The proposal must include a known before value, proposed after value, and supported destination.
3. Approve the exact payload.Changing the proposal requires a new approval.
4. Recheck the store.DT verifies ownership, permission, and current state before writing.
5. Read back the result.The task records whether the expected public value appeared.

Current automated SEO execution is deliberately narrow. Eligible homepage metadata and complete sitewide Organization or WebSite structured data can use the supported Shopify path. Catalog-wide, theme-specific, content-page, and unsupported changes remain precise review-ready instructions unless the dashboard states otherwise.

For a non-Shopify website, save its platform in Connections. DT can audit it and prepare a ready-to-paste patch, but it will not pretend to have a universal write connection.

Answer engines

Check AI visibility without confusing a signal for proof

Use the Assistant or Continuous SEO to track questions people may ask about the brand, product, location, or category. The result should name the source used, preserve uncertainty, and turn supported gaps into specific proposals.

• Use branded questions to test whether the business identity is understood.
• Use buyer questions to check whether relevant pages answer real demand.
• Connect a supported live answer source when the Connections page offers it.
• Verify suggested identity copy against the website and owner-confirmed facts.
• Measure mentions and citations over time; do not treat one response as a universal result.

Advertising

Prepare advertising without accidental spend

Start in Launch Ads. Describe the business and campaign in ordinary language. DT chooses among supported structures only after it has enough information to make a safe proposal.

1. Save the brief.DT records assumptions and identifies missing launch inputs.
2. Finish setup in Ad Manager.Confirm the exact account, campaign objects, tracking, limits, and provider capability.
3. Review the approval.The campaign plan, budget, assets, targeting, and destination should be understandable before creation.
4. Create paused.Supported connected providers receive an approved campaign in a non-spending state. Otherwise DT provides a provider-ready handoff.
5. Activate separately.Going live requires its own deliberate provider action or approval. The ad platform bills the advertiser directly.
6. Evaluate with real outcomes.Ad Manager separates provider attribution from backend-verified revenue and blocks confident optimization when tracking is unreliable.

Proof and recovery

Read results and work history

• Overview shows current blockers, work in progress, and the latest recorded changes.
• Reports stores scan evidence and findings.
• Task Queue shows the state of proposed and completed work.
• Ad Manager’s Activity tab records advertising actors, timestamps, before and after values, approvals, provider responses, and evaluation states where available.
• Continuous SEO compares supported search measurements after enough reporting delay.
• Ad Manager shows account context, tracking health, attributed outcomes, verified outcomes, recommendations, and recent actions.

When another person or provider changes the same object, DT should mark the evaluation or rollback as conflicted instead of overwriting the newer state.

Workspace safety

Manage more than one store

1. Add each business separately.Use Add a store instead of reusing one workspace for unrelated clients.
2. Connect accounts to the matching store.Do not reuse one client’s Shopify, Search Console, tracking, or ad account connection for another.
3. Check the active store before acting.The sidebar selection controls the Assistant, reports, queue, approvals, settings, and advertising context.
4. Keep facts store-specific.Goals, margins, locations, brand rules, and approvals should not leak across businesses.

Product truth

What DT 1.5 will not do

• It will not guarantee rankings, traffic, AI citations, revenue, or campaign performance.
• It will not change an unconnected website or advertising account.
• It will not treat a model’s prose as permission to spend money or publish a change.
• It will not invent an address, phone number, currency, price, margin, or other owner fact.
• It will not report a provider request as successful without the available execution evidence.
• It will not safely auto-apply a task when the current value, target, capability, permission, or approval is stale.

A clear blocked state is safer than a confident but unsupported action.

When something stops

Troubleshooting