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.
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
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:
The rest of the page is in full screen.
## 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
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.
| Crawler | robots.txt says | Used for | The line that decides |
|---|---|---|---|
| GPTBotOpenAI | Allowed | Training models | User-agent: GPTBot / Disallow: /prices.htm |
| OAI-SearchBotOpenAI | Not named | ChatGPT search | Falls to User-agent: * |
| ChatGPT-UserOpenAI | Not named | A page a person asks about | Falls to User-agent: * |
| ClaudeBotAnthropic | Not named | Training models | Falls to User-agent: * |
| Claude-SearchBotAnthropic | Not named | Claude’s search | Falls to User-agent: * |
| PerplexityBotPerplexity | Not named | Perplexity search | Falls to User-agent: * |
| Google-ExtendedGoogle | Not named | Training Gemini | Falls to User-agent: * |
| bingbotMicrosoft | Not named | Bing and Copilot | Falls 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 better | Signals | Costnot scored | ||||
|---|---|---|---|---|---|---|
| Page | Words | Clean | Readable | Main heading | Tokens | What it loses |
| /dd.exe | 3,939 | No <main> | Yes | None | 24,991 | No <main> and 1 more |
| /dex.chm | 1,708 | No <main> | Yes | None | 16,045 | No <main> and 1 more |
| /dexsetup.exe | 3,392 | No <main> | Yes | None | 24,995 | No <main> and 1 more |
| /dixml.chm | 610 | No <main> | Yes | None | 5,838 | No <main> and 1 more |
| /dixmlsetup.exe | 1,521 | No <main> | Yes | None | 9,669 | No <main> and 1 more |
| /drivemapsetup.exe | 2,742 | No <main> | Yes | None | 23,627 | No <main> and 1 more |
| /gdbprosetup.exe | 2,412 | No <main> | Yes | None | 24,977 | No <main> and 1 more |
| /help_gdb_chm/apfs_select.htm | 177 | No <main> | Yes | None | 442 | No <main> and 1 more |
| /help_gdb_chm/arrangement.htm | 971 | No <main> | Yes | None | 1,993 | No <main> and 1 more |
| /help_gdb_chm/checklist.htm | 807 | No <main> | Yes | None | 1,604 | No <main> and 1 more |
| /help_gdb_chm/details.htm | 2,971 | No <main> | Yes | None | 6,635 | No <main> and 1 more |
| /help_gdb_chm/disclaimer.htm | 537 | No <main> | Yes | None | 939 | No <main> and 1 more |
| /help_gdb_chm/driveinfo.htm | 1,366 | No <main> | Yes | None | 3,059 | No <main> and 1 more |
| /help_gdb_chm/drives.htm | 137 | No <main> | Yes | None | 534 | No <main> and 1 more |
| /help_gdb_chm/fileinfo.htm | 1,592 | No <main> | Yes | None | 3,393 | No <main> and 1 more |
| /help_gdb_chm/gdbfaq.htm | 2,194 | No <main> | Yes | None | 4,307 | No <main> and 1 more |
| /help_gdb_chm/glossary.htm | 1,563 | No <main> | Yes | None | 3,207 | No <main> and 1 more |
| /help_gdb_chm/image.htm | 190 | No <main> | Yes | None | 563 | No <main> and 1 more |
| /help_gdb_chm/install.htm | 106 | No <main> | Yes | None | 317 | No <main> and 1 more |
| /help_gdb_chm/intro.htm | 458 | No <main> | Yes | None | 1,241 | No <main> and 1 more |
| /help_gdb_chm/io_error.htm | 366 | No <main> | Yes | None | 787 | No <main> and 1 more |
| /help_gdb_chm/load.htm | 373 | No <main> | Yes | None | 718 | No <main> and 1 more |
| /help_gdb_chm/logical.htm | 191 | No <main> | Yes | None | 438 | No <main> and 1 more |
| /help_gdb_chm/menu.htm | 210 | No <main> | Yes | None | 926 | No <main> and 1 more |
| /help_gdb_chm/options.htm | 1,317 | No <main> | Yes | None | 2,649 | No <main> and 1 more |
Show where it stands
A card, a badge and a line, each with the figures.

A badge for the site
<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>
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
- Wrap 99 pages in <main>Clean measured
- Give 51 pages a main headingClearer
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/mcpSet 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 siteDrawn 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.