asherremodeling.com, read 23 hours ago. Back to the report
94 to 100 in 5 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 #10,192 of 264,157Step 1 top 1%Step 5 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
Use one main heading
+3 points, to 97, and #2,065, 8,127 places up, and into the top 1%
Give the page exactly one h1 that says what it is about.
9 pages
See the pages
- /
- /about
- /contact
- /flooring
- /gallery
- /homes
- /new-construction
- /pricing
- /services
- 2
Set a share image
+1 point, to 98
Set og:image so links to the page carry a picture.
11 pages
See the pages
- /about
- /bathroom
- /contact
- /exteriors
- /flooring
- /gallery
- /kitchen
- /new-construction
- /pricing
- /remodeling
- and 1 more in the copied plan
- 3
Link to orphaned pages
+1 point, to 99
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
- 4
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
- 5
Fix description lengths
+1 point, to 100, and full marks
Write a meta description of 70 to 165 characters that summarizes the page.
3 pages
See the pages
- /new-construction
- /remodeling
- /services
What else the read found
Half its pages start answering within 451 ms, inside the 800 ms a crawler is patient with. One fetch a page, the way a crawler sees it.
/kitchen563 ms/services551 ms/bathroom534 ms/new-construction522 ms/flooring458 ms
Fastest: /contact, 75 ms. Heaviest: /homes, 26 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.
WordPressPlatform
CloudflareHosting
Google Tag ManagerAnalytics
- GGoogle AnalyticsAnalytics
HotjarAnalytics
Google reCAPTCHALibrary
jQueryLibrary
Font AwesomeFonts
- page with strong signs
- 1
- hidden characters
- 0
- chat, markdown or placeholders left in
- 1
- dashes per 1,000 words
- 0
/flooringplaceholders never filled in
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: Use one main heading1 page/new-constructionfails 3: Use one main heading, Fix description lengths and Set a share image1 page/servicesfails 3: Use one main heading, Fix description lengths and Set a share image1 page/aboutfails 2: Use one main heading and Set a share image1 page/contactfails 2: Use one main heading and Set a share image1 page/flooringfails 2: Use one main heading and Set a share image1 page/galleryfails 2: Use one main heading and Set a share image1 page/pricingfails 2: Use one main heading and Set a share image1 page/remodelingfails 2: Fix description lengths and Set a share image1 page/bathroomfails 1: Set a share image1 page/exteriorsfails 1: Set a share image1 page/homesfails 1: Use one main heading1 page
And 1 more part of the site.
Rather go through these with one of our experts? Book a strategy session