bayviewcenter.org, read 3 days ago. Back to the report

66 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.

6666 nownow751#146,287812top 50%8739149459769971008full marks

Now #197,581 of 263,871Step 1 #146,287Step 2 top 50%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 way to get in touch

    +9 points, to 75, and #146,287, 51,294 places up

    Give the page a form or a clear link to request a quote or get in touch.

    12 pages

    See the pages
    • /
    • /2026eventsponsors
    • /about
    • /annualfundraiser
    • /foodpantry
    • /health-wellness
    • /kitchen
    • /mission
    • /programs
    • /staff
    • and 2 more in the copied plan
  2. 2

    Add a tap-to-call link

    +6 points, to 81, and into the top 50%

    Add a tap-to-call phone link.

    12 pages

    See the pages
    • /
    • /2026eventsponsors
    • /about
    • /annualfundraiser
    • /foodpantry
    • /health-wellness
    • /kitchen
    • /mission
    • /programs
    • /staff
    • and 2 more in the copied plan
  3. 3

    Add structured data

    +6 points, to 87

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

    11 pages

    See the pages
    • /2026eventsponsors
    • /about
    • /annualfundraiser
    • /foodpantry
    • /health-wellness
    • /kitchen
    • /mission
    • /programs
    • /staff
    • /support
    • and 1 more in the copied plan
  4. 4

    Fix description lengths

    +4 points, to 91

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

    12 pages

    See the pages
    • /
    • /2026eventsponsors
    • /about
    • /annualfundraiser
    • /foodpantry
    • /health-wellness
    • /kitchen
    • /mission
    • /programs
    • /staff
    • and 2 more in the copied plan
  5. 5

    Use one main heading

    +3 points, to 94

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

    8 pages

    See the pages
    • /
    • /foodpantry
    • /kitchen
    • /mission
    • /programs
    • /staff
    • /support
    • /volunteer
  6. 6

    Fix title lengths

    +3 points, to 97

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

    9 pages

    See the pages
    • /
    • /2026eventsponsors
    • /about
    • /foodpantry
    • /mission
    • /programs
    • /staff
    • /support
    • /volunteer
  7. 7

    Link straight to the final address

    +2 points, to 99

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

    11 pages

    See the pages
    • /2026eventsponsors
    • /about
    • /annualfundraiser
    • /foodpantry
    • /health-wellness
    • /kitchen
    • /mission
    • /programs
    • /staff
    • /support
    • and 1 more in the copied plan
  8. 8

    Describe images

    +1 point, to 100, and full marks

    Describe every content image in its alt text.

    5 pages

    See the pages
    • /
    • /2026eventsponsors
    • /health-wellness
    • /programs
    • /volunteer

What else the read found

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

  • /staff43 ms
  • /programs42 ms
  • /37 ms
  • /support35 ms
  • /foodpantry34 ms

Fastest: /kitchen, 18 ms. Heaviest: /programs, 137 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.

  • WixPlatform
  • ReactFramework
  • CloudflareHosting
pages with strong signs
12
hidden characters
199
chat, markdown or placeholders left in
0
dashes per 1,000 words
1.8
  • /volunteer hidden characters a reader cannot see
  • /mission hidden characters a reader cannot see
  • /staff hidden characters a reader cannot see
  • /annualfundraiser hidden characters a reader cannot see
  • /about hidden characters a reader cannot see

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 a way to get in touch, Use one main heading and Add a tap-to-call link1 page
  • /programs fails 8: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /volunteer fails 8: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /2026eventsponsors fails 7: Add a way to get in touch, Add structured data and Add a tap-to-call link1 page
  • /foodpantry fails 7: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /mission fails 7: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /staff fails 7: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /support fails 7: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /about fails 6: Add a way to get in touch, Add structured data and Add a tap-to-call link1 page
  • /health-wellness fails 6: Add a way to get in touch, Add structured data and Add a tap-to-call link1 page
  • /kitchen fails 6: Add a way to get in touch, Add structured data and Use one main heading1 page
  • /annualfundraiser fails 5: Add a way to get in touch, Add structured data and Add a tap-to-call link1 page

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

Fix bayviewcenter.org 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 bayviewcenter.org 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.