Home / AI Site Check

Hustle #005 / AI Site Check

AI Site Check: eight steps, one build.

A planned plain-English website audit for small businesses. The site and sample report are public. Checkout and live scanning are not available.

What we did

01 / Choose one customer

2 October

Small businesses need fixes, not another score.

  • The founder chose a website-check service. The offer is for small businesses that need to know what to fix and how.
  • The founder pushed for plain English. The sample should explain the real changes, not leave the customer with an unexplained score.
02 / Check the idea and the costs

2-3 October

Check what the audit can honestly promise.

  • The agent researched primary search guidance. It checked Google Search Central and OpenAI crawler documentation before describing SEO and AI-search access.
  • The founder challenged the planned £99 report. She said the sample needed to explain the real things that drive GEO.
  • The agent kept price and scope separate. £99 is a planned one-off price; the page allowance and delivery time are not final.
03 / Give it a name and a home

2-3 October

Name it and make the public home.

  • The founder chose AI Site Check. The agent built the site on Cloudflare Pages and connected aisitecheck.co.uk.
  • The agent set up the Google Search Console domain property. It added verification and submitted the XML sitemap.
  • The agent checked Google URL inspection. The homepage was reported indexed and its live access test passed; the sitemap fetch status remains open.
04 / Make one thing people can buy

3 October

Show the report before selling it.

  • The agent built a nine-area sample report. Each finding shows illustrative evidence, priority, exact fixes and a verification step.
  • The agent labelled the sample as fictional. Example Bicycle Repairs is not a scanned customer site.
  • The agent left checkout and scanning off. The secure scanner and payment route are not ready, so the audit stays planned.
05 / Put it in front of real people

3 October

Publish useful explainers alongside the sample.

  • The agent published two blog explainers. One separates ChatGPT search from training; the other explains the website basics behind Google AI search.
  • The agent added crawlable discovery files. The site has robots.txt, a five-page sitemap, canonical URLs and an informational llms.txt.
  • The agent linked the public build. The site is available at aisitecheck.co.uk without a payment or scanning claim.
06 / Learn from the first response

3 October

Make the sample useful after real feedback.

  • The founder rejected the first sample. She wanted more GEO depth and practical fixes for the planned price.
  • The agent expanded the findings. The revised sample covers access, entity clarity, answer-first content, JSON-LD, structure, evidence, FAQ limits, llms.txt limits and retesting.
  • The founder approved the deeper sample. Her response was: "Sample report much better".
07 / Hand over one repeatable job

3 October

Keep a repeatable watch, not a launch claim.

  • The founder requested a weekly search blog. It should explain what is changing and how LLMs search, using original sources.
  • The agent set an hourly sitemap-status watch. It waits for Google to fetch the sitemap or reports the unresolved issue after 24 hours.
  • The agent separated access from ranking. An indexed homepage is evidence of indexing, not a promise of rankings or AI citations.
08 / Improve it, change it or stop

3 October

Simplify the route before adding features.

  • The founder cut the navigation to three links. Home, How it works and Blog. The agent removed the complicated menu.
  • The agent checked desktop and mobile. The three-link navigation is readable at both sizes; no looping carousel or marquee is present.
  • The agent kept the launch boundary clear. Payment, secure scans and a final delivery scope are the next checks before taking orders.
3 October 2026

Today's update

  • The public site, deeper nine-area sample report and two blog explainers are live.
  • The overnight Google check reported the homepage indexed. At 05:43 the submitted sitemap showed "Couldn't fetch"; the watch remains open.
  • Home / How it works / Blog is now the whole navigation.
The build lesson

Biggest learning

  • A GEO report needs evidence, exact changes and a retest, not schema or llms.txt hype.
  • A submitted sitemap is not the same as a successfully fetched sitemap.
The next test

Next step

  • Finish the secure scanner and Stripe route, then confirm scope and delivery before taking money.
  • Resolve the sitemap fetch and keep the weekly explainers tied to current primary sources.

Use the build checklist for your own idea