Agent View

The site as an AI agent gets it, beside the site as a person sees it. What it can read, what it has to cut away, and what it never sees.

runtime.org99 pages read on October 23, 2026
Full screen
Save and Load Recovery
runtime.org/help_gdb_chm/load.htm
No main heading

Save and Load Recovery

Save Recovery

***Never save any files to the drive you are about to recover***

At any point after choosing a drive, you can save the current status of the recovery to a recovery file (.rec). This feature does not save the recovered files. It saves the status and structure of the recovery tree only. To save the recovered files, see Copy.

Go to DRIVE->Save current recovery and navigate to a location other than the "bad drive". Select a filename and choose between a compact or readable recovery file, then click Save. No matter what you choose, GetDataBack creates a file containing XML code describing the entire data recovery. If you save while in the Recovery Tree, the .rec file lists every single file. As the .rec file is readable, you can use it for your investigations or extract valuable information from it. It tells you the allocation of each file. It is even possible to modify the .rec file, adding or removing files, or changing their allocation.

Of course, the primary purpose of the .rec file is saving the current status for future use. This feature allows you to power down the computer, change the configuration, and load the .rec file and continue with the data recovery.

Load Recovery

Image with no wordsYou can load a previous recovery in GetDataBack at any point. To load a .rec file, go to DRIVE->Load previous recovery. Navigate to the recovery file and open it. You are now back where you were when you saved the recovery. The underlying drive (bad drive) for the saved recovery must be present when you load it. Otherwise, GetDataBack prompts you for a drive:

The rest of the page is in full screen.

Drawn from the HTML mttr fetched, not a screenshot.
page.md373 words, about 718 tokens
## Save and Load Recovery

#### Save Recovery

***Never save any files to the drive you are about to recover***

At any point after [choosing a drive](https://runtime.org/help_gdb_chm/step1.htm), you can save the current status of the recovery to a ***recovery file (.rec)***. This feature does not save the recovered files. It saves the status and structure of the recovery tree only. To save the recovered files, see [Copy](https://runtime.org/help_gdb_chm/step3.htm#copy)**.**

Go to ***DRIVE->Save current recovery*** and navigate to a location other than the "bad drive". Select a filename and choose between a ***compact*** or ***readable*** recovery file, then click ***Save***. No matter what you choose, GetDataBack creates a file containing XML code describing the entire data recovery. If you save while in the [Recovery Tree](https://runtime.org/help_gdb_chm/step3.htm), the .rec file lists every single file. As the ***.rec file*** is readable, you can use it for your investigations or extract valuable information from it. It tells you the allocation of each file. It is even possible to modify the ***.rec file***, adding or removing files, or changing their allocation.

Of course, the primary purpose of the ***.rec file*** is saving the current status for future use. This feature allows you to power down the computer, change the configuration, and load the ***.rec file*** and continue with the data recovery.

#### Load Recovery

You can load a previous recovery in GetDataBack at any point. To load a ***.rec file***, go to ***DRIVE->Load previous recovery***. Navigate to the recovery file and open it. You are now back where you were when you saved the recovery. The underlying drive (bad drive) for the saved recovery must be present when you load it. Otherwise, GetDataBack prompts you for a drive:

Look at the "Signature" of the missing drive, ***TImgFileDrive:8153087:1702440740***. The first part, ***TImgFileDrive,*** indicates an Image, ***8153087*** indicates the number of sectors, and ***1702440740*** indicates a hash of the drive. Compare this signature to the prompted drives as it must match. Once you identified the correct drive, you can confirm it and proceed. In our example, we had renamed the image we performed the recovery on. After loading the image, GetDataBack suggests this image as its signature matches the signature of the original drive.

[Introduction](https://runtime.org/help_gdb_chm/intro.htm) [[Select Drive](https://runtime.org/help_gdb_chm/step1.htm) **>** [Select File System](https://runtime.org/help_gdb_chm/step2.htm) **>** [Recovery Tree](https://runtime.org/help_gdb_chm/step3.htm)] [Settings](https://runtime.org/help_gdb_chm/options.htm) [Menu](https://runtime.org/help_gdb_chm/menu.htm) [Support](https://runtime.org/help_gdb_chm/support.htm) [Glossary](https://runtime.org/help_gdb_chm/glossary.htm)

No <main>: Wrap the page’s own content in <main>, so a reader knows where it starts and stops, and Clean can be measured. No h1: Give each one h1 that says what the page is.

The figures

99 pages, set against the 168,224 sites with figures.

Readablehigher is better
100%99 of 99 pages
All 168,224 sitesBetter than 47%

Pages whose own text is in the HTML the server sends, enough of it for their kind.

Cleanhigher is better
Nonemiddle page
All 168,224 sitesNo place yetWith no figure, it has no place.

Of the words before script, the share that are the page and not menus, footer and forms. 99 pages are not measured, with no <main> or no words.

Costshown, never scored
348,931tokens
About 3,525 a page

To read every page once. A long page that answers well is not worse for it. Tokens are estimated at about 4 characters each.

How its pages spread on Clean

No page measured

0 pages measured. Not measured: 99 with no <main> or no words.

Against its rivals

The sites nearest it by what they do, with figures. Close means similar work, not better.

No site near it by what it does has figures yet.

AI crawler access

What robots.txt says to each, as read on October 23, 2026. 8 of 8 may read the site.

Open robots.txt
Crawlerrobots.txt saysUsed forThe line that decides
GPTBotOpenAIAllowedTraining modelsUser-agent: GPTBot / Disallow: /prices.htm
OAI-SearchBotOpenAINot namedChatGPT searchFalls to User-agent: *
ChatGPT-UserOpenAINot namedA page a person asks aboutFalls to User-agent: *
ClaudeBotAnthropicNot namedTraining modelsFalls to User-agent: *
Claude-SearchBotAnthropicNot namedClaude’s searchFalls to User-agent: *
PerplexityBotPerplexityNot namedPerplexity searchFalls to User-agent: *
Google-ExtendedGoogleNot namedTraining GeminiFalls to User-agent: *
bingbotMicrosoftNot namedBing and CopilotFalls to User-agent: *

Every AI crawler mttr checks may read it. Not named means the rules for every crawler apply.

Every page

Worst first. Each opens in Agent View at the top.

99 pages of 99 lose something. Pick a loss to see what to do about it.Open the action plan

What an agent getshigher is betterSignalsCostnot scored
PageWordsCleanReadableMain headingTokensWhat it loses
/dd.exe3,939No <main>YesNone24,991No <main> and 1 more
/dex.chm1,708No <main>YesNone16,045No <main> and 1 more
/dexsetup.exe3,392No <main>YesNone24,995No <main> and 1 more
/dixml.chm610No <main>YesNone5,838No <main> and 1 more
/dixmlsetup.exe1,521No <main>YesNone9,669No <main> and 1 more
/drivemapsetup.exe2,742No <main>YesNone23,627No <main> and 1 more
/gdbprosetup.exe2,412No <main>YesNone24,977No <main> and 1 more
/help_gdb_chm/apfs_select.htm177No <main>YesNone442No <main> and 1 more
/help_gdb_chm/arrangement.htm971No <main>YesNone1,993No <main> and 1 more
/help_gdb_chm/checklist.htm807No <main>YesNone1,604No <main> and 1 more
/help_gdb_chm/details.htm2,971No <main>YesNone6,635No <main> and 1 more
/help_gdb_chm/disclaimer.htm537No <main>YesNone939No <main> and 1 more
/help_gdb_chm/driveinfo.htm1,366No <main>YesNone3,059No <main> and 1 more
/help_gdb_chm/drives.htm137No <main>YesNone534No <main> and 1 more
/help_gdb_chm/fileinfo.htm1,592No <main>YesNone3,393No <main> and 1 more
/help_gdb_chm/gdbfaq.htm2,194No <main>YesNone4,307No <main> and 1 more
/help_gdb_chm/glossary.htm1,563No <main>YesNone3,207No <main> and 1 more
/help_gdb_chm/image.htm190No <main>YesNone563No <main> and 1 more
/help_gdb_chm/install.htm106No <main>YesNone317No <main> and 1 more
/help_gdb_chm/intro.htm458No <main>YesNone1,241No <main> and 1 more
/help_gdb_chm/io_error.htm366No <main>YesNone787No <main> and 1 more
/help_gdb_chm/load.htm373No <main>YesNone718No <main> and 1 more
/help_gdb_chm/logical.htm191No <main>YesNone438No <main> and 1 more
/help_gdb_chm/menu.htm210No <main>YesNone926No <main> and 1 more
/help_gdb_chm/options.htm1,317No <main>YesNone2,649No <main> and 1 more
The worst 25 of 99 pages.Show all 99

Show where it stands

A card, a badge and a line, each with the figures.

runtime.org in Agent View: 100% readable
1200 by 630, for linksDownload

A badge for the site

Agent View: 100% readable
<a href="https://mttr.si/agent-view/runtime.org"><img src="https://mttr.si/agent-view/runtime.org/badge.svg" alt="Agent View: 100% readable" height="20"></a>
Drawn again after every read

The figures in one line

runtime.org in Agent View: 100% of pages readable, better than 47% of sites; Clean not measured; 348,931 tokens to read all 99 pages. mttr.si/agent-view/runtime.org

What to do next

Fix the pages, let an agent do it, and read the site again to see the figures move.

Fix what agents miss

99pages lose something
  • Wrap 99 pages in <main>Clean measured
  • Give 51 pages a main headingClearer
Open the action plan

Connect your agent

Claude Code, Codex or Cursor reads the site’s fixes over MCP, fixes a page in your code, has mttr read it again, and checks the fix landed.

https://mttr.si/mcp
Set up an agent

Claim the site

Prove it is yours with a DNS record or a file. Your agent can then reach its reads and jobs, and set each change to wait for your approval.

Claim the site

Drawn from the HTML mttr fetched on its read of October 23, 2026, not a screenshot, and only from the 99 pages read, where the read stopped at its page limit. An assistant’s own reader may differ. Tokens are estimated at about 4 characters each. A site an agent reads well is not a site an assistant cites.

Agent Viewruntime.org Close Esc
Save and Load Recovery
runtime.org/help_gdb_chm/load.htm

Its one image has no words, so an agent gets nothing of it.

No main heading

Save and Load Recovery

Save Recovery

***Never save any files to the drive you are about to recover***

At any point after choosing a drive, you can save the current status of the recovery to a recovery file (.rec). This feature does not save the recovered files. It saves the status and structure of the recovery tree only. To save the recovered files, see Copy.

Go to DRIVE->Save current recovery and navigate to a location other than the "bad drive". Select a filename and choose between a compact or readable recovery file, then click Save. No matter what you choose, GetDataBack creates a file containing XML code describing the entire data recovery. If you save while in the Recovery Tree, the .rec file lists every single file. As the .rec file is readable, you can use it for your investigations or extract valuable information from it. It tells you the allocation of each file. It is even possible to modify the .rec file, adding or removing files, or changing their allocation.

Of course, the primary purpose of the .rec file is saving the current status for future use. This feature allows you to power down the computer, change the configuration, and load the .rec file and continue with the data recovery.

Load Recovery

Image with no wordsYou can load a previous recovery in GetDataBack at any point. To load a .rec file, go to DRIVE->Load previous recovery. Navigate to the recovery file and open it. You are now back where you were when you saved the recovery. The underlying drive (bad drive) for the saved recovery must be present when you load it. Otherwise, GetDataBack prompts you for a drive:

Look at the "Signature" of the missing drive, TImgFileDrive:8153087:1702440740. The first part, TImgFileDrive, indicates an Image, 8153087 indicates the number of sectors, and 1702440740 indicates a hash of the drive. Compare this signature to the prompted drives as it must match. Once you identified the correct drive, you can confirm it and proceed. In our example, we had renamed the image we performed the recovery on. After loading the image, GetDataBack suggests this image as its signature matches the signature of the original drive.

Introduction [Select Drive > Select File System > Recovery Tree] Settings Menu Support Glossary

Drawn from the HTML mttr fetched, not a screenshot.
page.md373 words, about 718 tokens
## Save and Load Recovery

#### Save Recovery

***Never save any files to the drive you are about to recover***

At any point after [choosing a drive](https://runtime.org/help_gdb_chm/step1.htm), you can save the current status of the recovery to a ***recovery file (.rec)***. This feature does not save the recovered files. It saves the status and structure of the recovery tree only. To save the recovered files, see [Copy](https://runtime.org/help_gdb_chm/step3.htm#copy)**.**

Go to ***DRIVE->Save current recovery*** and navigate to a location other than the "bad drive". Select a filename and choose between a ***compact*** or ***readable*** recovery file, then click ***Save***. No matter what you choose, GetDataBack creates a file containing XML code describing the entire data recovery. If you save while in the [Recovery Tree](https://runtime.org/help_gdb_chm/step3.htm), the .rec file lists every single file. As the ***.rec file*** is readable, you can use it for your investigations or extract valuable information from it. It tells you the allocation of each file. It is even possible to modify the ***.rec file***, adding or removing files, or changing their allocation.

Of course, the primary purpose of the ***.rec file*** is saving the current status for future use. This feature allows you to power down the computer, change the configuration, and load the ***.rec file*** and continue with the data recovery.

#### Load Recovery

You can load a previous recovery in GetDataBack at any point. To load a ***.rec file***, go to ***DRIVE->Load previous recovery***. Navigate to the recovery file and open it. You are now back where you were when you saved the recovery. The underlying drive (bad drive) for the saved recovery must be present when you load it. Otherwise, GetDataBack prompts you for a drive:

Look at the "Signature" of the missing drive, ***TImgFileDrive:8153087:1702440740***. The first part, ***TImgFileDrive,*** indicates an Image, ***8153087*** indicates the number of sectors, and ***1702440740*** indicates a hash of the drive. Compare this signature to the prompted drives as it must match. Once you identified the correct drive, you can confirm it and proceed. In our example, we had renamed the image we performed the recovery on. After loading the image, GetDataBack suggests this image as its signature matches the signature of the original drive.

[Introduction](https://runtime.org/help_gdb_chm/intro.htm) [[Select Drive](https://runtime.org/help_gdb_chm/step1.htm) **>** [Select File System](https://runtime.org/help_gdb_chm/step2.htm) **>** [Recovery Tree](https://runtime.org/help_gdb_chm/step3.htm)] [Settings](https://runtime.org/help_gdb_chm/options.htm) [Menu](https://runtime.org/help_gdb_chm/menu.htm) [Support](https://runtime.org/help_gdb_chm/support.htm) [Glossary](https://runtime.org/help_gdb_chm/glossary.htm)
Drawn from the HTML mttr fetched, not a screenshot. An assistant’s own reader may differ.Tokens are estimated at about 4 characters each.