aaronelectric.net, read 2 days ago. Back to the report

73 to 100 in 10 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 nownow801top 50%86289392495596698799899910010full marks

Now #162,929 of 263,577Step 1 top 50%Step 10 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

    +7 points, to 80, and #105,966, 56,963 places up, and into the top 50%

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

    8 pages

    See the pages
    • /
    • /about
    • /contact
    • /landing-page
    • /portfolio
    • /privacy-policy
    • /projects
    • /service
  2. 2

    Add a tap-to-call link

    +6 points, to 86

    Add a tap-to-call phone link.

    8 pages

    See the pages
    • /
    • /about
    • /contact
    • /landing-page
    • /portfolio
    • /privacy-policy
    • /projects
    • /service
  3. 3

    Fix description lengths

    +3 points, to 89

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

    8 pages

    See the pages
    • /
    • /about
    • /contact
    • /landing-page
    • /portfolio
    • /privacy-policy
    • /projects
    • /service
  4. 4

    Fix title lengths

    +3 points, to 92

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

    7 pages

    See the pages
    • /about
    • /contact
    • /landing-page
    • /portfolio
    • /privacy-policy
    • /projects
    • /service
  5. 5

    Describe images

    +3 points, to 95

    Describe every content image in its alt text.

    7 pages

    See the pages
    • /
    • /about
    • /contact
    • /landing-page
    • /portfolio
    • /projects
    • /service
  6. 6

    Match structured data to the page

    +1 point, to 96

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

    The home page

  7. 7

    Set a share image

    +2 points, to 98

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

    8 pages

    See the pages
    • /
    • /about
    • /contact
    • /landing-page
    • /portfolio
    • /privacy-policy
    • /projects
    • /service
  8. 8

    Fix pages that fail to load

    +1 point, to 99

    Fix or remove the link. Every linked page should return 200.

    1 page

    See the pages
    • /services
  9. 9

    Use one main heading

    Under a point

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

    1 page

    See the pages
    • /privacy-policy
  10. 10

    Link to orphaned pages

    +1 point, to 100, and full marks

    Link to each of these from a related page. A page only the sitemap knows about is treated as unimportant.

    Once, for the whole site

1 more, to tidy up after 100
  1. 11

    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

What else the read found

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

  • /service815 ms
  • /landing-page715 ms
  • /projects692 ms
  • /privacy-policy487 ms
  • /contact69 ms

Fastest: /portfolio, 10 ms. Heaviest: /contact, 27 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.

  • WordPressPlatform
  • nginxServer
  • Meta PixelMarketing
  • jQueryLibrary
  • Google FontsFonts
pages with strong signs
4
hidden characters
0
chat, markdown or placeholders left in
4
dashes per 1,000 words
0.2
  • /landing-page placeholders never filled in
  • /portfolio placeholders never filled in
  • /projects placeholders never filled in
  • /service placeholders never filled in

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 6: Add structured data, Add a tap-to-call link and Match structured data to the page1 page
  • /services passes every rule1 page
  • /about fails 6: Add structured data, Add a tap-to-call link and Fix description lengths1 page
  • /contact fails 6: Add structured data, Add a tap-to-call link and Fix description lengths1 page
  • /landing-page fails 6: Add structured data, Add a tap-to-call link and Fix description lengths1 page
  • /portfolio fails 6: Add structured data, Add a tap-to-call link and Fix description lengths1 page
  • /privacy-policy fails 6: Add structured data, Use one main heading and Add a tap-to-call link1 page
  • /projects fails 6: Add structured data, Add a tap-to-call link and Fix description lengths1 page
  • /service fails 6: Add structured data, Add a tap-to-call link and Fix description lengths1 page

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

Fix aaronelectric.net 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 aaronelectric.net 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.