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

sonarsource.com, read 2 days ago. Back to the report

83 to 100 in 6 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.

8383 nownow901top 25%9329539749951006full marks

Now #81,829 of 264,198Step 1 top 25%Step 6 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 tap-to-call link

    +7 points, to 90, and #25,900, 55,929 places up, and into the top 25%

    Add a tap-to-call phone link.

    100 pages

    See the pages
    • /
    • /accessibility
    • /agent-centric-development
    • /blog
    • /brand-identity
    • /company/about
    • /company/careers
    • /company/contact
    • /company/contact-partner
    • /company/cookie-policy
    • and 90 more in the copied plan
  2. 2

    Describe images

    +3 points, to 93

    Describe every content image in its alt text.

    100 pages

    See the pages
    • /
    • /accessibility
    • /agent-centric-development
    • /blog
    • /brand-identity
    • /company/about
    • /company/careers
    • /company/contact
    • /company/contact-partner
    • /company/cookie-policy
    • and 90 more in the copied plan
  3. 3

    Use one main heading

    +2 points, to 95

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

    39 pages

    See the pages
    • /blog
    • /company/contact
    • /company/contact-partner
    • /company/newsroom
    • /company/press-releases
    • /de
    • /de/company/contact
    • /de/get-started
    • /de/request-demo
    • /es
    • and 29 more in the copied plan
  4. 4

    Link straight to the final address

    +2 points, to 97

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

    99 pages

    See the pages
    • /accessibility
    • /agent-centric-development
    • /blog
    • /brand-identity
    • /company/about
    • /company/careers
    • /company/contact
    • /company/contact-partner
    • /company/cookie-policy
    • /company/coverage
    • and 89 more in the copied plan
  5. 5

    Fix description lengths

    +2 points, to 99

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

    42 pages

    See the pages
    • /company/coverage
    • /de
    • /de/company/contact
    • /de/get-started
    • /de/integrations
    • /de/plans-and-pricing
    • /developers
    • /es
    • /es/company/contact
    • /es/get-started
    • and 32 more in the copied plan
  6. 6

    Fix title lengths

    +1 point, to 100, and full marks

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

    22 pages

    See the pages
    • /blog
    • /company/careers
    • /company/cookie-policy
    • /company/privacy
    • /de/company/contact
    • /de/integrations
    • /es/integrations
    • /fr/company/contact
    • /fr/events
    • /fr/integrations
    • and 12 more in the copied plan
6 more, to tidy up after 100
  1. 7

    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
    • /agent-centric-development
  2. 8

    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
    • /agent-centric-development
  3. 9

    Add breadcrumb data

    Under a point

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

    1 page

    See the pages
    • /agent-centric-development
  4. 10

    Replace unsupported sales claims

    Under a point

    Replace the sales claim with a fact that can be checked.

    2 pages

    See the pages
    • /fr/trust-center
    • /trust-center
  5. 11

    Remove ratings with no visible reviews

    Under a point

    Remove rating schema unless the reviews it counts are shown on the page.

    1 page

    See the pages
    • /company/about
  6. 12

    Add a way to get in touch

    Under a point

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

    1 page

    See the pages
    • /fr/software-development-roi-calculator

What else the read found

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

  • /sonar-at-rsac1.6 s
  • /sonar-excellence-awards1.5 s
  • /open-source/source-available1.3 s
  • /why-sonar1.0 s
  • /ko/plans-and-pricing960 ms

Fastest: /plans-and-pricing, 38 ms. Heaviest: /why-sonar, 145 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.

  • NetlifyHosting
  • Google Tag ManagerAnalytics

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

  • YouTubeSonarSource
  • FacebookSonarSource
  • LinkedInsonarsource
  • Xsonarsource
page with strong signs
1
hidden characters
2
chat, markdown or placeholders left in
0
dashes per 1,000 words
1.2
  • /requestaidemo 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 2: Add a tap-to-call link and Describe images1 page
  • /agent-centric-development fails 6: Answer the first question right under it, Add a tap-to-call link and Put figures in tables1 page
  • /blog fails 5: Use one main heading, Add a tap-to-call link and Describe images1 page
  • /de fails 5: Use one main heading, Add a tap-to-call link and Fix description lengths1 page
  • /es fails 5: Use one main heading, Add a tap-to-call link and Fix description lengths1 page
  • /requestaidemo fails 5: Use one main heading, Add a tap-to-call link and Fix description lengths1 page
  • /sonar-at-rsac fails 5: Use one main heading, Add a tap-to-call link and Fix description lengths1 page
  • /the-state-of-code fails 5: Add a tap-to-call link, Fix description lengths and Describe images1 page
  • /try-ai-demo fails 5: Use one main heading, Add a tap-to-call link and Fix description lengths1 page
  • /why-sonar fails 5: Add a tap-to-call link, Fix description lengths and Describe images1 page
  • /developers fails 4: Add a tap-to-call link, Fix description lengths and Describe images1 page
  • /eyeonai fails 4: Use one main heading, Add a tap-to-call link and Describe images1 page

And 38 more parts of the site.

The read stopped at its page limit, so pages no link leads to cannot be told from pages it did not reach, and neither is reported.

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

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