filebase.com, read 4 days ago. Back to the report
91 to 100 in 4 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 #21,378 of 264,643Step 1 top 5%Step 4 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
+6 points, to 97, and #2,065, 19,313 places up, and into the top 5%
Add a tap-to-call phone link.
100 pages
See the pages
- /
- /about
- /acceptable-use-policy
- /access-controls
- /all-features
- /aws-alternative
- /azure-alternative
- /backblaze-b2-alternative
- /cdn
- /cloudflare-r2-alternative
- and 90 more in the copied plan
- 2
Add structured data
+2 points, to 99
Add valid JSON-LD that says what the page is.
30 pages, 18 of them under /learning/
See the pages
- /all-features
- /cloudinary-alternative
- /comparisons
- /contact
- /developers
- /fastly-alternative
- /imagekit-alternative
- /learning
- /learning/access-controls
- /learning/add-custom-domain
- and 20 more in the copied plan
- 3
Link to your profiles
Under a point
Link from the home page, in its header or footer, to each profile you keep: Instagram, TikTok, YouTube, Twitch, Facebook, X, LinkedIn.
Once, for the whole site
- 4
Fix description lengths
+1 point, to 100, and full marks
Write a meta description of 70 to 165 characters that summarizes the page.
16 pages under /docs/
See the pages
- /docs/account/closing-an-account
- /docs/account/service-limits
- /docs/frameworks/apostrophe-cms
- /docs/frameworks/django
- /docs/frameworks/elixir-phoenix
- /docs/frameworks/laravel
- /docs/frameworks/nuxt
- /docs/frameworks/postman
- /docs/frameworks/strapi
- /docs/frameworks/vue
- and 6 more in the copied plan
4 more, to tidy up after 100
- 5
Bring deep pages closer to home
Under a point
Link to the page from a hub or a related page so it sits within three clicks of the home page.
11 pages under /learning/
See the pages
- /learning/add-custom-domain
- /learning/cors
- /learning/getting-started
- /learning/host-astro-site
- /learning/host-docusaurus-site
- /learning/host-gatsby-site
- /learning/host-nextjs-site
- /learning/host-remix-site
- /learning/image-optimization-via-gateway
- /learning/presigned-urls
- and 1 more in the copied plan
- 6
Describe images
Under a point
Describe every content image in its alt text.
2 pages
See the pages
- /image-optimization
- /ipfs-pinning
- 7
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
- /sites
- 8
Replace unsupported sales claims
Under a point
Replace the sales claim with a fact that can be checked.
The home page
What else the read found
Half its pages start answering within 37 ms, inside the 800 ms a crawler is patient with. One fetch a page, the way a crawler sees it.
/all-features236 ms/aws-alternative168 ms/165 ms/acceptable-use-policy162 ms/access-controls142 ms
Fastest: /ipfs-storage-calculator, 28 ms. Heaviest: /object-storage, 132 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.
GatsbyFramework
- GGoogle AnalyticsAnalytics
IntercomChat
Google FontsFonts
From the structured data on its home page, as the site says it: an Organization named Filebase. mttr does not check the profiles it names.
- Xfilebase
- GitHubfilebase
- LinkedInfilebase
- pages with strong signs
- 43
- hidden characters
- 276
- chat, markdown or placeholders left in
- 7
- dashes per 1,000 words
- 3.9
/docs/account/pricinghidden characters a reader cannot see/docs/frameworks/elixir-phoenixhidden characters a reader cannot see/docs/get-started/quickstart-aws-clihidden characters a reader cannot see/docs/get-started/quickstart-aws-sdk-pythonhidden characters a reader cannot see/docs/concepts/buckets-and-objectshidden 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 Replace unsupported sales claims1 page/all-featuresfails 2: Add structured data and Add a tap-to-call link1 page/cloudinary-alternativefails 2: Add structured data and Add a tap-to-call link1 page/comparisonsfails 2: Add structured data and Add a tap-to-call link1 page/contactfails 2: Add structured data and Add a tap-to-call link1 page/developersfails 2: Add structured data and Add a tap-to-call link1 page/fastly-alternativefails 2: Add structured data and Add a tap-to-call link1 page/image-optimizationfails 2: Add a tap-to-call link and Describe images1 page/imagekit-alternativefails 2: Add structured data and Add a tap-to-call link1 page/ipfs-pinningfails 2: Add a tap-to-call link and Describe images1 page/learningfails 2: Add structured data and Add a tap-to-call link1 page/nft-backupfails 2: Add structured data and Add a tap-to-call link1 page
And 32 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