assemblyrooftop.com, read 3 days ago. Back to the report

88 to 100 in 14 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.

8888 nownow911top 10%932943954965976987988989991099119912991310014full marks

Now #40,212 of 263,585Step 1 top 10%Step 14 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 description lengths

    +3 points, to 91, and #20,099, 20,113 places up, and into the top 10%

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

    12 pages

    See the pages
    • /
    • /about-us
    • /accessibility-statement
    • /contact
    • /email-sign-up
    • /event/thanksgiving-parade-at-assembly
    • /happenings
    • /location/assembly-rooftop-lounge
    • /menus
    • /press
    • and 2 more in the copied plan
  2. 2

    Fix title lengths

    +2 points, to 93

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

    9 pages

    See the pages
    • /about-us
    • /accessibility-statement
    • /contact
    • /email-sign-up
    • /happenings
    • /menus
    • /press
    • /private-events
    • /reservations
  3. 3

    Add depth to thin pages

    +1 point, to 94

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

    3 pages

    See the pages
    • /
    • /location/assembly-rooftop-lounge
    • /press
  4. 4

    Phrase headings as questions

    +1 point, to 95

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

    2 pages

    See the pages
    • /location/assembly-rooftop-lounge
    • /press
  5. 5

    Link straight to the final address

    +1 point, to 96

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

    11 pages

    See the pages
    • /about-us
    • /accessibility-statement
    • /contact
    • /email-sign-up
    • /event/thanksgiving-parade-at-assembly
    • /happenings
    • /location/assembly-rooftop-lounge
    • /menus
    • /press
    • /private-events
    • and 1 more in the copied plan
  6. 6

    Use one main heading

    +1 point, to 97

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

    2 pages

    See the pages
    • /accessibility-statement
    • /menus
  7. 7

    Answer the first question right under it

    +1 point, to 98

    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
    • /press
  8. 8

    Link to pages from related content

    Under a point

    Link to this page from the text of a related page. Navigation links say a page exists; links in content say what it is related to.

    2 pages

    See the pages
    • /location/assembly-rooftop-lounge
    • /press
  9. 9

    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
    • /press
  10. 10

    Put the text in the HTML

    +1 point, to 99

    Put the page text in the HTML the server sends. Most AI crawlers do not run scripts.

    The home page

  11. 11

    Add breadcrumb data

    Under a point

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

    2 pages

    See the pages
    • /location/assembly-rooftop-lounge
    • /press
  12. 12

    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

  13. 13

    Add lists or tables

    Under a point

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

    1 page

    See the pages
    • /location/assembly-rooftop-lounge
  14. 14

    Describe images

    +1 point, to 100, and full marks

    Describe every content image in its alt text.

    2 pages

    See the pages
    • /press
    • /private-events

What else the read found

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

  • /private-events32 ms
  • /menus18 ms
  • /accessibility-statement11 ms
  • /event/thanksgiving-parade-at-assembly6 ms
  • /email-sign-up6 ms

Fastest: /, 2 ms. Heaviest: /menus, 17 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.

  • FastlyHosting
  • Meta PixelMarketing
  • Google reCAPTCHALibrary
  • BootstrapLibrary
  • Google FontsFonts
  • Font AwesomeFonts

From the structured data on its home page, as the site says it: an Organization named Assembly Rooftop Lounge. mttr does not check the profiles it names.

  • FacebookAssembly-Rooftop-Lounge-580226928806546
  • Instagramassemblyphl
pages with strong signs
0
hidden characters
0
chat, markdown or placeholders left in
0
dashes per 1,000 words
0.2

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: Put the text in the HTML, Add depth to thin pages and Fix description lengths1 page
  • /press fails 10: Answer the first question right under it, Add depth to thin pages and Phrase headings as questions1 page
  • /accessibility-statement fails 4: Use one main heading, Fix description lengths and Fix title lengths1 page
  • /menus fails 4: Use one main heading, Fix description lengths and Fix title lengths1 page
  • /private-events fails 4: Fix description lengths, Describe images and Fix title lengths1 page
  • /about-us fails 3: Fix description lengths, Fix title lengths and Link straight to the final address1 page
  • /contact fails 3: Fix description lengths, Fix title lengths and Link straight to the final address1 page
  • /email-sign-up fails 3: Fix description lengths, Fix title lengths and Link straight to the final address1 page
  • /happenings fails 3: Fix description lengths, Fix title lengths and Link straight to the final address1 page
  • /reservations fails 3: Fix description lengths, Fix title lengths and Link straight to the final address1 page
  • /event/ 1 fail a rule. Worst: /event/thanksgiving-parade-at-assembly, 2 rules1 page
  • /location/ 1 fail a rule. Worst: /location/assembly-rooftop-lounge, 7 rules1 page

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

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