Skip to content
Sign inAccountFree ARC Scan
ARC Remediation · evidence to implementation

Fix the break. Record the closure.

ARC finds the problem, shows the evidence, defines the remediation and helps your team move from an approved fix to a verified result. Supported work is scoped to the actual findings and capability boundaries.

Start with a Free ARC ScanWhat ARC tests
From evidence to verified closureARC Remediation / agreed work
  1. 01
    Review

    Understand the original finding.

  2. 02
    Agree

    Define scope and ownership.

  3. 03
    Improve

    Implement the agreed change.

  4. 04
    Retest

    Rerun the relevant supported test.

  5. 05
    Verify

    Record whether the original condition is resolved.

Closure requires retest evidence. This process does not imply that remediation or verification has already occurred.

Already have an ARC Report?

Start with the findings you want to fix.

In your paid website report, choose Review Remediation Options to inspect supported services and server-priced totals. For Commerce findings or work needing specialist scope, contact Hoshiro to agree the evidence, access and deliverables first.

Open my reportsDiscuss ARC Remediation ↗

A proposal records scope, exclusions, eligible benefits and final terms before you accept. A recommendation alone does not authorize changes.

Remediation map

Every category has a clear next action.

Recommendations are grounded in what ARC observed. They are not a promise of unsupported implementation.

01Automatically executable

AI crawler accessibility

Make important pages and resources accessible to the systems that need to inspect them.

Review category

What it coversCrawl directives, indexability, reachable page paths and public resources.

Typical ARC findingsBlocked pages, inconsistent robots rules or important content that is invisible to an agent crawler.

Example remediationUpdate crawl rules, repair internal paths and expose the relevant public content.

What you may need to provideConfirm the intended public scope and any pages that must remain private.

Scope, approval and pricingThe category boundary above indicates the expected execution path. Final scope and pricing depend on the confirmed findings, applicable tests, access, specialist input and any approval required before implementation.

Retest and Verified ClosureAfter approved remediation, ARC reruns the same relevant test where supported and records the resulting closure status.

02Needs your context/access

Structured data and entity understanding

Clarify the business, offer, location and relationships machines need to interpret.

Review category

What it coversStructured data, page semantics, offers, locations, people and business relationships.

Typical ARC findingsMissing or contradictory schema, ambiguous entities or content that cannot be reliably associated with the business.

Example remediationAlign structured data and visible content, then validate the resulting entity relationships.

What you may need to provideProvide authoritative business facts, identifiers, locations, offers and ownership details.

Scope, approval and pricingThe category boundary above indicates the expected execution path. Final scope and pricing depend on the confirmed findings, applicable tests, access, specialist input and any approval required before implementation.

Retest and Verified ClosureAfter approved remediation, ARC reruns the same relevant test where supported and records the resulting closure status.

03Requires approval

Business identity and trust

Resolve inconsistent facts and missing proof that can make a business difficult to identify or trust.

Review category

What it coversIdentity signals, contact details, policies, reputation evidence and consistency across important surfaces.

Typical ARC findingsConflicting business facts, unclear ownership, missing policies or weak evidence for important claims.

Example remediationCorrect approved business information and strengthen the evidence a customer or agent can verify.

What you may need to provideConfirm the authoritative facts and approve changes to claims, policies or third-party profiles.

Scope, approval and pricingThe category boundary above indicates the expected execution path. Final scope and pricing depend on the confirmed findings, applicable tests, access, specialist input and any approval required before implementation.

Retest and Verified ClosureAfter approved remediation, ARC reruns the same relevant test where supported and records the resulting closure status.

04Needs your context/access

Agent actionability and conversion readiness

Improve the path from a useful answer to the next action, subject to the systems and permissions involved.

Review category

What it coversCalls to action, forms, booking or purchase paths, APIs and the hand-off from intent to action.

Typical ARC findingsDead ends, unclear next steps, inaccessible forms or actions that do not match the surrounding promise.

Example remediationClarify action labels, repair the journey and connect supported actions to the right system.

What you may need to provideProvide test accounts, workflow rules, API details or approval for transactional changes.

Scope, approval and pricingThe category boundary above indicates the expected execution path. Final scope and pricing depend on the confirmed findings, applicable tests, access, specialist input and any approval required before implementation.

Retest and Verified ClosureAfter approved remediation, ARC reruns the same relevant test where supported and records the resulting closure status.

05Automatically executable

Agent-oriented discovery

Organise documentation and discovery surfaces so relevant capabilities can be found and understood.

Review category

What it coversNavigation, documentation, capability descriptions, llms.txt and machine-readable discovery surfaces.

Typical ARC findingsImportant capabilities buried in the site, inconsistent terminology or documentation that does not explain the next step.

Example remediationReorganise discovery content and align terminology across the surfaces agents use.

What you may need to provideConfirm the capabilities, audiences and priority journeys the business wants to expose.

Scope, approval and pricingThe category boundary above indicates the expected execution path. Final scope and pricing depend on the confirmed findings, applicable tests, access, specialist input and any approval required before implementation.

Retest and Verified ClosureAfter approved remediation, ARC reruns the same relevant test where supported and records the resulting closure status.

06Specialist review required

Technical crawl and content accessibility

Address crawl, rendering and content delivery failures that interrupt the agent journey.

Review category

What it coversRendering, performance, redirects, content delivery, technical errors and compatibility with supported crawlers.

Typical ARC findingsClient-side-only content, failed redirects, slow or unstable responses, or rendering failures that hide evidence.

Example remediationRepair the technical delivery path or produce a bounded specialist implementation plan.

What you may need to provideProvide platform details, staging access and a technical owner where the change is not safely public-facing.

Scope, approval and pricingThe category boundary above indicates the expected execution path. Final scope and pricing depend on the confirmed findings, applicable tests, access, specialist input and any approval required before implementation.

Retest and Verified ClosureAfter approved remediation, ARC reruns the same relevant test where supported and records the resulting closure status.

ARC lifecycle

Finding to evidence-backed closure.

Only purchased and agreed scope is implemented. A finding is not an instruction to change a production system, and platform-specific work is never assumed to be automatic.

01Find

ARC identifies the issue.

02Recommend

Evidence and a likely fix are mapped.

03Agree scope

Proposal and SOW define the work.

04Kick off

Deposit and access apply only where agreed.

05Implement

Code, configuration or CMS changes are recorded.

06Retest

The same target outcome and evidence are checked again.

Start with evidence

Find the highest-value break first.

A Free ARC Scan establishes the bounded starting point. Deeper remediation follows the findings and the access available.

Run a Free ARC Scan