readcube.com, read 2 days ago. Back to the report

85 to 100 in 8 steps

Do them in this order. Each step says what to change, on which pages, and what it adds. Hand the whole plan to your agent, or work through it yourself.

8585 nownow921top 10%9329539649859969971008full marks

Now #62,394 of 263,590Step 1 top 10%Step 8 full marks

Worked out from this read, with every step before it done. A score says pages are well formed. It does not say an assistant cites the site.

The steps

Each is one change across the pages named. When one is live, read the site again and mttr marks it done.

  1. 1

    Add a tap-to-call link

    +7 points, to 92, and #15,084, 47,310 places up, and into the top 10%

    Add a tap-to-call phone link.

    2 pages

    See the pages
    • /
    • /privacy
  2. 2

    Publish a sitemap

    +1 point, to 93

    Publish /sitemap.xml listing every page that should rank, and name it in robots.txt.

    Once, for the whole site

  3. 3

    Set each page's canonical address

    +2 points, to 95

    Add a canonical link that points to the page itself.

    1 page

    See the pages
    • /privacy
  4. 4

    Describe images

    +1 point, to 96

    Describe every content image in its alt text.

    The home page

  5. 5

    Replace unsupported sales claims

    +2 points, to 98

    Replace the sales claim with a fact that can be checked.

    The home page

  6. 6

    Add an llms.txt

    +1 point, to 99

    Add /llms.txt: a short plain text map of the site for assistants. Its effect is unproven, so treat it as cheap insurance.

    Once, for the whole site

  7. 7

    Link straight to the final address

    Under a point

    Point links and the sitemap at the final address, not at one that redirects.

    1 page

    See the pages
    • /privacy
  8. 8

    Set a share image

    +1 point, to 100, and full marks

    Set og:image so links to the page carry a picture.

    1 page

    See the pages
    • /privacy

Done since the first read

  1. Answer the first question right under it

    Done, seen on the read of October 23. It failed on 44 pages before.

  2. Put the text in the HTML

    Done, seen on the read of October 23. It failed on 31 pages before.

  3. Show when guides were updated

    Done, seen on the read of October 23. It failed on 31 pages before.

  4. Add depth to thin pages

    Done, seen on the read of October 23. It failed on 33 pages before.

  5. Fix description lengths

    Done, seen on the read of October 23. It failed on 49 pages before.

  6. Put figures in tables

    Done, seen on the read of October 23. It failed on 46 pages before.

  7. Add lists or tables

    Done, seen on the read of October 23. It failed on 36 pages before.

  8. Name the publisher

    Done, seen on the read of October 23. It failed on 31 pages before.

  9. Use one main heading

    Done, seen on the read of October 23. It failed on 3 pages before.

  10. Phrase headings as questions

    Done, seen on the read of October 23. It failed on 40 pages before.

  11. Speed up the server

    Done, seen on the read of October 23. It failed on 1 page before.

  12. Match structured data to the page

    Done, seen on the read of October 23. It failed on 31 pages before.

  13. Fix title lengths

    Done, seen on the read of October 23. It failed on 50 pages before.

What else the read found

Read from its home page’s code and the headers its server sent. A tool that loads later, or only on other pages, is not seen here.

  • WordPressPlatform
  • CloudflareHosting
  • WP EngineHosting
  • Google Tag ManagerAnalytics
  • jQueryLibrary
  • Google FontsFonts
  • Font AwesomeFonts
pages with strong signs
0
hidden characters
0
chat, markdown or placeholders left in
0
dashes per 1,000 words
1

A sign is not proof. Hidden characters can carry a watermark or instructions meant for an AI, and they come off with a clean copy of the text.

  • / fails 3: Add a tap-to-call link, Describe images and Replace unsupported sales claims1 page
  • /privacy fails 4: Set each page's canonical address, Add a tap-to-call link and Link straight to the final address1 page

The read stopped at its page limit, so pages no link leads to cannot be told from pages it did not reach, and neither is reported.

Rather go through these with one of our experts? Book a strategy session

Fix readcube.com with your agent

Your agent makes the fixes. mttr checks each one. Free.

In the site’s repositorynpx skills add subinternal/mttr
Then tell your agentCheck readcube.com with mttr and fix what’s worth the most.

Claude Code, Codex, Cursor or any agent that reads AGENTS.md.

Claude Code, onceclaude mcp add --transport http mttr https://mttr.si/mcp
It needs a free key
Another agent
Read it againChanged something? A site is read at most once every ten minutes.