LeaderboardEvery site, rankedFree toolsChecks, no sign-upAgentsYour agent fixes itDocsThe API and MCP

visualis.media, read 7 hours ago. Back to the report

73 to 100 in 16 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.

7373 nownow781top 50%82284387488590692793894995109611971298139814991510016full marks

Now #160,177 of 263,590Step 1 top 50%Step 16 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 structured data

    +5 points, to 78, and #122,803, 37,374 places up, and into the top 50%

    Add valid JSON-LD that says what the page is.

    9 pages

    See the pages
    • /
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
    • /contact
    • /work
    • /work/blink
    • /work/ment
    • /work/sportico-world-summit
  2. 2

    Use one main heading

    +4 points, to 82

    Give the page exactly one h1 that says what it is about.

    9 pages

    See the pages
    • /
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
    • /contact
    • /work
    • /work/blink
    • /work/ment
    • /work/sportico-world-summit
  3. 3

    Show sources on guides

    +2 points, to 84

    Link the sources for the guide's facts where a reader can see them. Official and primary sources carry the most weight.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  4. 4

    Describe images

    +3 points, to 87

    Describe every content image in its alt text.

    9 pages

    See the pages
    • /
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
    • /contact
    • /work
    • /work/blink
    • /work/ment
    • /work/sportico-world-summit
  5. 5

    Answer the first question right under it

    +1 point, to 88

    Answer the first question in the paragraph right under it, in 25 to 90 words. Whether the paragraph truly answers is for the judge or a person to say.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  6. 6

    Match structured data to the page

    +2 points, to 90

    Use the schema type that matches the page: Article for guides, Service or Product for offers, Organization or WebSite for the home page.

    4 pages, 3 of them under /blog/

    See the pages
    • /
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  7. 7

    Show when guides were updated

    +2 points, to 92

    Show when the guide was last updated, and set dateModified in its schema.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  8. 8

    Link straight to the final address

    +1 point, to 93

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

    8 pages

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
    • /contact
    • /work
    • /work/blink
    • /work/ment
    • /work/sportico-world-summit
  9. 9

    Phrase headings as questions

    +1 point, to 94

    Phrase at least one heading as the question a person would ask.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  10. 10

    Add lists or tables

    +1 point, to 95

    Add a table, a list, or a definition list. Assistants quote these more readily than prose.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  11. 11

    Put figures in tables

    +1 point, to 96

    Where the guide compares options or gives figures, put them in a table.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  12. 12

    Name the publisher

    +1 point, to 97

    Name the author or publisher in the Article schema.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  13. 13

    Add breadcrumb data

    +1 point, to 98

    Add BreadcrumbList schema so the page has a place in the site.

    3 pages under /blog/

    See the pages
    • /blog/audemars-piguet
    • /blog/global-nikon-meetup
    • /blog/polestar-new-ev
  14. 14

    Add an llms.txt

    Under a point

    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

  15. 15

    Fix title lengths

    +1 point, to 99

    Write a title of 15 to 65 characters that leads with what the page covers.

    3 pages

    See the pages
    • /
    • /contact
    • /work
  16. 16

    Fix description lengths

    +1 point, to 100, and full marks

    Write a meta description of 70 to 165 characters that summarizes the page.

    3 pages under /work/

    See the pages
    • /work/blink
    • /work/ment
    • /work/sportico-world-summit
1 more, to tidy up after 100
  1. 17

    Link to your profiles

    Under a point

    Link from the home page, in its header or footer, to each profile you keep: Instagram, TikTok, YouTube, Twitch, Facebook, X, LinkedIn.

    Once, for the whole site

Done since the first read

  1. Add a tap-to-call link

    Done, seen on the read of October 24. It failed on 9 pages before.

What else the read found

Half its pages start answering within 125 ms, inside the 800 ms a crawler is patient with. One fetch a page, the way a crawler sees it.

  • /work/blink184 ms
  • /work/ment147 ms
  • /work/sportico-world-summit146 ms
  • /blog/audemars-piguet140 ms
  • /blog/global-nikon-meetup125 ms

Fastest: /, 7 ms. Heaviest: the home page, 38 KB.

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.

  • Google Tag ManagerAnalytics
  • Google AnalyticsAnalytics
pages with strong signs
0
hidden characters
0
chat, markdown or placeholders left in
0
dashes per 1,000 words
1.6

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 5: Add structured data, Use one main heading and Match structured data to the page1 page
  • /contact fails 5: Add structured data, Use one main heading and Describe images1 page
  • /work fails 5: Add structured data, Use one main heading and Describe images1 page
  • /blog/ 3 fail a rule. Worst: /blog/audemars-piguet, 13 rules3 pages
  • /work/ 3 fail a rule. Worst: /work/blink, 5 rules3 pages

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

Fix visualis.media 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 visualis.media 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.