superlative-caramel-87d5cb.netlify.app
1 page · 0.2s · Scanned just now
Mostly human-written
72% confidence
The score is a fingerprint of automation, not a quality judgment. A high score means the page reads as machine-generated. It doesn't mean the page is bad.
This is a functional web application (a trading journal tool), not a marketing or content page. The 105-word body is almost entirely labels, button text, and field descriptions, not prose suitable for AI-generation detection. The structure is custom application UI rather than a template. The tone is minimalist and task-focused. Signals of human authorship include the domain author credit ("built by @buyittradeit"), an idiomatic phrase, and a custom tool design that shows intentional human tool-building rather than AI page generation.
No governance risks detected
- Page title
- The Pit Board
- Meta description
- —
- Canonical URL
- —
- Robots directive
- Not set — search engines default to index, follow
- Language
- en
How the page presents itself in a Google result and as a shared link, rebuilt from the tags we crawled.
The Pit Board
- Title · 13 characters
- No meta description — Google will pull an arbitrary snippet instead
The Pit Board
- No og:image — shared links render as bare text with no picture
- No Open Graph title — the share card falls back to the page title
- Clear signalContent
Minimal prose makes content authenticity hard to assess; 105 words are mostly functional UI labels, not narrative text
Evidence- “Per-trade risk, sized to the drawdown”H3
- “Log the session net, watch the target or buffer close in, and keep the best day under the consistency cap.”body
Try thisIf this is a public landing page, add a brief explanation of what this tool does and who should use it; functional UI labels alone don't convey value to a visitor unfamiliar with the tool.
- Worth notingTone
Terseness and procedural focus dominate, though one idiomatic phrase ('beats one forced one') shows human voice
Evidence- “Three clean days beats one forced one.”body
Try thisAdd a short tagline or mission statement to give the tool personality; one phrase is not enough to establish consistent voice across the page.
Signals of human authorship the page is doing well.
- Structure
Custom application UI design with data visualization and form controls shows intentional human tool-building, not AI page builder output
- Tone
Idiomatic phrase 'beats one forced one' and domain author credit '@buyittradeit' signal human creator identity and domain expertise
- Content32
Minimal prose; technical labels ("Per-trade risk, sized to the drawdown") dominate; no narrative flow or personal voice
- Structure18
Custom application layout with form fields, input controls, and data-driven sections; no boilerplate template structure
- Imagery0
No images present; content is functional UI with text labels and input fields only
- Tone35
Terse, technical, rule-focused voice with one idiomatic phrase ("beats one forced one") but otherwise flat and procedural
- Words105
- Images0
- Alt coverage100%
- Internal links0
- External links0
- Schema blocks0
- HTML size13 KB
- Text-to-HTML5%
No common LLM-marker phrases found — none of the stock AI vocabulary we scan for appears in the body text even once.
- Meta tagsMissing 2 tagsWhy this matters
Why it matters. Title and description are the two strings Google shows in search results. They decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.
Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.
Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.
- Heading structureNo H2 structureWhy this matters
Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page. H2s break it into sections. Skipped levels and missing H1s confuse both.
Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 to H3 jumps).
Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2. Demote sub-points to H3.
- Mobile readinessResponsiveWhy this matters
Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.
Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.
Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.
- Page speed signals0.2s · 13 KBWhy this matters
Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.
Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.
Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.
- Schema markupNo JSON-LDWhy this matters
Why it matters. JSON-LD structured data is how you earn rich results: review stars, FAQ accordions, breadcrumbs, article cards. Skip it and Google has nothing structured to pull from when it builds your SERP card.
Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).
Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.
- Broken linksNo internal linksWhy this matters
Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.
Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.
Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.
- Image alt textNo imagesWhy this matters
Why it matters. Alt text is what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.
Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.
Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.
Every H1, H2, and H3 we found on the page, in document order.
Show heading outline
- H1The Pit Board
- H3Per-trade risk, sized to the drawdown
- H3Daily log
Was this report useful?
Share this scan
Every CrawlRanker scan gets a public, shareable URL. Send it to a client, post it in a thread, or benchmark a competitor.
Preview scan. SEO checks are live. AI scoring is in beta.