CrawlCheck

Directory · AI visibility monitoring

Machine Relations — what a crawler receives from machinerelations.ai

Website measurement, not a product review. This page records what machine clients received from machinerelations.ai. It does not evaluate Machine Relations software, features, pricing or support.

93
Agrade

AI assistants like ChatGPT can find, read and quote your site. 3 small things to tidy.

AI visibility 93/100, measured 2026-10-30 03:33 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can reach this site, read it, and quote a specific fact about it. That is the whole job.

Open the full report machinerelations.ai ↗

961. ReachCan a named answer-engine crawler get your pages at all?912. ReadOnce it has the bytes, can it find the words?923. QuoteIs there a specific fact it can state and attribute?

3

findings

✓

llms.txt on its host

✗

entity map on its host

4

scans on record since 2026-10-21

The three stages, in the order an engine hits a site

Each stage gates the next: an engine that cannot reach a page never reads it, and one that cannot read it never quotes it.

96

Stage 1 · 40% of the score

Reach

Can a named answer-engine crawler get your pages at all?

Every named crawler was served the same page a browser gets.

91

Stage 2 · 30% of the score

Read

Once it has the bytes, can it find the words?

The delivered HTML is mostly content, and the machine files point at the rest.

92

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

The facts an assistant is asked for are declared and consistent.

What to fix

3 findings on this site. Every one is named below; the top one is shown in full, free. What we saw, why each matters, how to fix it and the bytes behind it are what a licence buys — or we implement the whole list for you.

3 Note

1The homepage is reached through a chain of redirectshttp://www.machinerelations.ai/ takes 2 redirects to reach the page: 308 permanent (http→https) → 308 permanent (www→apex) → https://machinerelations.ai/ (200).NoteSetting

What we saw

http://www.machinerelations.ai/ takes 2 redirects to reach the page: 308 permanent (http→https) → 308 permanent (www→apex) → https://machinerelations.ai/ (200). Point the first redirect straight at the final address.

Why it matters

Reaching the homepage takes more than one redirect, for example http to https and then the domain to www. Each hop is another request and round trip before a crawler or visitor gets the page, temporary hops (302, 307) tell search engines to keep the old address, and Google stops following after ten.

How to fix it

Send every old address straight to the final one in a single permanent (301 or 308) redirect: in the host, CDN or plugin rules, redirect http://domain and http://www straight to the final https address instead of chaining scheme, host and path fixes.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

Fix it with a coding agent

Paste into Claude Code, Cursor or Codex, opened on the code that serves this site.

Show prompt
You are working in the codebase (or server/CDN configuration) that serves machinerelations.ai. A crawler audit found the problem below. Fix it at the source, keep the change as small as possible, and do not change anything a visitor sees unless the fix requires it.

Finding: The homepage is reached through a chain of redirects (REDIRECT_CHAIN, note severity)
Page: https://machinerelations.ai/
What was measured: http://www.machinerelations.ai/ takes 2 redirects to reach the page: 308 permanent (http→https) → 308 permanent (www→apex) → https://machinerelations.ai/ (200). Point the first redirect straight at the final address.
Why it matters: Reaching the homepage takes more than one redirect, for example http to https and then the domain to www. Each hop is another request and round trip before a crawler or visitor gets the page, temporary hops (302, 307) tell search engines to keep the old address, and Google stops following after ten.
How to fix it: Send every old address straight to the final one in a single permanent (301 or 308) redirect: in the host, CDN or plugin rules, redirect http://domain and http://www straight to the final https address instead of chaining scheme, host and path fixes.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/REDIRECT_CHAIN
Full report (markdown): https://crawlcheck.io/r/yrq3v3titt.md

When you are done:
1. Tell me which files or settings you changed and why.
2. If the fix is a server, CDN or cache setting you cannot change from the code, say exactly where it is set.
3. After deploying, re-scan at https://crawlcheck.io/?url=machinerelations.ai . The fix counts when REDIRECT_CHAIN is gone from the new report.
Why this was decided
RuleREDIRECT_CHAIN · rule pack sv34 · scope core
Evaluated2026-10-30 03:33:58 UTC
Decisiond1:c1aa4267caa621493c21 · finding f1:73453168045d8948a17a resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 48134344 from EWR · audit v4

What it rests on

IdentityStatusBytessha256Kept
crawlcheck200101,92071e720c2f1dfkept
anon200101,92071e720c2f1dfkept
gptbot200101,92071e720c2f1dfkept
claudebot200101,92071e720c2f1dfkept
oaisearch200101,92071e720c2f1dfkept
claudesearch200101,92071e720c2f1dfkept
perplexity200101,92071e720c2f1dfkept
googlebot200101,92071e720c2f1dfkept

21 more in the manifest.

Artifacts: manifest:4cfb133c229f0dc280554f70b73e6a02ecee94fd48eed531a6e2b9e6026508ee

Grade effect Does not cap the letter: only medium, high and critical findings do. Moves no points either; the score is built from the measured rows.

Rule REDIRECT_CHAIN under scoring rules v34 · fingerprint REDIRECT_CHAIN|/ · persisting (4 scans)

Verify the fix Re-scan after the change. This finding is cleared when REDIRECT_CHAIN is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.

REDIRECT_CHAIN · full transcript

2The machine files cost more than the page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
3Visitors and crawlers are being served an old copy of this page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 2

What we saw, why it matters, how to fix it, and the evidence bytes for every finding — on this report and every re-scan. From $29 a month.

Unlock the findings

Or have them fixed

We implement the list on your site and re-measure, with a sealed before and after. One site, $100 once.

Get this fixed — $100

The chain a crawler follows

The chain breaks at entity graph. Everything after that point is only reachable by a crawler guessing the conventional path.

✓robots.txtEvery crawler reads this first
✓sitemapNamed in robots.txt and resolves
✓llms.txtPoints onward, links stay on this host
✗entity graphParses as JSON and points home

A machine file that does not parse is worth less than one that is absent, because it looks present. Rows behind this.

Where the bytes go

Of the 101,640 decompressed bytes the homepage delivers, 12.4% is text a reader or a model can actually use. Workable, with room to trim.

  • Readable text 12.4% · 12,558 B
  • Markup & attributes 15.5% · 15,791 B
  • Structured data (JSON-LD) 11.8% · 11,980 B
  • Inline JavaScript 59.8% · 60,737 B
  • HTML comments 0.6% · 574 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline JavaScript · 7,845 B (7.7%) — unnamedopens self.__next_f.push([1,"{\"@context\":\"https://schema.org\",\"@graph\"
  • JSON-LD · 7,565 B (7.4%) — unnamedopens {"@context":"https://schema.org","@graph":[{"@type":"WebPage","@id":"h
  • Inline JavaScript · 5,281 B (5.2%) — unnamedopens self.__next_f.push([1,"3:[\"$\",\"body\",null,{\"children\":[[\"$\",\"
  • Inline JavaScript · 5,151 B (5.1%) — unnamedopens self.__next_f.push([1,"f:[\"$\",\"div\",null,{\"className\":\"site-wra
  • Inline JavaScript · 4,721 B (4.6%) — unnamedopens self.__next_f.push([1,"{\"@context\":\"https://schema.org\",\"@graph\"
Section average over 2 scans on this score version · held at 93 since 2026-10-30
0501002026-10-23 00:34 · 93/100 · 3 findings2026-10-30 03:33 · 93/100 · 3 findings2026-10-232026-10-30

What changed

  1. 2026-10-21score moved 90 → 89score-down

4 scans on record, first 2026-10-21. Score movements are shown only between readings taken under the same score version; finding codes are comparable across all of them.

Is this your site?

This listing reads the public record. Claim it and Watch keeps that record on your terms: every list this page holds back, finding age, and twice-daily re-measurement. Free for 30 days, no card.

Claim the record for machinerelations.ai

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If machinerelations.ai is yours you can prove it in a minute and for nothing — a DNS TXT record or one meta tag on the home page, both checkable by anyone.

Claiming marks you as the verified owner and lets you correct the category and the company name. It moves no score, no rank and no position.

Claim this listing — free or ask about a verified profile

Dispute or re-scan

If a reading here is wrong, it is our instrument that is wrong, and we want to know. Tell us what is wrong and the site is re-measured; the result is published as measured. Nothing about a listing, a payment or a request changes a number.

By email instead: hello@crawlcheck.io. Category “AI visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.