floridadistributing.com, read 21 hours ago. Back to the report
84 to 100 in 7 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 #73,294 of 263,590Step 1 top 25%Step 7 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 structured data
+7 points, to 91, and #20,083, 53,211 places up, and into the top 25%
Add valid JSON-LD that says what the page is.
5 pages
See the pages
- /
- /brand-finder
- /contact-us
- /product-catalog
- /sitemap
- 2
Set each page's canonical address
+4 points, to 95
Add a canonical link that points to the page itself.
5 pages
See the pages
- /
- /brand-finder
- /contact-us
- /product-catalog
- /sitemap
- 3
Settle on one address
+1 point, to 96
Redirect http, https, www, and the bare domain to one address, so the site is not indexed as several.
Once, for the whole site
- 4
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.
The home page
- 5
Describe images
+1 point, to 98
Describe every content image in its alt text.
2 pages
See the pages
- /
- /contact-us
- 6
Use one main heading
+1 point, to 99
Give the page exactly one h1 that says what it is about.
1 page
See the pages
- /sitemap
- 7
Set a share image
+1 point, to 100, and full marks
Set og:image so links to the page carry a picture.
1 page
See the pages
- /sitemap
1 more, to tidy up after 100
- 8
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
Done since the first read
Add a tap-to-call link
Done, seen on the read of October 24. It failed on 4 pages before.
What else the read found
Half its pages start answering within 274 ms, inside the 800 ms a crawler is patient with. One fetch a page, the way a crawler sees it.
/sitemap275 ms/275 ms/contact-us274 ms/product-catalog249 ms/brand-finder246 ms
Fastest: /brand-finder, 246 ms. Heaviest: the home page, 22 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
ReactFramework
nginxServer
Google Tag ManagerAnalytics
- pages with strong signs
- 0
- hidden characters
- 0
- chat, markdown or placeholders left in
- 0
- dashes per 1,000 words
- 1.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 4: Add structured data, Set each page's canonical address and Match structured data to the page1 page/sitemapfails 4: Add structured data, Set each page's canonical address and Use one main heading1 page/contact-usfails 3: Add structured data, Set each page's canonical address and Describe images1 page/brand-finderfails 2: Add structured data and Set each page's canonical address1 page/product-catalogfails 2: Add structured data and Set each page's canonical address1 page
Rather go through these with one of our experts? Book a strategy session