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

kirschbaumdevelopment.com, read 4 days ago. Back to the report

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

9090 nownow931top 10%94296397497597698799899910010full marks

Now #27,039 of 263,590Step 1 top 10%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

    Show when guides were updated

    +3 points, to 93, and #10,777, 16,262 places up, and into the top 10%

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

    47 pages under /insights/

    See the pages
    • /insights/a-practical-guide-to-mutation-testing-with-pest
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-and-the-developer-skillset
    • /insights/ai-solutions-for-modern-business-challenges
    • /insights/anatomy-of-a-prompt-for-ai-assistants
    • /insights/avoiding-long-lived-tokens-on-aws
    • /insights/build-and-mcp-server-with-laravel-loop
    • /insights/build-sequences-with-laravel-pipelines
    • /insights/code-that-can-handle-failure
    • and 37 more in the copied plan
  2. 2

    Answer the first question right under it

    +1 point, to 94

    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.

    39 pages under /insights/

    See the pages
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-and-the-developer-skillset
    • /insights/ai-solutions-for-modern-business-challenges
    • /insights/anatomy-of-a-prompt-for-ai-assistants
    • /insights/avoiding-long-lived-tokens-on-aws
    • /insights/build-and-mcp-server-with-laravel-loop
    • /insights/code-that-can-handle-failure
    • /insights/configuring-aws-services-for-laravel
    • /insights/crafting-effective-prompts-for-ai-assistants
    • and 29 more in the copied plan
  3. 3

    Phrase headings as questions

    +2 points, to 96

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

    42 pages, 38 of them under /insights/

    See the pages
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-and-the-developer-skillset
    • /insights/ai-solutions-for-modern-business-challenges
    • /insights/anatomy-of-a-prompt-for-ai-assistants
    • /insights/avoiding-long-lived-tokens-on-aws
    • /insights/build-and-mcp-server-with-laravel-loop
    • /insights/code-that-can-handle-failure
    • /insights/configuring-aws-services-for-laravel
    • /insights/crafting-effective-prompts-for-ai-assistants
    • and 32 more in the copied plan
  4. 4

    Put figures in tables

    +1 point, to 97

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

    47 pages under /insights/

    See the pages
    • /insights/a-practical-guide-to-mutation-testing-with-pest
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-and-the-developer-skillset
    • /insights/ai-solutions-for-modern-business-challenges
    • /insights/anatomy-of-a-prompt-for-ai-assistants
    • /insights/avoiding-long-lived-tokens-on-aws
    • /insights/build-and-mcp-server-with-laravel-loop
    • /insights/build-sequences-with-laravel-pipelines
    • /insights/code-that-can-handle-failure
    • and 37 more in the copied plan
  5. 5

    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

  6. 6

    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.

    34 pages under /insights/

    See the pages
    • /insights/a-practical-guide-to-mutation-testing-with-pest
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-solutions-for-modern-business-challenges
    • /insights/avoiding-long-lived-tokens-on-aws
    • /insights/build-sequences-with-laravel-pipelines
    • /insights/code-that-can-handle-failure
    • /insights/custom-laravel-packages
    • /insights/extending-php-enums-with-attributes
    • /insights/how-tailwind-css-adds-value-in-web-development
    • and 24 more in the copied plan
  7. 7

    Add breadcrumb data

    +1 point, to 98

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

    51 pages, 47 of them under /insights/

    See the pages
    • /insights/a-practical-guide-to-mutation-testing-with-pest
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-and-the-developer-skillset
    • /insights/ai-solutions-for-modern-business-challenges
    • /insights/anatomy-of-a-prompt-for-ai-assistants
    • /insights/avoiding-long-lived-tokens-on-aws
    • /insights/build-and-mcp-server-with-laravel-loop
    • /insights/build-sequences-with-laravel-pipelines
    • /insights/code-that-can-handle-failure
    • and 41 more in the copied plan
  8. 8

    Fix description lengths

    +1 point, to 99

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

    38 pages, 30 of them under /insights/

    See the pages
    • /
    • /careers/lead-web-application-developer
    • /cases/building-cultural-geospatial-mobile-app
    • /cases/socially-driven-restaurant-discovery-mobile-app
    • /insights
    • /insights/a-practical-guide-to-mutation-testing-with-pest
    • /insights/adding-a-second-server-to-your-app
    • /insights/advanced-guide-to-laravel-sail
    • /insights/ai-and-the-developer-skillset
    • /insights/ai-solutions-for-modern-business-challenges
    • and 28 more in the copied plan
  9. 9

    Fix title lengths

    Under a point

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

    27 pages

    See the pages
    • /about
    • /careers
    • /cases
    • /cases/building-cultural-geospatial-mobile-app
    • /cases/provider-configuration-for-a-healthcare-staffing-platform
    • /cases/socially-driven-restaurant-discovery-mobile-app
    • /cases/transforming-subscription-platforms-without-interruption
    • /contact
    • /insights
    • /insights/avoiding-long-lived-tokens-on-aws
    • and 17 more in the copied plan
  10. 10

    Add depth to thin pages

    +1 point, to 100, and full marks

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

    5 pages, 4 of them under /insights/

    See the pages
    • /insights/kirschbaum-filament
    • /insights/laravel-translations-loader
    • /insights/nova-inline-select
    • /insights/strategic-advantages-of-dynamic-software
    • /services/support
4 more, to tidy up after 100
  1. 11

    Add a tap-to-call link

    Under a point

    Add a tap-to-call phone link.

    7 pages

    See the pages
    • /careers
    • /careers/lead-web-application-developer
    • /privacy-policy
    • /services
    • /solutions
    • /technology
    • /terms-of-service
  2. 12

    Add real images to content

    Under a point

    Add a photo, drawing, or chart as an img with alt text. A CSS background image has no alt text and is not read as part of the page.

    4 pages under /services/

    See the pages
    • /services/rescue-projects
    • /services/support
    • /services/team-augmentation
    • /services/technical-leadership
  3. 13

    Show every FAQ question on the page

    Under a point

    Show every question in the FAQ schema on the page, word for word.

    1 page

    See the pages
    • /services/team-augmentation
  4. 14

    Describe images

    Under a point

    Describe every content image in its alt text.

    1 page

    See the pages
    • /about

What else the read found

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

  • /solutions/devops1.8 s
  • /solutions/saas1.6 s
  • /solutions/mobile1.5 s
  • /insights/how-to-set-up-a-new-laravel-project1.5 s
  • /team1.3 s

Fastest: /solutions, 144 ms. Heaviest: /insights/supercharge-laravel-development-with-ai, 76 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.

  • LaravelFramework
  • CloudflareHosting
  • Google Tag ManagerAnalytics

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

  • GitHubkirschbaum-development
  • LinkedInkirschbaumdevelopment
  • Xkirschbaum_dev
pages with strong signs
2
hidden characters
0
chat, markdown or placeholders left in
40
dashes per 1,000 words
0.5
  • /insights/supercharge-laravel-development-with-ai markdown never turned into formatting
  • /insights/build-and-mcp-server-with-laravel-loop markdown never turned into formatting

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 1: Fix description lengths1 page
  • /about fails 2: Describe images and Fix title lengths1 page
  • /careers fails 2: Add a tap-to-call link and Fix title lengths1 page
  • /insights fails 2: Fix description lengths and Fix title lengths1 page
  • /privacy-policy fails 2: Add a tap-to-call link and Fix title lengths1 page
  • /solutions fails 2: Add a tap-to-call link and Fix title lengths1 page
  • /technology fails 2: Add a tap-to-call link and Fix title lengths1 page
  • /cases fails 1: Fix title lengths1 page
  • /contact fails 1: Fix title lengths1 page
  • /services fails 1: Add a tap-to-call link1 page
  • /team fails 1: Fix title lengths1 page
  • /terms-of-service fails 1: Add a tap-to-call link1 page

And 9 more parts of the site.

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

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