mp3tomidi.app, read 5 days ago. Back to the report
84 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.
Now #79,144 of 263,634Step 1 top 25%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
Add a tap-to-call link
+7 points, to 91, and #20,125, 59,019 places up, and into the top 25%
Add a tap-to-call phone link.
21 pages, 11 of them under /zh/
See the pages
- /
- /ai-music-generator
- /ai-vocal-remover
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- /mp3-to-midi-bear-alternative
- /mp3-to-midi-piano
- /pricing
- /terms-of-service
- /zh
- and 11 more in the copied plan
- 2
Add structured data
+3 points, to 94
Add valid JSON-LD that says what the page is.
11 pages, 7 of them under /zh/
See the pages
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- /pricing
- /terms-of-service
- /zh/blog
- /zh/blog/change-song-to-midi
- /zh/blog/how-to-convert-mp3-to-midi
- /zh/blog/how-to-extract-piano-midi-from-piano-audio
- /zh/pricing
- /zh/privacy-policy
- and 1 more in the copied plan
- 3
Fix description lengths
+1 point, to 95
Write a meta description of 70 to 165 characters that summarizes the page.
11 pages, 7 of them under /zh/
See the pages
- /ai-music-generator
- /ai-vocal-remover
- /mp3-to-midi-bear-alternative
- /terms-of-service
- /zh/ai-music-generator
- /zh/ai-vocal-remover
- /zh/blog
- /zh/blog/change-song-to-midi
- /zh/pricing
- /zh/privacy-policy
- and 1 more in the copied plan
- 4
Show sources on guides
+1 point, to 96
Link the sources for the guide's facts where a reader can see them. Official and primary sources carry the most weight.
2 pages
See the pages
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- 5
Match structured data to the page
+1 point, to 97
Use the schema type that matches the page: Article for guides, Service or Product for offers, Organization or WebSite for the home page.
3 pages
See the pages
- /
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- 6
Show when guides were updated
+1 point, to 98
Show when the guide was last updated, and set dateModified in its schema.
2 pages
See the pages
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- 7
Put figures in tables
Under a point
Where the guide compares options or gives figures, put them in a table.
2 pages
See the pages
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- 8
Name the publisher
+1 point, to 99
Name the author or publisher in the Article schema.
2 pages
See the pages
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- 9
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
- 10
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
- /blog/how-to-extract-piano-midi-from-piano-audio
- 11
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.
3 pages under /zh/
See the pages
- /zh/blog
- /zh/privacy-policy
- /zh/terms-of-service
2 more, to tidy up after 100
- 12
Add breadcrumb data
Under a point
Add BreadcrumbList schema so the page has a place in the site.
2 pages
See the pages
- /blog/change-song-to-midi
- /blog/how-to-extract-piano-midi-from-piano-audio
- 13
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
What else the read found
Half its pages take over 2,628 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.
/zh/blog5.1 s/zh/blog/change-song-to-midi5.1 s/zh/blog/how-to-convert-mp3-to-midi5.0 s/mp3-to-midi-piano5.0 s/zh5.0 s
Fastest: /zh/privacy-policy, 904 ms. Heaviest: /zh/blog/how-to-convert-mp3-to-midi, 43 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.
Next.jsFramework
CloudflareHosting
Google Tag ManagerAnalytics
- GGoogle AnalyticsAnalytics
Microsoft ClarityAnalytics
- page with strong signs
- 1
- hidden characters
- 0
- chat, markdown or placeholders left in
- 1
- dashes per 1,000 words
- 8.5
/zh/blog/how-to-extract-piano-midi-from-piano-audiomarkdown 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 2: Add a tap-to-call link and Match structured data to the page1 page/terms-of-servicefails 3: Add structured data, Add a tap-to-call link and Fix description lengths1 page/ai-music-generatorfails 2: Add a tap-to-call link and Fix description lengths1 page/ai-vocal-removerfails 2: Add a tap-to-call link and Fix description lengths1 page/mp3-to-midi-bear-alternativefails 2: Add a tap-to-call link and Fix description lengths1 page/pricingfails 2: Add structured data and Add a tap-to-call link1 page/mp3-to-midi-pianofails 1: Add a tap-to-call link1 page/zhfails 1: Add a tap-to-call link1 page/zh/11 fail a rule. Worst: /zh/blog, 4 rules11 pages/blog/2 fail a rule. Worst: /blog/how-to-extract-piano-midi-from-piano-audio, 9 rules2 pages
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