Blog

The AI search SEO checklist: 12 things to check

A practical 12-point SEO checklist for small SaaS teams who want answer engines and search engines to read their site correctly.

Most SEO checklists were written for ten blue links. This one covers the basics that matter to both search engines and AI answer engines. Every item is something you can check in an afternoon.

To keep it honest, we ran it against our own site first. The heyEO demo shows that scan from 31 Oct 2026: 278 checks, 26 failing, 74 warnings and 178 passing. That is one scan, not a trend, and the demo may have changed since.

1. One canonical URL per page

Every page should say which URL is the real one. The first recommendation in our own scan was to add a canonical tag to the homepage.

2. Pick www or apex, and redirect the other

If www.example.com and example.com both serve pages, crawlers see two sites. Our scan flagged a www-to-apex canonical mismatch, so this one is real for us too.

3. One descriptive H1 per page

The H1 tells readers and machines what a page is about. Our sign-in page had none.

4. Titles that fit

Very long titles get cut off and very short ones say little. Two of our blog pages needed shorter titles.

5. Meta descriptions of a sensible length

Write one or two plain sentences that say what the page offers. Our demo and sign-in pages needed fixes here.

6. Structured data where it fits

JSON-LD for your organisation, articles and products gives machines facts they don't have to guess. Our homepage didn't have any yet.

7. Internal links from every page

A page that links nowhere is a dead end for crawlers. Even a sign-in page can link back to your guides.

8. Crawlers are allowed in

Check robots.txt and any firewall rules for the AI crawlers you care about. There's more in our crawler readability check.

9. Intentional noindex only

Private app pages should be noindexed, and public pages shouldn't be. Our scan asked us to confirm that the /app noindex was intentional.

10. A clear "who it's for" paragraph

Answer engines describe you using your own words. If you don't say who the product is for, they will guess. See writing a clear "who it's for" paragraph.

11. Question-shaped headings on key pages

People ask answer engines questions. Headings that match those questions make your answers easier to find. Our scan suggested adding them to the demo page.

12. Measure, change one thing, remeasure

A checklist is a starting point. Take a baseline, fix a few items, then scan again so you can see what moved. Read why the first scan matters most.