oregonblock.com, read 1 day ago. Back to the report

96 to 100 in 11 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.

9696 nownow971top 1%972973974985986987988999991010011full marks

Now #4,421 of 263,590Step 1 top 1%Step 11 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

    Fix title lengths

    +1 point, to 97, and #2,055, 2,366 places up, and into the top 1%

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

    14 pages

    See the pages
    • /
    • /about
    • /contact
    • /dealers/ground-control
    • /dealers/sisters-rental
    • /find-a-dealer
    • /gallery
    • /hello-world
    • /pavers
    • /pavers/ashlar-pavers
    • and 4 more in the copied plan
  2. 2

    Answer the first question right under it

    Under a point

    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.

    1 page

    See the pages
    • /hello-world
  3. 3

    Link to orphaned pages

    Under a point

    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

  4. 4

    Phrase headings as questions

    Under a point

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

    1 page

    See the pages
    • /hello-world
  5. 5

    Show when guides were updated

    +1 point, to 98

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

    1 page

    See the pages
    • /hello-world
  6. 6

    Speed up the server

    Under a point

    Cache pages or speed up the server. Crawlers give a slow site fewer visits.

    Once, for the whole site

  7. 7

    Put figures in tables

    Under a point

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

    1 page

    See the pages
    • /hello-world
  8. 8

    Add depth to thin pages

    Under a point

    Add true, specific detail until the page covers its subject.

    1 page

    See the pages
    • /hello-world
  9. 9

    Set a share image

    +1 point, to 99

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

    21 pages, 18 of them under /dealers/

    See the pages
    • /category/uncategorized
    • /dealers/all-about-stone-llc
    • /dealers/best-buy-in-town-landscape-supply
    • /dealers/eastern-oregon-rentals-baker-city
    • /dealers/eastern-oregon-rentals-island-city
    • /dealers/eastern-oregon-rentals-pendleton
    • /dealers/gerens-farm-landscape-supply
    • /dealers/ground-control
    • /dealers/highway-fuel-company
    • /dealers/lane-forest-products-eugene
    • and 11 more in the copied plan
  10. 10

    Describe images

    Under a point

    Describe every content image in its alt text.

    10 pages

    See the pages
    • /pavers/ashlar-pavers
    • /pavers/europa-pavers
    • /pavers/fieldstone-pavers
    • /retaining-walls/ab-aztec-collection
    • /retaining-walls/ab-collection
    • /retaining-walls/ab-europa-collection
    • /retaining-walls/ab-metro-collection
    • /seating-and-free-standing-walls/ab-courtyard-collection
    • /seating-and-free-standing-walls/ab-metro-patio-wall
    • /seating-and-free-standing-walls/brooklynne-stone
  11. 11

    Use one main heading

    +1 point, to 100, and full marks

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

    4 pages

    See the pages
    • /
    • /author/formadasocial
    • /category/uncategorized
    • /hello-world
1 more, to tidy up after 100
  1. 12

    Fix description lengths

    Under a point

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

    3 pages

    See the pages
    • /author/formadasocial
    • /category/uncategorized
    • /hello-world

Done since the first read

  1. Set each page's canonical address

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

  2. Link straight to the final address

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

  3. Fix pages that fail to load

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

  4. Add a way to get in touch

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

  5. Make near-copy pages distinct

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

  6. Add a tap-to-call link

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

  7. Replace unsupported sales claims

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

  8. Add structured data

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

What else the read found

Half its pages take over 1,870 ms to start answering, past the 800 ms a crawler is patient with. Caching or a faster server helps every page at once. One fetch a page, the way a crawler sees it.

  • /resources10.5 s
  • /contact9.5 s
  • /dealers/best-buy-in-town-landscape-supply9.2 s
  • /seating-and-free-standing-walls/brooklynne-stone8.8 s
  • /find-a-dealer8.5 s

Fastest: /seating-and-free-standing-walls, 77 ms. Heaviest: /dealers/leave-your-mark, 40 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
  • CloudflareHosting
  • WP EngineHosting
  • Google Tag ManagerAnalytics
  • jQueryLibrary
  • Google FontsFonts
pages with strong signs
0
hidden characters
0
chat, markdown or placeholders left in
0
dashes per 1,000 words
0.3

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 2: Use one main heading and Fix title lengths1 page
  • /hello-world fails 9: Answer the first question right under it, Show when guides were updated and Add depth to thin pages1 page
  • /find-a-dealer fails 2: Fix title lengths and Set a share image1 page
  • /about fails 1: Fix title lengths1 page
  • /contact fails 1: Fix title lengths1 page
  • /gallery fails 1: Fix title lengths1 page
  • /pavers fails 1: Fix title lengths1 page
  • /products fails 1: Fix title lengths1 page
  • /resources fails 1: Fix title lengths1 page
  • /find-a-contractor passes every rule1 page
  • /retaining-walls passes every rule1 page
  • /seating-and-free-standing-walls passes every rule1 page

And 6 more parts of the site.

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

Fix oregonblock.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 oregonblock.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.