Website report
Visit sitehttps://www.clocknext.com/
Bill AI agents with credits, outcomes, and units in one plan. Change pricing without a deploy and see margin per customer, per agent, and per model.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Cloudflare
Analysed Nov 7, 2026 · 15 categories · 106 passed · 23 warnings · 2 issues · 19 informational
Audit score
D58/100
Mixed
- Agentic
- 77
- SEO
- 62
What we found
2Needs a fix23Could be better106Looks good19Informational- 1.Needs a fix: No dead placeholder links: needs fixing. see checkWorking, descriptive links help people find the right page.
- 2.Could be better: Your page has no preferred URL. see checkA canonical URL tells search engines which version to use.
- 3.Could be better: Semantic HTML structure: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.
- 4.Could be better: Interactive controls have source labels: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
- 5.Could be better: Share image dimensions declared: needs attention. see checkComplete link previews make your pages easier to recognize and share.
Built with 3 technologies· detected stack
Read from the public source and response headers of the sampled pages.
CloudflareCDN / edge
WebflowCMS / platform
Google FontsFont integration
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata11Looks good
100/100Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "Usage-based billing for AI agents | Clocknext"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 45 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "Usage-based billing for AI agents | Clocknext" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "Bill AI agents with credits, outcomes, and units in one plan. Change pricing without a dep…"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description length
Looks good · Metadata · Review suggested
Observed evidence
Description is 148 characters and inside this audit's 70–160 preview range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 10 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing1Could be better14Looks good1Informational
88/100Could be better: Canonical URL setThe homepage has no canonical link.
Could be better · Indexing · Review suggested
Observed evidence
The homepage has no canonical link.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.
Recommended fix
Add <link rel="canonical"> (Next.js: metadata.alternates.canonical). It consolidates ranking signals when the page is reachable under several URLs (with/without query params, trailing slash…).
Not applicable: Canonical is absolute and self-referencingThe page declares no canonical URL, so there is nothing to validate.
Not applicable · Indexing · Measured on your page
Observed evidence
The page declares no canonical URL, so there is nothing to validate.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.
Recommended fix
Add <link rel="canonical" href="…"> pointing at the absolute, preferred URL of the page.
Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
No canonical declaration to conflict.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
No canonical target to validate in this check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 10 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. No path rule matches this URL.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://www.clocknext.com/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 24 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap declared in robots.txt
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt declares the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (www.clocknext.com).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (22 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 10 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content10Looks good1Informational
100/100Not measured: ReadabilityFlesch reading ease ≈ 44.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 44.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 910 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 910 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Text-to-HTML ratio
Looks good · Content · Measured on your page
Observed evidence
Text-to-HTML ratio is 11.4%.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: billing.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 10 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
10 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 10 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured data2Could be better2Looks good1Informational
100/100Could be better: JSON-LD presentNo JSON-LD structured data on the homepage.
Could be better · Structured data · Review suggested
Observed evidence
No JSON-LD structured data on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.
Could be better: Organization or WebSite schemaNo Organization, WebSite or Person schema found.
Could be better · Structured data · Review suggested
Observed evidence
No Organization, WebSite or Person schema found.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add an identity node so search engines and AI assistants can attribute your content to a real entity.
Looks good: JSON-LD parses
Looks good · Structured data · Measured on your page
Observed evidence
All 1 JSON-LD block(s) parse cleanly.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content-specific schema
Looks good · Structured data · Measured on your page
Observed evidence
Content schema found: Article.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Headings7Looks good
100/100Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "AI billing is complex.Let's make it simple again."
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Single H1
Looks good · Headings · Measured on your page
Observed evidence
Exactly one H1 on the homepage.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Heading levels don't skip
Looks good · Headings · Measured on your page
Observed evidence
Heading hierarchy is sequential across 24 headings.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "AI billing is complex.Let's make it simple again.".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
24 headings, averaging 3.5 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
7 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Element IDs are unique per document
Looks good · Headings · Measured on your page
Observed evidence
All inspected element IDs are unique within their documents.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images1Could be better3Looks good
84/100Could be better: Width/height attributes22 of 22 visible images lack width and height attributes: 6aa166ef7de58bfec4c91bd1_clocknext-locku…, 6ac5c9334aa5883319bce269_ca9902dbe9bef37…, 6ac5c933cd7347671d63c987_264dc304dcd6100…, ….
Could be better · Images · Review suggested
Observed evidence
22 of 22 visible images lack width and height attributes: 6aa166ef7de58bfec4c91bd1_clocknext-locku…, 6ac5c9334aa5883319bce269_ca9902dbe9bef37…, 6ac5c933cd7347671d63c987_264dc304dcd6100…, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Set explicit width and height so the browser reserves the space before the image loads. Without them the page shifts as images arrive, which is what Cumulative Layout Shift measures. next/image sets them for you.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 22 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Modern image formats
Looks good · Images · Measured on your page
Observed evidence
20 of 22 raster images have a WebP/AVIF source or come from a format-negotiating image service.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Lazy loading
Looks good · Images · Measured on your page
Observed evidence
22/22 images are lazy-loaded.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links1Needs a fix5Looks good
65/100Needs a fix: No dead placeholder links2 link(s) go nowhere (href="#", empty or javascript:), e.g.
Needs a fix · Links · Review suggestedCritical
Observed evidence
2 link(s) go nowhere (href="#", empty or javascript:), e.g. "Features", "Resources".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. Right now the sampled pages don't provide it.
Recommended fix
Point each one at its real destination, or remove it. If it opens a menu or panel, make it a <button> with aria-expanded instead of a link.
Affected pages (1)
- https://www.clocknext.com/
Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Anchor text is meaningful
Looks good · Links · Measured on your page
Observed evidence
50 of 50 links have descriptive text or labels.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 16 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
6 same-page fragment link(s) have source targets.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile1Could be better4Looks good1Informational
77/100Could be better: Interactive controls have source labels1 of 551 source controls lack a detectable name.
Could be better · Mobile · Measured on your page
Observed evidence
1 of 551 source controls lack a detectable name.
Why this matters
Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.
Recommended fix
Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.
Affected pages (1)
- https://www.clocknext.com/demo
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Responsive image markup
Looks good · Mobile · Measured on your page
Observed evidence
2/22 images ship responsive srcset variants.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: ARIA references point to source elements
Looks good · Mobile · Measured on your page
Observed evidence
20 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding2Looks good2Informational
100/100Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (https://cdn.prod.website-files.com/6a88381a8915da42648893b4/6acb17564eddd072e9ff4ca3_Clocknext%20favicon.png).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Apple touch icon
Looks good · Branding · Measured on your page
Observed evidence
apple-touch-icon is declared.
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Server response time | 257 ms | Looks good: goodThe audit received response headers after 257 ms from one test location. |
| HTML payload size | 100 KB | Looks good: goodThe page's HTML is a lean 100 KB uncompressed. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 22.1 KB | Looks good: goodInline styles total 22.1 KB. |
| Script/stylesheet count | — | Looks good: good11 total script/style resources — reasonable. |
| Web fonts don't block text | — | Looks good: goodGoogle Fonts links set a non-blocking font-display value. |
| HTML served compressed | — | Looks good: goodHTML is compressed with gzip. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 99.7 KB | Informational: measured source, not transferred bytes99.7 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: Frame embedding protectionNo frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Could be better · Security · Review suggested
Observed evidence
No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.
Could be better · Security · Review suggested
Observed evidence
X-Content-Type-Options: nosniff is not set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).
Could be better: Content Security PolicyNo Content-Security-Policy detected.
Could be better · Security · Review suggested
Observed evidence
No Content-Security-Policy detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=31536000.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Server technology disclosure
Looks good · Security · Measured on your page
Observed evidence
No X-Powered-By disclosure.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
2 declared form(s) submit over HTTPS to this site. Runtime submission behavior is untested.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Could be better: Semantic HTML structureSemantic landmarks exist (12) but there's no <main> or role="main".
Could be better · AI answer readiness · Review suggested
Observed evidence
Semantic landmarks exist (12) but there's no <main> or role="main".
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Wrap the primary content in one <main>. Readers, screen readers and content extractors use it to find the substance and skip the navigation and footer.
Could be better: llms.txtNo /llms.txt file.
Could be better · AI answer readiness · Review suggested
Observed evidence
No /llms.txt file.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Optional: publish an llms.txt index of useful pages. This proposal is not a requirement for Google AI features, and its absence does not reduce the core score.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.
Could be better: Question-style headingsOnly 15% of 136 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 15% of 136 H2/H3 headings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "New guide…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "New guide…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /about.md or /index.html.md.
Could be better · AI answer readiness · Measured on your page
Observed evidence
No markdown copy answered at /index.md or /about.md or /index.html.md.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.
Affected pages (2)
- https://www.clocknext.com/
- https://www.clocknext.com/about
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density97 concrete figures across 1205 words.
Not measured · AI answer readiness · Not established
Observed evidence
97 concrete figures across 1205 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not measured: llms.txt links resolve to this siteNo readable llms.txt was available to inspect for Markdown links.
Not measured · AI answer readiness · Not established
Observed evidence
No readable llms.txt was available to inspect for Markdown links.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish a readable llms.txt, then link its important pages with same-origin Markdown URLs.
Not applicable: Entity identity agrees across signalsThe page declares no site or organization name (no og:site_name and no Organization or WebSite schema name), so there is nothing to compare.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The page declares no site or organization name (no og:site_name and no Organization or WebSite schema name), so there is nothing to compare.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Declare the site's name once in Organization or WebSite schema and in og:site_name, and use the same name in the title.
Not measured: llms.txt follows the specNo readable /llms.txt, so its structure cannot be checked.
Not measured · AI answer readiness · Not established
Observed evidence
No readable /llms.txt, so its structure cannot be checked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish llms.txt first — the llms.txt check covers that — then this one verifies the structure.
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html; charset=utf-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html; charset=utf-8.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 20 words — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Freshness signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
dateModified present in schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
95 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Identity schema present.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Question headings have concise answers
Looks good · AI answer readiness · Measured on your page
Observed evidence
18 concise answer block(s) follow 20 question-shaped heading(s).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Machine-readable provenance signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
Found 4 of 4 machine-readable provenance signal types: author, date, contact, breadcrumb.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 29/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: Latest article has real depthThe newest article has 192 words of body text.
Needs a fix · AdSense policy · Measured on your pageCritical
Observed evidence
The newest article has 192 words of body text.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Publish articles that answer the question fully — under a few hundred words a page rarely carries more than a restated headline. Depth is measured here in words of body copy, not in padding.
Affected pages (1)
- https://www.clocknext.com/guides/pricing-economics-of-ai-agents
Could be better: Sampled publisher-content coverage2/7 editorial pages expose fewer than 250 publisher words; those 7 pages hold 5564 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
2/7 editorial pages expose fewer than 250 publisher words; those 7 pages hold 5564 publisher words in total. 3 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (2)
- https://www.clocknext.com/guides/pricing-economics-of-ai-agents
- https://www.clocknext.com/demo
Could be better: Latest article reads as edited workStyle pattern score 30/100 on the newest article: 0 numbers or dates per 100 words.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
Style pattern score 30/100 on the newest article: 0 numbers or dates per 100 words.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Edit the flagged passages: cut the stock phrases, break up the uniform rhythm, and add concrete detail. These are style patterns in the sampled text, not a determination of how the page was written.
Affected pages (1)
- https://www.clocknext.com/guides/pricing-economics-of-ai-agents
Could be better: Contact methodNo contact page or mailto link found.
Could be better · AdSense policy · Review suggested
Observed evidence
No contact page or mailto link found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.
Could be better: Policy pages linked site-wide1/10 crawled pages don't link to the privacy policy.
Could be better · AdSense policy · Review suggested
Observed evidence
1/10 crawled pages don't link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.
Affected pages (1)
- https://www.clocknext.com/demo
Could be better: Latest article names an author and a dateThe newest article shows an author but no date.
Could be better · AdSense policy · Measured on your page
Observed evidence
The newest article shows an author but no date.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add the missing one in the visible page and in Article JSON-LD, so the byline and the markup agree.
Affected pages (1)
- https://www.clocknext.com/guides/pricing-economics-of-ai-agents
Not measured: First-party contact emailNo public contact email was found in the sampled home, About, or Contact pages.
Not measured · AdSense policy · Review suggested
Observed evidence
No public contact email was found in the sampled home, About, or Contact pages.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
A public email is optional. The separate contact-method check covers whether readers have a way to reach the publisher.
Not measured: ads.txtNo ads.txt yet.
Not measured · AdSense policy · Not established
Observed evidence
No ads.txt yet.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Looks good: Privacy policy page
Looks good · AdSense policy · Measured on your page
Observed evidence
Privacy policy found: https://www.clocknext.com/privacy
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Privacy policy advertising disclosures
Looks good · AdSense policy · Published platform rule
Observed evidence
Fetched privacy policy contains cookie/storage, advertising, and third-party/vendor disclosure signals.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Terms page
Looks good · AdSense policy · Measured on your page
Observed evidence
Terms page found: https://www.clocknext.com/terms
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: About page
Looks good · AdSense policy · Measured on your page
Observed evidence
About page found: https://www.clocknext.com/about
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
7/7 editorial pages clear the audit's publisher-content triage threshold. 3 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Tool pages expose explanatory content
Looks good · AdSense policy · Review suggested
Observed evidence
All 10 sampled tool-style screens include crawlable explanation.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 9 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Article-style content exists
Looks good · AdSense policy · Measured on your page
Observed evidence
Article-style content detected.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | www.clocknext.com |
|---|---|
| CDN / edge | Cloudflare |
| IP addresses | 198.202.211.1, 2620:cb:2000::1 |
| DNS A | 198.202.211.1 |
| DNS AAAA | 2620:cb:2000::1 |
| DNS CNAME | cdn.webflow.com |
| DNS NS | journey.ns.cloudflare.com · lamar.ns.cloudflare.com |
| TLS | TLSv1.3TLS_AES_256_GCM_SHA384 |
| Certificate issuer | Google Trust Services / WE1 |
| Certificate valid until | Jan 11 05:17:56 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
910 publisher words
Page structure
html content
Observed discovery
Depth 0 · 9 incoming links
HTTP 200 · 99.7 KB source
Source interactions
58 controls · 0 unnamed
9 script / 2 stylesheet references
- Canonical declaration
- Not declared
- Schema types
- None observed
- Outgoing links in sampled graph
- /guides/pricing-economics-of-ai-agents · /features/credits-and-wallets · /features/usage-metering · /features/outcomes · /features/pricing-experiments · /features/composites · /features/margin-control · /features/billing-and-invoicing · /features/revenue-insights · /blog · /guides · /about · /pricing · /demo · /terms · /privacy
Routes: / · /about · /privacy · /guides · /features · /blog · /pricing · /demo · /terms · /learn
Resource origins 5
Resources associated with your website. External resources may belong to the same organization.
- https://cdn.prod.website-files.com/stylesheet, image, script · 107 references · cross origin
- https://fonts.googleapis.com/stylesheet · 11 references · cross origin
- https://d3e54v103j8qbb.cloudfront.net/script · 10 references · cross origin
- https://js-na2.hs-scripts.com/script · 10 references · cross origin
- https://s3.amazonaws.com/image · 2 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | Declared policy for this page. |
| Googlebotsearch | /about | allowed | Declared policy for this page. |
| Googlebotsearch | /privacy | allowed | Declared policy for this page. |
| Googlebotsearch | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| Googlebotsearch | /features/credits-and-wallets | allowed | Declared policy for this page. |
| Googlebotsearch | /blog | allowed | Declared policy for this page. |
| Googlebotsearch | /pricing | allowed | Declared policy for this page. |
| Googlebotsearch | /demo | allowed | Declared policy for this page. |
| Googlebotsearch | /terms | allowed | Declared policy for this page. |
| Googlebotsearch | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| bingbotsearch | / | allowed | Declared policy for this page. |
| bingbotsearch | /about | allowed | Declared policy for this page. |
| bingbotsearch | /privacy | allowed | Declared policy for this page. |
| bingbotsearch | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| bingbotsearch | /features/credits-and-wallets | allowed | Declared policy for this page. |
| bingbotsearch | /blog | allowed | Declared policy for this page. |
| bingbotsearch | /pricing | allowed | Declared policy for this page. |
| bingbotsearch | /demo | allowed | Declared policy for this page. |
| bingbotsearch | /terms | allowed | Declared policy for this page. |
| bingbotsearch | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | / | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /about | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /features/credits-and-wallets | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /blog | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /pricing | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /demo | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /terms | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| PerplexityBotsearch | / | allowed | Declared policy for this page. |
| PerplexityBotsearch | /about | allowed | Declared policy for this page. |
| PerplexityBotsearch | /privacy | allowed | Declared policy for this page. |
| PerplexityBotsearch | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| PerplexityBotsearch | /features/credits-and-wallets | allowed | Declared policy for this page. |
| PerplexityBotsearch | /blog | allowed | Declared policy for this page. |
| PerplexityBotsearch | /pricing | allowed | Declared policy for this page. |
| PerplexityBotsearch | /demo | allowed | Declared policy for this page. |
| PerplexityBotsearch | /terms | allowed | Declared policy for this page. |
| PerplexityBotsearch | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | / | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /about | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /features/credits-and-wallets | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /blog | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /pricing | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /demo | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /terms | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| GPTBottraining | / | allowed | Declared policy for this page. |
| GPTBottraining | /about | allowed | Declared policy for this page. |
| GPTBottraining | /privacy | allowed | Declared policy for this page. |
| GPTBottraining | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| GPTBottraining | /features/credits-and-wallets | allowed | Declared policy for this page. |
| GPTBottraining | /blog | allowed | Declared policy for this page. |
| GPTBottraining | /pricing | allowed | Declared policy for this page. |
| GPTBottraining | /demo | allowed | Declared policy for this page. |
| GPTBottraining | /terms | allowed | Declared policy for this page. |
| GPTBottraining | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| ClaudeBottraining | / | allowed | Declared policy for this page. |
| ClaudeBottraining | /about | allowed | Declared policy for this page. |
| ClaudeBottraining | /privacy | allowed | Declared policy for this page. |
| ClaudeBottraining | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| ClaudeBottraining | /features/credits-and-wallets | allowed | Declared policy for this page. |
| ClaudeBottraining | /blog | allowed | Declared policy for this page. |
| ClaudeBottraining | /pricing | allowed | Declared policy for this page. |
| ClaudeBottraining | /demo | allowed | Declared policy for this page. |
| ClaudeBottraining | /terms | allowed | Declared policy for this page. |
| ClaudeBottraining | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | / | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /about | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /privacy | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /features/credits-and-wallets | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /blog | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /pricing | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /demo | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /terms | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /about | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /guides/pricing-economics-of-ai-agents | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /features/credits-and-wallets | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /blog | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /pricing | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /demo | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /terms | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /learn/what-is-outcome-based-pricing | allowed | Declared policy for this page. |
Advertised APIs and machine interfaces
No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.
Public DNS and TLS endpoint
www.clocknext.com · observed · 198.202.211.1, 2620:cb:2000::1
- A
- 198.202.211.1
- AAAA
- 2620:cb:2000::1
- CNAME
- cdn.webflow.com
- NS
- journey.ns.cloudflare.com · lamar.ns.cloudflare.com
- MX
- Unavailable for this exact hostname
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Google Trust Services / WE1
Certificate valid until: Jan 11 05:17:56 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Your top fixes list is the priority order — clear the red items before creating more content.
- 02
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
- 03
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://www.clocknext.com/
- https://www.clocknext.com/about
- https://www.clocknext.com/privacy
- https://www.clocknext.com/guides/pricing-economics-of-ai-agents
- https://www.clocknext.com/features/credits-and-wallets
- https://www.clocknext.com/blog
- https://www.clocknext.com/pricing
- https://www.clocknext.com/demo
- https://www.clocknext.com/terms
- https://www.clocknext.com/learn/what-is-outcome-based-pricing