Your website.
A clear next step.
You built a business. You should not need to become a web expert to improve its website.
AI Site Check turns confusing website issues into practical fixes. Understand what matters, what to change and how to get it done.
A report you can actually use.
See the checks behind useful AI visibility: access, business facts, content, structured data and evidence. Open any finding for its fix, example and verification steps.
Example Bicycle Repairs
Public pages: home, repairs, puncture repair, brake repair and contact. All observations below are invented to demonstrate the report format.
01Crawl access + index eligibilityCan search tools reach your pages?Fix first
Illustrative evidence: /repairs has a noindex tag. robots.txt blocks OAI-SearchBot. The page is linked only from a menu that appears after a script runs.
Why it matters
A useful answer cannot be reliably discovered if its source page is excluded or hard to find. Google AI supporting links require an indexed, snippet-eligible page. ChatGPT search access is a separate control.
What to change
Remove noindex from the public repairs page. Add a normal HTML link from the homepage. If ChatGPT search visibility is wanted, allow OAI-SearchBot and its published IP ranges through the hosting firewall. Keep training permissions a separate owner decision.
Copy / configuration example
User-agent: OAI-SearchBot Allow: / # Choose GPTBot training policy separately. Sitemap: https://example.invalid/sitemap.xml
How we would verify it
Fetch /repairs: HTTP 200, no noindex in meta or X-Robots-Tag. Inspect the page in Search Console. Check robots rules and server logs for actual successful requests. A spoofed user-agent test does not prove real crawler access.
Limit: Eligibility is not a promise of indexing, citation or ranking.
02Entity clarity + local factsMake the business unambiguous.Fix first
Illustrative evidence: the hero says "Better cycling starts here". The service area is buried in an image. The contact page and business profile list different opening hours.
Why it matters
People and retrieval systems need a consistent answer to who you are, what you do and where you do it. Ambiguous names and conflicting facts make your page a weak source.
What to change
Use the same business name, service area, contact details and opening hours on the home, contact and service pages. Check the owner-controlled Business Profile against the website. Never invent an address, reviews or credentials.
Copy / configuration example
Example Bicycle Repairs repairs punctures, brakes and gears in Bristol. See our repair options, current opening hours and how to book.
How we would verify it
Copy those facts from each key page and compare them side by side. Ask the owner to confirm the authoritative version. Check the public Business Profile after the update.
Limit: Business-profile edits require account access; a website-only check cannot certify every external listing.
03Answer-first service contentAnswer the question before the sales pitch.Fix next
Illustrative evidence: /puncture-repair opens with 250 words of brand copy. It never says whether booking is needed, what is included or what changes the price.
Why it matters
A concise, useful answer gives people a reason to stay and makes the relevant facts easier to reference. It should still contain genuine depth, not repeated keyword filler.
What to change
Start the service page with a direct answer, then explain inclusions, exclusions, booking, price factors and the next action. Have the owner supply real prices and time estimates before publishing.
Copy / configuration example
Question: Do I need to book a puncture repair? Answer: [Owner-confirmed booking policy]. Included: [What the repair includes]. Price changes when: [Confirmed factors]. Next step: Book a bicycle repair.
How we would verify it
Read only the first paragraph: does it answer the question? Verify every commercial fact with the owner. Check the full answer is selectable HTML text on mobile and in the fetched page.
Limit: This format improves clarity; it does not guarantee inclusion in an AI answer.
04Structured data + business identityConnect the right facts with JSON-LD.Fix next
Illustrative evidence: the homepage has no business structured data. A plugin adds an Organisation name that differs from the visible business name.
Why it matters
Structured data can make business facts explicit, but it must match the visible page. A large schema block is not a substitute for useful content.
What to change
Use an appropriate LocalBusiness type on the relevant business page. Give the business one stable @id. Include verified name, URL and applicable contact/address details; link service descriptions to that entity. Include only facts shown on the page.
Copy / configuration example
{"@context":"https://schema.org","@type":"LocalBusiness","@id":"https://example.invalid/#business","name":"Example Bicycle Repairs","url":"https://example.invalid/"}How we would verify it
Parse the JSON successfully. Check supported markup in Google’s Rich Results Test and compare each field to the visible page. Supply required properties only when the owner has verified them; this short fragment is not a complete validated rich-result implementation.
Limit: No special AI schema is required by Google. Do not add invented ratings or hidden FAQ answers.
05Page structure + internal discoveryGive every page one clear job.Fix next
Illustrative evidence: the homepage has three H1 headings, repeated "Learn more" links and no link to the brake-repair page outside a JavaScript widget.
Why it matters
Descriptive headings, concise sections and useful internal links make the information easier to find, understand and reference.
What to change
Give each service its own descriptive page title and main heading. Organise sections under question-based headings. Link from the homepage and related services with meaningful labels. Keep important facts in HTML, not image-only text.
Copy / configuration example
Title: Bicycle brake repairs in Bristol | Example Bicycle Repairs H1: Bicycle brake repairs H2: What we check H2: What affects the price H2: How to book
How we would verify it
Inspect the heading outline and link destinations. Crawl from the homepage without using search or the sitemap. Check key facts appear in fetched/rendered HTML and remain readable at mobile width.
Limit: A heading count by itself is not an AI ranking score. The test is a coherent page people can use.
06Evidence + expertise + freshnessMake claims worth citing.Fix next
Illustrative evidence: "Bristol’s best repair team" has no supporting source. The guide has no author, reviewer, update date or original repair examples.
Why it matters
A claim that cannot be checked is a poor foundation for an answer. Bing recommends evidence, subject depth and current information.
What to change
Replace unsupported superlatives with verifiable facts. Add original repair examples, credited expertise and sources where a factual claim needs them. Name the responsible reviewer and use a genuine reviewed date, not an automatic "updated today" badge.
Copy / configuration example
Before: Bristol’s best repair team. After: We repair [owner-confirmed bike types]. Our brake check covers [confirmed steps]. Guide reviewed by [real name and role] on [actual review date].
How we would verify it
Open each cited source and check it supports the claim. Confirm the reviewer and original examples. Check dates and prices against current records. Distinguish owner assertions from externally verified evidence.
Limit: Do not invent customer quotes, accreditations, review counts or citations. More links alone do not make a page trustworthy.
07FAQ content + schema limitsAnswer real FAQs. Skip the schema hype.Useful content
Illustrative evidence: recurring booking questions are answered only in Instagram messages. A plugin generates FAQPage markup for answers that are not on the page.
Why it matters
Visible question-and-answer content can help visitors and retrieval systems. Google deprecated FAQ rich results in May 2026 and removed the documentation in June 2026.
What to change
Publish owner-verified answers on the relevant service page. Remove markup for hidden or invented answers. Do not sell FAQPage markup as a route to Google FAQ rich results or a guaranteed GEO gain.
Copy / configuration example
Can you repair e-bikes? [Verified scope and exclusions] Do I need to book? [Current booking policy] What should I bring? [Confirmed instructions]
How we would verify it
Compare visible questions/answers with any JSON-LD. Check keyboard/mobile access to expanded answers. Ask the owner whether each answer is current.
Limit: FAQ usefulness and FAQ rich-result eligibility are different things.
08Agent-friendly summary fileCheck llms.txt without treating it as magic.Optional
Illustrative evidence: /llms.txt returns the homepage HTML with status 200. Its draft links include a deleted service page.
Why it matters
An optional summary can give some agents a cleaner route to your public content. It is a proposal, not a universal search or citation requirement. Google says llms.txt has no positive or negative effect on its visibility or rankings.
What to change
If you choose to publish it, serve a short Markdown overview at /llms.txt with accurate public links and clear limits. Do not put private information, instructions to override other rules or invented trust claims in it. Fix crawl/index/content issues first.
Copy / configuration example
# Example Bicycle Repairs > Public repair information for a fictional Bristol shop. ## Services - [Repairs](https://example.invalid/repairs): Repair options and booking information.
How we would verify it
GET /llms.txt: HTTP 200, readable text rather than the HTML shell. Open every linked page. Keep the file consistent with the website.
Limit: Optional hygiene. No promise that a search engine uses it or that publishing it changes rankings.
09Baseline + retest + real outcomesFind out what changed, not just what scored higher.Measure
Illustrative evidence: no Search Console baseline, no record of which pages are indexed and no saved booking-conversion benchmark.
Why it matters
A changed checklist is not the same as improved discovery or more business. You need a baseline and an honest retest.
What to change
Record index status, key crawl failures and the report’s before/after findings. Where connected, review Search Console traffic and Bing AI citation activity over a stated period. Track actual enquiries or bookings separately.
Copy / configuration example
Retest log: URL / change / verification result / date / remaining issue. Outcome log: visits / enquiries / completed bookings over comparable periods.
How we would verify it
Re-run each check after the owner publishes the changes. Use actual tool records, not screenshots of a single AI answer as proof. Record the timeframe and anything else that changed.
Limit: Citation counts do not explain every ranking decision. A one-off prompt test is variable and cannot prove causation.
What a finished audit should hand you
Page-specific evidence, an ordered fix list, implementation examples, retest steps and a clear split between automated findings and checks that need a person. This sample demonstrates depth; the final £99 page allowance, delivery time and exact service scope are still being confirmed.
No guaranteed AI citations, Google position, accessibility certification or legal compliance. No payment or scan is available today.
One report. A clearer plan.
£99 once
- Plain-English report and ordered fixes.
- Page allowance and delivery time still being finalised.
- Not available to buy yet.
Want someone to do the fixes?
- Implementation is priced separately.
- Agree a fixed work list, quote and target date first.
- Review the changes before they go live.