AI readiness resulthttps://www.google.com

Assessment date ·

Check another site

AI readiness result www.google.com

A solid start. 3 issues to improve.

4 of seven checks pass in full. 3 evidence-backed priorities are ready to review.

Working nowLive-answer crawler access, Stable homepage response, Useful initial HTML, and 1 more passed in full.

Fix nextHeading structure can be improved; Verified sameAs references can be improved; and 1 more.

  1. Discovery10/10
  2. Content15/45
  3. Trust10/10
  4. Signals20/35

This automated assessment reflects public website evidence CiteSurge collected on . It covers the homepage only. It can be incomplete, wrong, or out of date. It does not measure AI citations, rankings, traffic, or revenue.

What is covered: Six checks review one public homepage or its redirect chain. One site-level check reviews the sitemap. The result uses non-rendered HTTP and DNS evidence. This is not a full-site audit.

What is not measured: This check does not judge writing quality, prove linked-profile ownership, or measure which questions buyers ask, which brands answer engines name, or whether a change moved those observations. A later comparison shows movement in this technical result only. A paid audit builds a question set for your market, records repeated answer-engine observations, and measures brand presence and change over time. It does not promise citations, rankings, traffic, or revenue.

05The 5-step CiteSurge process

From free readiness score to full AI visibility

Start with a free basic check to see where you stand. Then unlock the full CiteSurge process across your foundations, commercial pathways, content, positioning, and ongoing measurement.

  1. Step 1

    Basic readiness score

    55/100

    Readiness complete

    • Technical checks complete
    • Next prompts ready
    Unlock Steps 2 to 5
  2. Step 2

    Fix your foundation

    • Prompt set
    • Technical GEO fixes
    • Brand/entity setup
  3. Step 3

    Align commercial pathways

    • Product and service identity
    • Value clarity
    • Audience and use cases
  4. Step 4

    Improve content + positioning

    • GEO-ready content
    • Proof and publicity
    • Citable trust content
  5. Step 5

    Maintain your dominant position

    • Iterate prompt sets
    • Recheck after changes
    • Refine major commercial beats

The free score is just the start.

A CiteSurge audit unlocks your next four steps.

We'll run a deeper audit across engines, content, commercial signals and authority, then share exactly what is holding you back.

Claim your FREE deeper CiteSurge audit

Get in touch and we'll run a deeper audit for free.

Your next 5 prompts, ready to copy

Selected by default from this result. Remove anything you do not want in the copied set.

5 of 5 selected.

Result-based actions5
Repair

Describe the organization in JSON-LD with its official profiles

The homepage at https://www.google.com/ has Microdata and RDFa but no JSON-LD. The structured data on the homepage at https://www.google.com/ lists no sameAs links to the organization's profiles on other sites.

Preview prompt

The homepage at https://www.google.com/ has Microdata and RDFa but no JSON-LD. The structured data on the homepage at https://www.google.com/ lists no sameAs links to the organization's profiles on other sites. Add one JSON-LD block to the homepage that describes the organization, using Organization or a more specific type such as LocalBusiness or Hotel when it fits. Include its name, url, and logo, and a sameAs list of the official profiles it controls on other sites, such as LinkedIn, Wikidata, Crunchbase, or verified social accounts. Use only facts and profile URLs the organization can confirm, and do not invent a rating, offer, address, or relationship. If a declared profile link points at the wrong profile, repoint it at the correct one. Done when: the homepage's HTML contains at least one JSON-LD block that parses and declares an @type, and at least three of its sameAs URLs on other sites open publicly.

Repair

Give the homepage a clear heading outline

The homepage at https://www.google.com/ has no headings in its initial HTML.

Preview prompt

The homepage at https://www.google.com/ has no headings in its initial HTML. Use one h1 for the homepage's main title. Organize major sections with h2 headings and nest lower levels in order. Do not add empty headings or duplicate the main title only to change the score. Done when: the initial HTML has exactly one h1 and at least two heading levels, such as h1 and h2.

Verify

Verify sitemap discovery

Keep the sitemap reachable and parseable after publishing changes.

Preview prompt

Fetch the sitemap declared for https://www.google.com, including any sitemap index it references. Confirm each document returns successfully and parses as a sitemap. Repair only broken URLs or invalid sitemap markup.

Verify

Verify live-answer crawler access

Confirm the crawler rules still match the access policy you intend.

Preview prompt

Review robots.txt for https://www.google.com. Confirm each live-answer crawler rule matches the publisher's intended policy for the homepage. Preserve unrelated directives, then fetch robots.txt again and verify every changed outcome.

Safeguard

Recheck the working foundation

Confirm the repairs and protect the checks that already work.

Preview prompt

After the changes are live, run the AI Readiness Check again at https://citesurge.com/score and confirm the repaired checks now pass. Confirm that Live-answer crawler access, Stable homepage response, Useful initial HTML and Sitemap discovery still pass. Investigate any regression before publishing further changes.

Use with judgment.Each prompt is tied to evidence or a publisher-policy decision in this result. Verify changes before publishing.

4 pass. Review 3.

Start with the highlights. Open every check for the full technical record.

Strong foundations

  • Live-answer crawler access8 of 8 weighted live-answer crawler paths were allowed.
  • Stable homepage responseThe homepage resolved successfully in 1 redirect hop.
  • Useful initial HTMLPrimary content was present in the initial HTML.

Review next

  • Heading structure can be improvedHeading structure did not receive full credit in this measurement.
  • Verified sameAs references can be improvedVerified sameAs references did not receive full credit in this measurement.
  • Typed JSON-LD can be improvedTyped JSON-LD did not receive full credit in this measurement.
See all 7 checks55, displayed as 55

Seven fixed checks

What shaped this result

Live-answer crawler access

10 pts
100%10 points earned

Stable homepage response

10 pts
100%10 points earned

Useful initial HTML

5 pts
100%5 points earned

Typed structured data

25 pts
40%10 points earned

Heading structure

15 pts
0%0 points earned

Sitemap discovery

20 pts
100%20 points earned

External profile links

15 pts
0%0 points earned
100 points total

AI ecosystem crawler policy (not scored)

These crawlers request pages for AI training and product development rather than to answer a question now. Allowing them is a publisher choice, not a readiness requirement, so this row earns no points either way.

  • Amazonbotallowed
  • Applebot-Extendedallowed
  • Google-Extendedallowed
  • GoogleOtherallowed
  • meta-externalagentallowed
  1. high

    Heading structure can be improved

    Heading structure did not receive full credit in this measurement.

    Heading structure

    Use one h1 for the homepage's main title. Organize major sections with h2 headings and nest lower levels in order. Do not add empty headings or duplicate the main title only to change the score.

    View 6 evidence records
    GET · RetrievedRequest 3

    https://google.com/

    0 bytes
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    GET · RetrievedRequest 4

    https://www.google.com/

    84345 bytes · sha256:b581136f0490d586b05e3e0efe656dd50a75e8f73da9cb750c54585ea33e38ee
    cache-control
    private, max-age=0
    content-encoding
    gzip
    content-type
    text/html; charset=ISO-8859-1
    GET · RetrievedRequest 11

    https://google.com/

    0 bytes
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    HEAD · RetrievedRequest 12

    https://google.com/

    0 bytes · sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    HEAD · RetrievedRequest 16

    https://www.google.com/

    0 bytes · sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    cache-control
    private
    content-type
    text/html; charset=ISO-8859-1
    GET · RetrievedRequest 17

    https://www.google.com/

    84524 bytes · sha256:f279ac466c10d8e110e73c8df5d69270b228f30b0c74547f1af21f93cd87eff3
    cache-control
    private, max-age=0
    content-encoding
    gzip
    content-type
    text/html; charset=ISO-8859-1
  2. high

    Verified sameAs references can be improved

    Verified sameAs references did not receive full credit in this measurement.

    Verified sameAs references

    Add sameAs only for profiles or identifiers that represent the same entity and that the organization can verify. Three resolving off-origin references earn full credit for this check, and it reads up to ten of the declared targets. LinkedIn, Wikidata, Crunchbase, verified social profiles, and industry registries are common sources for another reference. If a declared target points at the wrong profile, repoint it at the correct one. Do not assert ownership or identity links without evidence.

    View 6 evidence records
    GET · RetrievedRequest 3

    https://google.com/

    0 bytes
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    GET · RetrievedRequest 4

    https://www.google.com/

    84345 bytes · sha256:b581136f0490d586b05e3e0efe656dd50a75e8f73da9cb750c54585ea33e38ee
    cache-control
    private, max-age=0
    content-encoding
    gzip
    content-type
    text/html; charset=ISO-8859-1
    GET · RetrievedRequest 11

    https://google.com/

    0 bytes
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    HEAD · RetrievedRequest 12

    https://google.com/

    0 bytes · sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    HEAD · RetrievedRequest 16

    https://www.google.com/

    0 bytes · sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    cache-control
    private
    content-type
    text/html; charset=ISO-8859-1
    GET · RetrievedRequest 17

    https://www.google.com/

    84524 bytes · sha256:f279ac466c10d8e110e73c8df5d69270b228f30b0c74547f1af21f93cd87eff3
    cache-control
    private, max-age=0
    content-encoding
    gzip
    content-type
    text/html; charset=ISO-8859-1
  3. medium

    Typed JSON-LD can be improved

    Typed JSON-LD did not receive full credit in this measurement.

    Typed JSON-LD

    Add valid JSON-LD for facts the page can substantiate. Include a supported @context and @type, then add only properties backed by the page or your verified business records. Do not invent an organization, product, author, rating, offer, or relationship to satisfy this check.

    View 6 evidence records
    GET · RetrievedRequest 3

    https://google.com/

    0 bytes
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    GET · RetrievedRequest 4

    https://www.google.com/

    84345 bytes · sha256:b581136f0490d586b05e3e0efe656dd50a75e8f73da9cb750c54585ea33e38ee
    cache-control
    private, max-age=0
    content-encoding
    gzip
    content-type
    text/html; charset=ISO-8859-1
    GET · RetrievedRequest 11

    https://google.com/

    0 bytes
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    HEAD · RetrievedRequest 12

    https://google.com/

    0 bytes · sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    cache-control
    public, max-age=2592000
    content-length
    220
    content-type
    text/html; charset=UTF-8
    HEAD · RetrievedRequest 16

    https://www.google.com/

    0 bytes · sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    cache-control
    private
    content-type
    text/html; charset=ISO-8859-1
    GET · RetrievedRequest 17

    https://www.google.com/

    84524 bytes · sha256:f279ac466c10d8e110e73c8df5d69270b228f30b0c74547f1af21f93cd87eff3
    cache-control
    private, max-age=0
    content-encoding
    gzip
    content-type
    text/html; charset=ISO-8859-1

Tips and details.

See what the scan found, with extra suggestions that do not affect your score.

Explore tips and scan details

Parser evidence

CiteSurge extraction preview

No reliable homepage text was retained for an extraction preview.

Since the previous check

No prior retained result yet

This is the first retained result available for a like-for-like comparison.

Compared with similar sites

No cohort comparison yet

CiteSurge has not recorded a comparable business type for this result, so there is no group to place it in.

Outside the headline

Capability modules

Agent discovery

Not applicable

No machine-readable API affordance was observed.

Agent authentication

Not applicable

No authenticated protected resource was observed.

Depth and deliverables

What this access level includes

Crawler delivery divergence

Paid access required

Compare robots.txt policy with bounded homepage responses for opted-in AI crawler identities.

Requires a matching paid project and an active same-domain grant. Crawler delivery also requires explicit domain opt-in.

Rendered-page comparison

Paid access required

Compare initial HTML with an authorized rendered-page observation.

Requires a matching paid project and an active same-domain grant.

Generated deliverables

Implementation artifacts

robots.txt

Paid access required

Generate a reviewed robots.txt change.

Requires a matching paid project and an active same-domain grant.

llms.txt

Paid access required

Generate a curated llms.txt draft.

Requires a matching paid project and an active same-domain grant.

JSON-LD

Paid access required

Generate JSON-LD from verified facts.

Requires a matching paid project and an active same-domain grant.

Readiness leaderboard

See where this result stands.

Completed results are listed automatically. Switch this result off whenever you want.

Your result55 is currently 21st.

26 sites on this readiness leaderboard.

  1. 1
    elevenlabs.ioChecked Sep 28, 2026
    100
  2. 2
    kleos.ioChecked Oct 13, 2026
    95
  3. 2
    marathonvariety.comChecked Oct 6, 2026
    95
  4. 4
    devgamm.comChecked Oct 6, 2026
    91
  5. 4
    www.crunch.co.ukChecked Oct 14, 2026
    91
  6. 21
    www.google.comChecked Oct 6, 2026
    55
Remove every result for your domain

Email us from an address that uses the domain. Include the domain name. We verify the request before removing its listings.

Request domain removal

The free score is just the start.

A CiteSurge audit unlocks your next four steps.

We'll run a deeper audit across engines, content, commercial signals and authority, then share exactly what is holding you back.

Claim your FREE deeper CiteSurge audit

Get in touch and we'll run a deeper audit for free.