cite-met, running on cite-met.com

    A walkthrough of the scan, the dashboard and the fixes, using our own site. The scan results are real. The dashboard screenshots are example data.

    See the platform

    Real scan results, example dashboard data

    This page walks through cite-met using cite-met.com. Two kinds of material appear on it, and each is labelled. The scan results come from the live scanner, and you can reproduce them. The dashboard screenshots show an example project, so every number in them is example data. We are not publishing cite-met.com's own traffic, referral or citation numbers here.

    Host

    cite-met.com is a TanStack Start app running as a Cloudflare Worker. It renders every page on the server, so the first response already holds the words a crawler reads.

    Measure

    cite-met.com is a monitored project on the platform dashboard. A small cookieless script reports page views and skips visitors who send Do Not Track. The site also runs Cite-Met Pulse, which works differently: it can keep a random ID in your browser to recognise a return visit, and it does not act on Do Not Track. Section 1.F of the privacy policy covers it.

    Improve

    The scan grades the live site and, for each failed check, says what to change. Here is what it reported for cite-met.com on 15 October 2026.

    What the live scanner reports for cite-met.com

    This is a live scan result, not example data, and you can run the same scan yourself.

    Scan record for cite-met.com

    Live scan on 15 October 2026, not example data

    Grade A+10 out of 10

    Core , 5 of 5 points

    • Passed: Content in the HTML

      The homepage sends 400 words of readable text in its HTML.

      2 of 2 points

    • Passed: Inner pages have their own content

      All 3 pages tested have 80 or more words of text in their HTML.

      2 of 2 points

    • Passed: HTTPS everywhere

      The site loads over HTTPS and http:// redirects to it.

      1 of 1 points

    AEO , 3 of 3 points

    • Passed: Search and AI search crawlers allowed

      Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot and PerplexityBot may all fetch the homepage.

      2 of 2 points

    • Passed: Indexable and quotable

      The homepage can be indexed and quoted.

      1 of 1 points

    SEO , 2 of 2 points

    • Passed: Titles and descriptions

      Every page checked has its own title, and the homepage has a description.

      1 of 1 points

    • Passed: Canonical URL

      The homepage names its canonical address.

      0.5 of 0.5 points

    • Passed: Sitemap

      A sitemap is listed in robots.txt.

      0.5 of 0.5 points

    Reported for information, not scored: AI training crawlers are allowed, the homepage has 6 JSON-LD blocks, the AI-crawler firewall test got the same answer as a normal request, Open Graph tags are present, and there is an llms.txt.

    What we did on this exact site

    • Rendered every page on the server, so crawlers get complete HTML on the first request.
    • Generated sitemap.xml in code, so it comes from the same data as the posts, feature pages and authors.
    • Published a robots.txt with one open group, so a rule meant for one crawler never shuts out another.
    • Put Organization, WebSite and SoftwareApplication markup on every page, with breadcrumbs and page-level markup where it fits.
    • Answered requests for Markdown: send Accept: text/markdown and a page comes back as Markdown at the same address.
    • Wrote the llms.txt by hand. It is optional and does not change the score.

    What the dashboard shows

    On the dashboard every visit is classed as Human, SEO (search crawlers), AEO (AI crawlers) or Bots. The AEO column counts fetches by AI crawlers. A fetch shows that a crawler asked for a page, not that an answer cited it.

    Traffic analytics splitting visitors into Human, SEO, and AEO

    The Traffic tab of an example project, not cite-met.com (example data)

    What it says when something breaks

    Site Health puts what is wrong, what visitors still see and what to do into one banner. The example below is a failed build.

    Site Health banner reporting a failed deploy and the version the public still sees

    The Site Health banner of an example project, not cite-met.com (example data)

    Check it yourself

    Run the free scan on cite-met.com and compare it with the results above. The scan reads the HTML our server sends, which is the page a crawler gets whether or not it runs JavaScript. Then scan your own site and compare.

    Grade your site against ours

    Free scan, no signup. See your CiteMET Score, then decide what to fix.

    Explore features

    Walkthrough FAQ

    Are these cite-met.com's real results?
    Only the scan section is. It records what the live scanner reported for cite-met.com on 15 October 2026, and you can run the same scan yourself. The dashboard screenshots show an example project, so their numbers are example data. We are not publishing cite-met.com's own traffic, referral or citation numbers on this page.
    How can I check cite-met.com's score myself?
    Run the free scan on cite-met.com, no signup. It grades the HTML your server sends (your words in the page, inner pages, HTTPS, access for Googlebot, Bingbot and the AI search crawlers, indexability, titles, canonical URL, and sitemap) and returns a CiteMET Score. Then scan your own site and compare.
    Do I have to move my site to use cite-met?
    No. The free scan works on any URL. If you want cite-met to host, measure, and improve your site, we connect your GitHub repo and deploy it, but you can check your own site first, for free, without changing anything.