Design and SEO checker
A site can look fine on the builder's canvas and break on a phone. The checker opens every page at three widths, lists the faults a visitor would hit, runs a contrast check, and reads what the published code tells search engines: titles, descriptions, headings, image text, sitemap and robots file.
- When it runs
- After the first draft of each site
- Used in
- 4 reviews
- Runs on
- A browser and an accessibility engine on my PC
What the design and seo checker is
Design faults are counted, not described: sideways scrolling, tap targets too small to hit, placeholder text left in, broken images and text blocks overlapping each other, once per page across the widths. The search-engine points are read from the code of each page and completed by hand where a builder's help pages hold the answer, such as redirects and the option to hide a page.
How it works
- For each page and each width, phone, tablet and desktop, it scrolls the page, takes a full-page screenshot and lists the faults.
- It runs the contrast rules of an accessibility engine on every page; for some reviews the full engine and a keyboard walk as well.
- At desktop width it reads the title, description, heading structure, image text, canonical address, robots rule, social preview tags and structured data of each page, and fetches the sitemap and robots file.
- A second pass reads heading order, structured data and every image's text, file name, format, size and loading.
- Each fault type is counted once per page, and the search-engine points are scored out of twelve with the hand-checked ones added.
What it records
- Per page
- The faults at each width, the contrast failures, and the search-engine facts read from the code.
- Per site
- The fault count and the points met out of twelve.
What it cannot catch
- Spacing, type hierarchy and images that do not fit the business are judged by eye, not by the checker.
- A preview or hidden site has no readable sitemap or robots file, and the review says so.
- Up to a dozen pages per site are checked this way.
Where it was used
Every published review that ran this checker, with the figure it produced there, read from the review’s own data. Each figure opens the test results behind it.
| Review | Figure | Tested |
|---|---|---|
| 38 · 8/12 design faults · SEO basics met | Invalid Date | |
| Landingsite.ai | 31 / 0 design faults and critical accessibility problems | Invalid Date |
| 22 · 9/12 design faults · SEO basics met | Invalid Date | |
| 21 · 10/12 design faults · SEO basics met | Invalid Date |
Review
- Tested
- Invalid Date
- Tested
- Invalid Date
- Tested
- Invalid Date
- Tested
- Invalid Date
The other checkers for ai website builder
Written by Miles Foster, Owner and tester, RankDude. How RankDude tests and grades is on the methodology page.