Back
Scan complete

one4.dev

1 page · 0.3s · Scanned just now

0/ 100
AI automation score

Mostly AI-generated

72% confidence

How to read this score
0–35 · Mostly human35–65 · Mixed signals65–100 · Mostly AI

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.

What we saw

The page shows strong structural signals of AI page-builder templating (hero-to-FAQ flow, consistent section patterning) and generic feature headings ("Ready-to-Use Regex Pattern Lib," "AI Natural Language to Regex"), paired with flat, repetitive body text dominated by regex patterns rather than explanatory prose. Imagery is comprehensive with proper alt-text but uniform in treatment. However, the core content—regex patterns and interactive tool labels—is necessarily technical and specific to the domain, which moderates the AI-generation confidence; the repetition of patterns in the body is functional (showing examples) rather than purely marketing fluff. The tone is uniformly promotional, and the page structure follows a predictable template, but technical specificity and full image coverage prevent a higher score.

80/100Managed
AI Governance· technical

2 governance risks detected

2 medium
What we scanned
Page title
RegexRef — Ultimate Regular Expression Cheat Sheet
Meta description
Interactive regex cheat sheet and builder. 50+ patterns, live tester, visual explainer, and multi-language support. Master regular expressions today.
Canonical URL
https://one4.dev/
Robots directive
Not set — search engines default to index, follow
Language
en
Built with
Next.js
Search & social preview

How the page presents itself in a Google result and as a shared link, rebuilt from the tags we crawled.

Google result
o
one4.devone4.dev

RegexRef — Ultimate Regular Expression Cheat Sheet

Interactive regex cheat sheet and builder. 50+ patterns, live tester, visual explainer, and multi-language support. Master regular expressions today.

  • Title · 50 characters
  • Description · 149 characters
Fine-tune this snippet in the SERP simulator
Shared link card
one4.dev

RegexRef — Ultimate Interactive Regex Cheat Sheet

Master regular expressions with our interactive playground, token reference, and code examples for JS, Python, Go, and Rust.

  • Open Graph image present
AI Governancetechnical · 57%
80/100
Managed2 risks detected
mediumAI score ≥ 70 (predominantly AI-generated content)

AI-generated content may not be copyrightable

The US Copyright Office has held that AI-generated content without sufficient human authorship cannot be registered and receives no copyright protection. This means competitors can freely copy AI-generated pages and you lose exclusivity over your content.

US Copyright Office — Copyright and Artificial Intelligence (2023)EU Copyright Directive
Fix
AI authorship documentation guide
## Protecting AI-Assisted Content

To maximise copyright protection for AI-assisted content:

1. **Document human contributions** — Keep records of the prompts used,
   the editorial decisions made, and the human modifications applied.

2. **Edit substantially** — Meaningful human selection, arrangement, and
   creative editing of AI output can establish copyrightable authorship.

3. **Register what you can** — Register works with significant human
   authorship via the US Copyright Office, disclosing AI use as required.

4. **Update your Terms of Service** to address AI-generated content:
   > "Content on this site may be created with AI assistance. We retain
   > rights to the selection, arrangement, and editorial expression of
   > all published content."

See the Copyright Office's [AI guidance](https://www.copyright.gov/ai/)
for current registration requirements.
Pro1 more risk hidden

Unlock the full breakdown

Pro shows each risk’s plain-English explanation, regulatory framework, official guidance links, and copy-paste fix snippets — plus the AI-generated governance document for your site.

1 medium
See Pro pricing
Top findings
  • Strong signalStructure

    Classic AI builder template order: hero, interactive tool, feature grid, library, pattern builders, FAQ

    Evidence
    • Live Interactive Regex PlaygroundH2
    • Essential Regex Building BlocksH2
    • Frequently Asked Regex QuestionsH2
    Try this

    Reorder sections to break the template flow—move FAQ earlier, combine pattern library and playground, or add a custom workflow section specific to your users' actual workflows.

  • Clear signalContent

    Feature headings lack descriptive depth; minimalist label-style copy throughout

    Evidence
    • Ready-to-Use Regex Pattern LibH2
    • Your Personal LibraryH2
    • AI Natural Language to RegexH2
    Try this

    Expand headings to full sentences with concrete benefit (e.g., 'Convert Plain English to Regex in Seconds' instead of 'AI Natural Language to Regex'); add 2-3 sentences of explanatory prose under each feature.

  • Clear signalTone

    Uniform marketing tone without distinct voice or narrative perspective

    Evidence
    • Master regular expressions todaymeta
    • Interactive regex cheat sheet and buildermeta
    Try this

    Inject a personal or team voice—name the creator, share a specific problem that motivated the tool, or add a brief first-person section explaining why regex matters to you.

What's working

Signals of human authorship the page is doing well.

  • Imagery

    Complete alt-text coverage on all 18 images demonstrates attention to accessibility and user review

SEO auditExcellent
100/100
AI breakdown by category
  • Content68

    Feature headings are generic ("Ready-to-Use," "Your Personal Library") with minimal descriptive prose; body text heavily regex-pattern repetition rather than explanatory writing

  • Structure78

    Boilerplate template order: Hero → interactive playground → features → library → pattern-building tools → FAQ, consistent with AI page-builder output

  • Imagery75

    18 images with full alt-text coverage; likely screenshots and UI elements rather than custom photography, uniform treatment across gallery sections

  • Tone68

    Consistent marketing register throughout ("master," "unlock," "essential"); no identifiable author voice, no humor or internal contradiction

By the numbers
  • Words3,805
  • Images18
  • Alt coverage100%
  • Internal links40
  • External links0
  • Schema blocks2
  • HTML size242 KB
  • Text-to-HTML9%
LLM-marker phrases0.3 per 1,000 words · Low density

Common AI writing tells we counted in the body text. A few hits is normal. A dense cluster is the signal.

Show counted phrases1 match across 1 phrase
  • comprehensive×1
SEO audit detail
  • Meta tags
    All present
    Why 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 structure
    1 H1, 7 H2
    Why 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 readiness
    Responsive
    Why 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 signals
    0.3s · 242 KB
    Why 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 markup
    2 schema blocks
    Why 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 links
    0/5 broken in sample
    Why 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 text
    All have alt
    Why 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.

Heading outline

Every H1, H2, and H3 we found on the page, in document order.

Show heading outline
  1. H1One4 devRegexRef
  2. H2Live Interactive Regex Playground
  3. H2Essential Regex Building Blocks
  4. H2Ready-to-Use Regex Pattern Lib
  5. H2AI Natural Language to Regex
  6. H2Text Selection to Regex
  7. H2Your Personal Library
  8. H2Frequently Asked Regex Questions
  9. H3Anchors
  10. H3Quantifiers
  11. H3Character Classes
  12. H3Special Characters
  13. H3Capturing & Lookaround
  14. H3Capturing Groups
  15. H3Lookahead & Lookbehind
  16. H3Regex Flags
  17. H3Email Address
  18. H3URL Validation
  19. H3Strong Password
  20. H3IPv4 Address
  21. H3Hex Color Code
  22. H3ISO Date (YYYY-MM-DD)
  23. H3Extract HTML Tags
  24. H3Trim Whitespace
  25. H3Pro Feature Locked
  26. H3Pro Feature Locked
  27. H3Save a Pattern
  28. H3Saved Patterns
  29. H3Pro Feature Locked
  30. H3Language Reference
  31. H3JavaScript.js
  32. H3Python.py
  33. H3Go.go
  34. H3Rust.rs
  35. H3Unlock RegexRef Pro
  36. H3From the Blog
  37. H3Regex for AI Prompt Engineering
  38. H320+ Common Regex Examples Every Developer Needs
  39. H3Complete Guide to Regex Form Validation in JS
  40. H3What is a regular expression (regex)?
  41. H3How do I validate an email address with regex?
  42. H3What is the difference between a positive lookahead and a negative lookahead?
  43. H3How do I test regular expressions online?
  44. H3Pro Monthly
  45. H3Pro Lifetime
Sampled links

We HEAD-check up to five internal links to spot broken paths quickly.

Show sampled links

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.