Menu

Agent readiness report

accountingstrategiesgroup.com

What an AI agent can and cannot do on this site, measured by an unauthenticated crawl and scored against the published rubric.

Scanned · rubric v1.0.1 · scored as a general site · re-scan (results are cached for seven days)

What to fix first

Ranked by impact first, then by how cheap the fix is — the same ordering the engine uses.

  1. 1C1

    Form usability

    High impact · Medium effort

    No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.

  2. 2B1

    JSON-LD present and valid

    High impact · Medium effort

    Only 2 of 6 crawled pages carry structured data. Add it at the template level rather than page by page.

  3. 3C4

    Machine endpoints and agent manifests

    High impact · High effort

    No machine-readable endpoint of any kind. Most sites score zero here, which is exactly why it is the cheapest differentiation on this rubric: an agents.json is a static file, and a documented read-only API is usually a subset of something you already run.

  4. 4D2

    Verifiable identity

    Medium impact · Low effort

    Fix: no contact page or mailto link found; no Organization schema. sameAs links to a company profile are how a model corroborates that you are who the page says you are.

  5. 5D3

    Policies discoverable

    Medium impact · Low effort

    Fix: no terms page linked.

Every check, with the evidence

No finding without evidence: each result shows what we actually captured during the crawl.

ADiscovery & access

  • A1Pass

    robots.txt exists and parses

    2/2
    What we captured
    {
      "groups": 1,
      "status": 200,
      "sitemaps": 1
    }
  • A2Pass

    Major AI crawlers allowed

    6/6
    What we captured
    {
      "of": 6,
      "allowed": 6,
      "blocked": []
    }
  • A3Pass

    XML sitemap valid and referenced

    3/3
    What we captured
    {
      "exists": true,
      "urlCount": 11,
      "referencedInRobots": true
    }
  • A4Partial

    llms.txt present

    3/4

    Add an llms-full.txt containing your key content as one markdown document. Agents that need the substance can then read it in a single fetch instead of a dozen.

    What we captured
    {
      "present": true,
      "llmsFullTxt": false,
      "describedLinks": 11
    }
  • A5Pass

    Bot user-agent HTTP health

    3/3
    What we captured
    {
      "probes": [
        {
          "name": "GPTBot",
          "status": 200,
          "ttfbMs": 22
        },
        {
          "name": "ClaudeBot",
          "status": 200,
          "ttfbMs": 19
        },
        {
          "name": "PerplexityBot",
          "status": 200,
          "ttfbMs": 13
        }
      ],
      "medianTtfbMs": 19,
      "edgeBlockingDespiteRobots": false
    }
  • A6Pass

    No hard interstitial

    2/2
    What we captured
    {
      "markers": []
    }
  • A7Pass

    Server-rendered content parity

    5/5
    What we captured
    {
      "ratio": 1,
      "rawTextLength": 4763,
      "renderedTextLength": 1477
    }

BUnderstanding

  • B1Partial

    JSON-LD present and valid

    3/5

    Only 2 of 6 crawled pages carry structured data. Add it at the template level rather than page by page.

    What we captured
    {
      "pagesCrawled": 6,
      "pagesWithValidJsonLd": 2,
      "homepageHasValidJsonLd": true,
      "pagesWithInvalidJsonLd": 0
    }
  • B2Pass

    Correct schema types for the site type

    5/5
    What we captured
    {
      "matched": [
        "FAQPage"
      ],
      "missing": [],
      "siteType": "other",
      "typesFound": [
        "Answer",
        "FAQPage",
        "GeoCoordinates",
        "LocalBusiness",
        "OpeningHoursSpecification",
        "PostalAddress",
        "Question",
        "WebSite"
      ]
    }
  • B3Partial

    Semantic HTML structure

    1/4

    Headings and landmarks are how a machine builds an outline of the page. One h1, no skipped levels, and real main/nav/footer elements — all template-level fixes, applied once.

    What we captured
    {
      "problems": [
        "https://accountingstrategiesgroup.com: missing footer",
        "https://accountingstrategiesgroup.com/make-a-payment: missing footer",
        "https://accountingstrategiesgroup.com/accounting-firm: missing footer",
        "https://accountingstrategiesgroup.com/consulting-firm: missing footer",
        "https://accountingstrategiesgroup.com/tax-service-letter: missing footer",
        "https://accountingstrategiesgroup.com/financial-resources: skipped heading level",
        "https://accountingstrategiesgroup.com/financial-resources: missing footer"
      ],
      "singleH1": 6,
      "allLandmarks": 0,
      "pagesCrawled": 6,
      "noSkippedLevels": 5
    }
  • B4Partial

    Meta and Open Graph

    2/3

    Fix: 1 description(s) outside 50–160 characters.

    What we captured
    {
      "goodTitles": 6,
      "pagesCrawled": 6,
      "uniqueTitles": true,
      "goodDescriptions": 5,
      "completeOpenGraph": 6
    }
  • B5Partial

    Clean text ratio

    2/3

    Visible text is 6.2% of your markup. Deeply nested wrapper elements make a page expensive to parse and dilute the content an agent extracts. Script and style contents are already excluded from this measure, so this is markup weight, not framework overhead.

    What we captured
    {
      "perPage": [
        0.052,
        0.038,
        0.044,
        0.048,
        0.032,
        0.16
      ],
      "averageRatio": 0.062
    }
  • B6Pass

    Alt text coverage

    2/2
    What we captured
    {
      "withAlt": 24,
      "coverage": 0.92,
      "contentImages": 26
    }
  • B7Pass

    Canonical and duplication hygiene

    3/3
    What we captured
    {
      "hostVariants": [
        {
          "url": "https://www.accountingstrategiesgroup.com",
          "status": 200
        },
        {
          "url": "http://accountingstrategiesgroup.com",
          "status": 301,
          "location": "https://www.accountingstrategiesgroup.com/"
        }
      ],
      "pagesCrawled": 6,
      "selfConsistentCanonicals": 6
    }

CActionability

  • C1Partial

    Form usability

    3.67/6.11

    No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.

    What we captured
    {
      "formsFound": 0
    }
  • C2Fail

    Navigable link graph

    0/4.89

    Fix: 1 clickable element(s) that are not anchors — an agent cannot follow a div; 17% of links use contextless text like "click here"; no breadcrumbs or clear URL hierarchy.

    What we captured
    {
      "anchors": 115,
      "genericLinks": 19,
      "genericRatio": 0.17,
      "hasBreadcrumb": false,
      "clickableNonAnchors": 1
    }
  • C3Partial

    Interactive element semantics

    2.44/4.89

    Fix: 1 element(s) act as buttons without being buttons. A div with a click handler is invisible to anything driving the page programmatically.

    What we captured
    {
      "realButtons": 7,
      "positiveTabindex": 0,
      "clickableNonButtons": 1,
      "keyboardTrapsTested": false
    }
  • C4Fail

    Machine endpoints and agent manifests

    0/6.11

    No machine-readable endpoint of any kind. Most sites score zero here, which is exactly why it is the cheapest differentiation on this rubric: an agents.json is a static file, and a documented read-only API is usually a subset of something you already run.

    What we captured
    {
      "found": []
    }
  • C5Not applicable

    Commerce actionability

    0/4

    Not a commerce site; these points are redistributed across C1–C4.

    What we captured
    {
      "siteType": "other"
    }
  • C6Fail

    On-site search

    0/3

    No on-site search found. If you have search, expose it as a GET form with a query parameter so an agent can jump straight to results.

    What we captured
    {
      "searchForm": false,
      "searchAction": false
    }

DTrust & freshness

  • D1Pass

    Transport security

    4/4
    What we captured
    {
      "hsts": true,
      "tlsValid": true,
      "mixedContentReferences": 0
    }
  • D2Fail

    Verifiable identity

    0/4

    Fix: no contact page or mailto link found; no Organization schema. sameAs links to a company profile are how a model corroborates that you are who the page says you are.

    What we captured
    {
      "sameAsCount": 2,
      "contactDiscoverable": false,
      "hasOrganizationSchema": false
    }
  • D3Partial

    Policies discoverable

    2/4

    Fix: no terms page linked.

    What we captured
    {
      "hasTerms": false,
      "siteType": "other",
      "hasPrivacy": true,
      "hasReturns": true,
      "hasShipping": false
    }
  • D4Partial

    Freshness signals

    1/4

    Fix: only 9% of sitemap URLs modified in the last 90 days; no visible dates on content. Staleness is a ranking signal for models deciding what to cite.

    What we captured
    {
      "sitemapUrls": 11,
      "withLastmod": 11,
      "visibleDates": false,
      "modifiedLast90Days": 1
    }
  • D5Partial

    Identity consistency

    1/3

    Fix: site name differs across title, og:site_name and schema name. An unexplained name mismatch reads as a signal the site may not be what it claims.

    What we captured
    {
      "title": "Financial Services and Accounting Firm | Preston, MD",
      "hasFavicon": true,
      "hasOgImage": true,
      "ogSiteName": "",
      "schemaName": "Accounting Strategies Group, LLC"
    }
  • D6Fail

    security.txt

    0/2

    Publish /.well-known/security.txt with a Contact field and a future-dated Expires field. It is a five-line text file.

    What we captured
    {
      "status": 404,
      "present": false
    }
  • D7Pass

    Multi-page stability

    4/4
    What we captured
    {
      "nonOk": [],
      "slowPages": 0,
      "pagesCrawled": 6,
      "consistentTemplate": true
    }
60C
Discovery & access24/25
Understanding18/25
Actionability6.11/25
Trust & freshness12/25

Keep this report

Get the permanent link and the ranked fix list by email. One message, no list.

Want this fixed?

We audit in depth and implement the fixes — in your codebase or your CMS, scoped by architecture.

Own this site?

This report and its leaderboard entry come from a public crawl. Prove you own the domain with an email address on it, and you can hide the report or publish it again yourself, in minutes.

To block future scans instead, disallow AgentFriendlyRankBot in your robots.txt — see how our crawler works.

Scan your own site

Same rubric, same evidence standard, about a minute.

Run a free scan →

Compare accountingstrategiesgroup.com with another site →